Leaderboard

Hi all, I've been reading your replies and they've really meant a lot to me, thank you. I've deliberately waited a few weeks before replying. All the very best for the future and, if you're at a trade show in the future, please come and say hello - this LinkedIn post shows where I've headed to, if you're interested! Jon

Good luck Jon but I'm not surprised. TBH since the Varilight take over it's felt like the beginning of the end. The issue of the latest software will probably be the last so I hope we all got our wish list items sorted.

I notice the two support personnel Jon quotes above have a combined contribution of posts on this forum of exactly zero (since Sept/Nov 2024 when they joined). Looks like we're on our own folks, or they've got some work to do to establish their credibility and start making an active contribution - which I guess is part of what they are paid to do (unlike us). A 'hello' and a short resume would be a start…

My post on the topic of OSC use with the Zero88 FLX S24 may be of interest. All free software and might give you a start in understanding the process.

Hi @SoleJan Blue UP to the sky, green DOWN to the grass. (Blue means that channel intensity went up, green it went down.) White, it's a blocking value, purple it's tracked. Red from the programmer (highest priority), yellow for some other controller. Red background is Parked. Grey background (for a short time) is moving on dark. They're all here: https://www.zero88.com/manuals/zeros/desktops-windows/output-window#colours

@DMH @RJP To be fair, some good answers there and, if delivered, could help the situation but... How it looks is important. In the absence of a published plan and feedback on progress, its all we have. We used to have trust but that has to be earned so, come on Vari-lite, start looking better. You've bought the rights to good hardware and software with an established customer base - many of whom have been using Z88 products for years, decades even @pcollins666. An unpaid sales force that was more than happy to sing the praises of a company that looked after them, had a solid track record of supporting them and of steady innovation. What do you think those established customers are saying to your potential customers now? It's clear the full FLX had to be discontinued but there's no talk of a replacement. The in-person training has stopped. Cwmbran is no longer a service centre and there are none listed on the Vari-Lite Web site in the UK (the two "dealers" listed are a 2nd hand equipment seller and a hire company). Plus, to return to the origin of this thread, there is now a charge for fixing the (inevitable) gaps in the fixture library. These things are probably not Vari-Lite's fault but what is being done to address them? How could I, in all conscience, reccomend a Z88 product today?

As a Zero88 stalwart user and supporter for more than 30 years, I asked a few questions just about what we might expect in the way of support following Edward & Jon’s departures. I did receive a prompt reply in red below. It at least gives their intent and maybe a base for us to push from…. With my two good friends, Jon Hole & Edward Smith departing in quick succession, can you describe the changes to the support services that we are likely to see going forward. I understand how this must look but I would like to reassure you the software development team that are in the background are still very much here and as will has a dedicated support department. The support department is manned in the UK and US so we can offer better global coverage. Up to this point I’ve had personal FLX Support response to emails usually within one working day. We do still try to respond withing 24/48 hours to direct emails, however this will also depend on workload as we also cover on site visits. Instant phone call response for show critical issues. Are there still FLX console experts available to take technical enquiries? We have and have always had an out of hours emergency response number, this is available from the Vari-lite website. Please find below the link. https://www.vari-lite.com/global/support/technical-support Daily monitoring and responding to forum posts, usually within one working day. No spam posts. The forum appears already to be out of control. The forum has slipped behind as we have been dealing with direct customer support, we are currently working on a solution to this. Fixture Library addition requests created and emailed back usually within one working day. We are creating fixture files for customers but as the workload has increased we have had to increase the estimated turn around time to up to a possible 21 days. We understand this is a big difference and we do endeavour to do them ASAP which is usually between 1 and 3 days. If the file is urgent, we recommend the customer creates the file themselves as this is a very easy process within the ZerOS Software, please see the link below. https://www.zero88.com/manuals/zeros/patching/add-fixtures/fixture-creator Ongoing ZerOS development with bug fixes and new features. Are there still dedicated ZerOS software developers actively in post? As I mention above, the software develop team has not changed this has in fact increased with developers in the UK, US and New Zealand. A roadmap for ZerOS progression, shared with users. A monitored ‘What would you like to see in ZerOS’ poll. Regular beta testing releases with feedback being acknowledged and logged. Updates and improvements to training manuals and YouTube content following ZerOS releases. Thank you for your suggestions, I will forward them to the product management team. As you can see from the above, Zero88 provided a truly comprehensive service to its users, at no extra cost. I would like to hope that a similar service will continue to be provided from the company that has the iconic and industry respected name of Vari-Lite. Thank you for your questions and I hope you find our response reassuring. We are constantly looking at our processes and internal procedures to improve the customer experience.

