i did not know the eos would do this

had a operator call me with a issue, she had fixtures that were getting intensity values and she could not figure it out. she could manualy make them go out but as soon as the manual value was folowed by a cue, the fixtures come on. i told her on the phone to just cut those units from the show as they were not being used and i would look at it in the morning.

when i opened the show file i found the issue. there was a submaster that had a effect recorded to it but it was not mapped to a fadder. when i mapped it to a fadder, the fadder went up to represent its value and i could deal with it at that point. it just semed odd that the data would be there with out being atached to a fadder.

  • Lane, it is not necessary for a submaster to be physically mapped to a fader to be recalled via the command line (as you have discovered).  There are a number of indicators that should be advising you of where data is coming from, including:

    Color indication of data.

    The about channel display

    This is where the syntax sub x (where x represents the first stored sub) thru home enter can become helpful if you are not sure what state the desk was left in.

    Hope that helps.

    a

     

     

  • thanks anne,

    that is how i found the errant sub data. about adress showed me the changing information and from that i was able to find the sub.

    is there a way to find out when the submaster was recorded? is there a date or time stamp in the code?

Related