Double precision interface for the caller to calculate frames consumed while using the callback API #226
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d while using the callback API
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello! I am a contributor to Mixxx (https://github.com/mixxxdj/mixxx), working as part of my GSOC 2025 project.
I have integrated the libsamplerate API into our software (See mixxxdj/mixxx#15005)
and have observed significant latency gains over our previous resampler. (See mixxxdj/mixxx#15005 (comment))
However, for correctness we believe double-precision tracking is necessary (not just for mixxx, but for other real-time applications as well). We would like to upstream the libsamplerate changes, but cannot do so without a double precision interface upstreamed to libsamplerate. Hence the PR.
Thank you!