Davidmk

An inhibit doesn't set the intensity level it limits what the maximum intensity can be so you can still have playbacks that set something less than 100% and they will still work as expected. e.g. You create two playbacks one of them (a) sets a fixture to 50%, the other (b) sets another fixture to 100% then you create an inhibit playback (i) with both fixtures at 100% (it doesn't have to be 100% but it usually is). With (i) at full, (a) and (b) work normally - 50% and 100%. With (i) at 50%, (a) will be at 25% and (b) at 50% With (i) at 0%, both (a) and (b) will be at 0% One thing to notice is that after you have created (i) you need to take it to 100% once to make it effective - if you just leave it at 0% it doesn't inhibit at all. A spin off of this is that, if the fader isn't quite making it to 100% (because it needs cleaning for example) you can never make it work. I generally find it is easier to delete and re-create inhibits than to try updating them if you need to add or remove fixtures. It's quite a powerful option but you have to get your head around it. Incidentally, there's also parking but I'm not sure if you can do that on S series. Or you could change the fixture defaults, this would put the ambients on unless you had a playback to set them off but the GM or an inhibit that included them would still put them out.

Make sure you are using record (not update) and have disabled SmartTag. See manual here.

No and yes. Normally the dedicated grand master controls all the intensity channels. However, in the last few versions of ZerOS the grand master can be programmed the same as any other fader so it is possible to re-program it as an inhibit fader for just the fixtures you want to include. Of course the S series do not have a dedicated GM fader so I guess you are referring to an MFF set to grand master so, for you, the solution is to NOT set it as grand master. Instead, select all the fixtures except your ambience ones, set them to full and record that on the MFF you wish to use as the GM. Then hold down setup and press the fader's button and select Inhibit on the playback settings menu. Note that using inhibit means the playback button will not be Blackout and there is isn't a way to replicate this.

@kgallen Not disputing your point but @ATC Tech seems to want snapshot pallettes and cues for reasons best known to them. What's bothering them is that subsequent changes to the pallette were not reflected in the cue. While I don't usually use snapshot pallettes or cues I do have playbacks with multiple cues that I use for busking where tracking defeats the purpose by moving on dark right to the last cue regardless of which cue I triggered (by OSC). Tracking isn't always your friend. I would agree that normal colour/beam/shape/position pallettes are more versatile and, thus, useful and easier to change though.

@pierotec That's good news. Thanks for sharing.

No, but I've used nearly 1024 and that was OK although it was a few versions ago. Just wondering if anyone has gone further.

I haven't tried what you are describing but my guess is that it's something to to with using 'overwrite" rather than "update". I think it is disassociating the playback from the pallette (as it would if you deleted and recreated the pallette). As a full FLX user, I'm not sure if you can do this but bring the playback up, select a fixture that should have values from the pallette and check the screen. If the playback is still associated with the pallette then the pallette name will show rather than numerical values. Same goes (I think) for the wheel labels. Obviously you could bring up the playback, select the fixtures, apply the pallette and update or overwrite the cue but that's going to get tedious if you have used the pallette in multiple cues. I'd suggest using update instead. Note that changing the group will not add or remove fixtures from the cue or the pallette. Also note, this is guesswork. I've not tried it. Hope it helps though.

Yes but the crucial bit is the bugs were ironed out.

I was setting up a basic showfile for a new client's venue from scratch a bit back and installed v8 before starting. I had a crash in programming and while I couldn't be sure it wouldn't have happened with the old version (I've had crashes with v7.14.3) I regressed the desk and started again. Since then I haven't dared try v8 again. Only rational if you consider how bad it looks if you are working in a professional venue, spurning their house desk, and have to restart your own mid show. Back in the day, when I had a day job in IT, the rule was never install an even numbered release. The even numbered ones (and that especially includes .0 ones) tend to have new features, the odd ones have the bug fixes to the even ones. Maybe that's a still a good rule to follow

I know that, in theory, ZerOS desks can handle a maximum number of DMX addresses spread over upto 64 universes but I'd be really interested to know the number of channels people are actually using without problems. Anyone using over 1024?

Check out my thread here. Back in the day you sent a scan of or link to the manual to support and a few office hours later you got a personality file back. The fixture would then be in the next release of the library for everyone to use. Now, it seems, the process takes longer and you have to pay for it. I imagine most people just use the Fixture Editor in the desk to generate their own. If there is a process by which fixtures get added to the library without someone requesting them then I am unaware of it. However I believe it is a resource shared with other manufacturers so you never know.

That's a nuisance. It was late when I scanned through the manual so, if I missed something about releasing it, I apologise.

I haven't used Rem Dim (or Highlight for that matter) but, checking the manual, I see that it applies to selected fixtures so I guess it is removed when you clear the programmer. Check the manual yourself for more details including the Apple watch app. Don't select a desk type as the S series may not have these features or at least not the MFKs to set to them.

I've got "form" for crashing FLX across more than one version of ZerOS. Not been able to find a way to force it to crash and neither have support so my ticket (ZOS-12410) is still outstanding. I updated one of my desks to v8 a few weeks back to create a new showfile for a venue I've started working at but had a crash on that so I took the desk back and started again. My crashes have all seemed to relate to the desk being busy with lots going on (effects and a chase running plus playbacks being flashed and lots of OSC messages). Buffer overruns and processor overloads have, apparently, been ruled out by support. That said, I've also had crashes where the desk was in a static state for a long time (hours). I have two desks, both seem to be affected. The fact that your issue seems to be repeatable gives some hope that it will give support more to go on. Fingers crossed 🤞.

@Veit0r Agree so much with @kgallen. They are great desks and make so much possible. The logic is biased towards programming shows and running them on the button but you can turn all that off and take control yourself if you want to. Enjoy your journey of discovery and come back to this forum if you need help.