The answer to that lies in this forum over the last few months. As a 30 year user/buyer myself, it’s spelled out in big fat letters. It’s the end of the line folks I’m afraid, they’re not interested. Jon managed to get in a last gasp with ZerOS 8 before he left. That will be the last, I’m sure of it. Zero88 and its beloved products and employees are no more.

@Jon Hole I wish you future success in your forthcoming move. I think Zero88 now have their work cut out to maintain the support levels we have enjoyed in recent times.

I'm my red mist I've so far failed to acknowledge @Jon Hole. My apologies. Thanks for so much Jon over the years - great products, accurate and timely support, recruiting some other great team members, and putting up with some quite strong feedback and comments from us on here. You will be missed as will all of the legacy Z88 team. Good Luck!

I took "forum admins" to mean they sort out the forum when it dies and deal with inappropriate posts. So, yes, my assumption has been that the prompt and helpful days of Edward and Jon are over and we are, as you say, "on our own". I, for one, would be delighted to have this cynical and depressing assumption proved wrong. The newish thread - 16 bit intensity really 8 bit - is one that seems to require their attention (even though you have tried to help).

Good morning @Sol, Welcome to the Zero 88 Forum! @Davidmk and @kgallen have done an excellent explanation of how to go about solving this with a 'master' playback triggering and releasing other singular playbacks. I would have done it the same way. I'll admit, this is something that should be able to be done easier, but this is unfortunately currently the only way to do so. I've written some guidance below, expanding on the discussed elements in this post, to help you along with this. (Apologies for the colossal message, I have tried my best to cut it down). In the following steps, you'll be programming individual playbacks with one lighting state each for each 'step' of your chaser. As Kevin and David have mentioned, we can then trigger and release these individual playbacks with a master playback (not the regular type of Master Playback with the main GO button though, to avoid confusion) that just has control over these individual playbacks. It's worth noting that the 'master' playback you'll program will be a chase, with the individual playbacks (the 'steps' of the chase) will be one state on each playback. E.g. Playback 10 has fixture 1 and 5 at full white, then Playback 11 has fixture 2 and 4 at full white, with 1 and 5 at zero, then finally Playback 12 has fixture 3 at full white, with 1, 5, 2 and 4 at zero. This creates the singular steps for an effect that will chase in towards the middle. By programming these individual steps onto separate playbacks (the last few playbacks available on your desk are recommended to keep them out of the way), it allows us to individually trigger and release them. When releasing a playback, ZerOS completely wipes it out from the outputs, returning to the underlying data for that fixture (if any at all), allowing fixtures to switch back to your original rainbow gradient. For example, if I have Playback 1 as fixture 1 thru 5 at full white, whereas in Playback 2 fixture 3 is at red - I bring up Playback 1 (all white), then I bring up playback 2 (fix. 3 at red) while keeping 1 at the same place. Fixture 3 will turn red. If I bring down Playback 2 (fix. 3 at red) to zero, fixture 3 will return to the original data it has in Playback 1 (white) as Playback 1 is still raised. Steps for creating each individual playback (acting as each step for the overall chase) Step 1: Bring those fixtures up for the first / next step of your chaser you want to program. Step 2: Put them in the colour 'White' so their colour is tagged. This will differentiate the colour from the underlying rainbow playback. Step 3: Tap 'Record' -> Tap an empty playback's flash button. (I recommend the last few playbacks, and ensure to leave room to place them in order so you know which one does what) e.g. 3 steps I would have Playback 46, 47, 48 with 46 being step 1 and 48 being step 3 (last step). After you've programmed each individual playback (e.g. each step) Step 1: Think about where you want to put your 'master' playback that will start your custom chaser. Pick somewhere which has an empty playback to the right of it (explained later*) Step 2: Ensure nothing is being output from the desk again. Tap 'Record' -> Tap that playback's flash button of where you want the 'master' playback to be. Then do the same for the empty playback to the right. This will record an empty cue on each playback. *The way this will work is the left one of the two playbacks will be the playback to start the chaser, and the right of the two will be the flash button to stop / release it (the whole chaser). Step 3 (repeat as many times as needed): Record an empty cue for each individual playback ('step') you have programmed onto the 'master' playback (left of the two). On the second cue recorded, the desk will show a prompt. Tap 'Create Chase'. The second cue has now been recorded, with the playback converted to a chase. This prompt will not appear for future cues/steps recorded to that playback, as it will just add another step to the existing chase. Step 4: Go to the first cue in this playback (VIEW + Playback Flash Button to view these cues) and tap 'Add' in the 'Settings' column for that cue. Step 5: As David mentions, use Macros -> Trigger Cue Stacks (tap 'Add' next to it) -> Select your individual playback for the first step. Tap OK. Tap OK again. Step 6: For cue 2, you should tap 'Add' in the 'Settings' column again, Macros -> Trigger your second individual playback for the second step, but under 'Release Cue Stacks', put in the previous step (for this - the first individual playback). That's the base of it done for the first two cues. You'll now want to repeat that for each individual playback (acting as each step) you have programmed, ensuring that for cues past the first trigger, you release the previous, and trigger the next. Cue 1 should have the first trigger, and releasing the last playback so when the chase repeats, no steps overlay each other. In the single cue in the playback to the right (the one we will use to stop the chaser all-together that I talked about earlier) - do VIEW + Playback Flash Button -> 'Add' in 'Settings' column -> Macros -> Release Cue Stacks -> Add in all of your individual playbacks. This will release all playbacks when you hit the flash button, stopping them. You can also trigger both of these playbacks in your main cue stack, so you don't have to worry about moving the faders. Note that if your 'master' playback for this chaser effect is still raised or active, then it will just re-trigger these individual playbacks, so when stopping using the playback to the right, ensure the 'master' playback is down. You may notice something odd with the fade timings for each step. To fix this, enter each playback's view like you've done previously (using VIEW + Playback Flash Button) and edit the fade times in the columns to whatever you wish. The console will listen to these fade times when triggering and releasing each individual playback. To set up your 'master' playback for a Tap Tempo, hold SETUP and tap your 'master' playback's flash button -> CHASE tab -> Use Global BPM (tap to get it with a red line to indicate it is selected). Then define an empty playback as a Global Tap Tempo by holding SETUP again and tapping a flash button of an empty playback -> Fader Function -> Global Tap Tempo -> OK. Again, I apologise for the very very lengthy message, but I hope this is relatively okay to understand, please do let us know if you need more help as this is quite painful to do, and many thanks again to Kevin and David for the initial replies! Archie

