kgallen

I’ve been reporting the spam posts/users as soon as I see them. I don’t know if the corresponding report emails are being seen or triggering the cleanup action. From what @Davidmk is saying, possibly not!

No, but I have now! The Intensity Wheel indeed works as 16-bit - although it's stepped so it's not smooth but certainly the LSB/MSB behave as a 16-bit 'pair'.

Hi @Neil Macmillan I had a play with my FLX (ZerOS 8.0) and a Cameo Q-Spot 40 which has 16-bit dimmer. The fixture definition was written by myself. I use the Z key to access the DMX Outputs tab to look at the DMX values sent to the fixture on addresses 1 and 2 where the fixture MSB and LSB intensity channels sit. If I use the channel fader to manually play with the intensity, at 0% I see 0/0 (MSB/LSB). As I move the fader up the LSB goes to 128 and the MSB increments. When I get to 100% I see 255/255. Instead, making the desk do the dimming, I set Programmer Time on at 10:00 (10 minutes) and type syntax 1@@. I now see the LSB incrementing from 0-255 and the MSB increment when LSB is 255. Similarly if I do clear-clear I see the LSB count down from 255 to 0 then the MSB decrement then the LSB 255 to 0 again. All the way down to 0/0. So when the desk does the dimming, true 16-bit dimming is performed. When the fader is used, the dimming is understandably simplified - that fader doesn’t have 16-bit resolution! Conclusion - 16-bit intensity dimming works as expected. Hope that helps.

I doubt it (but I need to do the research to substantiate that, so will endeavour to find "my light")! Being able to define intensity as 16-bit has been in the "old" fixture editor from well before FLX series desks were designed and I doubt they would have not written the software to support that on their latest range of consoles. If it was just 8 bit it would just use the MSB channel and leave the LSB at 0. Needs some more investigation unless another user already knows the answer (you never know, Edward or Jon might answer as they are still lurking 😉

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!

You could "Report" it and get the new mods to delete the thread. I don't think a user can delete - at least I don't find any buttons suitably named! Alternatively - anything useful you can share with the community?

Given the serial number, in theory if the database still exists and the will is there with the new support arrangements, Vari-lite should be able to give you a master code (I would expect, but I don’t have experience of this product).

Welcome! If I recall correctly, there are a few users on here with fairly elaborate OSC setups working. Typically I can’t find a good thread to link (there are some in the Beta forum but you won’t have access to that). Have a search of the forum, especially the FLX forum. Hopefully one of those users will be along to help. @Davidmk is probably one to look out for!

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…

Have you patched a fixture profile that has the intensity channels defined as 16-bit? i.e. the exact same correct 16-bit mode on the fixture and on the desk? Otherwise most fixtures have the intensity MSB as the "intensity" channel and you'll get 8-bit dimming as the "fine" LSB will just stay at 0. I think I might have the odd fixture with 16-bit intensity, maybe I could play sometime if I can find which one it is...!

This video should help:

I have a feeling locking stops programming changes but allows an operator to run a show. Could be wrong. Yea, looks (locks!) like it: https://www.zero88.com/manuals/zeros/z-key/lock-2

Eeeeeek! No pressure! 😆

@Jon Hole what’s the current policy regarding library releases and support for legacy ZerOS and pre-ZerOS consoles? I see on the Vari-lite website that there is no separate library release, the latest is bundled with ZerOS and only compatible with ZerOS 7.14.1 and later. There used to be a separate library release file for each of ZerOS (including pre 7.14.1) and other legacy consoles like Jester (and Frog, but I’m aware of the splitting-for-floppy issue). I realise support resource might be a bit tight at the moment but what is the current Vari-lite policy on this? Maybe you could make a statement on the main forum about this. If we have to ‘DIY’ from now on then at least we’ll know. Thanks, Kevin

@Charlie Newman S24 doesn't have a DVI-D monitor port (only S48 and full FLX). However I agree it's not clear what "right side" is, if the console is still otherwise full operable from the Monitor App. @LIGHTING can you clarify please? Is the console fully working except for the internal touch screen? I understand internal touchscreen failures are uncomfortably common on S24. If yours has failed and it's still in warranty (up to 3 years old), then you need an urgent service request entering with your supplier. If the console is over 3 years old, then Zero88 might still help but I've also heard that the touchscreen is a standard component used with Raspberry Pi boards, but just with some extra mounting parts that could be transferred over. However I have no other knowledge or experience of this.

@Klang Hi Ben. Here we go. Details and colour definitions, the whole shooting match. Phew! Any issues with it, let me know. ERA150Wash.ift

I think you’re right for FLX S (sorry!).

I assume you’ve already tried to reseat any ribbon cables, and extracted and reseated any SD cards. If there is a coin cell battery put in a new one.

Hi Ben, @Klang No problem. It’s quite a big one but I’ll try and get it done tonight and uploaded here. I’ll drop you a PM when it’s done. Cheers, Kevin

Welcome @Klang ! Point me at the manual pdf and which modes are your priority and I’ll have a bash tonight. ETA: assume it’s this one. Looks like there is just an 18 channel mode? Yea… with Edward and Keith leaving and Jon busy with his day job, support isn’t erm… what we’ve been used to… I hope it improves before too much customer damage is done. Kevin

Hi @Harold and welcome! Check if the Page Handover setting (change to Enabled) helps out. https://www.zero88.com/manuals/zeros/setup/settings/operational#page Regardless it seems like the behaviour you observe is a little unhelpful so hopefully @Jon Hole will take a look at your report and see if there is an issue there.

Just select your 4 spots (order matters) and light them, Effect, pick chase1/4, use encoders to set speed and size to adjust depth of fade. Select Forwards/Backwards as required. I’d record that into a new effect palette so you can grab it quickly. (Won’t store the intensity unless you green stripe that option in the record settings).

This forum is like a train. Nothing for months then everyone is prepping for a Christmas show 🤣. At least Santa is back from his holidays to help us out. 😎

Put the speed parameter onto a playback fader and do it by hand? I think you can do that… or is that Global Tap Tempo… 🤔

First I would check cabling, distribution and DMX termination. If possible try the other DMX output socket on the console (assuming you’re not already using it).