What are we doing wrong or Feature Request: Black Cue

My guess is that the Non Intensity Parameters (NIP's) are not being tracked thru to the next cue. My guess is that there is a "L" in the MV column on the PSD. that means that the NIP's are moving while the light is fading. In blind if you go to the cue that is your blackout and select the channels that are changing color (moving) in the cue and hit [@] [Enter] [Out] that will pull the values from previous cue and not fade color in your move.

To solve this in the future when you are in a cue and you make changes you what to make sure you are tracking the NIP's. If you are in cue only mode they will not track and move in the next cue if the value is different.

When i record a blackout i usually do it in blind. I would start in the Cue I wish to blackout and insert the the cue Number you wish to be the blackout after. [cue] # [enter]confirm, if it asks, and hit [select active] [out] this will set just the intensity values to zero and track the NIP's

If you are in tracking mode and inserting the cue in an existing list and do not want to track the intensity past the black out use the syntax [select active] [Cue Only] [out]. There are other ways to achieve the same results but for me this is the quickest and safest while people are working on stage.

Remember the Eos family is a tracking console. the mode you are working in (Cue Only/Tracking) affects how cues are recorded and updated. Generally speaking you want NIP's to track (though not always ] I find the following syntax to be helpful when updating a cue that you and want to update intensity Cue Only while working with NIP's {All NIPs} [Update] [Track] [enter] then [Update] [Cue Only] [enter]

Working with NIP's takes a bit of thinking about how when they move and mark and i recommend you watch this short video on how tracking works on the Eos family.

https://www.youtube.com/watch?v=JsrJ707cT0c&index=6&list=PLC95CA65C335B6376

To add, if you are adding a Block flag to a cue, you can add just an intensity block with [shift]+[block]. That lets any changes to NIP's propagate through blackouts while still blocking the intensities. I think I almost always call for Intensity Blocks now.

If you are only seeing the issue with LED's, you may also want to check that the fixture and console modes match. If a fixture has a virtual intensity mode, I find better results switching to direct color control and letting Eos handle the virtual intensity.

-Josh

Thanks again for all the input - I try to get my hands on the console later this day...
I will report...

I tried
X [Thru] Y {All NPs} @ Enter
in Live - it worked very good
but as soon as I hit Update, the behaviour went back to the wrong setting...

I tried it with Block, without Block, with and without Automark - all combinations I could think of....

Well this show is over anyway, so we'll just delete it. I'll save it on a USB stick, and upload it here - if I find out how to do that...

Bye
Orlando

P.S. A softkey as suggested in my initial question would be great.

Here it is - The Problen ist the transition between cue 50.8 and cue 51..

Dings ACHTung 2015-05-22 15-15-36.esf

I can see a live move as channels 75 Thru 80 fade out in Q 50.7.

Cue 50.8 into Cue 51, channels 81 Thru 86 fade out over 0.1 seconds and then change colour. What you maybe seeing is the channels not fully out after 0.1 (which is strange with LED's) so you see the colour params changing 0.1 seconds after you press Go.

To fix this problem (or check it is the problem) delay the colour time on Cue 51. [Color] [Delay] [1], the channels will now fade over 0.1, then wait 1 second and then change colour over 0.1.

I've not used these the LED cyc units so I don't know if they would have this problem.

Did you try changing the timing channel to 0? I know the suggested default and recommended is 255, but if it has a "dimmer curve" on the intensity, you would see this behaviour (has bit me more than once). There are other "live moves," but the Cue in question semms to be programmed correctly. Best of luck on the next show.

Jay

Hi all,
I did a few tests and it looks like the behaviour was due to the LEDs, not the desk.
I changed the timing to 20sec and there you could see it properly. the intensity went down in 20secs and then the color started changing - which took another 20secs (in black)...

Thanks everyone for your help...

Hi all,
I did a few tests and it looks like the behaviour was due to the LEDs, not the desk.
I changed the timing to 20sec and there you could see it properly. the intensity went down in 20secs and then the color started changing - which took another 20secs (in black)...

Thanks everyone for your help...