asearfos / chipper Goto Github PK

This problem come from how we are defining a syllable. Since a syllable is any signal between an onset and offset (with no frequency bounds) then any noise above or below what the eye would call the syllable is being counted when max and min are being measured.

Only idea to improve this as of right now is to use the note threshold and remove anything below it before conducting syllable calculations (including similarity check?).

pad really short songs to be more "regular" looking in the window rather than very stretched

Choose consistent color for noise among all songs in syllable similarity widget (dark gray maybe).
If easy, could color within syllable noise white like in the note threshold widget and color between syllable signal as dark gray.

make parameter output in .txt file in Hz and ms for user readability

Analysis could error out without providing any feedback to user. Need to put a try : catch block and let user know using the spinner.

in syllable segmentation, fix crash when submit is hit but there are no syllables (no lines)

Change the language so it is clear this is more about figuring out what is considered noise within syllables so that it is not considered in calculations.

only if this is an easy change

If a single file is selected instead of a folder the program crashes.

temporary save upon crash or exit

We added a catch for this in the actual analysis but Chipper also crashes if this happens in the syllable similarity threshold widget if the note size threshold is set too large (no notes in syllable).

if reset parameters, they currently go to the ones the user input; if parameters were found from a previously chippered gzip, they should go back to those instead (not sure how to do this without adding params as a self variable)

add output of frequencies and durations, not just average measurements

Rough frequency measures (rounded) were added at 0Hz and at half the full frequency of the spectrogram.

constrain where to look for gzips if using previous parameters, or give user option of which gzips

Instead of one output analysis file, have two with one being all note measurements. This can be labeled so as to warn the user to be careful/critical of these measurements (especially for noisy files), be sure they use the widgets, and check the outputs for reasonable values.

right now only computes as if the WAV files are 44100 Hz even if they are not

flag for too large of file; split really long songs, subsequently stitch back together before writing (@asearfos can integrate kivy popup to warn users not to change the sliders between songs)

• low-pass-filter @asearfos
• create note threshold page @asearfos
• welcome page (icon, link to GitHub/best practices) @asearfos
• connect analysis to home page @asearfos
• back button to previously altered parameters
• create syllable threshold page @asearfos
• make esc minimize not quit or have popup asking
• return to landing page or button with threshold choosing/analysis @asearfos
• fix radio buttons so that at least one has to be selected at all times
• button to play song @asearfos
• start on users home library @JamesPino
• make analysis faster
• fix crash when submit is hit but there are no syllables (no lines)
• fix crash on double enter @JamesPino
• temporary save upon crash or exit @JamesPino
• click a single file @JamesPino
• add one to syntax/syll_pattern so that there is not a "0" syllable
• make parameter output in .txt file in Hz and ms for user readability @asearfos
• fix crash when no input is given in threshold widgets
• garbage collect @JamesPino
• accept WAV files of different sampling rates @asearfos
• constrain where to look for gzips if using previous parameters, or give user option of which gzips @JamesPino
• flag for too large of file @JamesPino
• pad really short songs @JamesPino
• split really long songs, subsequently stitch back together before writing @JamesPino (@asearfos can integrate kivy popup to warn users not to change the sliders between songs)
• if reset parameters, they currently go to the ones the user input; if parameters were found from a previously chippered gzip, they should go back to those instead (not sure how to do this without adding params as a self variable)
• add test song file(s)

general garbage collection as well as checking variable handling when done and returning to landing page from each widget (each radio button)

This happens in syllable segmentation when you have already added or deleted a syllable onset or offset and hit enter. If you hit enter again, it crashes.

Make a test to make sure that the values are the same (similarity between two defined syllables).

Make a test to make sure frequencies dont overlap.