Moving the Capture Destination off the Startup Drive Completely
Hi
How do I configure SecuritySpy NOT to write to the standard capture destination on the startup drive AT ALL ?
I have a really fast external RAID drive, and have set every camera capture destination to point to a directory on the RAID drive. However, I still see temporary .sbf files getting created in the startup drive under ~/Documents/SecuritySpy/Captured Files. They disappear as soon as the motion detection recording stops, but I don't want SecuritySpy writing to this drive at all, is a huge bottleneck. I tried deleting the SecuritySpy directory altogether, it just gets recreated. I have tried moving the entire SecuritySpy directory to the RAID drive and setting a symbolic link to point there, but Securityspy then just hangs. ?? Is there any way to tell SecuritySpy to leave the startup drive alone for all things video writing ??
How do I configure SecuritySpy NOT to write to the standard capture destination on the startup drive AT ALL ?
I have a really fast external RAID drive, and have set every camera capture destination to point to a directory on the RAID drive. However, I still see temporary .sbf files getting created in the startup drive under ~/Documents/SecuritySpy/Captured Files. They disappear as soon as the motion detection recording stops, but I don't want SecuritySpy writing to this drive at all, is a huge bottleneck. I tried deleting the SecuritySpy directory altogether, it just gets recreated. I have tried moving the entire SecuritySpy directory to the RAID drive and setting a symbolic link to point there, but Securityspy then just hangs. ?? Is there any way to tell SecuritySpy to leave the startup drive alone for all things video writing ??
Comments
-
Hi,
You can set the capture destination for the video files to any drive via the Camera Settings window. But as you seem to have discovered, SecuritySpy does still use the ~/Documents/SecuritySpy/ folder for a few things, such as the temporary .sbf files that are used during the capture process (these are "SecuritySpy Backup Files" that exist in order to reconstruct movies in case they become corrupt due to a crash etc.)
There is no way to change this behaviour, however these .sbf files are tiny (they contain only metadata; no actual audio or video data), and will therefore not impact upon capture performance at all. The important thing is that the large files - the actual movies themselves - are captured to your fast external drive.
