All Activity

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 😉

Sorry for the slow reply! It's rising the two numbers simultaneously, so it is making some attempt at playing across the two channels. Just the two numbers duplicate each other. Perhaps the S24 is purely an 8 bit intensity setup and it just fakes being 16 bit to support the profiles. I do see on other channels, such as pan/tilt etc. it does use the full range. Something I'll need to try perhaps is to make a profile which has a 16 bit setting which isn't intensity (some other option such as a beam setting) and try to see if it is able to move those settings on a 16 bit fade. Just makes it a bit inconvenient that the fader wouldn't really do anything beyond selecting the light.

@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.

As I was about to post, I realised I'd not checked the patching. I found the Lantas have an updated patch profile so re-patched but the error remains. I've re-posted above. S.

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?

I have some Lanta Fireball par64 quad rgbw parcans on my rig which, when set to the same colour palette are receiving different dmx values. Our Panto baddie always has his own colour but it changes from year to year. I saved a new palette "Baddie Green", then a few options to choose from (nos 31-34) , using Lee filters, see photos. If I use palettes 31-34 I get consistent colour on all lights, but I'd have to update each cue if I want to change it. If I <update> Baddie_green with the selected colour, then apply it to my lights, I get different dmx values output to different lights. On the photo 1, the six lights start at dmx 151 and the 1st intensity values are set to 10, 20, 30 etc. In that test the 3rd light gets different values. I can reproduce this when I use any of the renamed colour palettes e.g Undersea_blue. In that case in photo2, lights 1-3 get 120-255-0-43 and lights 4-6 get 120-212-0-43. I noticed this as I've been programming the show, where one light was wrong. When I corrected it, all seemed fine for a while then it reverted to the error. Any ideas anyone? Simon

The order you start things in may be significant. My guess is desk first is best but it's by no means certain.

@Davidmk @Phil Kiernan Thank you both for your suggestions. Double checked everything last night but still wasn't getting anything on the Event Monitor. Ended up doing a full reset on the desk and starting a new SCS project and now everything is working correctly. Guess it was one of those strange glitches that will remain a mystery.

I'm putting this here as it probably applies to a number of legacy desks. There are a few posts re desks crashing or failing to boot where the recommended action is to "reseat the compact flash". I'm working on a Solution desk which failed to boot 1st time last winter (usually fine on 2nd attempt). It self-resolved before I could do anything then behaved normally ever since ... until this week. I've opened up & found the compact flash card; question how to remove. I've only ever slid cards into cameras etc, but it looks like this is a different kind of mount. Do I prise the card up out of the holder with a sharp implement or what? I was intending to hoik it out for a clean but is a good push sufficient? Simon

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).

It's been a long time since my previous post. The upshot of the situation is that the rack has been swapped out with the fourth rack in the rig leaving 36 ways rather than the 48 of the original install. I now have to re-address the rack as DMX 1-12 but am locked out of the control unit by a code that no body at the school has a record of. I will have to try and find out what the over ride code is.

Try the following command in the SCS Control Send Cue, Device = zeros, OSC Message = /zeros/cue/go/4 . If you put /zeros/cue/go it will operate the next cue in the stack. SCS setup - Production Properties, Devices, Control Send , Device Type=Network Out, Name used in cues=zeros. In the lower panel Remote Device=Other OSC Device, Network Protocol = UDP (defaults to TCP), Network Role = SCS is a network Client, Dummy Connection = unticked, IP address matches the Desk , Port = 8830

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.

@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.

So, @saitekx830, you seem to be doing the right things. If I was in this position I'd probably run Netscan (other network scanners are available) from the PC running your cueing software to just check that it can see itself and the desk. I'd expect that to work if the remote app is working but you never know. I use wired connections and find it helpful to disable WiFi to make sure the software isn't trying to use the wrong network. I guess, if you are using WiFi, you could disable any wired connections. Next, I'd go to the desk and after (like you) checking the network connections, I'd go to event monitor and send a few OSC commands. I do find that the first couple after switch on don't appear on the monitor (fine from about the 4th command and continues fine as long as the connection remains up) Now there are three possibilities, if you commands are not appearing then there is something wrong with the connection between your software and the desk, if they are appearing but with errors then they are just plain wrong (format, invalid commands or something) and if they appear without errors but don't do anything then they are valid but the thing (cue, playback, whatever) they should fire doesn't exist. If that didn't solve it then I guess the next step is to consult your neighbourhood witch or sorcerer. 😀

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

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!

Hi Everyone. Has anyone had any experience in using OSC to trigger the Master Playback cues on the FLX S48. All the network settings are configured and OSC is enabled in the settings as can be seen in the images. We know the network is operating correctly as we can control the FLX S48 using the Remote APP. We have tried using SCS control software as well as terminal software but nothing seems to be working. Have tried the following commands: /zeros/cue/go /zeros/cue/go/0/4 /zeros/playback/go Any advice would be greatly received.

Yup, couldn't agree more. I guess the days of technical support here on the forum from official sources are done, hopefully we'll be shown otherwise.

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).

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...!

I have some 16 bit capable fixtures which have channel 1 and 2 for intensity. I hoped to get some nicer smoother slow fade ups (at least to the capability of the fixture) by switching to 16 bit mode, but I don't seem to be getting a true 16 bit. So to follow, I bring the fader for the fixture to 100% then store to a playback. I then go into the setup for the playback, raise and lower tab then change the raise time to, for example, 255 seconds. When I watch the dmx output, I would expect to see the 1st channel stay at zero while the 2nd channel goes through 0-255 in 1 second, then the 2nd channel would reset to zero as the 1st channel increments to 1 and so continuing till in 255 seconds they both read 255 and 255. Instead, they increment as 0,0; 1,1; 2,2; 3,3; 4,4 and so on till 255,255 - in effect, only 8 bit duplicated over two channels as far as I can see. Am I missing something? I understand that the board only allows 0-100% control via the faders, in 1% increments, so it can never achieve even 8 bit control from a fader, but was hoping it may be able to automate it via raise time. For reference, I am on the latest version 8 firmware (build 8), running a FLX S24.

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