Show Cue System

I've had some brief conversations in the past regarding the inclusion of a central 'Library' (not to be confused with the 'audio library') where Cues and Sub-Cues could be created and stored. The library would probably consist of sub-folders to make it more practical.
My thoughts are, that when compiling Cues/Sub-Cues for a production you could import them from the library and that they would then actually be played from the library . . this would not only cut down on the amount of disk space being occupied but would also easily enable differing versions of a production to be quickly compiled. There could still be an option when importing those files to actually copy them to the relevant Production Folder if desired.
Another advantage here is that if an alteration is made to a Cue/Sub-Cue stored in the library then that would reflect in any production that uses that Cue/Sub-Cue. If any alteration is made that is not required for every production then the altered file could be 'saved as' under a different name.
Love to hear some thoughts on this one . . . .
Cheers . . . Martin
PS . . .sorry Mike . . not really trying to make more work for you.

I agree with the general concept. One of the "difficulties" I have when building a program is having to copy files from wherever to the production folder to make the SCS production portable for backing up. Having an option to consolidate all cue files into the production folder would be nice -- then you could build the production using audio files in the "library" area, and pull them together later on for portability. However you could run into a filename conflict issue if you have two files with the same filename in different source directories being used in the production.

"Create or ReSync the Prodution Folder" already exists on the Production Tab in Editor in SCS10. This will only collate the files for portability, of course, not their cue properties.

Playing cues from another cue list (as opposed to actually importing them) would be fraught with difficulty, I would have thought, including matching cue numbers and checking on device names, which is part of the import process.

Different versions of productions could be covered by enabling or disabling certain cues.

Malcolm

I do something like this already. I have a number of common cues (30)set up in a master show. this master show only contains the common cues and they are all are numbered 900+. All the common cues are disabled.
When I do a new show, I copy the master show as a starting point, rename it, then put the show specific cues in.
If I want to use one of the common cues, then just copy & paste into the correct point and enable it.
My common cues are mainly Midi commands for mics ON/OFF, effects unit changes and announcements.

HTH

Yup, I have to agree with all those comments and I'm basically doing what you are Boswell, i.e. having a 'master template' for the production and creating variations from that.
Although I had thought about this in the past it was highlighted recently when I wanted to add a Sub-Cue to an already existing Cue. Now this Cue was being used in six different versions of the production so I had to go to each of those six versions and add the Sub-Cue and it's properties. I actually did it to one and then went to each version in turn, deleted the old Cue and imported the revised one from the altered production.
Thanks . . . Martin