Edward Z88

Great question. This is a complex subject, so apologies if my explanations don't help! If you update a cue by simply changing values, you have to think about how the fixtures are going to get to those values, and how the fixtures are going to get from those values to the values in the next cue. However this is where SmartTag is your friend - if you set a fixture to 0 and update a cue, but the fixture was already at 0 in the previous cue, this operation essentially IS an Update > Remove. This is because SmartTag does not include an instruction for a light, if the light is already doing that thing in the previous cue. So if it was @ 0 already, there's no need to tell it to be @ 0 again. Intensity data is therefore removed - tick. SmartTag also strips out attribute data for the fixture if it is @ 0, hence this operation means all data is removed for the fixture in this cue. However, this then becomes a question of tracking. If you did this update as Cue Only, the next cue will now have data added in, to tell the fixtures to be in the same values, as if the previous cue had never been updated. So in this scenario, an UPDATE > SmartTag > Track Forwards would have been required. If you use UPDATE > Remove, your cue will have absolutely no instructions for the tagged parameters. The parameters can therefore continue doing what they were already doing, OR Move On Dark can grab that fixture in order to prepare it. This therefore could be a good option if the fixtures were on in the previous cue, and you want them to remain on in this cue with no change. So the choice as to whether to simply update the values stored in a cue, or remove them completely, really needs to be made on a case by case basis, thinking about how this could effect cue transitions. When programming quickly during plotting or even technical rehearsal, it may make sense to do a "quick and dirty" update, to just change the values rather than remove the values. Then, run through your cues prior to the dress. If there are any weird transitions, or Move On Dark isn't working as expected, you can then go into the troublesome cue, select fixtures > HOME > UPDATE > Track Forwards > Remove > ENTER if necessary to tidy things up. I hope this makes sense. Let me know if you have any questions.

Please find the fixture file attached for the BeamZ Ignite 740 in 45-channel mode... BeamZ Ignite 740 45Ch.zfix

That is correct. These changes are covered by the “ZerOS” manual which is available here… https://www.zero88.com/manuals When on this page, change the language drop-down at the top to “English”. You can then click and view the “ZerOS” manual. Hope this helps.

Solution consoles do have a CR2032 coin cell battery. However, when this was starting to go flat you should have received NVR errors upon booting the console, rather than the console just failing to boot. It would be worth checking the Compact Flash card in the console is seated correctly. At which point, you might as well replace the battery too whilst the console is open. Please let us know if you'd like instructions on opening the console.

Hi @UMB Thank you very much for the debug file from your console. Sorry to see you encountered this error. Your console is running ZerOS 7.9.2 software, which is several versions out of date. I would therefore recommend updating your console's software. ZerOS 7.14.3 is the latest software, and can be downloaded from the link below... https://www.vari-lite.com/global/products/zeros-software Please read through the release notes on this webpage from ZerOS 7.9.2 through to ZerOS 7.14.3, to ensure you're up to speed with the various improvements and new features. Please let us know if you have any questions.

On this occasion I think I’ll be lazy and leave it where it is. This conversation is useful for FLX S and FLX users alike.

Yes - when you press a GO button, you will go into that cue, and the cue's intensities will be inhibited by the playback fader's current level. So you will need to raise playback 1's fader to full, to achieve the intensity values you recorded. Hope this helps.

If an effect is running on a fixture, effect parameters will be shown on the encoder wheels upon selecting the fixture and tapping the Effect tab. That's correct, however this data cannot be viewed on the console.

Latest beats highest. If a playback is set to "latest" takes precedence, and the last thing you did was trigger that playback, that playback will output as programmed (it won't take control of parameters that it doesn't have programmed data for). So in your example, fixture 1 is @ 20% right now. Hope this helps.

Hi @Holger There's no clear way of seeing this on FLX S consoles. You would need to select a fixture (or group of fixtures), and then tap the Effects tab at the top. This would then give you the effect palette reference on the encoder wheels.

Thanks Kevin - your reply is really clear, so not much more I can add really. Your time is much appreciated on this. This is a fair comment - customers will occasionally say they have a "FLX", when they mean "FLX S24", so we just have to be mindful to not then tell them how to do something via syntax strings!

Hi @Zulu Really sorry to hear you have encountered this. If you see the LEDs below the faders flashing, this means the front panel has lost connection to the processor. This could suggest the console has encountered a power issue. If you have USB devices connected, try unplugging these, and see if this behaviour continues. If this seems to solve the issue, this could suggest one of the USB devices was causing the issue. Please ensure you are also using a genuine FLX S PSU. Please send us an email to support@zero88.com, and we can continue to troubleshoot this.

Kevin - thanks very much for letting us know. It seems no matter how clear you try to make something, people will still get the wrong end of the stick! If there is a particular thread you have found that you think it would be helpful for me to jump in, please let me know. Otherwise, I'll just keep a watchful eye out. Thanks again.

I'm very well thank you. Thank you for the show file. This show file was saved in ZerOS 7.13, so the version jump is not of particular note. Very strange. Not sure what's causing this behaviour on your system. I am unable to replicate the issue with your show file. It may be easiest to troubleshoot further over the phone/MS Teams. Please send us an email to support@zero88.com, and we can then arrange a time to investigate further.

Hi @O Thompson Hope you're well. Based on your description of the odd behaviour, it sounds like there are two consoles active, both trying to control the same lights, resulting in a data conflict. Thank you for attaching your show file. I have checked the DMX output from your show file, and can confirm that in ZerOS 7.14.3, DMX channels 1 thru 6 are constantly outputting at full as expected. I noticed in your show file that DMX, sACN, Art-Net, and CITP are all enabled. Are you using all four protocols simultaneously? If you are only using sACN for example, please ensure Art-Net and CITP are disabled. Would you happen to know which version you were previously running? If you have a show file that was saved on your console prior to the update, please send this to me, as this will include information on the software version it was saved in. Please let me know if you have any questions. Edward