Edward Z88

That would be great - thank you. Thanks for confirming.

Hi @ADCtech1855 Welcome to the Zero 88 Forum. Good to hear you have a FLX S48. Sorry to hear this. When you save a show file, ZerOS will include the unique RDM IDs of all of the RDM fixtures in the show file. Upon loading the show file, ZerOS will then compare the RDM IDs in the show file with the RDM IDs of currently connected fixtures. If there is a match, they will "link", meaning the show file will work with the fixture that's already discovered and patched. Duplicate fixtures therefore won't be added. If the RDM fixtures currently patched in the console have different RDM IDs to those already patched, the fixtures from the show file will be added. The behaviour you are seeing therefore suggests ZerOS is seeing different RDM IDs compared to when the show file was originally saved, which is unusual. Would you be able to email us a couple of show files to investigate? If so, please email us the original show file you wish to load. Please then load this show file, and then save a new show file which includes the fixtures that have been duplicated rather than linked. We will then be able to compare the RDM fixtures in the two show files. To avoid this issue, I would recommend unplugging the DMX line from the console, and then load in your show file. Then disable RigSync on the console, and then reconnect the DMX line. The console will then simply output DMX on the currently patched addresses. You can then save an updated version of the show file, this time with RigSync disabled. To confirm, was this working correctly in ZerOS 7.13 software, until that second ColorSource PAR was added? If you have any questions, please let us know.

Hi @Flabbe Merci @van den abbeele Eric pour les informations détaillées. Il existe de nombreuses différences entre FLX S48 et FLX. Les différences fondamentales sont détaillées ici... https://www.zero88.com/storage/downloads/e5be187a-86b8-4b00-8820-2536532c4d35/desk_comparison_chart_UK_0721.pdf Les consoles FLX incluent également davantage d'outils de mélange de couleurs et le moteur d'effets "Waveforms". Les consoles FLX S sont simplement limitées aux « effets automatiques ». Les consoles FLX disposent d'un puissant module de processeur Q7 ARM, ce qui signifie qu'elles peuvent recevoir des mises à jour logicielles pour les années à venir. J'espère que ça aide. S'il vous plaît laissez-nous savoir si vous avez des questions. Thank you @van den abbeele Eric for the detailed information. There are many differences between FLX S48 and FLX. The fundamental differences are detailed here... https://www.zero88.com/storage/downloads/e5be187a-86b8-4b00-8820-2536532c4d35/desk_comparison_chart_UK_0721.pdf FLX consoles also include more colour mixing tools, and the "Waveforms" effects engine. FLX S consoles are simply limited to "Automatic Effects". FLX consoles feature a powerful Q7 ARM processor module, meaning it can receive software updates for years to come. I hope this helps. Please let us know if you have any questions.

Hi @Ian_p As per @Davidmk's post, this sounds like a classic case of LED dimmer curves vs halogen dimmer curves. When LED fixtures are at 10-20% intensity, they can often be pretty bright, depending on the make/model. When halogen lamps are plugged into a dimmer set to 10-20% intensity, you often can only see the slightest glow. Many LED fixtures have a setting on them, allowing you to change the dimmer curve to respond more like generic dimmers. Some fixtures allow you to change this setting remotely from the console. If you cannot change the dimmer curve of the LED fixtures, you may need to program two separate cues in the console - one to bring on the dimmers, and the second to bring on the LEDs. The second cue could then be configured to run simultaneously with the previous cue, using an "Auto With" trigger. You may then wish to delay the Up time on the LED cue, or tweak its fade time, so that the LEDs and dimmers fade on together. Hope this helps.

This procedure is described here... https://www.zero88.com/manuals/zeros/patching/fixture-schedule/deleting-fixtures

Hi @beyond the blue You wouldn't be able to preview this transition prior to recording the cue. I would recommend recording the cue, and then as per @Davidmk's suggestion, you could use Speed Override to "fast forward" the transition, and then pause it. The fade progress bars are displayed at the bottom of the Cues window. If you then needed to tweak the cue you've just recorded, allow the cue transition to complete, and then edit and update it. As well as using the Speed Override encoder, you can configure a Speed Override playback fader. Please see the link below... https://www.zero88.com/manuals/zeros/cues-playbacks/special-playback-functions Hope this helps.

No problem at all- pleased to hear it.

