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