More often than not, significant latency is added by other devices in the IMAG chain that come after the TriCaster. Projectors are a common contributor, but at times the cameras themselves are a factor.
Here are some helpful points to consider when designing and connecting your system:
- If you use Multiview output from the TriCaster to the projector – if at all possible, match the resolution sent from the TriCaster to the native resolution of the projector. (On some projectors this allows the unit to avoid using its own internal scaling, which is often a significant factor in unwanted latency.)
- When possible, try supplying the projector with analog video. This can eliminate a lot of the complexity from the process (of course, this is not always possible.)
- Certain projectors provide a ‘low latency mode’ to disable features of the unit that carry a heavy toll in latency. Enabling this mode can make positioning the projector slightly more challenging (as you may sacrifice some ability to position and scale the image using projector menu functions) – but the latency reduction can be very worthwhile.
- Some cameras include features that add more latency than you would expect. For instance, image stabilization (by definition) adds one field of latency and sometimes more. Disable anything of that sort that you can.
- Latency may be slightly lower for progressive sessions, so for lowest latency, (genlocked) 720p cameras and session are theoretically ideal (again, for genlocked sources, consider disabling TriCaster’s Frame Sync – see Section 8.2.3).
For more information please download the entire document at new.tk/rt-m