Multiple cue list bug

When you say that Cue List one tells the lights to go out, what are you really telling it to do?

I would try one of two things.

1: Set Cue List 1/x to an All Fade

2: Make a macro that uses the Release command on the fader list two is using

 I guess my question, or misunderstanding, is that if no cue list is currently telling a light what to do I should simply be able to write a cue to tell the light what to do.  It seems to me the Ion is saying "Hold on, this other cue list told me to do something way back when and now a new cue is telling me to do something new.  Nope.  Not gonna happen."

 If I was talking about cue list 1/50 telling the lights to go out and 1/51 telling them to go on we wouldn't even be having this discussion.  The engineers and programmers would be working to fix this unfortunate situation.  But since cue 2/xx tells the lights to go out and after that cue 1/xx tells them to come on we're all like "yea, you just have to find a work around."  You're really harshing my perfect world here.

Sorry I got the light intensity reversed in my example, but you get the jist

Perhaps we are misunderstanding the issue you are seeing - its a little unclear if you want the lights to return to cue list 1 or if you don't (or perhaps I've just not had enough coffee yet).

This is a move-fade desk.  So lights respond when they are provided a move command. 

1)  If you DO want the lights to return to cue list one after they have been made inactive (or set to any condition really) in a secondary cue list, just assert the tracked values in the cue from cue list 1 when you want the lights to restore to the main cue list.

2)  If you do not want the lights to return to cue list 1, just make sure there are no move instructions for those channels in cue list 1 in the range you are talking about.    If you are taking control of the lights on cue list 2 (e.g.) and what them to only be controlled by that cue list once it is active, you can set an independent flag on the second cue list.     If that is more draconian that you'd like, just make sure those lights have no move instructions in the first cue list after they have been "stolen" by the 2nd list.  You have two options.  If there are move instructions in that range, select the cue range, select the channels at [at] [Enter] them.  (This is best done in blind spreadsheet so you can see what you are doing.    You can also place null flags on those channels.  That will maintain the move instructions, but will not call for the action on playback).

Does that help at all?

Anne

Perhaps we are misunderstanding the issue you are seeing - its a little unclear if you want the lights to return to cue list 1 or if you don't (or perhaps I've just not had enough coffee yet).

This is a move-fade desk.  So lights respond when they are provided a move command. 

1)  If you DO want the lights to return to cue list one after they have been made inactive (or set to any condition really) in a secondary cue list, just assert the tracked values in the cue from cue list 1 when you want the lights to restore to the main cue list.

2)  If you do not want the lights to return to cue list 1, just make sure there are no move instructions for those channels in cue list 1 in the range you are talking about.    If you are taking control of the lights on cue list 2 (e.g.) and what them to only be controlled by that cue list once it is active, you can set an independent flag on the second cue list.     If that is more draconian that you'd like, just make sure those lights have no move instructions in the first cue list after they have been "stolen" by the 2nd list.  You have two options.  If there are move instructions in that range, select the cue range, select the channels at [at] [Enter] them.  (This is best done in blind spreadsheet so you can see what you are doing.    You can also place null flags on those channels.  That will maintain the move instructions, but will not call for the action on playback.

Does that help at all?

Anne

 I have to do some more investigating into this.  The interesting thing is that I'm running multiple cue lists anyway and they all perform as expected.  When each cue list ends I can run another cue list and everything is fine.  This issue seems to be that I'm executing a cue list from another cue list, which I have also done before without issue only this time it's wonky.

 Let me look at it closer and see what I find.  The basic question remains though,  Cue list 2 tell the light to do something after which cue list 1 tells it to do something else, which is not happening.  Why?   Being that I'm in the middle of our passion play I may be missing something, but I'll look at it again when I get time.

Can you also confirm what software version you are running (we are interested in the application version).  The number you provided is the image version.  You can find the current software version in about.  If you press About with nothing on the command line, you'll see the version number there.

Feel free to email the show file (anne.valentino@etcconnect.com).  Just let me know the channels and the cue in list one where you are expecting to see them return.

Thanks,

Anne

I've uploaded the files to Anne.  I'll post my email here so as to keep everyone in the loop.  Thanks for all your inputs.  Assert was the final answer to this problem.  Hopefully they will find out why it was a problem: 

Anne,

 Here are the shows that I had problems with per our discussion on the forum, I'm zel BTW.  This is concerning channels 101-150, excluding 137-140.  The problem first showed up on file #1 after cue 578.  My fix for it was to add cue 102/45 to return the LED's to my control.  You'll also find I added 102/50 so that I can restart cue list 102 without having to go to cue out, but otherwise that issue is unchanged. 

The final version is in file 3.  I used asserts to solve the issue and discovered another problem, namely I inserted a Macro to grab some floor lights so I can roll up the intensity when the actors entered from the back (cue 158) but it would not execute.  It basically served as a reminder for me to press MACRO>1>ENTER in order to brings those address up. 

You'll also find that I have 10 other cue lists that I'm running (1-10).  These are 7 of the most commonly used scenes plus two available to program anything that may come up for that day as well as a generic exit play list (10).  I've had no issues with them.  Of course they are all self contained and don't execute anything outside their list, however I've done shows before using executables with no problem.  One in particular ran 16 different cue lists executed from one master list.  Many of them ran concurrently with no problem so I'm kind of stumped as to why this would be an issue. 

My hope is that in the heat of programming I've overlooked something or done something stupid that I can correct in the future. 

Let me know, thx. 

Bill MacLeod

FBC Media

904-265-7259

Faith is the currency of God's realm

Version 2.0.1