-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Don't immediately jump when loopOut is pressed in quantized mode #2260
Conversation
…ized mode Fixes LP1837077
Thank you for taking care. I think this fix is also relevant for 2.2. |
Your comments can be improved by removing the c++ explaining parts and add some more background info. I will give an example inline. |
@@ -354,19 +354,29 @@ double LoopingControl::nextTrigger(bool reverse, | |||
|
|||
LoopSamples loopSamples = m_loopSamples.getValue(); | |||
|
|||
// adjust loop in was toggled (slotLoopIn or slotLoopOut) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
//m_bAdjustingLoopIn is true while the LoopIn button is pressed, (slotLoopIn)
|
||
// adjust loop in was true and is now false and is only relevant in reverse mode | ||
// in non-quantized mode we jump immediately to the end of the loop while in quantized mode we wait until the loop start is reached | ||
if (reverse && !m_bAdjustingLoopIn && !m_pQuantizeEnabled->toBool()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// If the loop in button was released in reverse mode, we need to jump to loop end to not fall out of the just set loop. This must not happen in qantized mode. Here we need to jump to a qantized position, which is handeled in ....
I think this fix should work on 2.2 as well (commit can be cherry-picked). But I can not build 2.2 currently.
Seems like a missing include directory because the files exist under lin64_build/src but I have no knowledge of scons to fix this. |
Sometimes scons tricks itself when switching branches. You can try to call scons --clean or just delete the lin64_build folder an the .sconsign.dblite or a fresh checkout. In this case I think you there is no nee to bother with the scons issues. |
OK, cleaning didn't help. Did not try a new checkout. I will create a new PR soon. |
Don't immediately jump to loop start when loopOut is pressed in quantized mode.
Same holds true for loopIn in reverse mode
Fixes https://bugs.launchpad.net/bugs/1837077