Jon Hole

ZerOS 7.11 has been released which fulfils "Colour mixing with mutli-emiter LEDs (eg, Amber, UV, Lime, Cyan etc)" - so I've removed this option from the poll. At the time, it was at 8.83% with 25 votes, making it the highest voted feature.

Edward was referring to the 3rd option in the poll - "Discrete timings on FLX (apply specific timings to specific parameters)" - so if this is a feature that you'd like to see, vote for that one 🙂 Yes, they run as two completely independent cues, just at the same time rather than after each other. It's the equivalent of "Part Cues" on other consoles (when I use them, I have my first cue as Cue X, and then use point cues for the Auto-With cues, so Cue X.1, Cue X.2 etc). Just make sure you don't tag the same parameters in both cues (and definitely don't use snapshot!).

(As a side note: you can already achieve this with two seperate cues, by setting the second cue to go "Auto With" the first cue).

Thanks for your comments! We really do value them. Can you detail how you'd want this to work? Intensities are a single parameter either fading "up" and "down", but colour can be multiple parameters that are just "changing". Similar for gobos, positions, etc. If you could go into some detail of what you would like the end result to be, that would be really helpful. We're hoping to have some news about a fixture builder later in the year. We discuss this every-so-often, and it's certainly not impossible... but we don't have a roadmap for this yet, and I don't foresee it coming soon (and I say this as a Mac user... so I'm invested in this idea!!!).

(@Edward Z88 got there first!)

Hi Simon, I think the end result will be what you want, but not by the method you expect. When RigSync discovers and patches a fixture, the link between the console and that fixture is the RDM UID, not the DMX address. Therefore, if someone messes up all the DMX addresses and then you load your older showfile in, RigSync will make sure that your showfile works by: Repatching your showfile to match the new addresses Readdressing any fixtures where this isn’t possible (eg overlaps) Also, remember about the “Revert Rig” option. When RigSync discovers your fixtures, it will store the values of those fixtures into the showfile before then making any required changes. So… if your rig is “correct” at the point of RigSync discovery, RigSync will store these settings and patch your fixtures, but not make any changes. If someone messes up all the DMX addresses, you then have the option to load that showfile in and click “Revert Rig” (note – when loading in your showfile, RigSync might automatically make lots of changes to make the rig work, so if you want it back to how it was before, you’ll need to click “Revert Rig” and then reload your showfile)

...because Tracking isn't complicated enough 🤯🤯🤯 😂

Done 👍 I didn't even know this was an option! "Regulars" now have access to this.

I think your general concept is correct - if you start at Cue 1, and program sequentially into a single Cue List - never making any mistakes, updates or inserts - and so long as you always use the programmer (not other Playbacks / UDKs) then the tracking options shouldn’t affect what you see on stage. (however, they might affect the data recorded into your cue, which might affect the behaviour / output if you go back and make edits)

Hi Sven, Yes, hold SETUP and tap the button of an empty Playback. You'll see an option to set that Playback fader to a Grand Master.

Hi Kipotuzer26, Currently, the colour mixing in ZerOS just deals with additive (eg RGBW) or subtractive (eg CMY) colour mixing… it doesn’t support HSI/HSV. This is something we’re actively looking at currently, as part of an update to our colour mixing algorithms. For now, according to the fixture’s manual, 3ch, 4ch, 7ch and 16ch modes should work just fine:

We have ORB, ORB XF, Leapfrog 48, Leapfrog 96, Solution and Solution XL. Phantom ZerOS is a little different, as it doesn't include a linux Operating System as part of the package.

There's certainly no plan to stop support any time soon! Some new feature will continue to come to Solution (like Multicell, which we've just launched) whereas other's might not be appropriate or possible... however that's no different to ZerOS today, where FLX and FLX S don't always recieve identical updates. The only ZerOS-based console we've been forced to drop support for so far was the FROG 2 back in 2017 (but that was still 13 years after the console launched).

I've moved the topic into "FLX", updated the title and edited the origional post to clarify "FLX", not "FLX S24".

Thanks so much @davelowe for highlighting this to us so quickly. We're really sorry this has happened Just to confirm, the forum has not been "hacked" (I've updated the topic title) and there's absolutely no suggestion that personal details have been leaked. Instead, someone (or potentially a robot) signed up and successfully went through validation. They (/it) then started Personal Messaging accounts through the forum... depending on your account settings, you may then have recieve an email to tell you someone had sent you a Personal Message.