Hi Scottydog75, Apologies for the delay in response. The software team are in the process of finishing the next beta build for ZerOS. This should be released for testing on the forum within the next couple of weeks. Kind Regards

Hello Oliver_74 You can use the Add as additional address function found in the Edit DMX Address window to pair your five fixtures. When you select the DMX address of the first fixture you want to pair, the curser will flash in the DMX address window which will be blank. Type in the address of the second fixture in the pair, select Add as additional address, then Enter. The Fixture schedule window will show two addresses for the channel fader of the first fixture. I only found this last week when I wanted to pair dimmer channels under one fader.

I can confirm that the Flx S48 console worked well using about 2000 channels with 2 Artnet node and 13 used universes

Hi all. The iOS apps are now back on the App Store in their original capacity and under the same links they were before. ZerOS Monitor -> https://apps.apple.com/gb/app/zeros-monitor/id1033159176 ZerOS Remote -> https://apps.apple.com/gb/app/zeros-remote/id367342433 (cc: @Charlie Newman @Philh @ATC Tech)

Thanks everyone for your help on this, after digging through a good few training webinars on YouTube, I came across the simplest answer - offset, specifically how the offset fans across fixtures. You can change this behaviour by holding setup and tapping effects. I set my shift click to be 'fan first' (Also experimented with the other fan options for different effects) then selected my fixtures, hit chase, held shift and span the encoder wheel to fan the offset of the effect until the chase matched up on all battens. Worked super nicely and certainly opens up some more interesting possibilities for programming Battens Chase LQ.mp4

