Edward Z88

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.

Hi Mil, Correct - based on your original description I wasn't sure whether you were looking to sync to an audio track or live music. It is not possible to trigger a Global Tap Tempo playback over OSC. It is possible to send a Playback Go x message, where x is the playback you wish to trigger. Each time this command is sent you would step through each cue on playback x. If you sent these commands to a chase that was running, you would end up with a mixture of the chase automatically running using Tap Tempo, and jumping cues when OSC GO messages are received. I hope this makes sense.

These are the exact steps I'm following: Load show file Raise playback 13 ENTER ENTER (to select fixtures and see parameter table in the Output Window) The fixtures are in colour palette 12 (Blue) by default Raise playback 7 - the fixtures go Warm White as programmed Press playback 7's button - the fixtures go Red as programmed Apply colour palette 6 - the fixtures go Yellow as programmed Release playback 7, by either lowering its fader or hold CLEAR and tap playback 7's button - the fixtures remain in yellow, as colour palette 6 last changed the fixture's colour (LTP) If I DON'T apply colour palette 6 in step 6 above, the fixtures DO go back to default as expected upon lowering playback 7 in step 7. This is because if a playback has control of fixtures, and that playback is released, the fixtures then go back to the values of the playback that previously had control of the fixtures. If no playbacks that have values for the fixtures are currently active, the fixtures go back to their defaults. It is possible to prevent a playback from releasing when lowered, meaning it will remain in control of the fixtures until something else on the console takes control of the fixtures. To configure this, hold SETUP and tap the playback's button to open the playback's settings. Choose Raise & Lower from the top, set Release On Lower to disabled, and click OK. Hope this helps.

Hi Mil, FLX S consoles do not have Sound-to-Light functionality, so there is no way of automating a chase to follow the beat of an audio track. When a chase is programmed on a playback, the playback's button automatically becomes a Tap Tempo, allowing you tap the playback's button to synchronise the chase to a beat. You could program a sequence of cues on a playback. Theoretically, you could then send repeated OSC GO messages to trigger the cues on this particular playback one after the other, essentially resulting in the cue stack on the playback behaving as a chase. To do this you would need to come up with a way of a software package taking an audio track, and then repeatedly sending a particular OSC message on each beat. Alternatively, you could use more of a "timecoded" approach, where you start an audio track in a software package, and automatically at certain points in the track the software package sends OSC messages to FLX S, which then trigger certain cues at different points in the song. Hope this helps,

Salut @jeansted Bienvenue sur le forum Zéro 88. Pour voir les cues sur le Master Playback dans la fenêtre Cues, maintenez enfoncée la touche VIEW et appuyez sur le bouton GO du Master Playback. J'espère que ça aide. Hi@jeansted _ Welcome to the Zero 88 Forum. To view the cues on the Master Playback in the Cues window, press and hold the VIEW key and tap the Master Playback's GO button. I hope this helps.

Hi Mac, The core functionality and workflow of Solution XL consoles is similar to FLX, as they both run ZerOS. In many ways Solution consoles are more similar to FLX S than FLX - there is no syntax numpad, and you are limited on the number of fixtures you can patch. There are a handful of features introduced in recent versions of ZerOS, that have not come across to Solution consoles, due to Solution consoles featuring older processors. Solution consoles were discontinued in 2021, and so the warranty of the very last Solution consoles will be running out in early 2024. If you have any questions, please let us know.

Hi @PJRichards Intensity values in the programmer have the highest priority on the console. The CLEAR key is required to remove high-priority intensity programmer values, to allow cues to playback as programmed. All other attributes (Colour, Beam, Shape, Position) mix LTP, irrespective of whether they are being controlled manually or by a cue. You shouldn't be seeing this behaviour. If you have fixtures in red on a playback, you select them and tap your blue palette, lower the playback fader so it releases - the fixtures should stay blue, because nothing has told the fixtures to change colour. Therefore it sounds like there could be a setting in your show file that is affecting this behaviour. Please feel free to attach your show file, and detail which fixtures, playbacks and palettes you are using. We can then investigate further. Please let us know if you have any questions.

FLX S consoles can be locked to prevent programming from being edited and prevent settings from being changed. Whilst locked, cues can continue to be played back. @Davidmk has helpfully linked to the relevant section of the manual that provides more detail. If you have any questions, please let us know.