If the fixture is already in blue in the cue with the 12 minute fade, you’ll just just need to set the colour fade time of that cue to 12 minutes too. To set the colour time, tap the cue’s colour column, and then tap the first encoder wheel’s button. You can then type 12.00.00 into the numpad to achieve that.

Hi @beyond the blue To do this, tap on the cue that has the 12 minute fade time in the Cues window, so that it goes yellow. Then hold Z/SHIFT and press the GO button, to snap into the cue. You should then see the fixtures in their recorded values that they get to when the fade time has completed. You can then select the light you need, and change its colour. Then tap UPDATE, and tap the playback's GO button. Now, go into the previous cue, and press the GO button to run the cue. If the colour fade time needs tweaking, tap on the value in the cue's Colour column, and then tap the first encoder wheel's button, to open a number pad. You can then type in a colour fade time for the cue, and click OK. I hope this helps.

Hi @Zebroid66 Thank you for the information. This is an issue we are aware of on Solution consoles, caused by opening the "Panel" desktop. This issue will be fixed in the next ZerOS software update. Please let us know if you have any questions.

Hi @Zebroid66 Thank you for the update. Out of interest, what transmitter are you using? How have you solved the issue?

Hi @Zebroid66 Would you be able to attach a copy of your console’s show file, and confirm which type of fixture and how many of them you are attempting to patch?

Hi @Kauz No problem at all. No - this functionality is not possible. When in Manual Fade mode, the GO button is disabled, and the fader movement is the only way of activating the next cue. Have you experimented with the Speed Override control? This allows you to use the GO button to trigger cues, and a secondary fader to speed up or slow down the fade transitions. This also means you can lower the intensity output of the Master Playback using the Master Playback's fader, which is not possible when set to Manual Fade mode. Please click the link below for more information... https://www.zero88.com/manuals/zeros/cues-playbacks/special-playback-functions Let us know if you have any questions.

Hi @Kauz It sounds like you may not be running the latest software on your FLX. The two issues below have been fixed in ZerOS 7.14: The ability to change the playback Fader Function from "Manual Fade" back to "HTP Master" has been implemented, reference number ZOS-8363. ZOS-5803 has also been implemented. Both of these reference numbers can be found alongside the various other changes and improvements in the ZerOS 7.14 release notes... https://vari-lite.s3.eu-west-1.amazonaws.com/graphics/technical/documents/ZerOS-7.14-release-notes.pdf I hope this helps.

Done - https://www.zero88.com/manuals/zeros/controlling-fixtures/tagging

Thanks, Kevin You can clear a single fixture from the programmer, meaning it won't get recorded in cues when SmartTag is disabled. To do this, hold SETUP and tap an empty UDK. From the Normal dropdown, choose Clear Fixture, and click OK. Now, you can select fixtures, and tap the Clear Fixture UDK, and those fixtures will be completely removed from the programmer. I cannot think of a reason why you would want to leave a whole fixture in the programmer but untagged. If you wanted to do this, you would have to hold CLEAR, and tap each attribute key, and then tap the Intensity wheel's encoder button to untag intensity too. Personally if I had fixtures in the programmer, but only wanted some of them to get recorded, I would select the fixtures first, and then tap RECORD > Selected Fixtures. Hope this helps.

Hi @Amy Worrall As usual, @kgallen & @Davidmk have done an excellent job of responding to your points. Do let us know if you have any outstanding questions. Just to add a couple of extra comments on the points below... You are correct - you will definitely want to work with SmartTag disabled, coming from Eos. With SmartTag disabled, you are forced to build the next cue from the last cue, which is a workflow you'll be more familiar with. Personally I always program cue stacks with SmartTag disabled. Yep - all ZerOS palettes would be "by-type". Please see the link below for more information... https://www.zero88.com/manuals/zeros/palettes/advanced-palettes You'll see you'd be hard-pushed to do this by accident! On FLX, there isn't TIME syntax. Therefore, you will need to edit individual attribute timings for each cue. Note - if you tap on a fade time cell, you can hold SHIFT and tap the Up/Down arrow keys to increment/decrement by a second, which will speed things up, saving you having to type into each cell. FLX does not feature fixture-copy. You therefore cannot say "Fixture 15 copy to fixture 18". If fixture 15 and fixture 18 are the same type, you could do this via a palette. Please see the link below... https://www.zero88.com/manuals/zeros/palettes/advanced-palettes If you have a USB keyboard connected, you can use @ CUE syntax. 2 @ 0/10 ENTER would set fixture 2 to the values it is at in cue 10 of the Master Playback. I hope this helps. If you have any questions, please let us know.

