Edward Z88

You could also select the fixtures, and try the Candle effect (Effect 9). If this doesn't give what you're after, try Effect 4 (Chaser 1/8), but reduce the effect "Size" down using the encoders, and increase the "Speed". Hope this helps.

Hi @mxinkmusic We are indeed part of Vari-Lite. Not Philips though - Vari-Lite are owned by "Signify". See the link below... https://www.vari-lite.com/global/about/signify A preview of ZerOS 7.14 software was shown at ProLight + Sound trade show last week, and is currently being tested by our beta testers. Check out the link in @scottydog75's post for more information. Hope this helps.

Whenever you receive these Access Errors, please could you email me / forum-message me the reference number? Many thanks, and apologies for the inconvenience once again.

In ZerOS 7.14 software, Macros will capture "press and hold" messages of keys. This would allow you to record a macro of "press and hold VIEW and tap GO", for example. Hope this helps.

Hi @van den abbeele Eric There are no specific USB hub brands that we recommend. However, try to stick with USB hubs from a reputable brand, rather than "unbranded" devices.

Hi @Renato Thank you for emailing support@zero88.com regarding this. We have replied. Please let us know if you have any questions.

There are indeed a lot of messages when sending fader movements over OSC. However, this is very similar to how ZerOS processes "real" fader movements - each level change is reported as an individual message. This can be seen in Event Monitor.

If you are looking for a small "spare" console, with a maximum of 96 fixtures & 1024 DMX channels, I'd suggest looking at FLX S48... https://www.vari-lite.com/global/products/flx-s48 You will feel much more at home using this having come from FLX, compared to a legacy ZerOS console.

Hi @lacapella Thank you for attaching the debug files from your console. Sorry to see you encountered this error. The debug files are reporting very little information. Unfortunately there is not enough data to understand what may have occurred. Are you able to send us an email, with step-by-step instructions of what you did on the console when these errors occurred? For example, did these occur during patching, or upon pressing a particular button? We will then be able to troubleshoot further.

Hallo, Ich denke, die einfachste Lösung besteht darin, die Farbzeit Ihres Cues zu ändern. Halten Sie dazu VIEW gedrückt und drücken Sie die Taste unter dem Wiedergabe-Fader, den Sie aufgenommen haben. Dies öffnet die Wiedergabe im Cues-Fenster. Tippen Sie auf die Color-Fade-Zeit und stellen Sie diese mit den Encoder-Rädern auf 0 herunter. Wenn Sie nun die Wiedergabe erhöhen, werden die Fixtures sofort in ihrer aufgezeichneten Farbe sein. Bitte sehen Sie sich das Tutorial unten an, um weitere Informationen zu erhalten ... Hoffe das hilft. Hello, I think the easiest solution will be to change your cue's colour time. To do this, hold VIEW, and press the button below the playback fader you have recorded. This will open the playback in the Cues window. Tap on the colour fade time, and use the encoder wheels to dial this down to 0. Now, when you raise the playback, the fixtures will instantly be in their recorded colour. Please watch the tutorial below for more information... https://youtu.be/pbS4sX7VbKA Hope this helps.

Hi @showguy The issue shown in your video has been fixed internally, and the fix will be included in the next software update: ZerOS 7.14. This issue was logged as reference number ZOS-8363 on our system. To achieve this, I would recommend configuring the playback's button as a GO button, to prepare the fixtures, as per @Davidmk's suggestion: To do this, I would recommend recording a fresh playback, that contains just a single cue of your lighting state with intensity. Then, hold SETUP and tap the playback's button. From the bottom, change the button function from "Flash" to "Go". There are two Go options, to decide whether the playback's button goes to the cue using or ignoring the cue's fade times. If you also want flash functionality, you could configure "Go" as the button's shifted function. Once configured, leave the remaining settings as they are, and click OK. Now, before using the playback, tap its button, the fixtures will "prep", and you can then raise the intensity over the top using the fader. By default, lowering the playback will release its control over the fixtures, meaning there is no need to manually hold CLEAR and tap the playback's button. I hope this helps. Let us know if you have any questions.

