Skip to content
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

Minor output differences introduced by addclip20/multi optimization #11

Open
jcmoyer opened this issue Oct 20, 2024 · 1 comment
Open

Comments

@jcmoyer
Copy link
Owner

jcmoyer commented Oct 20, 2024

Since 7204125, behavior differs around extreme inputs. Comparing renderer output, some samples are off-by-one in a random direction.

Using the test midi here: nukeykt#101
Renderer output for upstream (left) and local (right)
image

Under normal circumstances, this doesn't happen - all the current integration tests produce bitwise identical results to upstream. When it does happen, inverting one of the two rendered waveforms produces near total silence, so there's not an audible difference between the two implementations. I have also been running a local validation branch that performs range checks on the output of these functions for the past 4 months, and it hasn't trapped yet except on this test midi. I trust the optimization to be sound since the midi also produces crackling with upstream.

It's not clear what the intended behavior is so I'll wait for someone with actual hardware or more insight into the problem before deciding whether or not this optimization needs to be reverted.

@jcmoyer
Copy link
Owner Author

jcmoyer commented Oct 23, 2024

The patch I posted in the linked issue fixes this problem and produces identical sample output; waiting for feedback from someone who knows the hardware better in case it's the incorrect approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant