The dropped frames aren't tied directly to IVS triggers. I say thing because the same thing happens to me on a hardwired external trigger. I think the firmware is messing up when it closes the old file and opens a new one on a trigger. If I'm right, the lost frames should happen on motion events, too.
Was waiting for when someone was going to mention that. I haven't setup my IVS rules yet but did have motion events turned on and experienced the problem, loss of frames when the action occurs. Thought IVS might be different...
i didn't have time to play(or set them ) with them yet its on my work place ..i just plug them to record on nvr 16p ..tomorrow will try to set open vpn so i can see them online ,for now watching them on 27 monitor plugged directly to nvr
The reboots on mine always follow IVS events. I'm going to disable IVS recording for the weekend and see how it goes. Wish I knew what that reboot code meant, don't want to waste time troubleshooting if it indicates a hardware issue.
On the camera end, this is how my 5231s are setup (currently, I've tried a few different ones over the last few days). I'm assuming this config factors into the equation on the NVR-end.
Don't know if you want to share your 5231 config here, but I could also try running your settings and see if that has any effect...
Ok, this might be a stupid question. @nayr I see you record at 20 FPS using VBR and a quality level of 6. Do these settings only apply to the NVR? I was under the impression the NVR and camera should be set the same. IE, if you record at 20 FPS then the camera should also be set up at 20 FPS. Is this correct?