• Date
    alexphillip85
  • Date
  • Replies 6 replies
  • Subscribers 184 subscribers
  • Views 6300 views
  • Users 0 members are here

Blue Numbers Revealed!

Haha. Okay sorry for the dramatic tagline.

 

Here's a question. Since I've started programming the Eos, I have from time to time come across the dreaded blue zeros : ) But I have also been recently having to clean up some situations where I have had blued out non-intensity parameters, and have created color or beam or focus times by simply @Entering a unit or by putting it back in it's same preset.

It seems like this mostly happens when I should be creating a partial block on a non intensity parameter.

 

Blue Zeros seem to be happening the first time a channel gets used. This makes some sense because it is the first time the channel is being stored (I see it in my first Block Cues a lot).  But I've heard of people making show files with like a .2 cue with everything in it in order to get rid of this. Is anyone else doing this? Also, I've always been able to fix the blue NP's problems by @Entering something in blind. Or by putting it back in its preset and updating, but it seems like extra keystrokes. Any insights into why we occasionally get blue values when nothing is changing between cues? It's happened to me both with moving lights parameter presets, and with mostly hue and saturation with color changing fixtures. I wouldn't mind the blue values, but the added non intensity fade times are no fun to look at....

 

Alex

--------------

Lightboard Operator

Alley Theatre

Houston TX

  • Alex, the blue zero only found in the first cue a channel enters a cue list, and it does not have an intensity value.  We force a zero there, and because 0 is a higher value than "null", the value is displayed in blue.  If you do not want this behavior, my suggestion would be to store using record only instead - as long as you understand that record only will only store manual values.  

    You can go into blind and [at] [enter] the intensity of those channels to make the zero disappear.  HOWEVER, that will have the following ramifications.  Let's say cue 1 is your first cue.   You set the scrollers into a position and record cue 1.  The blue zeros appear.  Those lights don't come active until cue 5.  You go to blind, select the scroller channels and press [intensity] [at] [enter] to remove the dreaded blue zeros.   

    You then store those lights to another cue list.  And then [Go to Cue] [1] [/] [2].  Those lights will stay active from the secondary cue list, because you haven't commanded them to a level in cue 1/2.  As long as you are good with that.

    :-)

    a

     

  • in reply to Anne Valentino

    Anne-

     

    I'm not so concerned about the blue zeros. That makes sense to me. Although I do still wonder if anyone else has been making a cue before their preshow which has all fixtures active in it in order to not see this ever. My real question regards non-intensity parameters for moving lights and color changing instruments which have gone blue when i believe I should be creating partial blocks.

     

    I actually just had this happen. So here's what happened. We were in rehearsal reblocking a sequence. We were in cue 25 and needed to make a new cue 29. In Cue 25 we only changed intensity parameters on conventional instruments. Then we rerecorded over cue 29. When we completed this, fixture 384, a VL 1000 had it's hue and saturation in blue and we had created a color time on our cue 29, despite the fact the values weren't changing. I had to hit blind 384 {color} @ Enter and reload the cue to keep going. It would've made sense to me that we made a partial block on all NP's but odd that we just created a blue hue and sat, and a color tme...

     

    It was early in the show and the fixture hadn't come up yet, but it has values throughout the show...

     

    Any ideas?

     

    Alex

    --------------

    Lightboard Operator

    Alley Theatre

    Houston TX

     

  • in reply to alexphillip85

    Hi Alex.   Several of us have read through this and are trying to make sense of it.  Can you drop your showfile to me (anne.valentino@etcconnect.com)?  

    Thanks much!

    a

     

  • in reply to Anne Valentino

    am glad someone brought this up as it happens to me all the time with NIP's

     

    When recording a cue if i do not change parameters on a tracked unit they sometimes record in blue thought they do not change.  It the indicates that there is a live o dark move depending on if the fixuter is in or out.  I do not like the D and L when it does not need to be there so i @ enter and it goes away.  Record the next cue and boom same fixtures sam parameters in blue and not moving.  @ enter again. 

    I to may have a show file with some of this on it if you would like to see as well could find one that i did not clean up

  • in reply to ehuber

    let me try that again in english...forgive the typos

    am glad someone brought this up as it happens to me all the time with NIP's

    When recording a cue if  I do not change NI parameters on a tracked unit they sometimes record in blue though the value has not changed.  The cue list indicates that there is a live/dark move depending on if the fixture is in or out.  I do not like the D and L when it does not need to be there so I @ enter and it goes away.  Record the next cue and boom same fixtures same parameters in blue and not moving.  @ enter again. 

    I may have a show file with some of this in it still if you would like to see as well i can find one that i did not clean up.  Have seen on all fixtures too M-Faders, VL1K, Seachanger and Color Blast.

    This was all on v 1.9.5 release. 

     Quick Reply

  • in reply to ehuber

    Are there discrete NIP values or from palettes?

    If you look in blind and use the [data] button to reveal the true values, are you seeing differences between the cues?

    The other thing I can think of is a color format change between HS values and CMY, but that would only apply to color parameters.

    -Todd

     

Related

www.etcconnect.com