crepe icon indicating copy to clipboard operation
crepe copied to clipboard

Larger values for step_size

Open ruizcrp opened this issue 4 years ago • 1 comments

Hi, I noticed in this package as well as in some similar ones, that the step_size is very small - for example 10ms. What would happen if the step_size is set to for example 1000ms or even 2500ms? Would this give similar results to when within 1000ms a bag of all the 10ms is taken? The reason is that I am interested by an average pitch every second or every few seconds and don't need to know for every 10ms the pitch. This would also reduce the calculation time as far as I see. But is there something logically flawed in taking larger values for the step_size? Thank you and kind regards!

ruizcrp avatar Apr 06 '20 10:04 ruizcrp

The choice of step size depends entirely on your application/needs, and is just a way of controlling the temporal resolution of the output. Since many audio analysis tasks (e.g. speech and music analysis) typically require such small step sizes (because the pitch of human speech and singing evolves very rapidly), default is small. If, however, your application only requires a pitch estimate once a second, you can definitely set the step size to 1000 ms, there's no logical flaw in using a large step size assuming it makes sense for your downstream application.

justinsalamon avatar Apr 06 '20 17:04 justinsalamon