-
Notifications
You must be signed in to change notification settings - Fork 404
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
Uni Spread "Absolute" mode doesn't work in Window and SH-Noise oscillators #1284
Comments
Oh yeah. That’s a bug that her been there since I implemented absolute in the summer. When I added absolute mode I bet I didn’t add it to window and S&H just the other oscillators. thanks! |
I'm going to push this out of 1.6.4 for now since I want 1.6.4 to be a bit smaller. |
Turns out it is just the window oscillator; S&H is doing the right thing if you set it in correlation=1 mode (where the frequency not the noise shows the pitch). |
The Window and S&H oscillators didn't support Absolute mode for Unison. So 1. Make a direct load of an FXP availble so we can unit test them 2. Set up unit tests to compare all the uni-featuring oscillators between absolute and relative 3. Modify the Window oscillator to obey Absolute, thus making the test pass Closes surge-synthesizer#1284
The Window and S&H oscillators didn't support Absolute mode for Unison. So 1. Make a direct load of an FXP availble so we can unit test them 2. Set up unit tests to compare all the uni-featuring oscillators between absolute and relative 3. Modify the Window oscillator to obey Absolute, thus making the test pass Closes #1284
Ah yes that's right, Absolute in S&H works fine, just tested as well. Awesome! |
While playing notes on different octaves in these two OSC modes, they are still being de-tuned proportionally to the notes I play, where as in other OSC modes, in Absolute spreading, the higher the note, the less detuned the voices are from each other (as it should be).
VST3 x64, FL Studio 20.5.1 x64, Windows 10 x64.
I think that this is a pretty old bug, as it was present in a version from last June (and possibly before that as well).
The text was updated successfully, but these errors were encountered: