Close

Continuous Recording

Having trouble with Sighthound Video? Post here for help.

Moderator: Staff

no avatar
desi
 
Posts: 1
Joined: Mon Oct 16, 2017 5:48 am

Continuous Recording

by desi » Mon Oct 16, 2017 6:05 am

Would it be possible for the videos to be moved to local storage (just like clips) instead of it being deleted? Local storage can be say E drive, where Sighthound is installed on C drive.

Is there an upper limit on video temp storage, default 48 hours?

How would Sighthound behave if the video temp storage is set to 48 hours, but disk space gets low say within 10 hrs of recording?

Is there replay function of videos in temp storage in the mobile app?

Is it additional processing overhead of converting videos from native format to mp4? If yes, can you consider persisting videos in native format and only converting to mp4 ad-hoc?

Thanks for your help.

User avatar
sv_alex
 
Posts: 42
Joined: Tue Jul 11, 2017 2:15 pm

Re: Continuous Recording

by sv_alex » Mon Oct 16, 2017 10:58 am

Hello,

Let me try and address your questions one by one (I assume you've seen this post already - https://www.sighthound.com/support/managing-your-video):
> Would it be possible for the videos to be moved to local storage (just like clips) instead of it being deleted? Local storage can be say E drive, where Sighthound is installed on C drive.

Yes, it is possible. Sighthound Video stores configuration and temporary files on the system volume, while the video archive location is configurable.

> Is there an upper limit on video temp storage, default 48 hours?

Yes, maximum time on the temp (aka "cache") video clips is settable via preferences, and defaults to 48 hours.

> How would Sighthound behave if the video temp storage is set to 48 hours, but disk space gets low say within 10 hrs of recording?

Assuming disk space gets low, cache clips will be removed first. If after that it is still low, clips will be removed, oldest first.

> Is there replay function of videos in temp storage in the mobile app?

Yes, with a "but". It is possible to view clips treated as cache -- e.g. clips where a motion was detected (resulting in the clip creation), but didn't result in triggering a rule (time/boundary/object type/etc). So in the mobile app it is possible to review all clips -- cache or not, but not the video where not perceived motion occurred. In the desktop app, timeline control allows for reviewing any video that had been recorded and is still cached.

> Is it additional processing overhead of converting videos from native format to mp4? If yes, can you consider persisting videos in native format and only converting to mp4 ad-hoc?

MP4 is just a container. As long as the camera is H264, there's no additional encoding is necessary to store that video. There is additional processing to store MJPEG video, which why we generally advise using H264, if the camera supports it (which most of the cameras worth considering do nowadays).

Hope that answers your questions.

- Alex


Return to Technical Support