-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Can't use SCENE SEL #4
Comments
You only want to move the cursor to 6? |
Yes I only want to move the cursor because I am also stopping playback ready to restart on cue. Using this in the theatre. |
ok your scene 6 stops all tracks? in that case a STOPALL could do the trick? |
Sorry I think I was tad ambiguous. This is a bit of an outline that I hope helps (scenes triggering sequentially via follow actions) The idea is that the music will stop when we hit Scene 5, wait for stage action, then hit enter to trigger Scene 6 when ready. |
Thanks I see now. With Live 11 scene follow actions you could tell Live to move to scene 6 after X bars, but it would start the scene 6. (but you know that you can auto select the next scene with the 'select next scene on Launch' option?) |
When using Scene follow actions to move through the scenes the select next scene on launch option only works on the scene's you trigger manually. For example, I trigger Scene 1, it selects Scene 2, Ableton plays Scenes 1-4. Scene 5 stops playback. The cursor is left on Scene 2. Normally I would use either |
I can't manage to use
[] SCENE SEL 6
to move the cursor position to scene 6.Works in my copy of ClyphX Pro in Live 10 but not in Live 11 with this version.
If it's limited to ClyphX Pro do you have a suggested workaround to select a scene with the cursor ready for triggering?
Should note that I have tried to use
MST/SEL 6
but it doesn’t work. Have triedMST/VOL <
and2/SEL 6
and both of these work as expected changing the volume of the master track and selecting track 2 scene 6 respectively.Have also tried calling the scene by it’s name and also just using > or < and neither of these work.
The text was updated successfully, but these errors were encountered: