How can I make this work next time?

Richard and Bob,

Again, thanks.  I fully respect your methods but  I think you are over generalizing in your use of the term classic.  My classic methods are based on 20 years of using all ETC console up to the Expressions and Strand LP90's and 500's.  I haven't yet had the opportunity nor neccessity to spend time on the moving light consoles (I'm not proud of that, but its true).  In all of that time, there has only been a small handful of instances where I found it neccessary to put some cues on a second playback.  I realize that there is a large contingent out there that think that's absurd, but it's not really.  99% of the lighting I do as a full time house guy is one sequence of events happening in one given space.  Using Parts, Links, Follows, etc, I have always been able to acheive the designers' visions no matter how intricate and elaborate.

This is not to say that I am rejecting the concept of using more than one cue list, but I personally find it hard to believe that building an empty dummy cue that activates another cue list that contains one cue, while assuring that every channel is owned and each list is asserted, and loading each one as you go is simpler than recording 40 cues then using the Move To function and 5 minutes to rearrange the show order.  Especially if the console is doing what I believe it should be doing.  Plus, as a result I get all forty cues in order on the Playback Status Display. 

Nick,

I tried the Allfade thing this morning, I too thought it should have worked, but it didn't.

John,

I tried the Link thing this morning.  I thought it wouldn't work because it results in skipping the cue where the Effect stops but it did work.  I would use that in a pinch, but it makes the PSD a little confusing for me like when I want to see what cue is third or fourth from now. 

Turns out, putting a Block on all the cues before moving them does work.

ETC Folks,

Seriously.  What's up with this?

Thanks everyone,B

I don't know if this particular method will work better for you or not, but here goes.

Build each piece as a cuelist, i.e.  Piece A -> Cuelist 1; Piece B-> Cuelist 2; Piece C->Cuelist 3...ad infinitum...

Then use [Cue] [x] [/] [y] [Enter] [Load], where x is cuelist and y is cue number.  So Loading Cuelist 2 would be: [Cue] [2] [/] [1] [Enter] [Load].  This will plop the corresonding stack onto the main playbacks as needed.  As long as the last cue in the stack and the first cue in stack are some sort of transition cue it should work out pretty easy.  I believe by using this method, you can build each piece independent of each other and not have to worry about Asserts and what not.  Tried this on the offline since our console is not set up at the moment, and seemed to work fine.  Depending on how you build the beginning and ending cues you may want to make them block cues, but I think it should work out.

Hope that helps in some way.

I don't know if this particular method will work better for you or not, but here goes.

Build each piece as a cuelist, i.e.  Piece A -> Cuelist 1; Piece B-> Cuelist 2; Piece C->Cuelist 3...ad infinitum...

Then use [Cue] [x] [/] [y] [Enter] [Load], where x is cuelist and y is cue number.  So Loading Cuelist 2 would be: [Cue] [2] [/] [1] [Enter] [Load].  This will plop the corresonding stack onto the main playbacks as needed.  As long as the last cue in the stack and the first cue in stack are some sort of transition cue it should work out pretty easy.  I believe by using this method, you can build each piece independent of each other and not have to worry about Asserts and what not.  Tried this on the offline since our console is not set up at the moment, and seemed to work fine.  Depending on how you build the beginning and ending cues you may want to make them block cues, but I think it should work out.

Hope that helps in some way.