Loading / Unloading Playbacks using Macros triggered from Cues

I've started using EOS today to prepare for a show next week. The console is fantastic and I'm having a great time with it! There's only one area causing me difficulty at the moment, and any advice would be appreciated ... This is the scenario:


1) Cue List 1 is running on the master playback.

2) When Cue 1/2 runs, cue list 2 needs to load onto Playback 1. Cue list 2 only contains 2 cues that are linked to each other. This is to allow repeated colour bumps to be manually triggered in time with music, over the top of Cue 1/2.

3) When Cue 1/3 runs, it Asserts all parameters back to tracked values. Cue list 2 can then be released.


These steps work fine if I manually load the Cue List 2 before running Cue 1/2 and manually release it after Cue 1/3. However I would really like to trigger Macros to do this from the appropriate Cues on the master playback. So I've created the following Macros using the Learn function, and I've set Cue 1/2 to trigger Macro 1, and Cue 1/3 to trigger Macro 2.

Macro 1:

Cue 2 / 1 []
LoadCue 1 Fader_1

Macro 2:

Fader_1 PlaybackRelease 1


However the following problems occur:

- If I recall Macro 1 from the Direct Selects or Macro button, Cue 2/1 correctly loads into Playback 1 ready to be used. However when Macro 1 is triggered from Cue 1/2, cue list 1 is loaded into Playback 1 rather than cue list 2.

- Whatever way Macro 2 is triggered, it only releases the playback if cue list 2 hasn't been 'used' yet - i.e. if Macro 2 immediately follows Macro 1 the cue list is released. If I recall Macro 1, use the Go button on playback 1 to trigger the colour bumps, and then recall Macro 2, the cue list is not released.

Any ideas on this? Is it to do with the context in which the Macros are recalled? Is there a better way of doing what I'm trying to achieve? I'm really trying to find a basic workaround to not being able to manually step through absolute / step effects (unless I've missed something?!). Worst case for now is I'll just have to load & release manually - the actual cue-list LTP & assertion is working OK.

As I said this is the only thing I've got trouble with right now - everything else seems fine - its a really, really nice console to work with. :)

Cheers,

David

Parents
  • Hey David.  Good to know things are going well.  Will look into the macro issue here, but I think an easier way to do what you want to do is use the execute field of cues in cue list 1.

    You have a couple of options,  in Cue 1/1, you can say [Execute] [2] [/] [1] [Enter].... when you then run cue 1/1, it will automatically load and run 2/1.  Could do the same thing for 1/2, etc.  Alternatively, if you were to say [Cue] [1] [/] [1] [Execute] [2] [/] [Enter] - you have now sync'ed cue list 2 to list 1.  Each time you execute a cue on list 1, it will automatically execute "like numbered" cues from list 2.   So, when you get to cue 1/3, which pulls all control back from list 2, the synchronization would be ended provided there are no more cues in list 2.

    Would that work?

    a
  • Thanks for the idea, it sounds like it might work - I'll give that a try later when I get to the theatre. Clearly it should cover loading the other cue list, but how about clearing it again? In this example, presumably cue list 2/1 gets automatically loaded into the first free playback; so if this happens a few times in a show the playbacks get progressively filled up? Not so much a problem on the current show, but there's another show I need to transfer to EOS where this would happen maybe 20 times, with a different secondary cue list each time - and I'd really like them to load onto the same page; hence wanting to release each cue list as soon as its done with.

    Cheers, David.

  • Hmmmm.... you could have macros release the older cue lists to make the lower numbered faders available for new cue lists....??

    a
Reply Children
Related