Record Only sub

Been wanting to do this for a while and finally did it, but not sure it is correct.

I have 40 subs which are stacked cues (most of them only 4 cues/steps each).  Easiest way for me in concert environment.  They are labeled fast, medium, slow to help me pick a starting point for songs then I use the bumps to make the visible changes already recorded.  Use Magic Sheets as well for on the fly stuff.

Anyway I wanted a sub that would take all fixtures, whether already on or not and switch them to full intensity, white and varying strobe parameters. (no gobos, keep same positions, etc.) That way no matter what is running all I need to do is press the bump on that sub and I create the strobe effect. Then when released they all resume their last look.

So I brought up one cue that had the fixtures I wanted and I changed the intensity & beam (open gobo, white, strobe vary each fixture, full intensity) and I used Record Only sub # thinking this only records those manual values I placed on the fixtures then taped that sub onto a fader.  Seemed to work great during testing but during the first show (only one so far) a select few fixtures would shut off strobing even when hitting the bump for the next cue.  I had to do a GTC Out then bring up the next cue to stop it. Didn't use it again for obvious reason.

Obviously something related to what I did with those select fixtures but not sure what.

I realize this might be a little generic but any thoughts.  Maybe the actual string to record that sub.

Parents
  • Jeff,

    It sounds like you were on the right path with that one. The only additional thing I'd recommend would be to use the ML Controls dialog to do the selective store:

    <Chan>[1][Thru] X {Intens}{Shutter Strobe} [Record] (or Record Only) [Cue] Y [/] Z.

    I'd be curious if asserting the cue would help at all in that situation. It should have behaved as you intended though. We'd want to see the show file or have steps to reproduce if it continues. 

    Thanks!

    Hans

Reply
  • Jeff,

    It sounds like you were on the right path with that one. The only additional thing I'd recommend would be to use the ML Controls dialog to do the selective store:

    <Chan>[1][Thru] X {Intens}{Shutter Strobe} [Record] (or Record Only) [Cue] Y [/] Z.

    I'd be curious if asserting the cue would help at all in that situation. It should have behaved as you intended though. We'd want to see the show file or have steps to reproduce if it continues. 

    Thanks!

    Hans

Children
No Data
Related