Unexpected behavior in blind, bug?

Hi All,

I was working in blind and using/trying out the syntax [cue] 0.1 [next] [thru] [enter], {channel} [at] [select active] and when I bumped the intensity wheel by accident after select active, it deleted not only the selected channels data but also a lot of other data from other channels from the cues.

The reason for trying this syntax is editing levels through the whole cue range without changing the points where the channel is at 0. By using +% or -%, +20 [enter] or /120 for proportional editing.

This is the data before using the syntax.

_____________________________________________

The data after the syntax. As you can see a lot more data has been changed.

We use EOS 2.3.2. because we don't have the possibility to update all machines at the same time during the season.

Greetings,

Bart

Parents
  • Because you bumped the wheel it added an Enter command, so you @ Enter'ed all the data.

    A couple of things about the syntax you're using.
    You can just say,
    Cue 0.1 Thru Enter, to select all the cues.

    Then Channel X +% will just add the +% value and not affect channels at 0%

    No need for you to type @ Select Active, +% does that for you.
    This is the reason +% does affect channels at 0. Helpful 50% of the time and the safer decision but it catches some people out.
Reply
  • Because you bumped the wheel it added an Enter command, so you @ Enter'ed all the data.

    A couple of things about the syntax you're using.
    You can just say,
    Cue 0.1 Thru Enter, to select all the cues.

    Then Channel X +% will just add the +% value and not affect channels at 0%

    No need for you to type @ Select Active, +% does that for you.
    This is the reason +% does affect channels at 0. Helpful 50% of the time and the safer decision but it catches some people out.
Children
Related