kgallen

My explanation was terrible and probably technically incorrect, but it feels like the cause. Probably you will have to change the Release on Lower setting on your Zoom fader too. The other point about the Zoom fader is the beam/shape parameter will be LTP, so if any other playback controls the zoom of these fixtures then your Zoom fader will be "out of date". Hopefully Edward can clarify!

It might also be that Release on Lower is set on the Intensity playback, this means once lowered the console is no longer controlling the fixture (i.e. zoom) from the playbacks.

Ummmm ok. Care to provide just a …little more info? Can’t do nuffin’ for you with that report matey.

Pretty sure it's limited by channel count, ie. 512 for 1 universe, 1024 for 2. And then on the FLX S, because you don't have syntax you use the flash buttons for channel selection, so you can't access more than 48/96 fixtures. ...and can FLX S actually be used for live tracking FLX backup? i.e. is that feature supported on FLX S? Unless you meant "backup" in the sense of another physical desk you could swap in rather than as an active tracking backup... (Probably you did, I'm over reading into it...!)

You need two cues with the different fade times for each set of lights related to the room and garden lighting. Be sure to record with tracking (i.e. don't record snapshot cues). On the second cue (say the garden lights), edit its setup to make it start with the first cue (room lights). This should be in the Cue Settings under Trigger (or something like that!). Here: https://www.zero88.com/manuals/zeros/cues-playbacks/cue-settings/cue-triggers Use: Auto (with previous cue)

Me too! (Hence the manual!) 😆

Intensity palette - uses groups. You’ll have to check the manual but I think you just record your group with intensities set then double tap the group palette to recall.

This is if RDM is on (and desired on) but you have some fixtures that misbehave - because they don’t decode the DMX start code as they should and read RDM packets as if they are DMX packets. Hopefully that is ruled out here as RigSync (AKA RDM) is turned off.

On top of what @Davidmk says, it might also be worth disabling RigSync in Setup to see if that stabilises things.

Yup. on your other playbacks you’ll need to decide if you want ‘Release on lower’ or not. Probably you do. setup+playback button There are other details like only record in your other playbacks stuff you deliberately want to control because C/B/S/P will be LTP and intensity probably HTP. For most purposes this will mean having tracking enabled and probably SmartTag - probably avoiding Snapshot!

@The Vault Arts Centre How's it going?

I'll try and find some related threads as this is asked a bit. Edward or Jon will probably answer properly when they come along. This is probably the most obvious thread: (Ignore my ramblings at the beginning).

I hoped it might have been posted last night so you had something to look at this morning... 🙃

Have you got the colour fade time at 0s (snap) on those cues that aren't intensity fading? Attach your showfile here.

Thanks Edward, better links than mine!

Hi Gabriel, Welcome to the Forum. The Martin Allure already appears to be in the library, for Jester, here: Legacy Console Library Look for "McAlPrBa.ift" and "McAlPrEx.ift" - in fact I'll attach them to this post - I think you just need to put them onto a USB stick and load them into the Jester ML. If you want to download the whole gft41 library file it can be found at this link. Otherwise, for a fixture profile, you need to follow the process here: https://zero88.com/library#support The Jester support page is here: https://zero88.com/control/jester Instructions for Jester ML libraries are here: https://zero88.com/storage/downloads/ab019f28-de03-4bc8-9cfe-39426850eb1d/Jester-MLTL-Fixture-Library-Update.pdf If this doesn't get you sorted then I'm sure Edward will help you out first thing in the morning. McAlPrBa.ift McAlPrEx.ift

We're expecting this in the next month or so. This is "multi-cell fixture" support. Keep 'em peeled for ZerOS 7.10 on this site. However unless you want to do fancy things with multi-cell effects then you will be fine patching and using as @DALX suggests. (Note: You will consume more of your 48 fixture slots on your FLX S24 if you instead want individual cell control, so the new ZerOS version will be useful for you.)

DMX - just daisy-chain in to out as you've already done, starting at the FLX S24, in and out of each fixture. Ideally you would add a DMX terminator on the end, but for getting going you should be fine without. Note you should aim to use cables that are designed for DMX, not microphone cables (although I suspect your fixtures have the official 5-pin XLR connection which would preclude you using audio cables). See also this Wikipedia article on DMX although you don't need to understand all of the nitty-gritty technical details, just the basic idea and setup. Also have a brief look at RDM as it sounds like your fixtures have some sort of implementation - however you may be better using a manual setup as Edward describes, at least until you get the hang of things. Regards your fixtures, Master will definitely be wrong. If there are no other options, then use Slave. If you are completely new to this then consider joining the Blueroom Technical Forum - this is a UK-based technical theatre forum. There is a Beginners section where you can ask basic questions without getting ridiculed.

We're equally sad. It freaked me out as after my reply the thread said it was unread and you'd edited it at *exactly* the same time. And so you had...! ...and I hadn't arrived here from an email notification, just happened to refresh the page, so it's not like we both got the email and decided to reply! Spoooky...

Wot he said ^^^^^ 🤣

A blocked value is one that stops any tracking ("purple" value) from an earlier cue. If you record a cue using SHIFT+RECORD then you will get a "snapshot" cue which records everything and thus blocks tracking and effectively restarts any tracking from that snapshot cue. The downside of snapshot (blocking) cues is they also block Move On Dark which is not usually a good thing if you have anything mechanical which needs to "prep" for a later cue. Examples are moving lights, colour scrollers, gobo rotators.

Hi @Edward Z88, thanks. Do you recall, was this the same issue with my FLX last year (when I came over to Cwmbran)? I don't remember if we recovered it prior to me leaving the console with you for service. If so do we know why this corruption occurs?

@Takuya Chinen, @Edward Z88 Is the solution shareable? It may be of interest for other users. 🙂

One other "minor" item we've spoken about before: some sort of "version control" on fixture profiles so we know which of our "identically named" fixture definitions are actually being used by the showfile. Current solution is when creating or updating definitions we have to keep putting something in the name like "v2" or "v3". This is a real pain when debugging/updating a new fixture definition as you're never sure what the desk is using!