A JOS file is likely to be a showfile. A fixture personality file is an IFT file so it may be they way you're trying to load the IFT file? Found this from Ed on another forum... The <Update Library> option in Super User can be used to update the fixture library on the console. If you just wish to load in a fixture file, not a whole library, please see page 49 of the Jester TL manual for information on assigning fixtures… https://www.zero88.com/storage/downloads/5ebda1d3-7348-4727-ae31-fecedf299a46/Jester-TL-and-TLXtra-Manual-3.0.pdf#page=49

Hi Give the attached a go and let us know how it goes LeLight LED Moving.ift

@DMH@RJP The SPAM postings seem to be on the increase with over 40 in last 24 hours plus others highlighted but still on the forum. Please can some trusted forum members be promoted in a way to allow removal of these posts?

Smart tag... Great at what it's meant for (recording cues in a stack for playback "on the button") confusing and a nuisance under other circumstances, especially for setting up a desk for busking (IMHO). Tracking similar. Default values, again great at making sure something happens when you raise intensity but default colour of white seems to throw a lot of people. Personally, I set R=G=B=0 as default for all RGB fixtures as a matter of course (and then get confused when I raise intensity and get full on black before remembering that was what I asked for 😁). Whilst having a mini rant... social media may not be the best place to look for help @kgallen and I and a few others watch this forum regularly and there's a lot of expertise here.

Hear hear... Where's the downvote button when you need one ⬇️ I wonder how long until the FLX S is canned - I had slight optimism at the ZerOS 8 launch that it sounded like FLX S would be hanging around for a while (https://www.vari-lite.com/global/news/releases/zeros-8-0) - perhaps not much longer with the 'core' Z88 team all gone now. Still wonder if we'll ever hear from our new Vari-Lite admins on this forum? (it's not too late to introduce yourselves, we don't bite! Would be great to get some of your insights on the future of FLX to allay our concerns!) Signed - a loyal Z88 user

@Davidmk I suspect you are pretty much bang on with all you say. I don't think Vari-Lite are interested in the console business, or any of Zero88's products. I think Zero88 was just a tiny operation that came along with their bigger purchase of Signify (or whatever transient companies bought the stable that included Zero88 on the way). Zero88's Cwmbran manufacturing operation is (/was, if it still exists) pretty much over to subcontract electronics build. They'll make a few Zero88 product batches as and when demand requires it. I suspect that will dwindle and drop off as demand drops and the lack of successor products means the Zero88 brand disappears. This forum will be funded until someone high up in VL realises they are spending money on it and/or the traffic drops off to a level they think there is no need for it any more. We've probably missed the boat but it would be desirable to get the schematics, Bills-of-Materials and if possible software source code out of the remaining Z88 databases and into the "public" domain before VL type "rm -rf /*" on it all and forget it ever existed. The software source code might be tricky as it might contain sub-licensed IP such that it doesn't have a GPL type license, I don't know, this is not my area. I've not heard anything about any new products with the Z88 brand and there is no evidence to date on the beta forum of ZerOS development work post 8.0 (although JonH did suggest there was an ongoing development plan on his leaving speech). But I don't think there is "anyone" left from Z88 to do this. I think Simon, the key software guy, was probably a sub-contractor [I could be wrong], so will have moved on to other ventures to keep paying his mortgage. If he is about, he's been very quiet and hasn't posted on here at all to say "don't panic guys, we're still here (just)". Time will tell. But I'm not holding my breath.

