I've been trying to understand Query MovesOnly for a while now. I think I have it narrowed down to a point where I can say with reasonable certainty that it's a bug ...
To reproduce:
- new show
- patch dimmers 1-10 at addresses 1-10
- make 5 cues:
cue 1: 1 @ full
cue 2: 2 @ full
cue 3: 3 @ full
cue 4: 4 @ full
cue 5: 5 @ full
with tracking, so by cue 5, 1 thru 5 are all at full - then in blind also change cue 1: 4 @ full. should create an autoblock for channel 4 in cue 4
- Run following command several times, standing in various cues in Live and in Blind: (lets call this Command 1)
Query Cue 2 thru 4 {Moves Only} <enter> - Same thing with following second command:
Query Cue Home Thru {Moves Only} <enter>
(de facto this is query cue 1 thru 5 moves Only) - Bonus round: in Live
Go to cue 1
Go to cue out time 20
Query Cue 2 thru 4 {Moves Only} <enter>
What Happens:
- different results depending on whether you're Live, in Blind, and which cue you're in.
- Live / Cue 1: returns 2 thru 4 for the first command, 1 thru 5 for the second command
- Live / Cue 5: first command returns empty channel list (even though tombstones 2-4 are selected). Second command returns channel 5.
- Blind / Cue 1: first command returns channel 4
- Blind / Cue 2: first command returns channel 2
- Blind / Cue 4: first command returns empty channel list, but again with tombstones 2-4 selected
- and so on. See attached screenshots.
- Bonus round: only if I run command 1 while going from Q1 to Q-Out, then it returns Channels 2+3. Which is kind of what I would have expected in the first place. Am I correct in assuming this would be the expected behaviour?
Tested on EOS Classic 2.9.2, Nomad 3.1.1 on Windows, Nomad 3.1.2 on Mac. Same behaviour all round.
For the windows screenshots I only had channels 1 thru 5 patched, not 1-10. Don't think that makes a difference.
