NetPlay Video has a fixed latency for all your zones.  The fixed latency allows for:

  1. TVs displaying the same source will be synchronized
  2. Centralized audio systems can be set to a fixed delay and have still have audio synched to video

The latency value is determined by the source type:

  • RTSP streams have a fixed end to end latency of 0.7 seconds (700ms)
  • HTTP and MPEGTS streams have a fixed end to end latency of 1 second (1000ms)
  • Non real time sources (files) do not have a fixed latency.  Use local audio for these or feed into an HDMI encoder.

Note that you can override the default fixed latencies using the --threshold source option.  Valid ranges will vary with the specific hardware used.  Our defaults are designed to be compatible across all hardware.  For example, --threshold 0.7  (entered as ",--threshold,0.7" in the source options field) results in a fixed end to end latency of 0.7 seconds for that source.

If you are using the CMX-A2, the delay value to use for RTSP streams is 170.  HTTP and MPEGTS use 240.

Latency also affects the response time when using a remote to control on screen menus.  In normal viewing mode, the response time is the same as the fixed latency.

NetPlay has an automatic low latency feature.  This feature automatically transitions the video to low latency operation when it detects several remote key presses (like menu navigation).  It also automatically transitions back to normal mode when you stop pressing remote keys.  

This feature is automatically enabled when using NetPlay for source IR or IP control.  In Control4, it is active if you use the SRC IR bindings on our driver.  For other control scenarios, you can directly start/stop low latency mode using protocol commands, or simply send the PULSEIR commands to NetPlay Manager even if IR is controlled externally.  See our protocol manual for details.

The following video shows the low latency mode in operation.  You can see that the control response delay is negligible in low latency mode.