Modect-Nodect slow to start linked recordings
Posted: Thu Nov 15, 2018 10:31 pm
I am using a low-res substream to capture alarms (Modect) and then linking the main stream to record the high-res (Nodect).
I am having an issue where the linked monitor recording seems to start very late. One example today where I was coming into my house and the sub alarm and recording caught most of my movement, but by the time the linked recording fired up I was basically already in the house.
My buffer on the main is 50 frames with a warmup and pre-event count of 25. My high-res is 1080P at 30FPS. I don't have an issue with drastically increasing the buffer and the pre-event count, but the docs make it seem like this could be troublesome. My system has 8G of memory and 12 threads (6core) that's mostly unused/idle. I'm not particularly concerned with burning CPU or memory to get a better high-res capture.
I was generally happy with the sub recording in terms of length and where the alarm kicked in. But I'm very unhappy with the linked recording.
Any thoughts on how to improve this?
I am having an issue where the linked monitor recording seems to start very late. One example today where I was coming into my house and the sub alarm and recording caught most of my movement, but by the time the linked recording fired up I was basically already in the house.
My buffer on the main is 50 frames with a warmup and pre-event count of 25. My high-res is 1080P at 30FPS. I don't have an issue with drastically increasing the buffer and the pre-event count, but the docs make it seem like this could be troublesome. My system has 8G of memory and 12 threads (6core) that's mostly unused/idle. I'm not particularly concerned with burning CPU or memory to get a better high-res capture.
I was generally happy with the sub recording in terms of length and where the alarm kicked in. But I'm very unhappy with the linked recording.
Any thoughts on how to improve this?