fix(gui): invalid chunk/pad range, fix slider minimum

[brandostrong]

librosa.util.exceptions.ParameterError: Invalid hop_length: 0 on 0 chunk seconds
Calculated padded input size per channel: (1). Kernel size: (2). Kernel size can't be greater than actual input size on 0 pad seconds

[34j]

I would appreciate it if you could fix other sliders as well

[brandostrong]

Hi, can you clarify?

[34j]

It would be nice if the slider for the maximum chunk seconds and the four sliders for "Realtime" also had a proper minimum value.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 19.56%. Comparing base (b116a05) to head (774b0f6).
⚠️ Report is 492 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #616      +/-   ##
==========================================
+ Coverage   19.55%   19.56%   +0.01%     
==========================================
  Files          39       39              
  Lines        3427     3424       -3     
  Branches      477      476       -1     
==========================================
  Hits          670      670              
+ Misses       2740     2737       -3     
  Partials       17       17              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[brandostrong]

fix #649 and fix #616

[34j]

@brandostrong #649 is not a bug. (#95) If you think it is really unfriendly, please create the feature to make the default at startup the same as the last time, or show additional prompts, etc. please create a separate PR for that. Also, I personally think a lower limit of 0.01 seconds for each slider would be preferable.

[brandostrong]

hi, I now see why it is like this. It makes sense for the presets to change back to "default file" instead of any other preset, but should it update the selections with the default? Would a good comprimise be removing apply_preset("Default File") and keeping window["presets"].update(set_to_index=list(load_presets().keys()).index("Default File")) ?

Otherwise, I can look at adding a toggle to "remember" settings.

[34j]

I don't even know what is the best solution, though I'd rather have a preset made than click on a toggle.