Differences
This shows you the differences between two versions of the page.
|
user:product:roscolive2.0:how_to_guide:reduce_data_usage [2023/04/05 14:13] codyh@roscovision.com created |
user:product:roscolive2.0:how_to_guide:reduce_data_usage [2023/04/12 20:39] (current) codyh@roscovision.com |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | == Placeholder == | + | ===== Managing Device Data Usage ===== |
| + | |||
| + | To ensure the best experience and to minimize unnecessary data usage, please try the following suggestions. | ||
| + | |||
| + | ==== Reduce Video Quality ==== | ||
| + | Reduce the video quality setting on your camera in order to lessen the amount of data needed to upload a video. This can be done in your **Settings Profiles** applied to your cameras. | ||
| + | {{ :user:product:roscolive2.0:how_to_guide:videosettings.png?nolink&800 |}} \\ \\ | ||
| + | |||
| + | Even at the most conservative settings, your camera will still upload HD quality video and you will save on the extra data usage! | ||
| + | |||
| + | ==== Adjust Event Settings ==== | ||
| + | There are many event settings you can adjust to lessen the data consumption used by excessive event video upload. | ||
| + | |||
| + | === Disable Unused Events === | ||
| + | Disable any events that you feel are not necessary or irrelevant to your fleet. | ||
| + | |||
| + | {{ :user:product:roscolive2.0:how_to_guide:toggle.png?nolink&200 |}} | ||
| + | |||
| + | === Change Upload Type === | ||
| + | Perhaps you don't need a video __and__ a snapshot for every event uploaded? This can be adjusted in the **Upload Type** drop down options. The options are: | ||
| + | - **Alert Only**: No video or snapshot will be uploaded. If you have notifications enabled, you will still receive a notification for this event. | ||
| + | - **Snapshot Only**: Only a snapshot of the event will be uploaded. Snapshots can still tell you a lot about an event while only being an average of 50 - 70 KB in size! | ||
| + | - **Video/Snapshot**: Will upload both a video and a snapshot of the event. Reserve this option for only events where video is needed to tell the whole story. This is option is best for Driver, DMS, and ADAS type events. | ||
| + | |||
| + | === Adjust Sensitivity Settings === | ||
| + | Sometimes the default settings may be too sensitive and require some fine tuning. Use the various sliders and threshold settings to adjust the sensitivity setting to a less sensitive value. This will help eliminate noisy and meaningless events while still allowing the more meaningful ones to be captured. For example, every bump and pothole causing a High G-Force event to upload? Drag the slider to the right to make it less sensitive. | ||
| + | |||
| + | ==== Limit Live Streaming ==== | ||
| + | Live streaming a camera frequently will consume data very quickly if not careful. Try to limit the duration of your live stream sessions and live stream less frequently to save on that data. | ||
| + | |||
| + | ==== Limit the amount of profile changes to cameras ==== | ||
| + | Even though making a profile change to a camera consumes a small amount of data, it still consumes a little bit for every change made. If changes are made frequently enough, they could add up and impact the data usage in a meaningful way. | ||
| + | |||
| + | ==== Limit the amount of Custom Video requests ==== | ||
| + | One of the top reasons for a data overage to occur is an excessive request for custom video from the camera. Every custom video request has to upload the snapshot and video file for that time duration requested. If requesting 5 minute videos excessively, this will eat up your monthly data in no time. Only request the video when it is necessary and when necessary, only make the least amount of requests for the shortest duration necessary to get the information you need. | ||
