• State Not Answered
  • Date
    Rick36616
  • Date
  • Replies 6 replies
  • Subscribers 186 subscribers
  • Views 3997 views
  • Users 0 members are here

Why do Trace and QOnly differ where they can be used?

I would think Trace and QOnly are very similar, one is backward looking and the other forward looking, yet QOnly can be used in blind, but Trace cannot be used in the same way.  How do you get the Trace functionality in blind?  What is the difference in where these can each be used?

Parents
  • 0
    Rather than QOnly and Trace being similar, imagine the console in QOnly default mode, when the button posts "Track" to the command line. Track propagates a change forwards and Trace backwards. In tracking mode, the opposite of trace is actually *not* commanding Q Only.

    @ Enter is really its own command, cancelling a move and thus pulling data from the cue before. QOnly decides whether to propagate that move into further cues or to end it there.

    This is a bit of a divergence, but @ Trace Enter could be a useful command sequence if it pulled a move one cue earlier, something I do all the time.

    -Josh
Reply
  • 0
    Rather than QOnly and Trace being similar, imagine the console in QOnly default mode, when the button posts "Track" to the command line. Track propagates a change forwards and Trace backwards. In tracking mode, the opposite of trace is actually *not* commanding Q Only.

    @ Enter is really its own command, cancelling a move and thus pulling data from the cue before. QOnly decides whether to propagate that move into further cues or to end it there.

    This is a bit of a divergence, but @ Trace Enter could be a useful command sequence if it pulled a move one cue earlier, something I do all the time.

    -Josh
Children
  • 0 in reply to jbenghiat
    Agreed. Trace does what Track does, but in the reverse direction. In fact, Strand called it "Trackback" rather than Trace.

    I like your suggestion for @ Trace Enter. Trace has no meaning when you remove the move for a channel (using @ Enter) -- it's going to Trace by definition. Pulling a move one cue earlier sounds like a good use of this degenerate case.
  • 0 in reply to Rick36616
    This makes no sense.

    Trace is a tracking function so if I have a channel tracking at 50% and it goes to 0 in cue 10. In cue 9 if you @ Trace Enter it pulled the move to 0 one cue earlier but it should then Trackback that 0 to when it went to 50%, because Trace (or trackback) is a tracking function.

    We do lots of things all the time because what we do isn't that clever most of the time. That's why we have Recall From Recall From Next!
Related

www.etcconnect.com