scottydog75

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

How much do we pay you @Edward Z88 to sit next to you at the production desk and absorb all this wisdom?! 😅 I've just recently finished a week of 'The Wind In the Willows' on the FLX, and although it was relatively a pain free experience, I still felt awfully clunky programming - practice makes perfect and all that..! It was quite the beast for me, a new venue to LD in, ~200 fixtures in total, resulting in about ~200 cues by the final performance!

I did try which didn't make a difference at the time, however... I have since dismantled the monitor, and given the optical sensors and reflectors a good clean, and currently (fingers crossed) the monitor is now working correctly both on PC and FLX! Sorry for the wild goose chase, dodgy hardware after all!

Hi Edward, I've re-plugged my touch screen into my PC and this is also now unresponsive - so I unfortunately assume the touchscreen element of the monitor is on the way out Thanks for the troubleshooting tips anyway!

Hi Edward, Unfortunately still no response. Iiyama ProLite T2252MTS. As suggeted by DALX, I tried downgrading to 7.12 & 7.11 - still both with no reponse, so maybe I'm wondering if it could be my monitor again after all?

No response from the desk, I try and tap on the first calibration point (and areas around it) and it doesnt detect any touch. I have previously confirmed the monitor is functional when connecting it to my Win 10 PC.

Hi Edward, I assume it is detecting it, as "0408:3008" disappears when I unplug the USB connection to the monitor.

Hi Edward, Is this a known issue on FLX as well? My current touch screen wasn't working, then it was, and now it is not again! (Running ZerOS 7.13) Thanks Alex

See the post below...

You're definitely right about being easier to find, I guess I was just hoping it would take up less space than another full size FLX!

Hi all, Is anyone aware of any companies that have ZerOS servers in hire stock, or if anyone has one personally they would be willing to hire? I have an upcoming production in late May - early June, where I would feel more comfortable knowing I had the server to rely on incase of any desk failures. Thanks, Alex

Hi gents, As usual programming time was very very short so I didnt end up getting exactly what I was looking for and the Chaser 1/8 sufficied in the end! I attempted using the Uni Blink effect but struggled to get it to perform as needed, im sure with a bit more fiddiling I probably would've got there. Either way, they still looked great! Pic attached for interest.

Just to close the loop on my particular touch screen issue - this now resolved when using ZerOS 7.13. Weird!

Thanks both for very good ideas as usual! I'm planning to get the desk patched for the show later this week, so I will consider using LED Multicell fixtures (hand't even thought of this as an option..!) and will have a play with the waveform editior. Great idea about getting a macro to do all of the work for me. Even if I dont go down that route on this occasion, I will need to try that another time and see how that works. Thanks again Alex

Hi all, I've got a show coming up next week where we will be fixing 300 RGB LED 'pixels' as decoration on the prosceinum arch. I am specifically trying to create an effect of a single pixel or a few pixels chasing up the SL leg, across the arch, and down the SR leg. We got all the LEDs and FLX out for a test at home this past weekend and had a good play! The only negative of having so many fixtures is when the Chaser 1/8 effect is applied, this will illuminate quite a tens of fixtures at any one time. Ideally I guess I need something like a Chaser 1/16 or 1/32! Does anyone have any clever ideas to reduce the 'tail' on this effect, other than creating a custom 300 step chase (not really feasible..!) Thanks, Alex

Hi Jon, Tried ZerOS 7.12 on an event this weekend (full size FLX), had the most peculiar issue where I had a 'dead' touchscreen zone on my external montior. I tried recalibrating several times to no joy. I ended up downgrading to ZOS 7.11 which then worked OK. Dead zone confirmed by using the 'draw' function after calibrating the screen; it was a diagonal zone extending from the bottom right corner. Touch screen is an Iiyama T2252MTS-3. Desk is out on another job this week, but will try some more testing when it is back on ZOS 7.12 again. I also thought the desk was maybe a bit more 'hang-y' when changing between setup and attribute pages than previously. Cheers, Alex

It doesnt look like its a current product anymore, but I use the Iiyama ProLite T2252MTS-3. Multitouch works with no issues. https://iiyama.com/gl_en/products/prolite-t2252mts-b3/

Thats great thanks Edward! The only one I've noted recently from training which I couldn't see on that page is: 'NAME' + Cue Number + Playback Button = Name Cue I also don't think the command string for 'NAME A GROUP, PALETTE OR PLAYBACK' is correct. I believe this should be: 'Name' + Group/Palette/Playback Button

Hi everyone, Does anyone have a 'cheat sheet' for key strokes on FLX? (Or is there a page in the manual I have missed!) Having been to a few training course recently I've picked up a few new ones where holding 'Shift' and pressing a button will perform an alternative action. e.g. 1 Thru = Selects all fixtures, Shift+Record = Snapshot Cue, Shift+Copy = Move, Shift+Go = Snap to Cue, etc Thanks, Alex