• Date
    Crispy
  • Date
  • Replies 6 replies
  • Subscribers 186 subscribers
  • Views 14965 views
  • Users 0 members are here

Updating cues and releasing channels

Dear All,

 

Please bear with me; it’s a little hard to explain…

If you select a channel and manipulate it (or force manual data) it turns red to indicate that the levels are not recorded. If you update the cue, they turn blue. Great. If you update a previous cue and the values track through the Live cue or Update a later cue and the values trace back then the manual data will be stored and, again, the display turns blue.

However, if you change a parameter and update a range of cues that don’t affect the Live cue then the manual values are still kept ‘active’ (i.e. displayed red) and you can keep recording/updating palettes till your hearts content.

If you update a previous cue and some values track through the Live cue then you lose those active channels but the channels without data in the Live cue are still controllable (i.e. they stay red and don’t turn blue).

 

The only problem that I had found was that I wasn’t aware this was happening and it would be very easy to think that after you have pressed update/record that all the values are null. If they’re not then you run the risk of updating lights when you don’t mean to. A possible excuse for ‘Shift Clear’?

 

Thoughts anyone? (If you still with me or haven’t fallen asleep with boredom)

 

Cheers, Crispy x

Parents

  • We call this behavior of converting from manual (red text) to playback (blue text)  "Autoplayback on record". The intent is that if the level for the channel is equal to the level in the active cue, then it should be blue not red. The following are all of the cases where that happens.

    It only happens on a cue record if:

    1) it's either a full record (no channel list list included in the record), that cue now becomes the active cue

    2) a record that creates a new cue that follows the active cue, that cue now becomes the active cue

    3) a record to the active cue (this includes update enter)

    4) a record to the source cue for a channel that is tracked in the active cue

         Ex:active cue 5 chan 1 tracks cue 3's chan 1 level, and you record to cue 3

    The first 3 are all or nothing, meaning either all or none of the channels included in the record are autoplayed back. But #4 can leave some channels red, because they contain moves not tracks in the active cue.

    This doesn't answer the problem of your not knowing that some channels may still be manual (red), but it may help this discussion to explicitly list the rules that Eos is following. 

Reply

  • We call this behavior of converting from manual (red text) to playback (blue text)  "Autoplayback on record". The intent is that if the level for the channel is equal to the level in the active cue, then it should be blue not red. The following are all of the cases where that happens.

    It only happens on a cue record if:

    1) it's either a full record (no channel list list included in the record), that cue now becomes the active cue

    2) a record that creates a new cue that follows the active cue, that cue now becomes the active cue

    3) a record to the active cue (this includes update enter)

    4) a record to the source cue for a channel that is tracked in the active cue

         Ex:active cue 5 chan 1 tracks cue 3's chan 1 level, and you record to cue 3

    The first 3 are all or nothing, meaning either all or none of the channels included in the record are autoplayed back. But #4 can leave some channels red, because they contain moves not tracks in the active cue.

    This doesn't answer the problem of your not knowing that some channels may still be manual (red), but it may help this discussion to explicitly list the rules that Eos is following. 

Children
No Data
Related

www.etcconnect.com