Hi @Jakob Thank you for the feedback. If you would like to see OSC Output functionality added to ZerOS, please vote for "Trigger Outputs" here... This poll allows people to vote for features they'd like to see in ZerOS. Please let us know if you have any questions.

Hi @Malvern I have just replied to your support email regarding this.

The ZerOS Online Manual PDF can be found here... https://www.zero88.com/storage/downloads/manuals/zeros-en.pdf?230718

Hi @discover FLX S consoles do not have an internal battery, which means there's no way of keeping time. FLX consoles do have an internal battery. FLX S consoles have a different processor to FLX consoles. Hope this helps.

To be clear, FLX S consoles do not have an internal date/time clock. Therefore files saved from FLX S will appear to have erroneous dates/times when viewed in Windows File Explorer for example. If you would like to keep track of when your show file was saved, you can of course add the current date/time to the end of the file name.

MIDI Timecode is ideal for triggering the console in applications like this... https://www.zero88.com/manuals/zeros/setup/triggers/midi-timecode Any USB to MIDI interface that is compatible with Windows and supports MIDI Timecode can be used. Show Cue Systems is a Windows software package that can trigger audio tracks and MIDI Timecode. However, I don't personally have any experience of using this.

Hi @LIGHTING I believe you have been emailing Keith regarding this. Let us know if there's anything else we can help with.

Excellent - really pleased to hear it. Let us know if there's anything else we can help with.

Ciao, 1) Per controllare il Prolights V575Spot, consiglierei di patchare un "Acme iMove 575 Spot", che è incluso nell'ultimo software ZerOS. Questo dispositivo condivide la stessa mappa DMX del Prolights V575Spot. Il Prolights V575Spot non ha un parametro "Dimmer Mode". Per controllare il parametro "Shutter Strobe, Shake", selezionare il dispositivo e toccare la scheda Beam. Quindi tocca il pulsante encoder del parametro "Shutter Strobe, Shake" per aprire le opzioni del parametro. 2) Per accedere al parametro Zoom del Prolights ArcLED 7361 Zoom in modalità TOUR, selezionare il proiettore, quindi toccare due volte la scheda Beam nella parte superiore del touchscreen. Questo sposterà i parametri Beam sulle ruote dell'encoder, per consentirti di accedere a Zoom. Spero che aiuti. Fateci sapere se avete domande. Hello, 1) To control the Prolights V575Spot, I would recommend patching an "Acme iMove 575 Spot", which is included in the latest ZerOS software. This fixture shares the same DMX map as the Prolights V575Spot. The Prolights V575Spot does not have a "Dimmer Mode" parameter. To control the "Shutter Strobe, Shake" parameter, select the fixture, and tap the Beam tab. Then tap the "Shutter Strobe, Shake" parameter's encoder button, to open the parameter's options. 2) To access the Zoom parameter of the Prolights ArcLED 7361 Zoom in TOUR mode, select the fixture, and then tap the Beam tab at the top of the touchscreen twice. This will page through the Beam parameters on the encoder wheels, to allow you to access Zoom. I hope this helps. Please let us know if you have any questions.

Click the link below for information on the Output Window, including the "Source" button, and the colour coding... https://www.zero88.com/manuals/zeros/desktops-windows/output-window

The purpose of Fader Controls, for all attributes including Effects, is that you can raise a playback fader, to transition fixtures from their current values to the recorded values. If Fader Controls Effect didn’t control both Speed and Size, the fader couldn’t be used as a subtle crossfader - you’d either see the Size or Speed snap in upon raising the fader. Dedicated Speed and Size masters are a separate feature, that are on the todo list. This is covered under the “Improve Effects” item in the poll. As mentioned previously, Speed Override faders can currently be used as Speed Masters.

As @Davidmk mentions, record the parameter you want at its desired maximum level to a playback. Then in the playback’s settings, enable Fader Controls for the attribute that is included in the playback. For example, if Gobo is recorded, enable the Shape attribute under Fader Controls. The playback fader can then be used as a variable crossfader between the recorded fixture’s current values, up to the maximum value you recorded. Let us know if you have any questions.

Great, thanks for confirming.

There are currently no plans to support OSC output in the next version of ZerOS. MIDI Out is on the poll above, but has a fairly low number of votes, so sending trigger commands from the console is currently fairly low-down the priority list.