- This allows you to drop a file into `/dev/shm/streams/dropInEvents/[GROUP KEY]/[MONITOR ID]` to trigger an event.
- This is useful for cameras that can do FTP upload on Motion detected with their internal detector.
- `dropInEventsDir` can be configured in conf.json
- this will avoid the `ER_LOCK_WAIT_TIMEOUT` error by breaking up the video list into sets of 100 then querying each set as a single query rather the entire video list as a single query.
- Instead of including the npmjs module; the rtmp portion has been ripped from the main package.
- to enable the RTMP server with default settings just add `"rtmpServer":true` to your conf.json
- `rtmpServer` object in conf.json correlates to `rtmp` object in NodeMediaServer configuration.
- WARNING : currently no authentication for incoming RTMP streams.
- Notification Video Length : The length of the video that gets sent to your Notification service, like Email or Discord.
- New option appears under Recording Timeout.
It's very annoying to get partial video because the process died or was shutdown uncleanly. This fixes the issue. Here is an explanation of the options set:
Normally, a MOV/MP4 file has all the metadata about all packets stored in one location (written at the end of the file.
faststart: Will move the metadata to the beginning of the file after the recording is complete.
frag_keyframe: Starts a new fragment at each video keyframe. This allows a file to work, even if the metadata isn't written at the end or beginning of the file, since it encodes with each keyframe. (Tested with kill -9 on and start/stop recording where the end metata data wasn't written)
empty_moov: will cause output to be 100% fragmented; without this the first fragment will be muxed as a short movie (using moov) followed by the rest of the media in fragments.