Jon Hole

I'll look into this when I'm back in the office. I've logged it as ZOS-6841

Hi James, Go into Setup on the Jester, and into Test Mode. What does the larger internal LCD say? Jon

Hi Thomas, Have you enabled it within SETUP > Network > Remote? If you updated your software and didn't load a showfile back in, it would probably be disabled. If you have done that, please let me know the IP address of your console and the apps. Many thanks Jon

Thanks Kevin. I've made a slight update - I've changed the default value for the Dimmer channel to 100% (255). Although this sounds slightly strange, this is the only channel that's different for "default" and "home", so although in the fixture library it says "default value" what it actually means is "home value" - in the desk software we force Dimmer to be 0% by "default". Chauvet_BeamShot.ift

Hi Sven, Here's the fixture profile for you. SRM-6115.ift All the best Jon

Is that the Slimline LED Par RGBW which is 6 channels? If so, that looks like it has a dimmer channel anyway :-)

Hi Luke, The problem here is that the fixture doesn't have a dimmer channel, so there is no true "intensity" - hence the blackout, grandmaster, channel fader and 1@@ syntax doesn't do anything. I've created a fixture which has a "virtual dimmer" that scales whatever the shutter channel is doing from 0 - 100%. I've then defaulted the shutter to 190 (which is dimmer at full). That means if you don't change the shutter parameter, this should work ok, but if you change shutter to strobe etc, the intensity is going to do something a little strange (so you won't be able to have strobe at half intensity for example). Unfortunately this is the problem with these fixture manufactures who decide to omit fundamental parameters such as intensity from their fixtures! QTX Light.ift

Hi Luke1307, Please can you send me a showfile? Thanks Jon

Hi Ian, OK, let's chat through this over the phone... I've just tried to call you but got through to answerphone. Maybe you can give me a call when convienent?

Try patching just normal standard dimmers on these addresses, and see if that works with your dimmer addressed to 200? I'm not sure what is causing the issue. I'm willing to be proven wrong, but with what you've described so far I very much doubt it's the console .

How do you mean by "erratic"? If the Pan / Tilt is a 16bit parameter, when moving either of these I'd expect one dimmer to flicker a lot, whilst the other raised and lowered. I'd also expect a lot of dimmers to be at random levels, matching the default values of all the parameters of the fixture patched. Drop it into an email to me - jonhole@eaton.com

Try addressing your dimmers to those DMX addresses. Then, when you increase the Pan / Tilt, you should be controlling dimmer channels instead. That will tell you if it's the console or the fixture that's causing the problems.

Hi, If this is only happening on some of the fixtures and not the whole rig, I would suggest we might need to be looking at the fixtures, rather than the console. Have you got a DMX tester that allows you to see the channels changing in the DMX stream? Alternatively, if a fixture is meant to be addressed to "150" for example, and stops working the following day, try changing the address of one of the working fixtures to 150, and see if that responds correctly. Jon

Brilliant - congratulations on a successful show! Send us some photos and we'll share them on social media etc :-)

Hi Chris, No, nothing's changed - we've just formally released it now :-) Jon

We now offer free-of-charge FLX training courses at our factory in Cwmbran, South Wales. We also regularly visit theatres, venues, places of worship, distributors and schools all around the world to offer on-site training. For more information please visit zero88.com/training/ There are now also FLX training videos available on our YouTube Channel. The playlist of six training videos can be found by clicking here. Various other introduction and overview videos are available by clicking here.

Zero 88 are pleased to announce the launch of ZerOS version 7.8.5 software - a new software release for FLX. This update is recommended for all users. More information can be found at http://zero88.com/software/zeros A full list of changes are available in the Release notes. If you have any questions, please don't hesitate to contact us at the office. Our contact details are: email: support@zero88.com phone: +44 (0)1633 838088 Best Regards,

Hi James, I've got the debug file here which tells me the serial number etc. The console you were using was an early prototype console with known issues, so that console shouldn't have been used in the training session, sorry about that! Jon

Ahh, what we do internally and say externally are rarely the same, and should never be mixed up!

Playback 0 would have moved on dark ready for cue 3. Triggering Playback 1 changed the parameters. Releasing Playback 1 releases them back to Playback 0. Because Playback 0 is in Cue 2, it takes them back to that value. Once the fixture has been at 0% intensity for 1 second, move on dark kicks back in, and moves it again. They are computed "on the fly", you're right. The grey box is shown once the fixture has completed its move on dark movement. So, at default MOD settings of 1s wait, 3s fade, the grey box should appear 4 seconds after the fixture has gone to 0% (if it's going to move on dark). It's to let you know the move has completed, so you can choose not to GO if it's midway through a MOD fade. Will do!

I wouldn't say slow. Let's call it procrastination!

Hi Kevin, There's some Move on Dark settings going on here too (that's what a grey box around the intensity in the Output Window means). So for example, if I'm in Cue 2 of Playback 0, and then I raise Playback 1 up, Fixture 49 goes to 55% intensity but RGB all at 0%. When I then lower Playback 1, the intensity comes down with the fader, but then a second after it hitting 0%, the colour starts to change to Blue, and it takes 3 seconds to do this (as per the move on dark times). This is moving on dark ready for Cue 3 of Playback 0, which has Fixture 49 at 47% in blue. Does this help explain what you're seeing?

I see the problem... I was being slow. In ZerOS 7.8.4 CLEAR + Fader Function only releases the Multi Function Faders. In ZerOS 7.8.5, we've added UDKs to the list of things CLEAR + Fader Function releases. This fixes that problem. The other problem (CLEAR + UDK not working) has been logged as ZOS-6794

I'm trying this on ZerOS 7.8.5, and CLEAR+UDK doesn't work, but CLEAR+Fader Function does appear to be working. I'll try 7.8.4 now.

Happy to make some subforums... let me know the sort of subforums you'd like within the FLX one and I'll get them created. I'd like it to, but no plans set in stone yet.