Closes #7 - create ffmpeg timelapse binary

[aysent911]

nvr_timelapse

[128keaton]

Looks great Teddy, can you put the target inside of the common CMakeLists.txt? Thanks!

[aysent911]

Moved target inside the common CMakeLists.txt

[aysent911]

Now able to sort the snapshot files in ascending order; from earliest to latest. It's amazing the h.264 encoded mp4 file size is 3 times smaller after the sorting.

[aysent911]

nvr_timelapse now encodes only snapshots within last n days and in order.

[aysent911]

Latest code uses h.265 codec. Yields a much smaller video size

[aysent911]

Usage nvr_timelapse <days> <full_path_to_camera_json> <time_interval_between_frames> Where the <time interval between frames> is an optional argument and is specified as <minutes>m or <hours>h. For instance;
nvr_timelapse 16 /nvr/cameras/camera-1.json 1h will encode camera-1 snapshots in 1 hour intervals starting from the last 16 days. If time interval is not specified, the binary will encode all the snapshots within the specified days. Run as root.

[aysent911]

Run nvr_status_manager to start server.
Run nvr_camera start /nvr/cameras/camera-1.json to start nvr-record@ and nvr-stream@ units.
Run nvr_camera stop /nvr/cameras/camera-1.json to stop nvr-record@ and nvr-stream@ units.
Run nvr_camera restart /nvr/cameras/camera-1.json to restart nvr-record@ and nvr-stream@ units.
Run nvr_camera status /nvr/cameras/camera-1.json to view status of nvr-record@ and nvr-stream@ units.
will return {"status" : "active"} or {"status" : "inactive"}