Edward Z88

There are currently no plans to implement a dedicated way of triggering the console's Global Tap Tempo remotely via OSC. What you could do, is record your different lighting states into a playback. Then, rather than converting the playback into a Chase, leave it as a Cue Stack. Then, you could send the console a Playback x GO message over OSC each time there's a "beat", to advance through the lighting states on the playback in time with a beat. Please let us know if you have any questions.

Hi Tobi, Apologies - I must have missed your original forum post. Glad to hear you have found that to page through the colour controls on the encoder wheels, you tap the "Colour" tab again. Please see this article for more information... https://www.zero88.com/manuals/zeros/controlling-fixtures/parameters Please let us know if you have any questions.

In ZerOS there is no information that logs the system time of the last boot up. Would you be able to explain why this information might be useful in your situation?

The "Connected Load" parameter of the "Non Dim" fixtures can be set to any level between 0 and 255. It will default at either 0 or 255, depending on the "Non Dim" variant you patch. The "Video" fixture was an old "Generic" fixture from our legacy fixture library. This fixture is no longer included in the latest ZerOS Library. This fixture defaulted at a value of 127. This is problematic for controlling relays, as for some relays this is "on", but for others this value would be "off". The "Connected Load" parameter of the "Non Dim" fixtures will not be affected by intensity masters such as the Grand Master, but can be recorded into cues. Yep - no problem. The main reason I mentioned this, is on occasions I have encountered people making custom dimmers/relays featuring domestic 13A sockets, where the cleaner has then come along and plugged the hoover into what they think is a spare 13A socket. Theoretically if this was to happen with your box, this could damage the relay channel, and in an extreme case, dependent on the failure of the relay, could cause a fire. Of course, the likelihood of this happening depends on how accessible your relay panel is!

When you save a show file, this will be saved with a timestamp of the console's date/time, and will also include the console's current software version information. Is this the information you are after?

Hi @Simonkbike I would recommend patching the relay channels as "Non-Dim" fixtures, which can be found under the "Generic" manufacturer in Add Fixtures. The nice thing about this, is there are two variants of this fixture - Default On and Default Off. For example, if you want the relay channel to be powered as soon as the console is active, you could patch a Default On. This would still provide the ability to then switch it off if required. I would recommend patching the Non Dim fixtures to the Solution's MFKs, which are numbered as fixtures 101 thru 300. Once patched, you can then select the Non Dim fixtures on the MFKs, and under BEAM, you'll see the ability to switch the "Connected Load" using an encoder wheel. In the picture I can't see any fuses between each relay output and its respective socket. If you are plugging in devices with a 3-amp fuse in the plug this is fine, but it would be best practice to ensure there is protection, in the event of a load with a 13-amp fuse being plugged into a socket.

Par défaut, les émetteurs UV SONT utilisés par les outils de mélange de couleurs ZerOS, ce qui signifie qu'ils seront contrôlés par les palettes automatiques, le sélecteur de couleurs, les tableaux d'ambiance, etc. En effet, dans de nombreux luminaires LED, les émetteurs UV ne sont en réalité que du violet, et donc il est logique de les traiter comme un émetteur visible. Cependant, dans le "Fixture Schedule", des paramètres seront disponibles pour vous permettre d'empêcher le paramètre UV d'un projecteur d'être contrôlé par le mélange de couleurs ZerOS. https://www.zero88.com/manuals/zeros/patching/fixture-schedule/fixture-settings#uv J'espère que cela t'aides. By default, UV emitters ARE utilised by the ZerOS colour mixing tools, meaning they will be controlled by Automatic Palettes, Colour Picker, Mood Boards, etc. This is because in many LED fixtures, UV emitters are in reality just Violet, and so it makes sense to treat them as a visibile emitter. However, in the "Fixture Schedule", settings will be available to allow you to prevent a fixture's UV parameter from being controlled by the ZerOS colour mixing. https://www.zero88.com/manuals/zeros/patching/fixture-schedule/fixture-settings#uv Hope this helps.

