Leaderboard

Same here, hazer and house lights are an absolute pain. I sometimes just have to give up with smart tag and use "SELECTED FIXTURES ONLY" if I need to change something whilst people are moving around the house for example. Would love an exclusion feature.

Hi @barefootcoder, I'm assuming you're working on a Jester 24/48, or a 12/24? Unfortunately, this isn't possible on those consoles due to the trigger functionality not being present. You'll simply have to press the GO button twice quickly. However, the answer is different if you are on a console that's on the ML side of things (Jester ML, ML24, ML48). If you are on a Jester ML console, you can do the following: 1. Go to the cue that you'd like to then program addition cues to snap down and fade down. 2. Bring the fixture you'd like to snap down to an intensity of 0. 3. Ensure 'Down' is 'Snap'. Then hit Program to store that cue, after selecting which memory to record to. 4. Now bring the other fixtures down to an intensity of 0. 5. Define a 'Down' fade time. 6. Use the 'Special' tab on the front panel to tap 'Trigger'. This will change it to 'Auto', which will be an instant follow-on from the previous cue. You can then hit program again. In Run mode, after hitting the GO button on the snap-down cue, the fade-all down cue will automatically follow. An example of this is what I've created below, where cue 1 is the state where all those fixtures are up, cue 2 is bringing a single fixture down in a snap, and cue 3 is an auto-follow of a fade of 2 seconds bringing everything else down: I hope this helps.

Wir freuen uns auf die ersten 2026 ZerOS Workshops für die Vari-Lite FLX S Lichtsteuerungen. 24. Februar 2026 bei Focon Showtechnic, 49504 Lotte/Wersen bei Osnabrück - Infos & Anmeldung 31. März 2026 bei cast C.ADOLPH & RST DISTRIBUTION GmbH, 58099 Hagen - Infos & Anmeldung

Hi @Alexandre, apologies for the late reply but I thought it was worth sharing this. Thank you for providing your show file. You're correct, the crash behaviour is related to Move on Dark being used in Playback 7. Upon further investigation of your show file, cue 3 in Playback 7 contains the 'Smooth' effect (E5 to be precise) applied to fixtures 2-9 and 49-54. After messing around with Move on Dark and only enabling specific attributes (position, effect, etc.), it appears that Move on Dark is looking forward in the cue stack (from cue 1 & 2) and is attempting to apply an intensity effect (Smooth) to fixtures that are at an intensity of 0 in that cue (essentially - those fixtures have no intensity values to modify by the effect / have had no intensity instructions as their intensities are not set in that cue and the previous ones - tracking is enabled). Note that 'Smooth' is an intensity based effect, which is likely the reason for the crash behaviour from what I can see. Instead of disabling Move on Dark generally for the whole playback, in ZerOS we have the option to disable certain parts of it, ensuring you don't lose out on any advantages of using Move on Dark e.g. with colour and position in sacrifice of effects to prevent crashing. To do this, you'll need to turn off the effect attribute for Move on Dark for the specific cue(s) that are causing you problems with Move on Dark so the console ignores any effects that may cause issues for that cue specifically. You could alternatively go the simple route - disabling effects in Move on Dark for the whole playback instead of just individual cues, but that will result in (for example) position based effects not being taken into account by Move on Dark, meaning effects such as 'Circle' won't be applied in dark - you will see them apply from 0 effect size to their defined effect size for that cue over the defined fade time as the fixture's intensity is brought up. You can, however, resolve this*. Disabling Move on Dark for effects only on specific cues: In the 'Settings' column in the cue stack, tap 'Add' on the cue you wish to disable effects with Move on Dark Tap 'Don't Move Effect' so it has a red indicator as opposed to a blue one (red is 'activated/selected', blue is not) Tap 'OK' Effects with Move on Dark has now been disabled for just that cue. When launching into this cue, effects will now be applied on the press of GO into that cue. You can do this for every cue that is causing a problem. Disabling Move on Dark for effects only on the entire playback: Hold the 'Setup' key on your console's front panel and tap your playback's flash button On the internal touchscreen (or monitor if using a FLX S48), tap 'Move on Dark' Tap 'Don't Move Effect' so it has a red indicator as opposed to a blue one *By enabling 'Don't Move Effect' for the whole playback in the playback's settings, inside each specific cue's settings referred in my first set of bulletpoints, that option will now have changed to 'Move Effect' (only for cues within that playback). This allows you to tell the console to look ahead in the cue stack and move the effect-based things for a specific cue anyway, ignoring the playback's general settings for Move on Dark that all effect movements are disabled. An example of this is shown in the image below in the far left column of options: I hope this helps, and I hope your FLX S continues to serve you well. Kind regards Archie

Same happens to me, but not for hazer, but for houselights. I would very much like that "exclusive playback" feature.

I have long been asking for Exclusive Playbacks for the very same reason. This is what Edward Smith sent me back in March 2023: Exclusive Playback" faders are currently assigned to ZerOS 8 on our roadmap. Please note that this could move if our priorities change. If a playback is configured as exclusive, this would prevent it from being recorded into cues, even if recording with SmartTag.

As far as I’m aware you can select the fixture and then edit with the on-console editor. https://www.zero88.com/manuals/zeros/patching/add-fixtures/edit-export