Jon Hole

Hi kgallen, Thank you for making this - I've added it to our library ready for the next release. I made a few minor changes: - On the "long name", I've put a colon ":" instead of a dash "-"... ZerOS uses this colon to split between fixture name and the different modes. If the text before the colon is identical, it groups them together. - I've defaulted CMY to 0 instead of 255... because CMY is subtractive, rather than additive, CMY defaults to 0 to achieve white, whereas RGB defaults to 255 to achieve white. - I've defaulted Zoom to 127... this is personal preference really - I've defaulted Hue to 0 rather than 255. Both of these values are "red", so I use 0 so you can turn the encoder clockwise, rather than anti-clockwise Spotlight Fresneled 150 RWBW.ift

Hi, please could you drop me an email with a short video of this? My email address is jonhole@eaton.com

Afraid not, no

Here you go Ian :-) Prolights Studio COB FC.ift

Hi Kevin, This would work naturally. You just go into channels, "catch" the channel (take the fader to the current intensity of that channel) and you now have control of it on the fader. To release this, you can either use the "clear" button (but that will clear EVERYTHING within the programmer), or alternatively one of the options on the UDKs (hold SETUP and press an empty UDK) is "Clear Fixture", which will just clear the currently selected fixtures. Another option on the UDKs is "park", which is useful in the situation of a lantern getting knocked (as per your example). When you press "Park", the selected fixtures will get locked onto that value. Even the grandmaster / blackout won't affect those channels. So you can merge these two features, to catch the intensity, bring it to 0%, and then "Park" it at that value.

Sure, no problem, give me a call on +44 (0)1633 833133 a bit later

Hi Luke, If you can drop me a showfile over on email (email address in signature below) I'll take a look. Let me know cue numbers, fixture numbers etc. Jon

Hi Stefan, We're solving this in a different way... allowing you to update groups (which would be the "correct" way to do this) Each software update we release we're trying to improving upon this. When you next see it's slow, please could you save the show and drop it to me in an email please? (email address in signature below) We're working on a few various things for the effects engine :-)

Hi Vincent, I've added a comment into ZOS-5598 and this has been scheduled for ZerOS 7.9

So ZerOS 7.8.2.36?

For the 36 channel mode, we'd suggest patching this has 12 x "RGB Dimmers". This profile is available within "Standard Fixtures" (the top option when the Patch Wizard shows you the list of manufactures). Use the same DMX start address, but put a quantity of 12, and the console will patch them correctly. You will then have 12 fixtures on the console - one to control each cell of the batten (so you're treating each bar as if it's 12 separate fixtures rather than just 1 unit). Hope this makes sense?

Hi Kevin, Recorded as ZOS-6930, scheduled for ZerOS 7.9 Recorded as ZOS-6097, scheduled for ZerOS 7.9 As you say before, they grey boxes show you which fixtures are on which "bank" of six faders. So, for example, if you only had fixtures five - 10 patched, you'd get a grey box around channels five & six because they are on one of the banks, and then another box around channels seven - 10 as they are on another bank. When you have "gaps" like this, rather than a sequentially numbered patch, they grey boxes aren't as clear which fixtures are on which faders. Added another comment to ZOS-6114, and changed it to be scheduled ZerOS 7.9 Hope it goes well!

Hi Vincent, What version of ZerOS software is your console running? I think it might be an older one? Jon

Hi Ian, Yes you can - the software installation process wipes absolutely everything that was on the console previously and starts the installation from scratch, so it won't know what the previous version of software was. Jon

Hi. You should be able to resize the console front panels by just dragging out the sides / corners. The monitor outputs though are locked at 1024*768 on all consoles apart from FLX.

You must start with a square grid (any size) but not every "cell" must be "populated" with a fixture. So if you want a curve, or a circle, you just create a suitably sized square grid and then just "populate" the cells you require.

The screenshot shows a 10 x 6 grid, so that could be 60 individual fixtures, or maybe 6 sunstrips or something like that. I can't really answer any more questions at this stage :-)

You mean something like this? These are early screenshots of something we're working on in the background :-)

Hi Kevin, Thanks - you're finding them all at the moment! We really appreciate it :-) Added as ZOS-6856

Good spot - added as ZOS-6855 to solve that syntax issue!

We’re currently preparing the app for release :-)

Pressing the middle button shows all the options within that parameter, but for some reason they aren't being created as palettes. We'll be going over to a new fixture library soon, so all of this code will be reviewed then anyway!

Hi Sven, Hopefully this will help! The bottom 20 faders ("playbacks") can be Cue Stacks 1 - 20, 21 - 40, 41 - 60 etc, using the syntax STACK PAGE x ENTER, where x is the page number. (On ORB XF, the "stack" button actually says "select stack"). You can also use syntax like STACK x MOVE TO STACK y ENTER to move stacks around. Hopefully the above tells you this - you could change to a different page, or move the stack somewhere else. To delete a stack, use the syntax "STACK x DELETE" or "DELETE STACK x ENTER", but this will permanently delete all the cues within that stack. We call this "releasing". Hold down the RELEASE button, and press the flash button of the playback. Currently, you can only pause on the Master Cue Stack on ORB XF Yes, hold SETUP and press the flash button, and then change the "Intensity Mixing" option in the window that opens. I'd advice releasing the stack (as above) after you change these settings.

of course :-)

Hi Luke, There are various options, the easiest way would be to go into the cue settings (last column in the Cue Window, and then press Enter). In that window are options to "Don't Move Colour", "Don't move Position" etc etc, so do this in the cues beforehand. Alternatively, if you program in Tracking Mode and with "Smart Tag" turned off in the Record Window (press and hold RECORD to open the Record Window), when you tag parameters, they will be stored in the cue as "hard values" so they won't move in dark.