-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement Request: Allow for Longer Buffer Length. #73
Comments
The 1000 ms limit was just to make the slider usable over the range one might use for a VU meter and give users some indication of what a "sane" buffer value is. I suppose I could switch it to a numeric input and just assume that anyone putting in 600000 understands the consequences. |
I see, switching to a numerical input would definitely work, actually that's how I found that the limit was 1000, I tried to key in numbers in the box to the right of slider and found that the value could not go higher. |
You can use the gaussian filter to smooth the graph, it's not perfect but it should do the trick. As for sample rate, the data is already resampled according to the size of the graph. If your buffer is 1000 ms and your graph is 100 px, then the sampling interval is effectively 10 ms. |
Just pushed this to master along with general improvements to waveform rendering. Still needs some adjustment but it'll work for now. |
Firstly thanks for your awesome job, the plugin really helps in my usage where I want to add a visual clue in my recordings to when I got excited and made some noise. Unfortunately, currently I can't set the buffer time to a value above 1000ms when using the levels meter, which really limits it's usage.
I don't know C++ very well, so I failed to find out if supporting a longer time span is just a change of magic number or it will require other changes. Could you please change it to support time span like 1 to 10 minutes?
I guess 1000ms is not an intentional limit, but you might have other concerns. I would try to help if that's the case.
Looking forward to your reply~
The text was updated successfully, but these errors were encountered: