Darn Auto-Block again!

You're confusing a Move instruction with an auto-block.

An AutoBlock only appears when you purposefully give something the same level as it is in the previous cue. The desk recognises you purposefully entering this information and 'protects' it for you. What you're seeing is a standard Move instruction (Blue going up, Green going down). Magenta is tracking at a level previously set and then an auto-block appears in white to show it's been purposefully set (not just tracking) at the same level.

So in your example if you had changed Cue 3 to have Ch1 at 50% - Cue 6 would show an auto-block. with the 50% in white because you had already previously put it at 50%.

Does that make sense?

You're confusing a Move instruction with an auto-block.

An AutoBlock only appears when you purposefully give something the same level as it is in the previous cue. The desk recognises you purposefully entering this information and 'protects' it for you. What you're seeing is a standard Move instruction (Blue going up, Green going down). Magenta is tracking at a level previously set and then an auto-block appears in white to show it's been purposefully set (not just tracking) at the same level.

So in your example if you had changed Cue 3 to have Ch1 at 50% - Cue 6 would show an auto-block. with the 50% in white because you had already previously put it at 50%.

Does that make sense?

Oh dear! Putting it like that it does make sense. Having the program on my computer at home is amazing. I was able to go back to cue 3 and change (woops "move") CH1 to 50%. Sure enough in cue 6 it turned white and back in the PSD the underscored, white b appeared as you said it should. So the program, when I made the 1st move, treated it as just that - a move that would stop a 'track' anyway and hence no need for an Auto-Cue. Nice explanation - thank you.