Troubleshooting

Ensure Eos is configured per EOS Integration and that both CueCam and your Eos console are on the same network. If you're using a wired network for your console then make sure the access point you are connected to can see the same network.

In most cases the start of the IPs should be similar. e.g. if your iPhone is showing 10.20.1.38 and your console is on 10.20.1.3 this should work. If your iPhone has a 192.168.1.x address and your console is using 10.x.x.x it will not, contact whoever is responsible for the network.

If you already use iRFR or aRFR, then CueCam should work.

If it appears that the cue times are lagging, or updating once per second, this is usually an indication that Third Party OSC is disabled in EOS Integration, and CueCam can only connect on the other port.

Alternatively, you may be running an older version of Eos. Versions prior to 3.2 will not perform as well.

If the Timestamp is WHITE it is being provided by your iPhone, check the date and time in settings. If the Timestamp is AMBER and has a diamond on the end the it is being provided by your Eos console, check the date and time on your console or disable time sync in Settings

If your OSC commands are not being processed (i.e. no markers or stop/start is not working via OSC), but cue status is being shown correctly, then Eos is connected via Third Party OSC only. Check Eos is configured correctly per EOS Integration and that OSC Control is enabled in Settings

Check RTSP Server is enabled in Settings.

You could also try VLC or another third party RTSP client, enter the URL shown in settings suffixed with /status or /video.

Latency will be caused by one of two factors; the performance of your device, or the network. With a modern iPhone (e.g. iPhone 16 Pro) on a decent WiFi network it can be as low as 2-4 frames. Older hardware and poorer networks can have significantly poorer performance.