• State Verified Answer
  • +1 person also asked this people also asked this
  • Date
    John Demaree
  • Date
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 187 subscribers
  • Views 2311 views
  • Users 0 members are here

Multiple Cue Lists

I have seen many threads on here about multiple cue lists, but none have quite had the problem I did.    Using and ION, I set up about 10 cues in a cue list 2 to run my cyc lights and do a 20 minutes sunrise while the cues in cue list 1 continued to run with the GO button.  The problem I had was that the cues in list 1 would "sometimes" override the cues in list 2.  I could never figure out why some would and some wouldn't.  I was careful not to program any values for the cues in list 1 while list 2 was running.  When a cue in list 1 did  take over I would go into the cyc lights in that cue and change their value to null, but this didn't seem to help.  I was running in cue mode not tracking mode.  I made sure that the cues in list one were not specifically calling the cyc lights with color or intensity.  I eventually gave up and just staged the sunrise within the cues in list one.  Is there something simple I missed.  I haven't done much with assert, not sure this is what I needed or not.   Any thoughts about what I was doing wrong?  

Parents
  • 0

    a channel's parameter is owned by the cuelist that controlled this parameter last. if there is a move instruction in a cuelist for a channel that's curently not owned by this cuelist, then that parameter is stolen from the other cuelist.

    to make sure your sunrise fade can run, you must avoid cuelist 1 stealing parameters away. this would happen either by a conflicting move instruction in cuelist 1 or by an assert in cuelist 1 (if the cyc lights have tracked values in cuelist 1). if you do have a move instruction in cuelist 1 that you want to get rid of, the way to do this is At Enter (if in Blind, it's just Chan 1 At Enter; in Live Chan 1 At Enter Update Enter).

    GotoCue Out would also stop and re-set all cuelists. if cuelist 2 should continue but not cuelist 1 the alternative would be GotoCue 1/Out

    using the Back button includes an Assert, so if you Back on cuelist 1 and you have tracked (magenta colored) values for your cyc lights, this will also steal the parameters from cuelist 2's fade and set them to where cuelist 1 says they should be

Reply
  • 0

    a channel's parameter is owned by the cuelist that controlled this parameter last. if there is a move instruction in a cuelist for a channel that's curently not owned by this cuelist, then that parameter is stolen from the other cuelist.

    to make sure your sunrise fade can run, you must avoid cuelist 1 stealing parameters away. this would happen either by a conflicting move instruction in cuelist 1 or by an assert in cuelist 1 (if the cyc lights have tracked values in cuelist 1). if you do have a move instruction in cuelist 1 that you want to get rid of, the way to do this is At Enter (if in Blind, it's just Chan 1 At Enter; in Live Chan 1 At Enter Update Enter).

    GotoCue Out would also stop and re-set all cuelists. if cuelist 2 should continue but not cuelist 1 the alternative would be GotoCue 1/Out

    using the Back button includes an Assert, so if you Back on cuelist 1 and you have tracked (magenta colored) values for your cyc lights, this will also steal the parameters from cuelist 2's fade and set them to where cuelist 1 says they should be

Children
No Data
Related

www.etcconnect.com