As @iank99 says, this error is nothing to worry about. FLX uses FeRAM technology, as opposed to the more traditional RAM in the x86-based consoles (Solutions & Orbs). You may therefore get different test results depending on the hardware you're using. Ultimately, this test is designed for internal use, and only during very niche troubleshooting.

Amazing! Thanks very much for the feedback.

You would need to re-patch the fixture manually, to be able to access the "Add As Additional" and "Unpatch" buttons. The "RDM" version of the fixture stays patched so that it can be used again if RigSync is re-enabled.

Setup > Fixture Schedule > tap on a fixture's DMX address to open "Edit DMX Address". If the "DMX Universe", "Unpatch", and "Add As Additional" buttons are hidden, this indicates that the selected fixture is an RDM device that has been discovered by RigSync. It is not possible to unpatch a fixture discovered by RigSync, or give it multiple start addresses. Sorry to hear that RigSync changed the settings of RDM fixtures when you didn't want it to. If you go to Setup > Universes > Remote Device Management, there is a "Revert Rig Back" button, which will tell the fixtures to go back to the settings they had when the console found them. This is something we are actively discussing internally. I have made a note of your request for this. This is logged as reference number ZOS-11927 on our system. Very sorry to hear RigSync caused various headaches and struggles for you. Please do let us know if there's anything we can help with.

Bonjour, Oui - par défaut, lorsque vous enregistrez un fichier de show sur une clé USB depuis Configuration > Enregistrer, tous les paramètres, patchs et programmations seront inclus. Hello, Yes - by default when you save a show file to a USB drive from Setup > Save, all settings, patching, and programming will be included.

Yep - exactly right. RDM can be enabled/disabled on the Gateway 4 for each of its ports... https://www.zero88.com/manuals/gateway4/configuration-2/g4web-server

Si une mémoire contient uniquement des informations sur la couleur, où seules les valeurs de couleur changent lors de l'entrée dans la mémoire, vous ne verrez qu'un temps de fondu affiché pour la couleur. Vous ne verrez les temps de fondu affichés pour « Up » et « Down » que si le signal inclut des changements dans les valeurs d'intensité. If a cue just contains colour information, where only colour values change when going into the cue, you will only see a fade time shown for colour. You will only see fade times shown for "Up" and "Down" if the cue includes changes in intensity values.

Bonjour, Les notes de version pour chaque version du logiciel ZerOS sont disponibles sur la page Web de ZerOS... https://www.vari-lite.com/global/products/zeros-software Ceux-ci couvrent les fonctionnalités et les modifications introduites par chaque version. J'espère que cela t'aides. Hello, Release notes for each ZerOS software release are available on the ZerOS webpage... https://www.vari-lite.com/global/products/zeros-software These cover the features and changes introduced by each version. Hope this helps.

When creating a fixture in the ZerOS Fixture Editor, if a Virtual Intensity parameter is required, ZerOS will automatically create one to scale LED emitters.

If you clicked "Source" in the Output window, and the fixture's source showed as "PRESET" in yellow text, this confirms that the channel faders are in HTP mode, and the respective channel fader is at a higher intensity percentage than any cues that are controlling that fixture. If the channel fader wasn't actually raised, this could indicate you've got some temperamental faders on the console. If this is the case, please let me know, and I can share information on how to clean the faders. When in HTP mode, the channel faders will only take affect if they are raised higher than the fixture's current intensity value. If any intensity percentages are shown in red in the Output window, these have the highest priority on the console, and will override any HTP channel fader values. This is not correct. The Preset Control button is used when the console is in "Wide" mode, to temporarily "freeze" output, to allow you to then use the preset faders to set up the next scene. You can then crossfade from the active "frozen" scene, to the scene you've just created on the preset faders, using the A/B masters. Once you've crossfaded, you can then use the Preset Control button to "freeze" the state again, allowing you to then set up the next scene, and so on. The A Master and B Master have no bearing on the levels of playbacks. If the POSITION key in flashing, this indicates that the encoders are still controlling Position parameters, whilst the MFKs are providing other options. Yes - if you press the RECORD key, you should see the Record Options open on the external monitor. In here, you should see a "SmartTag" button. By default, SmartTag is enabled, indicated with a red stripe. This means the console will store all the required values, to achieve the active lighting state on stage. This means the console will store a mix of channel faders and playbacks in cues. If you tap the SmartTag button in the Record Options, it will go blue, meaning disabled. Now, only manually adjusted fixtures will get recorded into cues, and active playbacks will not be included. If you cannot see a SmartTag button in the Record Options, this essentially means the console is in "basic" mode, and so this functionality is unavailable. Please click the link below for more information... https://www.zero88.com/manuals/zeros/cues-playbacks/record-options When the Output window is in "Source" mode, it will provide a code, for example 1/2. This tells you that the light is being controlled by playback 1, cue number 2. Please see the link below for more information... https://www.zero88.com/manuals/zeros/desktops-windows/output-window

