Bug in tracking with Auto-mark on?

This is how automark works. You have a cue, cue 1, technically with two move instructions in it.

1. The move to the home values
2. The move to the marked values

You then created a new cue 1, by homing the lights, and recording a cue 1. You haven't told the lights to re-mark (you can do this by typing "Go to Cue Enter), so they are just going to stay in their most recent values - in this case the home values. This is why you get that live move.

Eos is showing you the values that "win" at the end of the cue.

When you backup into cue 1, you are telling the desk that it should be set up for cue 2. So the lights mark. The move instruction is unfortunately hidden by the mark - if you turn off automark and part out the referenced mark you can see the moves in two different parts.

This is how automark works. You have a cue, cue 1, technically with two move instructions in it.

1. The move to the home values
2. The move to the marked values

You then created a new cue 1, by homing the lights, and recording a cue 1. You haven't told the lights to re-mark (you can do this by typing "Go to Cue Enter), so they are just going to stay in their most recent values - in this case the home values. This is why you get that live move.

Eos is showing you the values that "win" at the end of the cue.

When you backup into cue 1, you are telling the desk that it should be set up for cue 2. So the lights mark. The move instruction is unfortunately hidden by the mark - if you turn off automark and part out the referenced mark you can see the moves in two different parts.

I don't understand.  If I change the values in Blind in Cue 1 which you see me do, am I not overriding the automark?  Why does it show correctly in Blind but not in live? The fact that I was able to do the live move initially but then not repeat makes it seem like it's a bug.

You went from cue 2 into cue 1 (play back the state of cue 1, and the marked values)

You then homed the lights

You then recorded cue 1 again

But you hadn't told Eos that you wanted those lights to re-mark. Sadly the console can't read your mind (probably v5.0!) and doesn't know when you're done working with those lights. If you had homed the values, recorded cue 1, and then turned them on and they were marked for cue 2 you'd probably be pretty miffed!

Alternatively, you can just "force" the live move. Since the Skypanels intensity is at 0 in your original LQ 1, the console's auto-mark feature isn't aware that you want to see the live move. It just thinks you want the colors to be marked so that as the Skypanels fade up, the color is already there. (Scott covered all of that already)

So, if you put the Skypanels intensity to 0.05 % or 0.01 % and update LQ 1, you can achieve the fade from white to the color you chose in LQ 2, aka the live color fade. And technically, it won't be marking anymore. 

For the record, I have never seen an LED source (and definitely not incandescent) become visible at less than 1%. Many cheap LED's can blink on at 1%, yes, but literally all you need is that 0.01% as a data point for the console to see.

Sorry, so if I'm understanding correctly if I just, in Live, "Go to Cue 1 Enter" it will be different than going backwards in the cuelist?  That still doesn't work.  When I "Go to Cue" the color doesn't change.

The problem with this is you can see a skypanel on at .01%

Another point that might be causing confusion is that in the 1st half of your video, when you went back to Live and stepped back into LQ 1, you still had Data Latched on. This meant that you were seeing the purple (tracking/marking) Intensity of "0.0" for each Skypanel, as opposed to the "MK" notation associated with channels marking.

If you had unlatched the Data, you'd see a bit more clearly that you had stepped back into the "complete" LQ 1, including the mark for the Skypanels color. So, you'd have purple "MK"'s in Intensity, and (green) "Q 2"'s in each NIP field.

Another tip would be to keep an eye out for your flags in your PSD. Often times a quick glance over there for an M, D, or an L can illustrate how the console thinks with auto-mark.

How about 0.001 %? 

You can go even further...

Gotcha I didn't realize that.  Is there no way to make this work other than that trick?  I can't just turn automark off for that cue?  When I tried it didn't seem to work

No, he's saying that because you had *just* recorded a new LQ 1, and were still sitting in it, that the console didn't re-mark the lights for you. It didn't process the auto-mark for the channels you were just working with. It just was sitting happy exactly how you recorded it, in case you were going to make further changes to those channels. This is why you saw a change when you re-recorded LQ 1 and then advanced to LQ 2. You weren't actually in a "complete" LQ 1. You were in LQ 1, without any marking being re-applied. This obviously never happens when you are running a show in order.

The Go2Q Enter command he's suggesting isn't going to show you a live color move from white to the color of LQ 2. It's essentially saying to the console "re-load this cue" which is telling the console to reload it fully, including the mark that you have setup for LQ 2. He was telling you a way to tell the lights to re-mark.

As a test, go through your video process again, re-recording your LQ 1 as Skypanels @ Home. And then instead of advancing to LQ 2, just do a G2Q Enter. You'll see the mark happen. (Again, if Data latching is off, you'll see the purple MK show up in the intensity field, indicating the mark).

Of course there is :) You can, indeed, just turn automark off for that cue.

Where were you trying to turn automark off? Your LQ 1 is my guess? (Hint... it's actually LQ 2 that it needs to be off for... since this is where the data is actually stored!)

So, either in Live or Blind: Cue 2 AutoMark Off (which is Softkey 3) Enter

https://www.youtube.com/watch?v=XdbUTKMbcio&ab_channel=ETCVideoLibrary

Thank you so much for your response!  Yes I was in Q1.  Sheesh lots to learn still!