Strange Behaviour in Blind Mode?

i guess it would help to know your software version. but basically At Enter should remove all move instructions for this channel from a cue and instead have tracked values. so if in the cue before the channel is at full, it will be at full as well after you "at-entered" it.

2.1.1 is what we are running. I've not experienced this issue before and we have been using the Ion for several years.

Most of our user groups can't get their heads around tracking, so the console is normally set in Cue Only Mode. Imagine my surprise when I quickly edited several cues in blind during a show that was running only to have the channels that I had used [At][Enter] all came on at full instead of being out as I had expected.

[At][Enter] is also not always clearing all of the attributes in Blind either. We have been running into situations where information controlling our Media Server gets held even after editing cues in blind causing unexpected transitions to happen.

The Eos line is always a tracking console. Enabling "Cue Only" does not turn it into a preset console.

Using [At][Enter] in blind will remove (nullify) a move instruction. This is not the same as clearing an attribute.

If a move instruction is removed then the channel attribute will track the prior move instruction until such time as it encounters another move instruction or a block.

Why doesn't this behaviour happen every time I use [At][Enter]? It only puts the level at full sometimes. At other times it removes all of the information including the level.

at enter removes a move instruction. what remains is the tracked value of the cue before that. you should get the same value as in the cue before but written with magenta font.

is this what you're seeing?

[At] [enter] is not used to place a null value it looks backwards and post last known state.

if channel 1 is full in cue 1 and at 50 in cue 2 using @ENTER in cue 2 will post full.

If in cue 1 and there is no cue before cue1  it will post a Null value.

if you want to use @ENTER for a single cue in tracking mode would use the syntax

1 [Cue only] [at] [enter] and the it will not track forward.

If you are in cue only mode you do not need to use cue only.

[At] [enter] is not used to place a null value it looks backwards and post last known state.

if channel 1 is full in cue 1 and at 50 in cue 2 using @ENTER in cue 2 will post full.

If in cue 1 and there is no cue before cue1  it will post a Null value.

if you want to use @ENTER for a single cue in tracking mode would use the syntax

1 [Cue only] [at] [enter] and the it will not track forward.

If you are in cue only mode you do not need to use cue only.