Ensure the internet service provider offers plans with sufficient upload speed and that there are no "blackout" periods or other restrictions related to continuous high traffic usage.

Starllion Cloud is a versatile platform designed for efficient monitoring and timelapse footage capture. One key advantage is its ability to use the same camera for both live monitoring and timelapse recording. Starllion Cloud enables the creation of exceptional timelapse footage in low-bandwidth environments through careful configuration and resource management. Adding a second camera copy, fine-tuning settings, and optimizing resolutions and frame rates allows for capturing remarkable timelapse sequences without overloading a limited internet connection. Striking a balance between timelapse recording and live monitoring ensures a seamless and efficient setup. Assistance with configuring these settings or additional information is readily available upon request.

The required bandwidth varies based on the camera manufacturer and the desired video quality. Some cameras provide sufficient details at 100 Kbits/sec, while others may need up to 2 Mbits/sec. Generally, a minimum of 700 Kbits/sec is recommended for full HD streams to ensure smooth video. This parameter is highly dependent on the camera manufacturer, codecs used, and the expected video quality. In certain cases, 50 Kbits/sec can suffice, but advanced features like face recognition or license plate reading require higher bandwidth.

Determine the appropriate average bitrate for the camera based on resolution, frame rate, image quality, and camera capabilities. For instance, a 1080p camera at 12 FPS might use 750 Kbps. Decide the number of cameras and whether the internet connection is dedicated or shared. Estimate total bandwidth by multiplying the average bitrates by the number of cameras and adding necessary bandwidth for other users if applicable. Add 1 Mbps of overhead for every 5 cameras to account for metadata traffic and congestion. Without this, instability in components like cameras, routers, or ISP lines can cause issues. For example, a project with 7 cameras set to 1080p and 12 FPS on a dedicated channel, the total bandwidth requirement is 7 * 750 Kbps + 2 Mbps overhead = 7.25 Mbps upload bandwidth. Adjust the overhead if the connection is unstable or shared. To estimate storage consumption, multiply the number of cameras by the average bitrate and the duration. For 7 cameras at 750 Kbps: · Total bitrate: 7 * 750 = 5250 Kbps · Convert to KB: 5250 / 8 = 656.25 KB/s · Convert to MB: 656.25 / 1024 = 0.6408 MB/s · Convert to GB: 0.6408 / 1024 = 0.0006258 GB/s · GB per hour: 0.0006258 * 3600 = 2.25 GB · GB per day: 2.25 * 24 = 54 GB · Monthly estimate: 54 * 30 = 1620 GB This ensures an understanding of bandwidth and storage needs for optimal camera performance.

The initial step is to decrease the frame rate and increase image compression to the maximum extent possible, ensuring that playback or live streaming remains unaffected. Additionally, bandwidth requirements can be reduced by using smart codecs, though this might lead to playback issues on certain devices and create a delay in live streaming due to the camera buffering images to optimize bandwidth consumption.

The cloud service is designed to have cameras operating continuously, and any interruption in service should be avoided. There are no built-in features in the cloud to automatically connect and disconnect cameras on a schedule. Implementing such a schedule could create security risks, as when cameras are offline, the cloud cannot monitor or alert for potential issues. If a client insists on scheduled camera operation, there are several potential solutions on the camera side. Some cameras can be set to sleep and wake up on a schedule, but such models are limited. Another option is using power outlets with timers to turn cameras off and on or controlling internet/network access to disconnect cameras according to a set schedule. The best approach will depend on the client’s equipment and needs. However, it’s important for the client to understand that when cameras are not streaming, there will be no access to footage or alerts, and there will be a delay of a few minutes between powering on the cameras and when they start streaming. In some cases, manual reconfiguration may be required if network settings change after a reboot. Scheduling camera operation is not recommendable, as it is more reliable and secure to allow cameras to run 24/7, rather than relying on scheduled startups and worrying about potential issues during each cycle.

The optimal solution varies based on the number of cameras and the desired storage duration. Options include installing an NVR on the premises or adding SD cards to each camera. For personalized advice, contact a local integrator to determine the most suitable option for the specific situation.

For large installation sites, the bandwidth requirement will be significant. It's important to check with the local ISP to ensure they can provide adequate bandwidth at the location.

Using an SD card is recommended to prevent loss of footage during internet interruptions.