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
unexpected keylock release behaviour #8745
Comments
Commented by: daschuer The related code is here: |
Commented by: ronso0 Thank you! Since I only feel my use case (controller with jogwheels), I need some other opinion on that: |
Commented by: daschuer The key lock mode was introduced here: One argument for the current behavior was that it should be possible to return to the original key without any pain. This is quired to go back to clean sound and save a lot CPU. An other issue was that the key knob should not turn when enabling and disabling key lock. Maybe we need an additional control for your mode. Do you have experiences with other tools or player? |
Commented by: ronso0 Okay, I will have a look at the code and the conversation and see if I can do something at all.
|
Commented by: daschuer Greate. IMHO your use-case is valid and would be a nice addition as a
|
Commented by: ronso0 From what I understand so far, it would be enough to add a condition like So, that condition, a new CO called i.e. "unlockKeyToOriginal" and associated controls in Preferences dialogue would have to be added, right? If there's not much more to it I could to that. |
Commented by: daschuer Yes, but I am not entirely sure. |
Issue closed with status Fix Released. |
Reported by: ronso0
Date: 2017-01-03T08:49:08Z
Status: Fix Released
Importance: Wishlist
Launchpad Issue: lp1653631
I explain what I'd expect:
That's a scenario currently not covered by "Lock current key" or "Lock original key" setting:
Right now, when releasing keylock while rate is above or below original, key jumps to that newly calculated key and thus sounds odd.
Could someone point me to where this lock/unlock is done in source?
I can't say if this SHOULD be covered by current settings or if a third option could handle this.
The text was updated successfully, but these errors were encountered: