Track Thru

Hi Ed,

You need to append Q Only to your syntax otherwise you're asking it to track from the final cue in your selection.

Cheers

Dan

maybe i should have mentioned i was in cue 101 and there where a few cues after cue 106.

I know i have used this syntax in the past.

when i hit [update] it posts current cue number [thru] 106 again tracks entire cue list.

i tried [update]101 [thru] 106 and same result.

I have never had to hit [cue only] when doing this before so it was odd to me. shouldn't  giving a specific range be sufficient? it is possible i was in cue only mode in the past....

oh and thanks Dan!

so as i pondered this a bit further and the need to hit q-only i came to this conclusion in my mind....

i see update thru as a cue only function regardless of what mode i am in.  in essence i know that i want channel one to be at 50 in cues 1 thru 6 and not any further i don't understand why [update] [thru] 6 tracks....

If I make a change live in cue 101, and cue 103 is blocked, I might use [Update][Thru][103][Enter] to get the change to track through the block in cue 103, and continue to track until it is given a command at some point after cue 103.

Requiring [Cue Only] at the end of a range update is consistent with the behavior elsewhere.  So while it's true that [Update][Thru][103][Cue Only][Enter] is far more common than [Update][Thru][103][Enter] in actual use, we do need both syntaxes.

~Paul

If I make a change live in cue 101, and cue 103 is blocked, I might use [Update][Thru][103][Enter] to get the change to track through the block in cue 103, and continue to track until it is given a command at some point after cue 103.

Requiring [Cue Only] at the end of a range update is consistent with the behavior elsewhere.  So while it's true that [Update][Thru][103][Cue Only][Enter] is far more common than [Update][Thru][103][Enter] in actual use, we do need both syntaxes.

~Paul