scottydog75 Posted Friday at 04:18 PM Report Posted Friday at 04:18 PM Is anyone aware if there is a way to always exclude a fixture from being recorded into a cue stack? I keep accidently recording my haze machine into my main PB, which can be resolved by deleting and re-patching the hazer, but feel like there must be a better way? Cheers Quote
Davidmk Posted Saturday at 09:14 AM Report Posted Saturday at 09:14 AM If you are operating with tracking options set to "Cue Only" or you have "Snapshot" enabled when you record then you have effectively told the desk to record everything. See manual here and here. In the Record Options, "SmartTag" enabled could record the hazer - if you changed one or more of its values in the programmer. For full control of what gets recorded you need SmartTag off. You can then select "Tagged Fixtures" which will record every fixture that has been changed or "Selected Fixtures" wich only records the currently selected Fixtures. See manual here. Cue Only, Snapshot & SmartTag all let the desk decide what to record, turning all of them off makes you decide but then you need to be sure you have included everything you want. Tagged Fixtures will generally get that right, with Selected Fixtures there is a risk that you will select a fixture, change it, de-select it, select another and change it then record - in this case only the 2nd fixture gets recorded. Essentially, the desk will do what you tell it but you need to understand what you've told it. There are videos in the linked manual references, these might help. To remove your hazer (or anything else) from a cue, select it, press Home then Update and select Remove. Hope that helps. 1 Quote 2 x FLX with Raspberry Pi's running TouchOSC, ZerOS Wing, Leapfrog, Jester M24L Eurolite ArtNet/sACN nodes. Regular tech in two Milton Keynes music venues plus occasional festival work.
kgallen Posted Saturday at 09:50 AM Report Posted Saturday at 09:50 AM I was going to suggest inhibit but I think that’s more a sticking plaster over the issue rather than a proper approach that David described above. Quote
Davidmk Posted Saturday at 10:36 AM Report Posted Saturday at 10:36 AM @kgallen @scottydog75 1 hour ago, kgallen said: sticking plaster Well yes, but in a show situation, when you discover your hazer (or anything else) has been caught in cues, you can quickly set up an inhibit to get you through the performance. Quote 2 x FLX with Raspberry Pi's running TouchOSC, ZerOS Wing, Leapfrog, Jester M24L Eurolite ArtNet/sACN nodes. Regular tech in two Milton Keynes music venues plus occasional festival work.
scottydog75 Posted 1 hour ago Author Report Posted 1 hour ago I think my issue is mainly when updating a cue(s) during a rehearsal or during a run, I naturally have the haze machine running, so it inadvertently gets recorded into the cue. A good reminder about the 'Remove' feature for the odd cue or two, but I've generally found the delete fixture route catches all my errors if its been a big update session! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.