In order to hide the PTZ camera movement, you will need to use a stinger or move the camera prior to going to a transition. Some issues I've found with the stinger approach (maybe I don't know enough):
1. Stinger transitions using a 'black' background with the opacity set at 0% and then with a cut somewhere after the movement has been completed does work, but you must live with the delay.
2. Stinger transitions do not allow any other transition type, only a cut.
3. I've noticed that if you use the fade function to move the preview, the stinger may override and cause it to go to a preset. We had some PTZ movements in the live stream when fully unintentional. Looking for any potential shortcuts that may be conflicting.
4. I would be great if other transitions could be selected rather than cut.
5. We may need to move to using preset locations and then manually transition to avoid what was noted above.

We've only used the new ptz camera once now, so there's still a lot to learn. We setup an input for each preset position and each of those inputs has a keyboard shortcut key assigned to transitionIn for that input. The inputs have triggers to enable/disable the appropriate overlays etc. What we were doing was using a single left mouse click on a ptz virtual input to have the camera move to that preset position, then pressing the keyboard shortcut when we wanted to transition to that camera. Then try to plan our angles so that we can switch to another camera, before cue'ing up the next ptz preset. I'm just looking for a way to eliminate the mouse click so that there's only the keyboard shortcut needed, even if that means there's a slight (1-2s) delay while the ptz positions.

We have to use 4k or better for ptz controls anyways so I'll look into this. Thanks.