Jon Hole

Ah, I understand - sorry. Whenever I need a flicker effect, I create a chase of 5 - 10 steps at different intensities, and then set the chase to "random". I can then add that chase to cues as-and-when I wish. Jon

There's the "random offset (individually)" button?

Hi Sean, ZerOS 7.9.4 will probably be released next week, so you may want to delay updating. The Solution Manual, plus the release notes of each software release since the manual (currently just 7.9.3) is exactly what you need. Jon

Full filter lookup libraries are only available on FLX, not FLX S.

Some of the networking protocols are bandwidth-heavy and include limitations that are acceptable due to ZerOS being designed for use on a dedicated lighting network. Eaton have strict Cyber Security requirements for products designed to live online. ZerOS is not one of these products.

Unfortunately, Iiyama (who produce these screens) appear to have two different drivers but the screens report themselves back identically. In a normal consumer's situation this isn't a problem - the correct driver is included within the box, they install it on their PC and it works. However, when we have to store all the drivers, if monitors requiring different drivers don't identify themselves uniquely, we don't know which is which... so we've had to include a manual method of switching between the drivers.

Hi John, No, it's not possible to change the DMX refresh rate. Have you tried disabling "RigSync"? If the fixtures have poorly implemented DMX this might be causing problems.

Hi grusus, the "old" method (entering values within Setup) had many many limitations: Values had to be entered "blind". This meant you generally had to write down all the values you wanted, enter SETUP and then type them all in. Values had to be updated one-by-one, or use the same value for every fixture - nothing inbetween. Values were stored as percentages only. So a fixture with 540 degree pan just moved to the nearest 5.4 degrees - not very useful! There were no "details" (for Gobo, Shutter etc), just numerical values There were no Palette References, so when touring it was difficult and time consuming to update values The new method solves all these problems - allowing you to use "normal" programming techniques (groups, encoders, referencing palettes, parameter details etc), update the values live to ensure they're correct, and the console stores these values as 16bit parameters resulting in the outcome being much more useful and accurate. I'm sorry to hear you think this - we've had a lot of positive response to our software updates recently, especially from Solution users. Over the last 13 months alone, the Solution has benefited from: Multiple Playbacks, significantly improving the functionality and flexibility of the console New "syntax" order, bringing Solution in line with most other consoles Updated "Special" MFK layout, making many tools within this menu much quicker and simpler to use Improved Remote Apps, including adding Syntax control Global Tap Tempos SETUP+INSERT brings features such as Highlight, RemDim and Park which Solution never previously had Improved ASCII importing, including from ETC showfiles "Auto-select" option on Channel Faders Automatic Effect Offset options Remote Device Management New Fixture Schedule layout allows you to manage fixtures much more quickly and simply New Add Fixtures process with many new functions including Universe Preview and Patch Offset Expanded CITP functionality Over 100 other enhancements and bug fixes

Richtig!

Hi grusus, This is all detailed within the Release Notes of ZerOS 7.9.3:

If you take the intensity to 0% there could be, but if you leave it at full you should be fine.

Hi Mathias, I'm a little late to jump in here, but please could you let me know the make and model of EVERYTHING plugged into your console on USB, including the memory stick? Jon

From memory, there were some small conducive "bits" inside the console which were shorting the tracks on the PCB - a quick blast of air sorted the problem.

Yes, that's correct. The rules are along the lines of "snapshot" (record absolutely everything) except for: Ignore fixtures at 0% Ignore parameters which are the same as the previous cue (or default if you're recording the first cue) This is helpful, as it avoids any "blocked" values being recorded (in tracking mode, blocked values are values which are recorded even though they are identical as the previous cue, and so don't need to be stored again).

It was introduced with FLX two years ago, and then transitioned over to the rest of the ZerOS range last year. Ultimately, you can probably trace it back to my next door neighbor who convinced me to purchase a Mac all the way back in 2005!!

We have now started testing through Apple's TestFlight. If you'd like to be part of this, please email me with an email address that's accessible on the iPhone which your Apple Watch is paired to.

We just tried this again on a lower-powered machine, and were able to recreate. Logged as ZOS-8548.

Hi Edi, I've just tested this, and it is working fine for me. What Operating System are you running? Please could you save the showfile and email it over to me? Thanks Jon

Hi Emmanuel, As Kevin says, record all your cues onto a single Playback. Press the Play/Pause icon top left and you'll see those cues. You can select any of the cells and adjust the cue's fade time using the encoder wheel. This allows you just to press the GO button, and get smooth, recreatable fades. However, if you want to do this manually, just hold SETUP, press the GO button, and then change "Fader Function" to "Manual Fade (2 ways)". I've just tested this and it behaves how you want. I believe the issue Kevin's describing is that if you switch back to HTP Master, you'll need to release the playback first (Kevin, is that correct?). To release the Playback (release="turn off"), hold down the CLEAR button, and press the GO button.

Hi, the Preset Master Faders are still used, but only when the console isn't in "Wide Mode". It's not possible to change their functionality. There's no "exclusive" option for Playbacks on the Leapfrog 48s, but you can use the "Inhibit" function. Record the Haze machine at full output onto a Playback, go to the Playback settings and enable "Inhibit". This allows you to record the Haze machine at full into all your cues, but have a dedicated "Master" for the Haze machine... which would give you a similar result as you're looking for, just in a different way. Jon

Rob, we've left you a voice message - hopefully we can get someone onsite tomorrow to investigate what's up, and if needs-be carry out a repair

There are no plans to currently.

Although we're in a Fixture Tools thread, are you talking about Phantom ZerOS?

As Edward says, so long as you're in Tracking mode, this should happen automatically as ZerOS executes "Move Fades" - ie, the only parameters that "move" (change) are the parameters that are recorded within that cue - so as long as those parameters aren't included within future cues, they'll be left alone doing whatever they were doing before - in your case, a 20 minutes fade. (Don't get confused with the word "move" - this is nothing to do with moving lights, and just describing that a "parameter" (could be intensity, colour, beam, position etc) is moving from one value to another). Therefore, if you're finding that in your next cue the fixture is snapping, you're either (a) not in tracking mode, or (b) have programmed that moving light into the following cues. You can use the "Remove" function within the Record Window to solve this - go into the "following cue", clear the programmer, select the moving light, press HOME (this is just a quick way of "tagging" all the parameters of that fixture), and then press RECORD {REMOVE} CUE x ENTER. Alternatively, as mentioned by Pete, you could store this on an additional Playback and either run it manually, or trigger it via a macro.

Hi Peter, In the Output Window, intensities shown in red are from the "Programmer". The easiest way to think of this, is it's where information goes before you record it somewhere. So if you push faders 1 - 6 up to 100%, this information goes into the "programmer". You may choose to then record this (so the information is transferred from the "programmer" to where you record it), or you may choose to clear the programmer, by pressing CLEAR twice (first press clears the selection, second press clears the programmer). If you pull those six faders back down to 0%, this new information goes into the programmer. The important thing to remember about the programmer is that the programmer always wins. So often, you may push up faders, record to a cue, pull down the faders, and then try and play back that cue. But pulling down the faders has added lots of 0%'s into the programmer, and the programmer always wins, so it appears like the cue hasn't worked. Press clear twice, clear the programmer, and now the cue works. Another thing to bare in mind if you're coming from a Frog console - don't lower the Playback Fader when recording cues. If you're recording cues into a Playback (the Master Playback for example), just keep the fader at full (100%). You may find out YouTube training videos helpful.