-
Notifications
You must be signed in to change notification settings - Fork 12
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
Implement FFT partitioning to reduce latency #42
Comments
Right, so yeah that's an option if you want better resolution in the lower frequencies at the expense of more latency. Evidently you already know how to change it. I think here would be a good use of exposing these parameters through a config file |
How about an extra parameter in the specbleach_adaptive_initialize call? |
Yeah I kinda make sense just for this one. In the future I plan to use a multiresolution fft which would get rid of this issue. Will depend on how efficient my implementation is though |
Sounds interesting... |
Do you mind if I change the issue name so it's clear it's a request? To something like Expose frame size configuring possibly through the api |
Sure, rename it as you wish |
In my software's filtering I use FFT Partitioning - I'm sure we could use this to reduce latency, for example I can reduce the latency of 128ms down to 4ms. |
Ahh yeah someone el se has mentioned this once. I'll investigate further, this will be for sure useful! |
Uses more CPU but at these sample rates will not be an issue. |
Hi,
I see the frame size is 20ms. If latency and CPU load are not a problem, is there an advantage in using a much bigger frame size, for example 160ms?
The text was updated successfully, but these errors were encountered: