Force Sequence of Cues

[caffeineking]

Something that I read in a previous thread that was a problem with running a fade while in either edit or blind edit mode. OK, this is probably more applicable in blind edit. What was mentioned is that while you editing a memory blind, if you trigger the next cue, the one you are editing will fade to output. So my suggestion is that you build an auto sequence or forced sequence function that run the next memory in the queue after the one that is currently live without worrying about what is currently being edited or manipulated. Another thing that I think this could extend to is that if you are running through the cue list using the +/- keys on the main console, the desk will skip over memmories that have not been programmed.

 

Thanks for listening

[Jazzy]

Another thing that I think this could extend to is that if you are running through the cue list using the +/- keys on the main console, the desk will skip over memmories that have not been programmed.

 

I think this would only work if the desk had dedicated RUN and PROGRAM Modes like the Sirius 24 /48 as how would you be able to get to unprogramed memories if you had no keyboard?

[caffeineking]

Another thing that I think this could extend to is that if you are running through the cue list using the +/- keys on the main console, the desk will skip over memmories that have not been programmed.

 

I think this would only work if the desk had dedicated RUN and PROGRAM Modes like the Sirius 24 /48 as how would you be able to get to unprogramed memories if you had no keyboard?

 

The way I see this working is that a function key would be bound to the auto/force sequence function. When this function was invoked, the desk would then skip unprogrammed cues. So I suppose this could be called RUN/PROGRAM mode switch.