cryptelli
Pulling my weight
I have been communicating with Ken to see if he can make IVS work with BI.
Obvious question incoming... what's the news?
I have been communicating with Ken to see if he can make IVS work with BI.
are you sure you dont have standard motion detection enabled again?he actually emailed me back today to see if I could see anything in the event section of onvif device manager, which I set up an intrusion zone and triggered it and I sent him back this and told him to let me know if he needs anything else.
View attachment 17143
event section of onvif device manager, which I set up an intrusion zone and triggered it and I sent him back this
are you sure you dont have standard motion detection enabled again?
So Ryan's advice is to set the iframe to match the fps? Not double the FPS. Is that how I understand this? I lose less than a second, but my iframe is double the frame rate.Same. The dropped frames happens pretty much on every event but took nayr's advice an matched the i-frame to the frame rate and that only results in 1 second being lost, better than nothing.
I tried the same thing only using a tripwire but couldn't see anything coming through like you have on the events section of the onvif device manager.
So Ryan's advice is to set the iframe to match the fps? Not double the FPS. Is that how I understand this? I lose less than a second, but my iframe is double the frame rate.
SD
So Ryan's advice is to set the iframe to match the fps? Not double the FPS. Is that how I understand this? I lose less than a second, but my iframe is double the frame rate.
SD
The rule of thumb is to match iframe to fps, I dunno why the PAL firmware on the starlights auto doubled it, the NTSC firmware does not.
Yep. With the i-frame double the fps I used to get a large gap, now being matched to the fps it's only a small jump.
The small jump still sucks, IMO.Yep. With the i-frame double the fps I used to get a large gap, now being matched to the fps it's only a small jump.
New problem and I don't know yet what to do. Not only does the NVR reboot on an event, but when it does, it does not always re-establish network connectivity. Sometimes just pulling the Ethernet cable off, waiting, and plugging it back in resolves the problem. The rest of the time, I have to Restart the NVR. Message I get is the network login timed out. Anyone else ever see this?
I guess I have to install SD cards in all the cams, as yesterday I lost about 20 hours of recordings. I really hope Dahua comes out with new firmware soon.
I've had this happen once. Thought it was something local to my setup.New problem and I don't know yet what to do. Not only does the NVR reboot on an event, but when it does, it does not always re-establish network connectivity. Sometimes just pulling the Ethernet cable off, waiting, and plugging it back in resolves the problem. The rest of the time, I have to Restart the NVR. Message I get is the network login timed out. Anyone else ever see this?
@Tygunn -- that's the last update I heard (from 4/5).Just heard back from Andy. The problem has been reported to Dahua and will be addressed in an upcoming firmware version, which he reckons should be out soon.
@Tygunn -- that's the last update I heard (from 4/5).