Skip to main content

Best Practice and Troubleshooting CloudLink

Best practices and troubleshooting when using CloudLink.

Best Practice

Optimally configuring your Spiideo cameras and CloudLink device is essential to prevent workflow disruptions. Below, we’ve outlined the best practices to ensure a seamless CloudLink experience.

  • Spiideo Cameras should:

    • Have a stable network with speeds of at least 15 Mbps per camera.

  • Your CloudLink device should:

    • Be connected via Ethernet.

    • Have Wi-Fi disabled.

    • Have a network speed of at least 10 Mbps (download).

    • Be running the latest version of the external tool you're importing the CloudLink feed into.

For a full list of the CloudLink requirements, click here.


Troubleshooting Questions and Answers

CloudLink Stuck in 'Processing'

When you've created a CloudLink in Spiideo Perform, it can take up to 5 minutes for the link to process.


The CloudLink is Generated, but There is No Footage

If your CloudLink has been generated and has been opened in an external program where you can only see a black screen or no footage, there are a few possible causes:

  • Stream isn't ready yet: wait a few minutes before trying again.

  • External program issue: test the link in VLC to isolate whether the issue is CloudLink or the third-party tool. If the link works in VLC, it is likely an issue in your external program.

  • Spiideo cameras are offline or have a poor network connection: ensure that your cameras are online and have sufficient network speeds.

  • Network limitations: If possible, try connecting your device to another network to see if the issue persists. The receiving device needs to be connected to a network that supports RTSP traffic.


AutoFollow is Not Following the Game

If AutoFollow isn't tracking movement on your CloudLink session:

  • Allow the session a few minutes to start. AutoFollow can take up to 5 minutes to kick in after the session has started to process.

  • Please confirm that the CloudLink you have generated isn't using fixed view.


CloudLink feed is Choppy, Laggy, Freezing, or Has Artifacts

To avoid choppy, laggy, freezing, or footage that has artifacts, we require:

  • 15 Mbps per camera on the scene.

  • A low level of packet loss during upload.

  • Minimum 10 Mbps download speed on the user device.

Please ensure that:

  • The camera and device network requirements are met.

  • The camera's and the device's network connections aren't fluctuating or dropping out.

  • The device you're importing CloudLink to should be able to handle the workload. Older devices, or ones with too many programs or apps running at once, may struggle with the CloudLink feed.


CloudLink Works in VLC but Not Sportscode/OBS/Catapult/etc.

If you are having issues viewing the CloudLink footage in third-party programs but not in VLC, this is most often because of an error with the third-party program configuration, compatibility, capture settings, or tool-specific handling of RTSP.

Sportscode

If you enter the CloudLink URL into Sportscode, but it fails to load, ensure that the Sportscode setting 'Enhanced Capture' is disabled.

To disable this, go to Sportscode settings, check 'Disable Enhanced Capture' under 'Capture'.


Fixed View Configure Window is Black

If you've created a CloudLink with a fixed view and you see a black screen with the text 'Retrying in X seconds', the feed from the camera isn't ready yet. Please wait for the footage to load.

If the footage hasn't loaded within a few minutes, ensure that your cameras are online.

Did this answer your question?