Hi @Jakob Klucke Welcome to the Zero 88 Forum. To do this, you could record an Inhibit playback, to create a custom intensity master fader: First, set all of the fixtures that you would like to be controlled by your custom master fader to full. Then tap RECORD, and tap an empty playback's button. Hold SETUP, and tap the button of the playback you just recorded, to open the Playback's Settings. Under "Intensity Mixing" choose Inhibit, and click OK. Now, this playback fader will act as an intensity master control, just for the fixtures recorded to it. Please see the link below for more information on Inhibit... https://www.zero88.com/manuals/zeros/cues-playbacks/playback-settings/general#intensitymixing Let us know if you have any questions.

Hi @DALX ZerOS will not map the DMX Input universe to a DMX output and merge the console output. DMX Input is not designed to provide full remote control of fixtures patched in the console. DMX Input can be used to control individual fixture intensities, or playback levels. Please see the links below for more information... https://www.zero88.com/manuals/zeros/patching/fixture-schedule/dmx-in https://www.zero88.com/manuals/zeros/setup/triggers/dmx-in-2 There are currently no plans for this functionality. What would be the real-world scenario where this could be useful? Let me know if you have any questions.

Hi @Harold Welcome to the Zero 88 Forum. No. ZerOS 7.14 includes a significant change to how colour mixing is processed internally, which means show files saved in ZerOS 7.14 cannot be loaded into earlier versions of ZerOS. Where possible, we aim to make show files saved in the latest version compatible with the previous version, however in this instance it is not possible. We never guarantee that show files can be loaded into earlier versions of ZerOS. We do always guarantee show files from earlier software can be loaded into the latest version. The console's software will need to be updated. Software updates only take a couple of minutes to do and are straightforward. Once updated, you will be able to load in your show file without issue. If you have any questions, please let us know.

Makes sense 👍 OK great. If you would like to send over your show file first I would be happy to investigate. There's nothing obvious that comes to mind, so a show file would be helpful.

Hi @SCE If you would like ONLY the rainbow effect to be recorded, without intensity, you will need to ensure that SmartTag is disabled in the Record Options window. When SmartTag is enabled, the console will only record fixtures that are on. If you can share your show file, I would be happy to take a look to see what may be preventing the effect from outputting. If you do share your show file, please detail the fixture numbers you are using, the effect you are applying, and the playback you are attempting to record to. I will then be able to investigate. As a side note, the latest software for Solution consoles is ZerOS 7.14. If you would like to update your console's software, please let me know, and I can share installation instructions.

Bonjour, Heureux d'apprendre que vous êtes en mesure d'utiliser la console comme prévu. FLX n'enregistrera JAMAIS automatiquement un cue en appuyant sur RECORD. Vous devez définir où vous voulez stocker l'état après avoir appuyé sur RECORD. Si la mémoire enregistrait automatiquement sur la lecture 1, cela suggère que le bouton de la lecture 1 était enfoncé ou que quelque chose appuyait sur les touches d'un clavier externe. Hello, Pleased to hear you are able to use the console as expected. FLX will NEVER automatically record a cue upon pressing RECORD. You must define where you want to store the state to after pressing RECORD. If the cue was automatically recording to Playback 1, this suggests either playback 1's button was stuck down, or something was pressing down keys on an external keyboard.

The "White Strobe" playback would need both intensity information and colour information stored, to ensure that whatever the fixtures were doing, you would achieve an intensity strobe in white when played back. Therefore, if the colour of the fixtures is currently in the programmer, this playback would take that data out of the programmer when it is triggered. So, you would either need to store your look to a palette (SHIFT-RECORD to include everything in a single palette), and apply this after using the strobe playback, or as you say, you would need to record the current state onto a fader, trigger it, and that way upon releasing your white strobe playback, the fixtures will go back to the state in the active playback. Hope this helps.

If you trigger playback 7 again, this then becomes the latest instruction for the fixtures, and so playback 7 takes control over the fixtures. If these fixtures were the only things in the programmer, and playback 7 has taken control of them, the programmer is emptied - you'll notice that the LED in the CLEAR button turns off, because playback 7 has taken control, and so there is nothing left in the programmer. Therefore, lowering the playback fader, results in the fixtures going back to default. This is where you could disable release on lower to prevent the fixtures going back to default.