Edward Z88

Hi @discover Please search for the apps on the Google Play store, and attempt to download them again. You should now be able to download and install them. Please let us know how you get on.

Hi Kevin, For now, we'll have to say no. The online manuals platform was created by an external web developer, so we would need a business case to reopen this. As mentioned when we initially created the platform, the "Next", "Previous", and "Up" buttons we first implemented were not working how we wanted, so we had to remove them. If we receive further requests for this, we will of course investigate.

Hi Dave, If you hold Z/SHIFT, and tap a playback’s button, this will “Solo” the playback (if the playback only contains a single cue). Does this achieve what you’re after?

Hi @Jouper There is not a key equivalent to the FLX Z key on Solution consoles. What would you like to achieve/what function would you like to access?

There is no way of setting a playback "minimum" level. The playback fader will take the intensity level of the current cue down to 0%.

Hi @Jouper If when you lower a playback fader, you want your fixtures to stay on @ 30%, you could program another playback with your fixtures recorded @ 30%. Then, you can raise this playback fader to full, and leave it. With this playback up, the lowest value that these fixtures can then be taken to by your cues is 30%. I hope this achieves what you're after.

Hi @emilie Welcome to the Zero 88 Forum. The LumenRadio CRMX Nova TX is a single universe wireless DMX transmitter, with no Ethernet functionality... https://lumenradio.com/products/crmx-nova-tx/ You can therefore plug the DMX output from the console into the CRMX Nova TX's DMX input, to transmit the universe wirelessly. If your device has an Ethernet port, please could you link to the product's webpage, so we know exactly which unit you have? What network protocol are you trying to use?

Haha that would have been a much more interesting way of doing it! I did it the boring way and looked in our brand guidelines 😆

After loading in a show file, tap Z/Shift -> System Information -> System Text. In here will be a line of text, that states the show file version the loaded show was saved in.

Done. Let me know your thoughts on the changes.

Hi @alg Can you confirm your FLX S48 is running up to date software? If there are no address conflicts, RigSync should leave start addresses as they are. As @kgallen mentions, you can remotely readdress your dimmer channels from the console using the Fixture Schedule, in exactly the same way you would readdress a “normal” fixture. Once you have addressed them how you need, the patch information will be stored in the show file on the FLX S, meaning that FLX S will remember “the address of channel 5 of dimmer 2 is x” for example.

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.