scottydog75

Nice work @Jon Hole & team! New features gratefully received on FLX! Not being a FLX S user its good to see these desks also get a big capability upgrade by doubling the fixture count - a FLX S 48 may almost become a legitimate option as a 'show week' backup desk for my FLX now. It's also good to read Vari-Lite's ongoing support for the FLX S and integration between RigSwitch and other Vari-Lite fixtures (although not been shouted about on your news page yet! 😉 https://www.vari-lite.com/global/news#page=1). Here's hoping the support is long lasting for this very valuable control surface and OS! Noting the cut off for ongoing support for the 'legacy' ZerOS consoles with the release of V8 & V7.14.4, are you able to share any insight in the development roadmap for ZerOS going forwards? It must be a lot simpler with only the FLX range to consider within your future software updates now? Or if nothing official - what would be your top three wishes be for ZerOS's next feature set?! Wishing a Happy Christmas & NY! Alex

@Jon Hole just announced a ZerOS 8.0 'Release Candidate' in the beta-release testing forum yesterday. (7.15 is no longer a thing..!) I should imagine a couple more weeks with final testing and it'll be published.

Simple question first, you're not trying to draw more than 32A from the Betapack? If not, there is likely something inside the Betapack, or from one of the lanterns connected to the Betapack, which is leaking current to earth, causing the RCBO to trip. If you move all of the lanterns on Betapack #5 to Betapack #4, does the fault move across with them? That should hopefully rule out a lantern or dimmer issue. Intermittent faults are always the worst to try and diagnose, good luck!

Yeah exactly that! I'm sure someone else might come up with another better idea, but that's how I would approach it.

Cool looking units - however some of those DMX charts look a mess! Personally looking at the manual I would run them in 192 Ch Mode, and then create a custom fixture profile for each strip, something like this (although there is already a Zero88 profile for these units in the desk) This way you could patch this 'custom fixture' for each of your strips, easily run FX across all 24 strips, or dive into the multicell control and run FX on each individual strip. This should also avoid the complexities of trying to work out what 'cell' 1.28 is compared to cell 1.49 for example if you were to use the Z88 provide fixture profile. Hopefully ZerOS 8 will be out well before your show, so you should have plenty of disposable DMX channels to play with! Cheers

I was thinking we might have heard something with PLASA being on..! 😅 One day left to go perhaps..?

Wow Edward, big news! A real shame for us here on the forum & FB community groups, as your support was always immediate and spot on! Wishing you all the best with whatever you turn your hand to next! Cheers Alex

FLX S already has syntax support when used with a keyboard. See guide here: https://www.zero88.com/manuals/zeros/shortcuts/keyboard-shortcuts?filter=1

You can record any combination of lights to a single Playback or "Multi Function Fader" (MFF), and when the desk Fader Function is in "Playback" mode (which sounds like you are), the button below each MFF should act as a Flash button by default (it's function can be changed: Hold SETUP and press the button). However, I can't immediately think of a way how you can make this button act as a 'reverse' flash button. Perhaps a 'Latch' might work with a couple of extra button presses? As you've probably experienced, if the Fader Function is in "Channels" mode, the button acts as a select key, rather than Flash in this instance.

Strand LD90 Dimmers. Yes, DMX outputs window would have been a good idea to check, but I'm pretty sure the FLX was doing what I thought it should be! I'll have to dig the desk out and have a look at what it is doing. Great, thanks!

Evening all, I'm back after another successful week at the theatre with the FLX. Encountered a rather peculiar bug(?) or gremlin in the theatre infrastructure (in which case ignore this post) but the house technician hadn't seen this before..! I had a Fresnel on LX1, Channel 101. When running my rig check each day "1 Thru 812" and slowly dialled up the intensity encoder, this Fresnel would not illuminate. When selecting 101 only and setting intensity, fixture comes on. If I selected my Fresnels group, all Fresnels expect 101 illuminates, even though the output window suggests it should be on. Fresnel 101 also did not respond to cues within the Master PB. I ended up resolving this by physically plugging the Fresnel into a nearby dimmer circuit, and re-patching the desk, which then resolved all issues (so this makes me suspect it could be a dodgy infrastructure issue) however as mentioned earlier the house tech, who runs an ETC Ion, has never seen this behaviour before. Any thoughts? Completely unrelated, is there anyway the desk can calculate total cues (including . cues)? I know there is a 'last cue' number in the PB view, but this number does not include . cues. (Purely for bragging rights with my local lighting folk..! ) Thanks, Alex

Thanks again both. Will keep that guide to hand on the tech Kevin!

Resurrecting this thread as I have a similar query for a similar set up this year. I will have a large number of pixels once again, different venue but similar idea. I've pre-patched these as mutli-cell fixtures (10 'cells' in each fixture). I've tried to record an effect where the cells of each fixture chase 1 thru 10 (I.E. 1.1, 2.1, 3.1, 4.1, etc chase through to 1.10, 2.10, 3.10, 4.10) When in the programmer, this acts as expected, the cells chase through intensities 0-100%, I then record this as a custom effect palette, however when re-calling palette this the intensity is only 0-50% and displays the figures in yellow within the Output Window. Any direction as to what I have done wrong in the process? A bit rusty on the controls since the last show in June..! Snip as an example:

Perfect thanks! Like a dunce I was trying to 'turn' the encoders with my cursor - that will explain the odd control I was experiencing!

Anyone got some good hints for manipulating the FLX Encoders when using Phantom ZerOS? I often struggle to understand how these are supposed to be used with a mouse (or is there some secret keyboard snytax?) - perhaps someone can enlighten me! 😅 Thanks Alex