If Vari-lite aren't interested in ZerOS, it would be good if they could put the source code in the public domain so it could be turned onto an open-source project.

Spam seems to be getting worse on the daily! Perhaps some sort of user verification is required?

Hey, so I tested the show file during the final rehearsals on Friday and on two shows today. They work perfectly. Without you, those fixtures wouldn't have been used in this production. Thank you SOOOOOO much, you're the best! ♥ ♥ ♥ All the best from Leipzig Lena

Update as promised: Using the personality in the desk, and when viewing the DMX Output charts under the Z Key, the values corresponding to CMY remained on '0' even after changing colour parameters, or running colour effects etc. Definitely confirmed it was a personality error at this point. So using the inbuilt fixture editor, I took a copy of the existing personality and amended the CMY control channels to be 'Other Colour' control parameters. This worked and enabled the encoders to control the CMY parameters, however colour palettes or picker didn't work as the desk didn't know what colour they actually were. So I then edited the 'copied' personality, changed the 'Other Colour' parameters back to CMY, which then worked as it should have done so in the first place. I now have full control of CMY, using colour palettes or the colour picker! No idea what was going on, but quite the oddity and an annoying time sponge trying to resolve! Either related or unrelated, I also had the desk crash four times throughout plotting, so will forward on the crash reports to the team after the show is done. Thanks again all for suggestions, research, and the created fixture profile @kgallen

Hi @Lena Here you go, all three modes (phew!). Everything is in there including all channel "details". You will find lots of channels under Colour and Beam(shape) so you'll have to rotate through the "pages" of them on your S24. However there is a limitation in what I've created. The FLX S24 will support multi-cell fixtures and the TMH-W555 looks like it could benefit with being defined as a multi-cell fixture for the 36 and 48 channel modes. However the Windows Fixture Editor does not support this (as it's a new console feature). You would need to request such an enhanced fixture definition from Vari-lite (or write one using GDTF which I'm not capable of!!!). I'm not sure if the colour palettes will work in the 36 and 48 channel modes as I've not picked any of the RGBW 1/2/3/4/5/6/7 as "primary". But they should work fine in the 24 channel mode. You'll have to see how you go on in 36/48 channel mode and come back to me if it's a little unworkable - I would need you to tell me which segment 1-7 you want to be "primary". Just put this file on a USB stick and use Load on the console. When you patch it, it will show in red text as a "non-library fixture". Enjoy! (ps there is a lot of info I've had to enter so if you see an error or spelling mistake, let me know) eurolite_tmh-w555.ift

Raise lower effectively emulates moving the faders, which are limited to 8bit. All other calculations for fades etc, are 16bit. I have raised this as issue ZOS-12581 for future consideration.

Just re-reading my initial post it’s a real dogs dinner! I’m glad @Davidmk and @Archie D have brought some clarity to the exercise with the neat use of a chase on the ‘master’ playback. Great work chaps!

@kgallen No worries. My post offered no more than a hint, you went further and @Archie D has gone right into the detail. I think, between us, we've covered this at every level.

Wir freuen uns auf die ersten 2026 ZerOS Workshops für die Vari-Lite FLX S Lichtsteuerungen. 24. Februar 2026 bei Focon Showtechnic, 49504 Lotte/Wersen bei Osnabrück - Infos & Anmeldung 31. März 2026 bei cast C.ADOLPH & RST DISTRIBUTION GmbH, 58099 Hagen - Infos & Anmeldung

Same happens to me, but not for hazer, but for houselights. I would very much like that "exclusive playback" feature.

@SimonH One of those occasions where I am glad to be wrong 😀

It had been set to flash, rather than Go(Fade). I will set back after current show is finished. We have been running the show on one of the sub-masters which works fine. Thanks for the hint.

An ohmmeter won’t help you. The cables don’t have a different dc resistance they have a different ac impedance. The most practical way to tell is from markings on the sheath of the cable that will tell you it’s ’DMX’ or ‘digital’ cable maybe. If it says ‘microphone cable’ it’s not really for DMX use. You can use ‘DMX cable’ for microphones but ideally not ‘microphone cable’ for DMX. (My response coincided with David’s posting, I’ll read that now!).

So now you are into something of a grey area - I fully expect this response to attract comment. It especially needs comment from a sound tech as I'm hazy about that side of things. You can often get away with audio cables for DMX but no-one in their right mind would recommend that because you might not get away with it and you can bet the problems would only be apparent mid show and not at fit-up. The easiest way to tell the difference is to see if it is printed on the cable . 150ohms is not the resistance of the cable it is the impedance. Cables do have a resistance but it is dependant on length and is only important if the cable is meant to carry a current (as in mains cables where it is very important and is part of PAT testing). As far as I can tell from researching it, DMX cables should have an impedance of 150ohm as you said). 110ohm is allowed but not recommended. I'm guessing, but I suspect anything below 110ohm is likely to cause problems. The standard for audio is 110ohm but there is a wide range in use - 60ohm to 150ohm is quoted. Apperently, the main thing for audio is that the source and cable should be low impedance and the sink should be high (e.g. 10,000ohms). I Googled "what is the correct impedance for balanced audio cables" and read the AI response to get this information. This would suggest that a "standard" impedance audio cable would be acceptable for DMX but the really low (below 110ohm) cables would not. You can measure the impedance of cables with the right equipment but you can't use the resistance range of a multimeter. Google "how to measure the impedance of a dmx cable" for ways to do it. Your physics lab techs might be of help in this area. Ultimately it is better to keep your audio and DMX cables apart and mark them with something obvious so you can put them away properly. (That's a big ask in a school I know.) There is a reason why the standard for DMX is 5pin XLRs even though it only needs 3pins and 3pin XLRs are cheaper.

