Jon Hole

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.

What a horribly long fixture! With this one, like this one, I'd highly suggest patching it as seperate fixtures for each cell. I've added it to the main library, but put it under "showline" rather than "philips" as the manufacture

I love this thread :-) They are :-) This has already been answered - but yes, they are fine to use As long as you keep within the USB standards, you'll be fine. If you try pulling to much current, FLX will just cut off that USB port until you unplug the device. It's worth noting that this goes against the Manufacturer's recommended guidelines

Hi Johnny Have a look at the "Trigger" settings on page 55

Hi James, Kevin's explained pretty much everything. I've gone through your post and added links that will take you to more information about each thing (I've possibly gone overboard with the links...!) Jon

I've replied to your PM Matt, but probably best I publically post it here too. Hi Matthew, Sub-fixtures don't quite work like that. They work designed for fixtures where two separate DMX addresses are required - for example a lantern with a colour scroller, or a moving light like the VL1K where the tungsten lamp can be plugged into the house dimmers. For fixtures like the KAM Parbar, where realistically they are four separate fixtures connected together, I would make separate profiles that control each part individually. This makes programming much easier. So, for the Parbar, I'd either make a "control" fixture that is just channels 1 -3, and then patch four RGB Dimmers (available in the library under "standard fixtures"), or I'd create a profile with the control channels and the first RGB channels (so channels 1 - 6), and then patch three more RGB Dimmers. Does that make any sense? Jon

"Fader Controls..." is used so the physical fader controls the level of those attributes, rather than them getting triggered at the "trigger level". So, for example, by default, if I move a fader to 5%, the intensity will come on at 5%, and the Colour, Beam and Position data will get fully triggered to their positions over their fade times. If I then say "Fader Controls... Colour", only Beam and Position will get fully triggered, and Colour will only move 5% from the previous colour to the new colour. As I slowly move the fader up, Beam and Position won't change (As they've already been fully triggered) but colour will get closer and closer to it's end value. If I start moving the fader back down, colour will return back to the previous colour, whereas Beam and Position won't change (until I go below 5% when they'll release). I often use this with position, and record a fader with the position of my moving lights pointing up at the ceiling above the audience. Then, if I have all the moving lights running effects over my stage, I can use this fader to pull that effect out into the audience (around 50%) or keep going and put the effect up onto the ceiling. To filter what's being recorded into a cue in the first place, you need to use "tagging" and the record window. In the record window, under the "attributes" heading, you can choose which attributes to record. Green means all parameters within this attribute (as per position below) Red means tagged parameters within this attribute (as per intensity, colour and effect below) Off (blue) means no parameters within this attribute (as per beamshape below)

There's talk about how we can make this work. Something I really want, that's connected into all this, is for triggers / releases to be "tracked" through the stack - so if a playback is triggered in Cue 8, and released in Cue 12, if I jump to Cue 10 the playback should automatically start, or if I miss / jump over Cue 12, the playback should automatically release. It's all connected with the above requests.

Hi Leon, Thanks for these comments - we'll keep them in mind during future software updates. On FLX, individual "playbacks" that are chases have BMP buttons, so maybe this will move over to Solution eventually too!

Yes please - will make it easier for me to follow! Potentially yes - you could be playing back parameter settings from one playback (LTP) and intensity settings from another playback (HTP).