kgallen

You sound like you know what you're doing - but just to check, the colour fade time listed in the colour column on the output/playback screen is non-zero isn't it? I think the default is 3.0 seconds. I'm guessing your issue is something else, but just wanted to check the obvious one...! Kevin

Hi Eric, I'd stay with 7.9.4 for your shows. Do you have effects? Migrating to 7.9.5 without time to review what the impact of 7.9.5 might be on your effects would not be wise in the middle of your production run. Anyway I had a desk freeze with 7.9.5 the other day so there is no guarantee your crash concern has gone away. Yes, I experienced a number of desk lockups too on FLX with 7.9.4. I'm in a production run now on 7.9.5 and hoping for no more misbehaviour (dress rehearsal went ok last night)... Good luck! Kevin

Not if it's the first cue in your stack. Subsequent cues, if the light is dark in cue n and lit at a different position in cue n+1, then the light should "Move on dark" after cue n has run and thus when it lights in cue n+1 it is in the correct place already. Cue n can't be a snapshot (blocking) cue. If the light is lit in cue n and also in cue n+1 then there is no Move on Dark opportunity. You would need a point cue ("n.5") to create a "marking cue" where the light is dark and the move can take place. If you wanted the move then light behaviour on say a UDK then I don't know if you can do that, as it's a two-step process - move then light. (Sorry no UDKs on FLX S). Kevin

Hi Edward. No I haven't. The FLX is at the venue now. It is Tech tomorrow I'll aim to give it a go. But what's your view on my initial observation? Thanks Kevin

Cheers Peachy good call I’ll give that a go 👍 Kevin

Bug probably. (Moved my other bug reports to a thread in the ZerOS Beta Test Forum).

Hi Eric, I am also without some answers. I hear that staff may be at the ABTT Conference and they may also be having IT issues. Kevin

Ar*e. Thanks Simon...

You need to patch each cell as a separate fixture plus another "fixture" for any common channels. If you have a search on the ZerOS/FLX/Solution forums it's asked quite a lot on there, so there are some comments from the Z88 chaps.

Poke... LX plot this week, so would appreciate knowing if I'm doing something wrong or if there's a potential bug and I need to go about this a different way. Thanks.

Thanks Jon. I think I have the basis of a usable "sea" now. Same snag recording it as ICBE as this thread though.

