Jon Hole

On the next version of software the "Insert" button becomes a customisable button, and one of the options is "Clear Fixture" which does exactly what you're looking for.

Hi, We're in the middle of designing a user interface that will make this all much easier! Instead of using the different waveforms (+90, +180 etc), instead use the "Offset" column which allows you to set the same waveform / function across each colour parameter, and then offset each parameter compared to each other.

Here you go! Elumen 8 Beam 1RE.ift

Exactly correct. There are a few situations it *can* be useful (for example, maybe you want colour to go to white when you click your glass gobo beamshape palette), but for most people, in most situations, a new looks palette would be a lot better

It's on the list :-)

Thanks for all your feedback on the previous version Kevin, tried to take as much as possible on board!

Hi Lightmaster, There are various options, depending on what you want. One option is if you hold SETUP and press the flash button of the submaster, there's a setting called "Submaster Controls..." - make sure "Effect" is enabled. Now, the effect will get larger and faster as you bring up the fader, and smaller and slower as you bring the fader back down.

Hi Jan, Hopefully this will help: Having either "Smart Tag" or "Snap Shot" enabled will ensure the previous cue doesn't affect the new cue. Having "Cue Only" enabled will ensure the new cue doesn't affect following cues. When people are inserting a cue (say, Cue 28.5), I generally suggest they go into the previous cue first (say, Cue 28), make the changes they want to make, and then record it as the inserted cue. This way, Smart Tag and Snap Shot aren't required. 1) Update the cue, with "Track Forwards" enabled 2) Update the cue, with "Track Both" enabled 3) This is the same as 1 Ensure the programme is empty, tag the parameters you wish to remove (it doesn't matter what their values are, as long as they are tagged) and then in the Record or Update window choose "Remove". Ensure Smart Tag, Snap Shot and Cue Only are all disabled. This should happen when copying cues anyway Although "Cue Only" is accessible within the Record and Update windows, they are whole console setting - so the logic still applies when deleting. Therefor, if "Cue Only" is enabled, following cues won't be affected by the deleted cues, whereas if "Cue Only" is disabled, following cues will be affected. Let me know if there's anything not clear, or if you have any further questions!

There won't be pixel mapping software released by your event in November, however there are probably other ways of doing this. If you put the batten into 54 channel mode, you can then patch it into the console as 18 separate "RGB" fixtures. This gives you control of each one individually, but also allows you to select them all, run and effect on them, and offset that effect across the individual cells.

For completeness, here's the list of spare fader part numbers for each console we've ever produced: http://zero88.com/support/index.php?/Knowledgebase/Article/View/512/219/

Hi, If you are "a beginner to network setting" then we should probably start at the beggining... I think we need a little more information on your setup. - What IP addresses are everything on the network. - Are there any switches / hubs / routers? - Are you using Straight or Crossover cables (each individual cable you're using) - How is everything plugged up If you give us all this information, we can have a look at what might be wrong.

Hi All, Sorry I didn't post on this thread sooner - the updated manual is in the Beta Test forum - it's there as it references all the new features of ZerOS 7.9.1. Everyone in this thread are part of the Beta Test group. Jon

Why? That's why we're here!

Drop me an email (not a personal message on the forum), and I'll forward it to someone who might be able to arrange something.

100% agree it's past the point of needing it now, and I'll get you an updated one tomorrow. Then we'll wait a week or two for feedback, and then release it properly. As a side project, I'll look at the possibility of an online (crowd sourced?) manual for the future, so it's easier to keep it up to date. This will benefit all the consoles.

Only if you select all of one fixture (by pressing "GROUP" in the Edit Fixtures window) and then changing the "ALL" row.

Thanks for the comments Jan! Within ZerOS, we're currently combining Submasters and Playbacks together (submasters were available on Solution and ORB consoles). Once we've done that, the next job is to combine UDKs and Playbacks. Once we do this, it'll be much easier to link in MIDI commands as you suggest.

Hi Kevin, We wrote our driver several years ago when WYSIWYG didn’t support Art-Net directly. However, now (and for several years) it has supported Art-Net, so that’s by far the easiest option – ignore the WYSIWYG driver, and ignore the settings in the “visualisation” part of SETUP, instead just concentrate on the Art-Net settings, as if it was any other Art-Net device.

Thanks for the comments! We use monospaced fonts for various reasons. The main one is so intensities don't "jump" / "shake" all over the place when running a fade. There's another issue here that's not been covered... which is licensing and distribution. Unfortunately we can't just choose any font and start shipping it

That's why we're here :-)

Hi, I imagine the decimal is showing the Universe and the address. So, 1.35 would be Universe 1, address 35. The Jester console only has 1 universe, so you can ignore the "1." part. However, if there's a 2. or 3. something - you might need to rethink a little!

When I said "they can come in two flavors", I was talking more generally rather than specifically on our consoles. We've moved from topset over to proportional on our Inhibitors currently, as that's usually the more popular option.

It is on the roadmap - in fact ZerOS already supports MIDI Notes on other consoles, we just haven't brought it across to FLX yet as, truth be told, I think we can do a better job at it! Which, leads me to the question... How would you like MIDI Notes to work? What exactly would you like triggered, and how? Thanks Jon

Hi, here's the fixture you need Starway SuperKolor.ift If there's anything else we can do, please let me know!

Thanks for that detailed explanation - great stuff! Just expanding on two areas: Inhibitors Inhibitor faders can come in two flavours - one that just sets a topset, and one that proportionally scales (as Jan described above). If a fixture was at 50%, and then the Inhibitor was taken to 50%, a Topset Inhibitor would keep the fixture at 50%, whereas a Proportional Inhibitor would take the fixture to 25%. LTP Normally for Intensity we use "Highest Takes Precedence" rules - so it doesn't matter what order you do things in, if a fixture is at 50% on one fader, 75% on another, and 25% on another, the fixture will be at 75% - as this is "highest". However, LTP stands for "Latest Takes Precedence" - it means the latest thing you do is what "takes precedence". However, LTP gets a lot more messy thank HTP. Imagine you have a fader with a fixture at 100%, and you put it to full. And then you have another fader with the fixture at 50%. As soon as you start pushing that up, technically the "latest" command is to go to 1%, then 2%, then 3% etc. However, it's very unlikely that that's actually what you want to happen. So we are developing two different options - Soft LTP and LTP Catch. Soft LTP will fade the intensity from it's current level (whatever that might be) to its new one, even if that's in the "opposite" direction. LTP Catch works slightly differently. It says that nothing happens until you match (or "catch") the level - so if you have a fader up with a fixture at 50%, and then another fader with the same fixture at 100%, as you fade this second fader up, nothing will happen until you match the 50% level, and then the second fader will take over. Up to that point, it's not much different to HTP, however the difference is when you pull that fader back down, it will go all the way to 0%, not stop at 50%. We're still working on Soft LTP and LTP Catch - think of them in "beta" still!