Jon Hole

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.

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 .