-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Support for upsample filter #137
Comments
I haven't thought of this but makes sense to include. And why not add decimation at the same time. |
Thanks Henrik! |
All filters in a camilladsp pipeline must work at the same sample rate, it's not possible to use different rates in different parts of the pipeline. That's why the resampling is handled in the capture thread, before passing the audio data to the pipeline. I have started looking at how to add this to rubato. It seems pretty straightforward, shouldn't take very long once I get started. |
That's fine. I understand the constraints are there for a reason and making them more flexible would be more effort on your part - and likely not many would be interested in this feature. |
Presently I am using sox upsample filter (insert 0 value samples) to expand the bandwidth and follow it up with camilladsp FIR for interpolation with my custom coefficients. It would be great if upsampling can be done (with 64 bit float) in camilladsp itself. That way I can eliminate sox out of my pipeline altogether and just chain filters within camilladsp config file itself.
presently it is something like this:
sox -c 2 -r 44100 -b 64 -e floating-point -t raw - -r 705600 -t raw - upsample 16 | camilladsp -l off <path_to_config.yml>
Love your work btw! CamillaDSP has replaced by brutefir pipeline ever since :)
The text was updated successfully, but these errors were encountered: