Buddy cue lists

Could be useful....that way you don't have to put a comment macro on every cue in stack 1 to fire stack 2 as well.

Ross,

Can you give me an idea of what you would want to split between the 2 lists? If you always know that both will be triggered at the same time, why not just put everything in one list?

Thanks.

Sounds Jands Vista-ish.
I do not need this function.
However, I want the macro that can send Go to console 2 at any time.
Thanks,
Akito

Hi Tom,

As always these things come up on shows. I have just finished programming a very complex show with little time and 2 programmers, one controlling moving lights, and the other controlling Catalyst visuals etc. We worked with the same cue numbers and although one desk may have had a few extra cues here and there the show structure was essentially the same. Although the show will merge for the tour onto one console, for the first few shows there were notes to be done in both areas, and having separate lists allowed a level of flexibility for each operator to amend only their lists, or to slip a visuals cue forwards/backwards by simply changing the cue number on that list only. The ability to synchronize the lists without merging the data would have been fantastic.

Thanks

Ross

Ross,

Great explanation. I've logged this as feature request #9114 and added your comments to the bug.

Thanks.

If you were using two seperate consoles at the time, why would you not use MSC to link them during this process?

Hi Jason,

The point is that the show was "programmed" on 2 consoles and "operated" on one. The touring operator had to learn the show before the programmers left. The programmers had to watch the performance with the creative team making notes, then action amendments.

Ross

Gotcha.