Hi, can we get a feature request in place to make the temporary record path for the reolink client (this is based on the windows installation) configurable.

At present in the app you can set the record path to be a specific app directory. However each camera has a temporary record path to store the stream before its exported as a single file to its destination record path. The current location for this temp location is in 'C:\Users\<username>\AppData\Local\Temp\recordTMP'
This means for users which want to use an SSD for their base operating system installation, then use external storage for their CCTV footage, all read/write iops are first written to the local \C: drive before being offloaded to the CCTV Disk array.

That means the SSD is going to wear our really fast depending on size of deployment and configuration settings (24x7 etc). If this path can be configurable to also store the temp files on the CCTV array, then the host OS can be created on one drive medium without wearing it out and use the high wear drives for the actual footage.

For example, i record 9 Cameras at present 24x7 in 1440p and 1 of these in 4k. My daily recording is ~475GB that i store for 7 days. Thats 475GB that is being written not once, but twice, first to the \C: drive, then a second time to the external storage. If this is all configurable, it should only be recorded and written once - reducing overall wear on the drives and speeding up most systems as it doesn't need to do the internal transfer.

I had originally used symlinks to mark the recordTMP folder on the external storage, but these were flaky on upgrades and restarts of the OS.

This is not only a major QoL improvement for the application, but also a cost saving and hardware saving measure that would make the app more appealing as well! Otherwise i'll be forced to migrate to a third party provider.

Thanks,

Aaron

Hi,

Reolink do off the Reolink Client that is there Software Based NVR. https://reolink.com/gb/software-and-manual/ -
this works pretty well and can do 24/7 recording / motion recroding / visible timeline of motion events as well. Allows you to setup and configure your cameras as needed - much like their proprietary hardware.

The community continues to pester about Linux based NVR as it would be kinder on resources and a lighterweight deployment overall (at the end of the day, their proprietary hardware uses linux under the hood so its very much possible).