OSC is really useful from my perspective for when you just want to run your show off one main control centre, but not having lights + sound (and possibly projection) all programmed in on a singular machine. If that one machine goes down, you've lost all lights, all sound and all projection. Whereas, if you run lights separately with the computer controlling sound and projection, while a lighting console is controlling LX separately, if the main computer goes down then you still have light on stage and can control that independently. Something like this can be done with OSC via QLab (with Network Messages) however QLab does require a license for this, or using something like Multiplay (another sound + projection cue-based tool) as @Neil Macmillan has used, is another option that is free to use (but still very very good!). So, if you are looking for a cue-based solution and you use a Mac, QLab is probably the best option (you could have a "magic sheet" as @Davidmk has, using Cue Carts within QLab). These "cue carts" can fire Network Messages over OSC to trigger certain cues on the LX console, like a soundboard but for lights. However, if you use Windows, Multiplay is also a good option (not sure about cue carts on it though). If you're on a Mac and instead of using QLab, you want to use Multiplay, you could run it via Wine but this won't run natively on your Mac and I'm not sure if OSC would work with how Wine handles things, but it could be worth a try. Unfortunately QLab on Windows isn't an option as it is developed primarily on the Apple platform, and so relies on Apple infrastructure for features such as AppleScript integration. QLab Network Message Cues - https://qlab.app/docs/v5/networking/network-cues/ QLab Cue Carts - https://qlab.app/docs/v4/general/cue-carts/ If you do use Multiplay, I very much point you to Neil's video! (I used it myself when having a play with OSC over Multiplay to my Phantom ZerOS setup, so thank you very much Neil for making that video). Best of luck with what you want to do with OSC.

I'll have a look when I get home (I fear I may have deleted my bookmark), but that's a good shout