Three more videos for your viewing pleasure! "Using Mutlicell on FLX S" "Using Multicell on FLX" And lastly, "How Multicell works" - a more techie "behind the scenes" look at Multicell

I've added a translation, as I hope you're recieve some great replies! Ajout d'une traduction, car j'espère que vous recevrez de bonnes réponses !

Click on the wheel and then move in a linear line (vertically or horizontally) rather than a circle.

Dear All, We’re excited to announce the availability of ZerOS 7.10, a new update to the award-winning software available on Zero 88 consoles as well as the Strand FLX S Series recently launched into the Americas market. The new ZerOS 7.10 Update introduces several innovative features that give designers more creative capabilities and improved flexibility to control their luminaires how they want, including new multicell support, a major fixture library update, and new move-on-dark configuration options. Watch this video for an overview of everything included in the new release: ZerOS 7.10 introduces other capabilities and bug fixes as well, including the ability to use +/- syntax on the Zero 88 FLX console to adjust intensities, fade times, etc. See the release notes for details on all updates and bug fixes in the software. We have also created several training videos to get you up to speed on the latest changes: ZerOS Training – 7.10 Technical Overview ZerOS Training – Multicell on FLX ZerOS Training – Multicell on FLX S ZerOS Training – How Multicell Works ZerOS 7.10, Phantom ZerOS 7.10 (offline editor) and the Release Notes can be found at zero88.com/zeros If you have any questions, please don't hesitate to contact us at support@zero88.com Best regards, Jon

Hi Tony, To answer your question we need to know about the whole system, not just the console. Do you know who installed the lighting system in the school? If so, contacting them would be a good starting point as they hopefully have the whole system documented and will be in a position to help much quicker than we will be able to. If not, please provide as much information / photos of anything you can find that might be part of the lighting system - including close up pictures of the lights themselves (showing make / model etc) and we'll try to help! Jon

">" acts as THRU There's a full list of keyboard shortcuts for FLX S available here: https://zero88.com/manuals/zeros/shortcuts/keyboard-shortcuts#flxs ZerOS uses "/" in lots of syntax, meaning it wasn't available for THRU. For example, on an ORB, the syntax "CUE a/b TIME x/y ENTER" applies an up time of "a" and a down time of "b" to cue "y" of Cue Stack "x"

Worth noting that there's a current thread discussing and voting for new features in ZerOS. One of the options is "Exclusive Playbacks", which is what you're describing.

Just so you know, it’s a hardware limitation that makes this feature unavailable, so we could never introduce this as a software update. However, there are potentially other options - such as maybe introducing a “startup state”. Almost none of the listed features have been fully scooped or spec’d, so at this stage it’s hard to say. However, if we’re doing this, it would cover all the new features. Whether it was a full builder within ZerOS, or a simple builder within ZerOS and a full builder somewhere else, is up for discussion.

A good question. All these features would need scoping and specifying. With MIDI, I suspect the main uses would be for MIDI TimeCode (Cue X starts timecode, Cue Y stops timecode) and MIDI Show Control (Cue X automatically sends out a GO CUE X MSC message, Cue Y automatically sends out a GO CUE Y MSC message, etc). Whether we also need to allow completely customisable MIDI Messages to be transmitted needs investigating.

I did think about doing this, and internally we have a "Resource vs Value" spreadsheet that tracks some of these issues... but I fell back to the "KISS principle" to make it simple to understand and vote. But it's a completely valid point. This is a great suggestion which we forgot to add. I've added it to the list (you can edit your vote, but it involves reselecting the items you selected last time) FYI - FLX (full size) has the hardware ability to generate and output MIDI. The "Thru/Out" port has a software switch to switch it between "Thru" and "Out". Currently, ZerOS doesn't support outputting MIDI, so this is always set to "Thru" (which is why one of the poll options is "MIDI Out support on FLX") I'm sure it would! Each item on the list would ideally include a few paragraphs of text explaining the feature. A new skin isn't just for a visual refresh (although I do feel that's needed too). We receive comments about font size and readability, Remote App scaling at certain resolutions, the size of some buttons and keyboards, accessibility (colour schemes, contrast etc) - so it incorporates all of that.