![]() ![]() The exception to this is if the console isn't up to running the show (i.e. If I have 40 automation cues and one playback cue then the console can trigger QLab. If it's a playback show with two automation cues, then QLab can trigger the console. If I am going to have a single button trigger both automation and playback then my rule of thumb is this: the master trigger is the device with the most cues. Even then (especially if there's only a couple of playback cues in the show) I'll sometimes use a separate button on the console as a QLab trigger, especially if there wasn't a tonne of programming time during the production process. Personally, if I'm line-mixing a musical, I want that GO button to be as close to the VCAs/DCAs/CGs as is physically possible, which usually means a button on the console. This is simpler to setup and program, and means you'll never accidentally trigger a sound effect when you meant to hit an automation cue (or vice-versa). I've known some very good A1s who insist on having automation recalls and playback triggers be totally separate. Quote from: Russell Ault on January 27, 2021, 01:38:32 AM It ultimately comes down to preference, but IMHO it depends on the desk and the show. QLab is triggering itself, plus recalling settings on a couple of processors, etc., etc.) in which case QLab will have to run the show (but I'll still want to be able to trigger it from a button on the console's surface). ![]() It ultimately comes down to preference, but IMHO it depends on the desk and the show. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |