What are we doing wrong or Feature Request: Black Cue

Hi all,


I always have Problems getting a decent BlackOut cue without some LEDs changing colors while dimming down the intensity.

What exactly can I do to prevent this? I tried Automark On/Off, Block, etc. (I am on an Element 40 btw., but had the same problems with an ION, all newest software)

I also talked to several of my colleagues here, all years of experience with ETC Eos Software, they all have the same problems with Move-in-black features/automark.

Sometimes the Moving heads change posistion while going to the next black and so on.

What are we all doing wrong?

Is there a possiblity to make a softkey for us dummies that marks a CUE as "BLACKOUT" - meaning there are no changes until all intensity channel have reached 0 and only then the non-intenstiy parameters change?

Any help is appreciated....

  • 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
  • I should add that the moves you are seeing are not created from being marked. The AutoMark function has no affect on a Live Move (NIP's moving while fading). It is possible that you will create a live move if the fixture is up and does not fade to zero before it's next NIP change. A light cannot mark if it is above Zero.

    I sometimes notice a light that is fading to 0 and then needs to mark for the next cue i will see it move as it will mark as soon the fixture hits 0. Now i am not sure you can do this on the Element but if that is the case try putting a delay on the NIP's time at the cue level. If a zero count Blackout delay the NIP's 1 second.
  • Hi Ed,

    thanks for your input.
    There was a "L", so I tried it with the "@ enter Out" - after that I had a "+" in the MV column, so I have now both Live and Dark moves...
    But as far as I could try it out now, there was no change - it still flashes white (that is my special problem this time - a red background not fading out but flashing over white to fade out...)
    I use tracking mode...

    I find it a quite disturbing thought to change into Blind for every black...
    Usually we don't have much time to program, so in Live I just do it as you said - select all active and out them...
    I know how tracking works, but somehow it just won't work with blackouts.
    The funny thing is, that none of my colleagues here can make it work every time.
    Usually we try around a little bit, but most of the times we delete the problematic cues and make them new....

    Bye
    Orlando
  • sorry you are having problems still. If you send your show file i would be happy to have a look at it. Like in blind recording a blackout in live would not not create a live move unless specifically told to.
  • The underlying issue is that you've recorded unwanted colour information in your Blackout, so the LEDs change colour while fading out - because that's what they were told to do.

    To fix an existing cue, simply remove all the NIPs from the Blackout cue:
    X [Thru] Y {All NPs} @ Enter.
    - If you do this in Live, don't forget to [Update] the cue.

    Recording records all manual (red) data (unless otherwise specified).
    So in short, don't touch the colour unless you want a new colour.

    If you try a new colour and decide you don't like it, put it back to tracked values before recording/updating - eg x [thru] Y {color} Sneak Enter.
    If you Home it instead, you'll be recording Home - usually White!

  • 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...
Related