You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CROSS SCREEN being enabled in arranger view now lets users have PLAY start from current location and <>+PLAY start from the beginning of the arrangement; the opposite of the old behavior.
However, this is also a community features option: Alternate Start Playback Behavior.
If a user has both enabled, they are unable to use either combo to start playback at the start of the arrangement.
What is the expected behavior?
Always have one shortcut available to allow user to start arrangement from beginning. Perhaps get rid of playback alternate when CROSS SCREEN is enabled as it's confusing to have the ability to do the same thing in two different ways. (Alternatively the community feature option could be the option to remove instead)
When did you start noticing the issue?
just now
Is there a relevant Pull request?
No response
What hardware did you reproduce it with?
OLED
What firmware did you reproduce it with?
Release 1.2/Chopin
What is the firmware name:
1.2.0
If possible provide the steps to reproduce the issue and upload additional media:
No response
The text was updated successfully, but these errors were encountered:
Please describe the problem:
CROSS SCREEN being enabled in arranger view now lets users have PLAY start from current location and <>+PLAY start from the beginning of the arrangement; the opposite of the old behavior.
However, this is also a community features option: Alternate Start Playback Behavior.
If a user has both enabled, they are unable to use either combo to start playback at the start of the arrangement.
What is the expected behavior?
Always have one shortcut available to allow user to start arrangement from beginning. Perhaps get rid of playback alternate when CROSS SCREEN is enabled as it's confusing to have the ability to do the same thing in two different ways. (Alternatively the community feature option could be the option to remove instead)
When did you start noticing the issue?
just now
Is there a relevant Pull request?
No response
What hardware did you reproduce it with?
OLED
What firmware did you reproduce it with?
Release 1.2/Chopin
What is the firmware name:
1.2.0
If possible provide the steps to reproduce the issue and upload additional media:
No response
The text was updated successfully, but these errors were encountered: