-
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
Snap to semitones on pitch modulation amount slider #1501
Comments
So the only problem with this is right now Cltrl-Click when modulating clears the modulation and doesn't allow subsequent editing (try it!) It's pretty easy to do this, either by extending the editing or changing the binding. Will noodle. |
So the east thing to do is start dragging and press control - integerized but I think the second is probably a "bad idea" since if you accidentally drag it will undo the clear of modulation from control click
Welcome thoughts here. |
Can you make it so that reset to zero happens on mouse up rather than mouse down? Then we can start dragging and holding control, or holding control and start dragging, both would integerize, but if we keep control at mouseup then it resets to zero. Too complicated? |
Oh that’s a good idea. |
Oh sigh; the short answer is: that's a good idea but it's not easy. Have to change the collaboration between SurgeGUIEditor and CSurgeSlider in a way which is a bit further reaching than I would like. So I'm going to push this one out of 1.6.5. Sorry! |
@baconpaul I'd like to try tackling doing value quantizing on modulation amount sliders, since Ctrl+click doesn't do anything anymore (because we removed that when I did the Ctrl+drag quantizations of regular parameters). Baconsignal ahoy! |
Yeah |
I'm gonna close this as a dup of #1024 at this point. |
Currently, when tweaking oscillator Pitch parameter and holding Ctrl/Cmd, it snaps to semitones. However, this doesn't happen when tweaking the pitch modulation amount (regardless of modulator used).
It would be nice if it did happen, though!
The text was updated successfully, but these errors were encountered: