• State Not Answered
  • Date
    lightingStudent
  • Date
  • Replies 6 replies
  • Subscribers 184 subscribers
  • Views 4572 views
  • Users 0 members are here

Ion Channel Fade on Cue Change Question

Hello - I am just learning to operate a Tracking/MoveFade console for the first time(the Ion) and have a question about a recent issue I encountered.

Channel X was mistakenly set to full in cues A and B.

While the board was in cue A I went into blind and set channel X to 70 in cues A and B (not tracking previous values with [at][Enter], but rather explicitly setting [at][7][0][Enter].

Changing any level in the currently active cue in blind does not change the currently active level on the stage, so no change was seen and that makes sense.

However, when I pressed go and transitioned into cue B the level did not change to 70, instead remaining at full.

I thought perhaps I had captured the channel somehow and so performed a [Sneak] on channel X and then a general [Sneak] but the level did not change.

I then manually set the level of channel X to 70, then performed a [Sneak][Enter] and the level remained at 70.

This failure to transition from Full to 70 on the cue change doesn't make sense to me as the level was explicitly set in blind for Cue B.

I was thinking perhaps a 'highest level wins' rule was in effect somewhere but while in Cue B I manually set the level to 75 and a [Sneak][Enter] brought the level down to 70 again.

With that, I'm stumped and so I ask you all, "Why did my light do that?!"

Thanks for any help you can offer in explaining this curiosity.

 

Parents
  • 0

    Hi.  Welcome to the Eos forum (and tracking desks).   We have discussed in the past that the playback buffer should update all levels on the next go (so tracked levels would then reflect exactly what you'd see in blind).  After much back and forth, we decided not to do that.  You can assert the cue or go to cue enter -- both of those actions will update the playback accordingly.  

    Hope that helps.

    Anne

     

Reply
  • 0

    Hi.  Welcome to the Eos forum (and tracking desks).   We have discussed in the past that the playback buffer should update all levels on the next go (so tracked levels would then reflect exactly what you'd see in blind).  After much back and forth, we decided not to do that.  You can assert the cue or go to cue enter -- both of those actions will update the playback accordingly.  

    Hope that helps.

    Anne

     

Children
  • 0 in reply to Anne Valentino

    Thank you for your quick response!

    I'm still not sure I understand what is happening though. You mention tracked levels, but from what I gather (from the bobblehead video - thanks for that) the level of a channel is 'tracked' forward until another MoveFade command is seen.

    The level of channel X was changed from full to 70 in blind for the currently active cue A as well as for cue B.

    Is the reason the level did not change when moving to cue B because the level of channel X was identical (70) in the recorded cue A and so it didn't consider the level 70 in cue B to be a MoveFade command but rather a level tracked forward(and one not to update on [Go])?

    I understand [Assert][Cue][B] or [Go to Cue] [Enter] to solve the issue in the moment, but I want to understand what happened in the first place.

    If, for instance, with cue A up I had blind updated channel X at 71 in cue A and channel X at 70 in cue B, then would the inequality of the two values have caused the channel to update on the next [Go], or have I misunderstood entirely?

    Thanks again for your help!

  • 0 in reply to lightingStudent

    Still no response to this ... any ideas out there as to this strange behavior?  I was unable to replicate it using the EOS Offline software.

  • 0 in reply to lightingStudent

    Hi,

    Here is an example:

    Cue 1 - 1 @ 70 (move blue)

    Cue 2 - 1 @ 70 (tracked purple)

    Live in Cue 1.

    Go to Blind and in Cue 1 change 1 to FL. In Blind Cue 2, 1 is also at FL and tracked,

    In Live hit Go, nothing changes.

    This is because Cue 2 does not contain have a move for Chan 1. If you want to pull in the values from Blind you can either use Go To Cue or Assert.

    Hope that makes sense.

    Dan

  • 0 in reply to dsmurfin

    Thanks for your response Dan.  What you said makes sense to me, but the odd thing was that I didn't just change the move value in cue 1, I actually selected cues 1+2 then set the channel level.  .... I just tried this in the offline client and it behaves like you say.  So - it doesn't matter whether or not a value is explicitly declared for a channel in a cue - the level will only change if it is a new level as compared to the previous cue, not what is onstage.  I had thought the hyphen indicated the value would be tracked, not the different colors of the channel levels.  This is definitely different than the preset-based Expression!  Thanks for your help (and please correct me if I have this wrong)!

  • 0 in reply to lightingStudent

    for all values from 1 to 100 and FL, the color is the only indicator. a value of 0 will not only be written in magenta font but also as a hyphen instead of a 0.

Related

www.etcconnect.com