This is why we’re here! Keep asking/sharing and we’ll do our best. If you can help out another user - either directly by asking a question of your own which is answered, or more directly, then even better. That’s how this forum works, especially now the Vari-lite support is minimal.

@Veit0r when adjusting values you want the background of the field above the encoder wheel to be blue not black. Blue means the parameter is tagged. This is the information the console uses to know what to record - it records tagged values. If you click the field to make it have a black background you untag it. The console will then not record the change. Also in the case of reprogramming the default I turn off SmartTag. This is because I wanted to reprogram the RGB default values whilst I had the intensity at zero (and not tagged). SmartTag will only record intensity (at zero) if intensity is zero, it won’t record other tagged parameters (this is related to allowing Move On Dark to work). Hope that clarifies things and you can now have more success with your programming! https://www.zero88.com/manuals/zeros/controlling-fixtures/tagging

@kgallen Correct, although I suspect the processor board isn't custom, more likely an off the shelf unit that has become uneconomical because other customers have moved on. I figured that... The problem with producing FLX is the availability of the processor/screen combination. ZerOS has been shown to run on Rasberry Pi, not only that but an old model of RP. Newer RPs have more muscle than old ones. So it is possible, probable even, that a RP 5 has the capability to run as an FLX The problem with that is interfacing the hardware bits the FLX has and the S doesn't. I speculate that the various peripheral boards inside an FLX actually talk to the processor via USB. We know the fader wing does so its possible the internal faders do as well plus it is the sort of interface an off the shelf board might use. Even back in the day, Zero 88 wouldn't want to develop a whole new protocol so, even if it isn't USB, it will be something for which an RP hat might already be available. So, assuming the hardware interfaces are USB, or something that someone in the community could sort out with widely available circuitry (OK, that might not be possible), then, with access to the source code, you have to identify how it 'knows' what hardware it is running on and all the places it uses that information. For that, you need a software specialist. I'm rusty, and it would probably be in a language I'm not familiar with but I reckon I could give that a go and I'd bet I'm not alone. I don't know the background of everyone in this and the Facebook forums but, given that about half the LX techs I know have backgrounds in IT and/or telecommunications the expertise is out there. The flaw in this is that Vari-Lite have paid for the ZerOS intellectual property and are highly unlikely to give it away for free. Plus they wouldn't want all the support calls which would result from the unofficial versions that would spring up as a result. The other thing is why has there been no announcement of a Pi based FLX S+ to replace the full FLX? Is it that it is much harder than I have assumed or that they bought Zero 88 for the other products?

Darren @DMH, Ryan @RJP any thoughts on the matter, is this a bug? I also cross posted to the Facebook group, someone called Bobby who also appears to work at Vari-lite left me with no solution either. Disappointed at the new 'service' level!

Have fixed.. full update tonight. Thanks both!

@Davidmk Thank you for your response. I'm not back in the theatre until Tuesday evening but will check out the Event Monitor then to see if anything is reaching the desk. All network connections are wired and the PC doesn't have WIFI so shouldn't be a network issue but you never know with networking.

@kgallen Yep, seen it but busy ATM. @saitekx830 Settings both ends look good will give it some thought later.

Thanks guys, saving a group with intensity is a great help. Confirmed it doesn't link the group level into the cue, so unlike a palette, changes to the Group levels don't affect existing cues. I also found the trick to turn off Smart Tag so I can save lights into the Group with zero intensity. Allowed me to clean up existing cues that were a bit randomly balanced so they're all identical. S

My sentiments exactly. Keith, Edward and now you. My disappointment knows no bounds.

As far as I’m aware you can select the fixture and then edit with the on-console editor. https://www.zero88.com/manuals/zeros/patching/add-fixtures/edit-export

Far and away my biggest want is Mac Phantom zerOS. My Apple silicon Mac runs Capture at 100+ fps without the fan even turning on! Phantom is pretty stable under Parallels 19 running side-by-side on the same monitor with Capture, but there are some glitchy bits that I assume are due to the emulation.