Thanks for the information. I'll continue to investigate.

Software update instructions can be found here... https://www.zero88.com/manuals/zeros/setup/load/zeros-software

Hi @Lex If you hold SHIFT and tap RECORD, you can then tap an empty palette within any attribute (Colour, Beam, Shape, Position, Effect). This will then store a snapshot of all parameters of all fixtures into the palette. Tapping the palette will then apply the values to the selected fixtures. If there are fixtures patched with Intensity, Colour, Beam, Shape, and Position parameters, the palette will be annotated ICBSPE. If you only have fixtures with intensity and colour parameters patched for example, the snapshot palette will be annotated ICE. Please feel free to send us your show file if this doesn't seem to be working, and we can take a look.

When @Tim Meinecke posted this topic, we were encountering server issues. As a result, we were unable to post a reply. For the benefit of others, this is the reply I emailed to Tim in response...

Hi Mac, Thank you for the show file. This is a bit of a headscratcher. I am unable to replicate this issue with your show file. The following playbacks are set to Solo: 7 thru 16, 19 thru 24, 26, 32, 40, 42. All of these playbacks are soloing correctly, taking excluded fixtures to 0, when the playback's button is pressed. If you see this behaviour happening again, please take a video of what you are seeing. Then, power cycle the console. On reboot, does the issue still occur? If you have any questions, please let me know.

To answer the title of this thread - no, it certainly hasn’t. However, we are currently experiencing significant supply issues on components required for FLX and ZerOS Server hardware, resulting in exceptionally increased lead times. We’re working hard to reduce these lead times as soon as possible. Let us know if you have any questions.

Hi @SimonH ZerOS consoles do not support large-capacity drives in the exFAT format. Large-capacity drives (64GB+) in the NTFS format should be compatible with ZerOS. Drives in the exFAT format can be reformatted to NTFS. Hope this helps.

Hi @milon Based on your description of the issue, it sounds like your console may require its internal storage card to be re-flashed. Please email us a picture of your console’s serial number sticker to support@zero88.com, and we can email you instructions. Please let us know if you have any questions.

Hi @DRP To update a group, first ensure no cues are running, and the CLEAR button is off. Then, you can double tap the group to see it outputting, make your changes such as adding in a new light, and then ensure all the fixtures you wish to include in the group are selected. Then tap UPDATE, and tap the group. This is similar logic to updating a cue - output it first so you can see it, make your changes, and then update it. If you add a new light in to a group, this will not automatically add the new light into cues that were programmed using the group. Let us know if you have any questions.

Hi Mac, Which playback is configured as your “Solo” playback? Are there certain playbacks that are not being set to 0% when a playback is soloed, or do none of them go to 0%? To troubleshoot further, we’d need to see this show file, along with detailed instructions of which playbacks are set as solo, and which playbacks are not going to 0%. If you are using Art-Net, please ensure the “Light Converse Integration” option is disabled, unless you are controlling a Light Converse visualiser.

Hi @MaltingsTech Please send us a picture of your console’s serial number to support@zero88.com. We can then send you instructions on how to re-flash the console’s storage card, which should then allow the console to boot normally.

Hi @alg These error messages suggest that at some stage RigSync has been enabled on the console. The console has then seen your Betapacks, and stored information about them to the show file. The error messages all have the same code, which ends with ":0" through to ":6". This suggests that the console cannot see one of the Betapacks (error ending ":0"), and cannot see any of its channels (":1" thru ":6"). Please check whether RDM has been enabled on your console, from Setup -> Universes -> Remote Device Management. If you do not wish to use RigSync, ensure it is disabled.

Hi @Ian_p I have checked our MS Teams registration, and I can only see that you registered this afternoon for today's session - I cannot see a previous registration. You should have received an automated registration link shortly after registering. It may have gone to your junk/spam. Today's training session covered "Chases & Effects". This session is available on YouTube here... Hope this helps,

Hi @showguy Thanks for reporting this. Really sorry for the inconvenience caused. If you do continue to receive this, please email support@zero88.com to reach us.