Why does the first Go on a cue list include an Assert?

Question

I hate when I have manual data that gets lost when pressing Go on a cue list. I want to be able to have a Cue list in my show that has no effect at all on anything other than a specific channel. Is this even possible? 
 Thanks!

eos moderator · Accepted Answer

The official explanation by Anne Valentino (found on this forum): 
 A linked cue is considered "out-of-sequence" and follows all of the rules of such a cue. These rules are: 
 1) Replay the entire state of the cue, including tracks. 
 2) Restore all manual overrides to home, unless those manual overrides are to other playback content (i.e., another cue list or a sub). 
 The reason for that is to get back to the just the content of the cue you stored and are returning to, and not have "dangly bits" around that you have to manually clean up.

ueliriegg · Answer

this will not make a difference in your situation right now, but it's still important to note: it's not the first cue that has an assert. you're using probably Go From Last = Wrap? this is an out-of-sequence command which (like all other OOS commands) triggers the assert behavior. some other examples are: GoToCue Back Link instead of Go From Last try using Cue Link Loop 0 Enter

Kris Ladd · Answer

Sorry, I know this is an old post, but I have an answer that may help you. 
 In the fader config for your cue list, if you do a channel filter for only the channel(s) that are in the cues, then running the cues will not affect any manual data on any other channels. 
 (I too have been annoyed with losing manual data on a Go. I busk movers with manual commands, but have the houselights on a cue list. My intensities are always on subs, so I didn't know/remember that intensities fade out. With NIPs, they lose manual status and the reference labels disappear, but the parameter values don't change... so the show isn't affected, just my ability to know what that fixture is doing exactly.)

Why does the first Go on a cue list include an Assert?

Top Replies