>>> Jump needs a GUIDE CUE track solution

[nevillewhitemusic]

When using “>>>” (a jump section), any +GUIDE Cues become unusable/ unwanted.
What about the following solution: Similar to the +LOOPGUIDE functionality (where it mutes the +GUIDE track when the loop is active), in Ableset create a NEW type of “Guide” cue track, but for >>>Jumps.

Perhaps using a +JUMPGUIDE or +JG name. When a >>> JUMP is a measure away (or whatever per the quantization) from executing the “JUMPGUIDE” track would UNmute (allowing some CUE to be heard), and both the +GUIDE and +LOOPGUIDE tracks would MUTE (because those will be incorrect for the upcoming >>>jump).

Once the Jump is executed, the +JUMPGUIDE track would MUTE again.

This creation of a +JG track would be natural, since maintaining it would require the same planning as the +LOOPGUIDE track.

note: this is related to the following GENERAL thread…
Feedback Wanted: Displaying Automatic Jumps in the Setlist

note: regarding DOCs, just a small thing. I have noticed that +GUIDE and other tags must be in ALL CAPS. It might be helpful if the DOCS said this (it took me a bit of time to flush this out a few months ago).

btw, is possible Feature Request also is related to the below post:

Make Performance View Section (quick link) Cues ">>" MIDI mappable via OSC solution, But +GUIDE is a challenge

I like the Performance View Section Cue “>>” (Quick links) feature, which adds icons on the screen (with the section name, like “Chorus”), and upon hitting the icon (assuming the transport is moving) that “quick” section will play next. Yet a common on-stage goal is to avoid touching a Screen, so I am pondering how these “>>” Quick section links (per song), could be mapped via midi. Since every song will have its own unique different “>>” sections to quick-link to (one song may need “verse 2” …

Live ver: 11.3
AS ver: 7.4.1

[leolabs]

I’ve just implemented this as well, with the difference that the +JUMPGUIDE is unmuted for the entire time that another section is cued. This is more in-line with how the +LOOPGUIDE track works.

@nevillewhitemusic

note: regarding DOCs, just a small thing. I have noticed that +GUIDE and other tags must be in ALL CAPS. It might be helpful if the DOCS said this (it took me a bit of time to flush this out a few months ago).

That’s a good point! I’ll update the docs to mention this