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