Some users have reported problems with recording a cue or DMX stream incorporating moving lights - and when they attempt to play the cue or stream back, the moving lights replay every parameter correctly except for Pan and Tilt positions, which appear to have been recorded incorrectly.
This isn't actually a problem. What's happening here is actually easy to explain and fix.
When recording cue snapshots or streams from an external console, the output of the console is attached to the input of the CueServer, then the output of the CueServer is attached to the lighting fixtures. The scene(s) or show is played on the console and CueServer is used to record the DMX data.
After the cues have been recorded into CueServer, the console operator typically hits Release, Clear, Blackout or whatever is appropriate for the console being used.
Then, the CueServer is used to play the cues or streams back and the operator notices that the Pan and Tilt positions are incorrect. This is because by default, CueServer merges the data coming from the DMX Input port with the cues it is playing back using a "highest-takes-precedence" (HTP) method of combining the two sources.
When most moving light consoles are cleared, released, or blacked-out, they send mostly zero levels to all of the fixtures, except for Pan and Tilt, which are typically each sent at 50%/50%.
When CueServer merges the show that was recorded with the 50%/50% Pan and Tilt coordinates coming from the console, the user can sometimes see that the moving lights don't point to the proper locations on stage.
How to fix it
There are three ways to resolve this issue:
1. Unplug the input from the console.
2. Set Playback 1 to Override mode so that its active channels will always override the DMX Input (until you do a Release on Playback 1).
3. Execute the command
Input Disable, which will temporarily keep the DMX Input from affecting the playback faders and output (until you do an