Multiple cue lists and macros

Following up with things I have learned in case it might prove useful to others, or aid ETC Support in confirming this is expected behaviour.

Hans helped me reframe the question and I was able to get this to work, mostly, by using "Assert 0" to force control back to the master cue list, which is running on the master fader. I say "mostly", because there seems to be inconsistent behaviour when this is done via macro. Foreground macros don't work with the syntax I am using, and background macros don't always execute the Go To Cue, or perhaps they do, but not necessarily on the the asserted cue list, which might be timing related. Where the Go To Cue is particularly an issue is when an ML is part of the cue. It is not coming back to the main cue list unless the the Go To Cue command is entered manually. Is that a User 0 versus User 1 issue?

2012 10 30 10:08:08 Context Cue 91 4

<snip>

2012 10 30 10:08:32 Eos Consol Firing Macro 88
2012 10 30 10:08:32 Key_Event U:0: Live CLEAR_CMDLINE
2012 10 30 10:08:32 Key_Event U:0: CLEAR_CMDLINE
2012 10 30 10:08:32 Context (L)USER: 0-> Live
2012 10 30 10:08:32 Context Cue 1 2 
time: 330 10:08:32 Context Go 33
time: 030 10:08:33 Context Off 33
2012 10 30 10:08:34 Key_Event U:0: Assert 0

So then I tried using the fader Off command which might produce better results, but I won't know until I try it with the live rig.

2012 10 30 10:08:40 Key_Event U:1: MacroButton
2012 10 30 10:08:41 Key_Event U:1: 3
2012 10 30 10:08:41 Key_Event U:1: 3
2012 10 30 10:08:41 Key_Event U:1:
2012 10 30 10:08:41 Eos Consol Firing Macro 33
2012 10 30 10:08:41 Key_Event U:0: Live CLEAR_CMDLINE
2012 10 30 10:08:41 Key_Event U:0: CLEAR_CMDLINE
2012 10 30 10:08:41 Context (L)USER: 0-> Live
2012 10 30 10:08:41 Context Cue 1 3
time: 330 10:08:41 Context Go 33
2012 10 30 10:08:42 Key_Event U:0: Assert 0 Go_To_Cue Time 0

... and yet more feedback on my ongoing struggles with what ought to be really simple but isn't (see the first post for the scenario)

Macro (background mode) is:

Go 32 Macro_Wait 1 Assert 0 Macro_Wait Go_To_Cue Time 0 *

which is supposed to execute cuelist 32 (looping 2 step cue), wait for it to finish, assert the main cue list and then force that cue to bring back any channels that might have been grabbed by 32.

The Go_To_Cue doesn't consistently work when fired from a macro but always work when executed manually. So the macro has been modified to mostly run in the background but fire the Go_To_Cue in the foreground by calling another macro for that task:

Go 32 Macro_Wait 1 Assert 0 Macro_Button 40 *

Macro 40 (foreground) contains:

Go_To_Cue Time 0 * 

This convoluted approach seems to be yielding more consistent results but I won't know until the run-through tonight. Maybe the Assert should be a Fader_Assert and also run in the foreground, but I don't have time to experiment.

I think things would be a whole lot simpler if there was a Macro mode called do-what-it-would-have-done-if-somebody-physically-pushed-the-button.

sk8rs_dad said:

I think things would be a whole lot simpler if there was a Macro mode called do-what-it-would-have-done-if-somebody-physically-pushed-the-button.

And I always thought, that is what the learn button does. Or is it not.....

Have you tried using learn?

Florian is correct.  You should be able to write a macro for your secondary cue list of [Release] + [Load].

??

a

As this long chain will attest, I agree that I should be able to write a macro, but the macros do not behave as expected. I have spent about 10 hours getting to this point and shown all my work but it doesn't work as expected, and I get different behaviours when it is a foreground or background macro. So the question remains, what should I be doing.

Thanks.

/Karl

... and yes I started with "Learn" and it did not work without having to add Go To Cues and even then it didn't work because the Go To Cue wouldn't take in a background macro.

OK.  One step at a time.

Just to be clear.  You are simply trying to write a macro that releases a secondary cue list to the last cue list that had control of specific lights - which in your case is your master list?  I'm not clear on why you were asked to use an assert command or go to cue - one of the developers and I discussed this and unless we are completely missing something, we are confused by that.  But I've put in a call to Hans.  Perhaps he can help clarify. 

Please assure that you have not set a background disable flag on your master cue list.

Put yourself into some cue in the master list that involves these lights.

Manually playback your secondary list.

Can you use the release command on your secondary list manually and return control to the master?   (That would be Release and Load).  The release command will leave the secondary cue list where it is.  If you want to release and also set the secondary list to the top of the que, use Off and Load.

If you can do it manually, can you learn a macro 

learn macro n enter [Off or Release] and Load. Learn

Rerun the cues as before and manually run the macro?  Does it work?

If that works, how are you triggering the macro in your show.

I just tried this, and unless I'm missing something that you are trying to do, it works fine.  

If it isn't working, please email me your showfile (anne.valentino@etcconnect.com)

Thanks so much.  We will sort out what is going on.

a

Thanks Anne. I have always figured it is something I am screwing up but I had to blaze ahead with limited knowledge because we open on Sunday and a half-baked answer is better than no answer at all. I will give your recommendation a shot when I am back in the theatre this evening. I thought I had already tried it but maybe I messed up a keystroke somewhere.

Thanks Anne. I have always figured it is something I am screwing up but I had to blaze ahead with limited knowledge because we open on Sunday and a half-baked answer is better than no answer at all. I will give your recommendation a shot when I am back in the theatre this evening. I thought I had already tried it but maybe I messed up a keystroke somewhere.

No problem at all.   Very interested to hear what you find.

Thanks much!

a