Move on Dark glitch

[Zulu]

Hi. I’m using a couple of moving lights in various cues, for my theatre style cue stack on the master playback.

move on Dark is set, and the light does as expected when entering the cue.

But….. when moving to the next cue which does not need the moving lights, the moving lights visibly move and change colour during the fade-out. Not the desired effect, as I’m just wanting it to fade before moving.

any thoughts?

many thanks, Zulu

[Archie D]

Hi @Zulu,

It sounds as if the cue in which your fixtures fade out have position and colour information too. To let these fixtures fade out without any movement or colour changes, we need to remove that information from that cue.

First, save a copy of your showfile so you can revert to it if needed (Z/Shift -> Save Show).

Now select your problematic cue (the one to fade out the fixtures) and tap GO to proceed into that cue. Select your moving fixtures, then tap the Home icon (top left of the internal touchscreen). This homes & tags all parameters for the selected fixture(s). Now, we want to un-tag only the Intensity parameter so that the intensity of the fixtures still go to zero (e.g. that information is preserved), instead of previous values tracking through. To do this, tap the Z/Shift key, then tap 'Intensity' above the first encoder wheel - it should switch to have a dark background. That parameter is now un-tagged.

Now tap the UPDATE key (you may have to hold it for the Update Window to appear on the internal touchscreen, this behaviour can be adjusted in SETUP -> Settings -> Record & Update), ensure 'Remove' has a red stripe (enabled) and Smart Tag has a blue stripe (disabled). Also make sure that 'Cue Only' has a red stripe so that we are only dealing with and affecting this cue. Tap your Master GO button to submit the update.

You should now find that the fixtures fade out without changing position and colour. If you have any questions feel free to ask.

Archie

[Zulu]

Hi, Archie

thanks for your consideration on this. I’ve just tied it on Phantom, at home, and it seems to work just as you described. Although I can’t really test it until I apply it at the theatre. (no lighting rig at home!)

as this problem exists on several cues in my stack which use the moving lights, must I apply this solution to each following cue? Or is there a global solution for the entire Playback? (I notice your recommendation includes ensuring “This Cue Only” is enabled.

thanks again, Zulu.

[Brian F]

I’m a relative newbie and still getting my head around a few of the concepts (remove being one of them). A few days ago I managed to accidentally record another playback into my main cue stack while I was editing. I’d recently saved the show so the quickest option for me was to reload a previous save as it was in the middle of a rehearsal. I now realise how I could have relatively quickly removed the offending fixtures from that explanation. I vaguely recall however seeing seeing source options at the top of the update / record screen so I’m now also wondering if that can be used in a similar way to remove the incorrect playback as a source? Is that possible for the next time I make a similar mistake?

 

edit,

Thinking about it though I’m assuming the answer must be ‘no’ as once I’ve updated the main cue stack that becomes the source rather than the playback so I’d have to resort to removing the relevant fixtures.

[Archie D]

Hi Zulu,

No worries, glad to hear the solution worked on Phantom ZerOS for you.

7 hours ago, Zulu said:

as this problem exists on several cues in my stack which use the moving lights, must I apply this solution to each following cue?

To 'fix' an individual cue, repeating the steps listed would work perfectly. However, if you have a range of cues together which all have the same problem, you could attempt using Track Forwards in the tracking options along with 'Remove' within the Update Window, but be aware of potential blocked cues. If the values that cause the movement and colour change during the fadeout are tracked through to following cues, then Track Forwards will work alongside 'Remove'.

You can alternatively use Cue Only in the tracking options within the Update Window and simply use syntax (UPDATE 3 THRU 7), which would apply the 'Remove' to all of those cues for tagged parameters.

8 hours ago, Zulu said:

Or is there a global solution for the entire Playback?

As the issue you're facing is rooted from information stored in cues, the cues themselves must be updated to remove that information.

If you have any other questions, please feel free to ask.

Archie

[Archie D]

 Hi Brian,

7 hours ago, Brian F said:

A few days ago I managed to accidentally record another playback into my main cue stack while I was editing.

When a playback with values stored is raised or active while recording a cue, those values are stored into that newly recorded cue. You can circumvent this by disabling Smart Tag in the Record / Update Options window (tap RECORD or UPDATE, then tap again to exit - selection will be stored). When Smart Tag is disabled, values coming from other active playbacks will not be recorded in, preventing slip-ups.

7 hours ago, Brian F said:

I vaguely recall however seeing seeing source options at the top of the update / record screen so I’m now also wondering if that can be used in a similar way to remove the incorrect playback as a source?

The source options at the top of the Update Options window are effectively a way of telling the console what things you want to update in a single operation. It can be added to via syntax, e.g. UPDATE (the cue I am currently in is automatically in the source options), AND 2 (adds cue 2 to the source options, to specify cues from other playbacks at the same time use Playback Number/Cue Number). This means the console will be updating both the cue I am currently in as well as cue 2 with the desired 'Remove' operation. You can tap various items in the source options area to exclude them or add them, indicated with red and blue stripes.

7 hours ago, Brian F said:

Thinking about it though I’m assuming the answer must be ‘no’ as once I’ve updated the main cue stack that becomes the source rather than the playback so I’d have to resort to removing the relevant fixtures.

Correct - the values would be stored inside the recorded cue within the main stack, therefore they need to be removed from the cue. To remove a fixture entirely from a cue, you can follow my listed steps in my earlier post but leaving out the un-tagging of Intensity. Go into the cue, simply home the fixture(s) to tag all parameters and then remove from the cue via Update.

I hope this helps - if you have any queries or require further explanation feel free to ask.

Archie

[Brian F]

Thanks, that’s useful.