I'm still confused by how I record an Effect that has the ICBPE components I want and not the ones I don't. In this example I don't want Position recording. I just have my movers pointing where I can see the Effect I'm trying to create, not where they will be if/when I use this Effect palette. OK so I'm trying to get myself a decent Fire effect. I'm using 7.9.5. I point the movers where I can see the result. The Position is not required as part of the Effects palette - I want the colour, the beamshape and the effect attributes. The intensity too if I must. For the purposes of creating effect I put the fixtures to intensity full. I trigger the 7.9.5 Fire effect. I get the flickering and adjust up the speed to where I want it. But the effect is washed out (the fixtures started from Home). So I go to colour and take out all the blue and half of the green, which leaves me at Red=255, Green=80, Blue=0 (and other colours White, Amber=0). I go to Beamshape and get that as required. It now looks (C/B/E) how I want it. So I want to dump this to an Effects palette so I can recall it. From previous advice I know I need to do a Record All because I want to trap multiple attributes (ICBE). So Shift+Record to get up the Record Options dialogue box. By default Snapshot is enabled (red bar), so I can't adjust much else. For now I'll say if I use these default options, I can save the Effects palette and it's labelled as ICBPE and if I clean up then trigger it I get what I want but including the mover position, which I don't want to record to the palette - but at least I know it "works". So I know I need to customise the Record All to avoid recording the P. Let's do it again. I get the Effect back how I want it. So on the Record All dialogue, I turn off Snapshot (neither Snapshot or Smart Tag are lit red). This means that I can toggle the other buttons. So I set Intensity, Colour, Beamshape and Effect to red (on) and Position to blue (off). I tap the palette. It's labelled as "E". So it hasn't recorded the I, C or B elements. If I clean up and recall the palette: it's junk. The only parts I get from it are the flicker and the speed (so the "E" part). The colour is the Home default - white. The beamshape settings are not as I set them, they are also Home defaults. I'm not surprised - the palette is labelled as "E" when I need it to contain "ICBE". I've tried lots of other combinations on the Record Options form, trying smart tag, having some buttons with the green bar (what's that?). Trying Selected Fixtures and Tagged Fixtures. So how? Why is this (still) so hard/confusing? What am I not doing correctly? Thanks, Kevin The attached Record Option dialogue shows what I want to record: selected fixtures, I/C/B/E. Not P. But it doesn't. Second picture shows two Effects palettes. The "Pyre" one, recorded with these settings says "E" - not ICBE. The "Pyre all" is from Snapshot settings and says ICBPE. These attribute labels do reflect what's in there.

I need to create an effect on RGBW LEDs to depict (gentle) movement of the sea. In this instance I'll have 4 mover wash LEDs and 3 non-mover LEDs as backlights. ZerOS 7.9.5. I think this would be a colour effect (and maybe but not necessarily a position effect for the movers - gentle side to side swoosh?) that uses probably an offset sine function to colour fade some mid-blues, paler-blues and whites. Can I pick your brains (Edward) on how this could be set up (then saved as an effect palette I presume)? If it's good, maybe this could be added to the Auto Effects palette for 7.9.6 as "Water" to go with the new "Fire" 😊 Thanks as ever! Kevin ps My movers don't have any usable gobo functions for this - they are Showtec Shark Wash and Shark Combi-Spot (you made me the fixture definition).

I just downloaded the Effects definition file from Edward's link, so it's certainly there now and downloadable when you're logged in 👍

Well I'm glad you posted that last one Edward. I didn't want my Forum login to be closed down by posting same...! 🤣

Well, Nathanael, welcome from us all! Them's some big 'ole boots (Edward) you're gonna be "competing" with!

So "Nathanael - Zero 88 - 1 post". Gonna introduce yourself? 👍

The elephant in the room he's talking about is Frogger.

I hope this isn't a "Friday afternoon job" 😆 Well done team - I bet you're glad to see the back of that one! 😁

I should know that (from an earlier explanation from Edward!)... thanks for the clarification! But to Mac's requirement of non-white-colour+white, is this possible with an Auto Palette --> so in prospective 7.9.5 can we do "sparkle" with an RGB mix base colour? (True, I could use my brain, but at "non-theatre-work" at the moment so it's easier to ask those who know 😋)

Jon, If Mac wants to RGB mix his own colour (he said "say red") can this be achieved with any of the "step off" effects and still get the colour+white combination - rather than say orange+green which I think is what you'd get if you dialled in green to the red-step-off effect. Thanks!

Think that would be the ‘red step off’ effect. Edward will elaborate more I’m sure!

Hi Edward, Yes, agreed, you'd run out of numbers one side or the other with a non-zero offset, that's implicit in having this ability. DMX-wise this is the addition of a positive or negative number ("the corrective offset") to the prospective DMX value then saturated (to 0 or 255 or 65535) to prevent under- or overflow of the 8- or 16-bit DMX value that is ultimately transmitted to the fixture. The harder bit is probably the UI definition to allow the user to get the "corrective offset". The user would want to select the fixture, dial the pan (or tilt) until the fixture was "aligned", and then capture the difference between the live and the "perfect" value (probably only have the home value available to use for this) to calculate that offset which gets stored against the fixture. As ever, the devil will be in the detail because this "offset" would need to work properly when doing fan operations - although maybe that just comes out in the maths. I guess you already have saturation code anyway since when fanning, some fixtures may end-stop their DMX values whilst other fixtures still have travel. Again, as with fanning, when you come back the other way, the fixture has to "pick up" consistent with the fan position. I guess internally the software works on a higher bit width then "windows" down to the 8/16 bit DMX value that's transmitted. Anyway I digress and should stop waffling on about the software design...! Back to Eric's questions! Thanks! Kevin

Yes but nothing there says you can define a ‘corrective offset’ which is what I think you’re after. Having a modified home position does not adjust the absolute position programmed in a cue.