Search results

5.4.6.4 was "confirmed stable". That's how we got into this mess. Thank you.

We are not allowed to have all features working in every release

Ken says he's fixed it again in whatever version is about to come out

5.4.7.5 broke ONVIF again. Stick with 5.4.7.4 (as long as you can live with the other shit broken on that version)

Yeah I was having similar issues with both versions. I'm curious if someone else can verify.

Yes it's been reported. The make/break time is disregarded, so every time an ONVIF trigger hits BI (which can be several times a second), it's generating individual alerts for each. Can you specify what problems you were having. My BI motion detector cams were not having issues.

Do NOT install 5.4.6.4 or 5.4.7.0 especially if you use ONVIF triggers they're hopelessly screwed 5.4.6.4 should not be on the stable release train.

That's why we're having this discussion

Refute my claim then. What did I say that was false? What could I know about it, I only have 3 systems with mismatched FPS between sub-stream and main stream and have no issues?

Yes probably

"should" and "must" are two different things. there doesn't seem to be any side effect from not doing this, aside from UI3 not displaying the main stream in the correct FPS.

You don't even need it for activation. If it can't reach a server, it will give you a code to input on a website (which you can do on another machine) and a response code to input into the activation window.

Ken examined my Hikvision DVR that was experiencing compatibility issues with 5.3.1.2 and thinks he'll have it fixed

I can max out Blue Iris camera-wise and the whole system will eat up about 7GB of RAM I have to imagine this is NVIDIA-related

5.3.1.0 and 5.3.1.1 introduce more problems than they fix at the moment

You can no longer update if you don't have an active support plan

Yes. Don't check the 're-encode' box. You'll get the original format.

Notwithstanding the DST settings, are they successfully picking up NTP from your server?

It may help. If you're using UI3 then I think it might just be a quirk; does the correct clip play if you click it again

Did you turn off use RTSP timecode yet

This is a known issue, I reported it and so did a few others in various threads. Just stay at 5.3.0.3 if you're experiencing that issue

Thanks Oddly enough didn't affect hikvision cameras, just the DVR.

This broke all cameras streaming from a Hikvision DVR on RTSP. Did it for anyone else? Had to revert back to 5.3.0.3 on this system.

my bigger systems (40-64 cams) run Skylake i5s with 16GB of RAM, CIF resolution on the sub streams @ 256-512kBps where possible. about 20-40% CPU.

You don't need third party NTP software; Windows Time service has a server built in, you just need to enable it and then open the firewall port for NTP. At times I was pointing the cameras at my Cisco switches to sync time, now I have them syncing from the BI box, which syncs to a DC, which...

There are a lot of new point versions being released. Very few of them have actually grenaded one of my systems, often they just introduce some annoyance for a week or so until the next point release. Don't install a 5.x.y.0 release on a production system

Control Panel and all the Windows Vista-era control panel items are very slowly being assimilated. The Windows NT-style stuff though, lingers and persists forever.

it's been ok watch out if you use Intel PROset drivers for doing VLANs or something, update those first.

My 40, 50 and 64 camera systems use an SSD for the 'New' drive, which is bounced to one, two or three HDDs based on capacity requirements from there using Blue Iris' archiving settings. Ken made an adjustment last year to the way these file copies happen; the last drive in the chain gets its...

Okay but the default string (aka the Universal Good Dahua String) the find/inspect pulls out will work 120% of the time