ZerOS (and therefore Phantom ZerOS on PC) has the ability to search for fixtures that feature the same DMX map as the light you are trying to control. This then tells you the alternative fixtures you could patch to control the fixture, one of which may already be in the Jester's library. Please see the links below for more information... https://www.zero88.com/manuals/zeros/phantom-zeros https://www.zero88.com/manuals/zeros/patching/add-fixtures/searching-filtering

Bonjour, Veuillez nous envoyer une copie de votre fichier d'émission à support@zero88.com. Veuillez confirmer les lectures que vous souhaitez et les appareils que vous souhaitez qu'ils contrôlent. Nous pourrons alors y jeter un oeil, et si besoin créer des playbacks pour vous. Hello, Please email us a copy of your show file to support@zero88.com. Please confirm what playbacks you would like, and confirm the fixtures you would like them to control. We can then take a look, and if necessary create some playbacks for you.

Glad to hear the Jester is up to date with JesterOS 4.1 software. This setting lives in Setup > DMX Input Setup. You will not need to configure the DMX Input in order to simply output DMX.

D'après votre description, je pense que vous aimeriez que les couleurs se mélangent toujours de manière additive. Si vous souhaitez contrôler les couleurs de manière additive, au lieu d'utiliser les outils de mélange de couleurs tels que les palettes, le sélecteur de couleurs et les Mood Boards, il serait probablement préférable de faire fonctionner vos appareils dans leur mode le plus simple, puis de patcher des gradateurs individuels pour contrôler les LED individuelles. des luminaires. Cela signifie que la console mélangera nativement les émetteurs en utilisant « la priorité la plus élevée », car elle traitera chaque canal de couleur comme une intensité pour cette couleur particulière. Based on your description, I believe you would like colour to always mix additively. If you wish to control colour additively, instead of using the colour mixing tools such as palettes, colour picker, and Mood Boards, you would probably be best to operate your fixtures in their simplest mode, and then patch individual dimmers to control the individual LEDs of the fixtures. This means the console will natively mix the emitters using "Highest Takes Precedence", as it will treat each colour channel as an intensity for that particular colour.

Veuillez nous envoyer une copie de votre fichier d'émission à support@zero88.com et fournir des instructions étape par étape sur les lectures que vous essayez d'enregistrer. Nous pourrons alors y jeter un œil. Please email us a copy of your show file to support@zero88.com, and provide step-by-step instructions on the playbacks you are trying to record. We can then take a look.

Hi @jmd I would recommend watching the tutorial below if you haven't already... This is available here... https://www.zero88.com/storage/downloads/2f885eff-adc0-4525-8859-1803970c6fb5/ZerOS-Français-7.9.9-V-3.51a.pdf

Gateway 4 will only consume 2W. So roughly 222mA @ 9v, 42mA @ 48v.

Hi @showguy To control the intensities of individual fixtures with the ZerOS Remote app, you can use syntax commands. The default screen of the app is a number-pad where you can type these commands. Please see the link below for information on syntax commands… https://www.zero88.com/manuals/zeros/selection-and-intensity/commands Alternatively, if you wanted to use onscreen faders to control intensities, you could use the ZerOS Monitor app instead, and view the Faders desktop. The Faders window can then be put into Fader Level mode. See the link below for more information… https://www.zero88.com/manuals/zeros/setup/settings/operational#mff I hope this helps.