Suppose I make a change to a sequence, Qonly. That works fine, but the channels used in the Qonly will no longer track past the Qonly. Is there a way to make Qonly not impact the following cues? I can use a preset and it will track by changing the preset. What I would like is something like @Group-Cue that would set the values to the other cue. Any way to get that?
I would recommend putting blocks in where you want the console to stop tracking. All QOnly commands only control the command in the command line, but if you place blocks in then you will not have any issues…
Is it a channel with a level in the cue only? Do the channel(s) have move instructions in the q-only cue?
It you want to track it cue 1 to 10 you can do "channel X update cue 1 thru 10 enter" and it will…
Just do your updates in live, you don't even have to be in the cue (or any cue for that matter)
Get you manual values how you want them and update a range of cues
update 1 thru 15 cue only (if in tracking…
Even if there were a way to link to the previous cue before the Qonly, it would not be the same as tracking because the new value would be a reference to the old, not the actual value. A tracked value is the same value as the previous cue, not a reference to that value. Trace would not work if it were a reference. In order to get what I am looking for, the console would need to know the cue is stored Q-only and just ignore it for Tracking and Tracing purposes. That could be done, but then what about two consecutive cues, or three, or four...
I'll continue to use a preset to do this, which is my current solution. It means you have to update-all and need a preset for every place it's used, but it works. It is tedious and can get to be messy in complex strings of cues. I was hoping someone might have a better solution, but it looks like there is none.
I think we are either misunderstanding what you are trying to do, or you are missing something.
In a show where its set in tracking mode then if I want a single queue that does something and then I want everything back as it was, I can just record that one cue as Q Only and that means on GO it just goes back to the state prior to the Q-Only cue and changes I make to the cues prior to it track through - that is the function of a Q-Only. I use this often for say when I want the lights to go to a lower setting during playback of a video and then carry on exactly as before
I want Track and Trace to work when a cue has been recorded as Qonly in a tracking show by ignoring that cue. I can go back and make the scene a little bit brighter and it will trace to the end. If I have a Qonly somewhere it the middle, it prevents tracking.
Track is your friend. Trace is another good friend.
It's not a "Qonly in the middle preventing tracking".
You have a Q where the values are different. THAT is what is preventing tracking. That's a Feature. It prevents you from tracking one value throughout your entire show file.
There is no other way to know where to stop tracking, so the console stops it every time the value changes.
Q Only is not a "Thing", it's a "How".
My two cents to help me understand. If I'm "Cue Only" and change a early cue I have options; I can make the change and update [QOnly/Track] to carry my changes downstream. This ripple will stop when a later cue that had already been changed and was (on our ELE2) auto Blocked. If I want to ripple past it I could; delete the block (before changing the earlier cue). If I want it to stop the ripple downstream I could insert a block.