Search results

my system did not like 5.3.3.3 at all. ram went straight up to nearly 6G and CPU jumped straight up to 100 and stayed there. reverted back to 5.3.3.2 which was stable (for me) for more than 24 hours up time. that is a big improvement (for me) on previous versions which had been randomly...

I have always had awesome service from Andy and his deliveries are currently taking 8 days to reach New Zealand, which is faster than some domestic suppliers here at the moment, with level 3 lock-down. Chris. [not a builder]

UI3

me too, on 1x 8MP dahua, I followed someones advice and de-selected "use RTSP/stream timecode" in BI and that seems to have fixed it.... time will tell.

It was problematic for a while, for some users, however the last two builds have resolved most issues, it seems.

I have slightly different settings for all 3 cameras as they are each at different angles, distances, lighting conditions, etc (3 separate locations) The main tip I can give you is forget about using default settings and experiment with manual exposure settings (for daytime I am using 1/2000...

I have 3 of these for LPR: IPC-HFW5241E-Z12E I only buy cameras from Andy: US $225.15 7% OFF|2019 New Arriving Model IPC HFW5241E Z12E 2MP Starlight WDR IR Bullet AI Network Camera ,free DHL shipping|Surveillance Cameras| - AliExpress There are some tricks to getting these working well at...

which version of BI are you running? the latest version shows the full stream in UI3 for me

5.2.9.18 is out now

Just had an email reply from Ken now

for me, 5.2.9.17 has been a big improvement and almost eliminated the unexpected service restarts..... I have had two days uptime now with no restarts on 1 of my BI systems and only 1 restart on the 2nd system this stability along with main (HD) streams now showing in UI3 makes me very happy

I have had great success with small bits of self-adhesive "Draught Excluder". I apply 3 bits in a triangle surrounding the tiny microphone hole. Kills wind noise but microphone is still effective. It comes in 5m rolls, 5mm wide, consists of many fine synthetic hairs sticking out of the adhesive...

BI rocks! You may start out small but adding cameras is addictive. I started with 3 and am up to 29 now that BI can handle them (using substreams).

5.2.9.6 still has service crashing for me

I just tried matching FPS & iframe (on main stream and substream) on one camera and did not see any difference, so am leaving the others as they are (low FPS on substream).... happy with the trade-off and don't use autocycle

Yeah, as it is random and I now have a fully redundant (duplicate) BI system running, the chances are one of my two BI instances will catch the few seconds that are lost while the other system recovers. I feel happier now having the second system ticking away (headless) in the corner as a...

If it works for you that is great I have 29 cameras at different frame-rates (some of the LPR cameras at 50 FPS with their substreams at 3 FPS) and no stuttering problems. Until UI3 is able to view the full stream when individual cameras are selected, I prefer to keep the resolution of the...

hit and miss here also. same error did happen a while ago (in May 2019) when they needed to increase their AWS resources also had it happen when BI was too busy doing something, however now with sub-streams taking a lot of load off my CPU, I would have thought that would be less of an...

Thanks

did you get toast to work? I get an error about a DLL file missing [api-ms-win-core-winrt-l1-1-0.dll]. I have downloaded it and put it in the BI directory & windows/system directory but this has not helped.

this solved the problem for me: (to be clear, I had to disable "Require/decode all camera frames when streaming")

He has only posted a few times - each time supporting Digifort..... so "Peter / walet39" is probably an employee or reseller.

Digifort is massively expensive.... thousands of dollars to get what BI gives me for $100, with 29 cameras

It may be just coincidence, but deleting the offending camera and re-adding it (i.e. letting BI auto-detect it, not restoring the old settings) resulted in no irregular time-stamp overnight, so maybe a legacy setting on that one camera was causing the time-stamp + clip length corruption

thanks

ah, now that you mention it, I did see that twice last night on a single camera (same symptoms you describe.... time-stamp out by 3.5 hours + clip length corrupted) - camera is not set to do any reboot. 1 camera out of 29 is not too bad. I will delete it and re-add it to see if that helps.

I am very happy with 5.2.8.3... it has allowed me to expand to 29 cameras (thanks to substreams), with another 3 to be ordered from Andy soon, since the PC can now cope with them. Only two improvements I would like: main streams on UI3 (when individual cameras are selected) and several times a...

oops... yeah UI3 thanks just noticed there is still something funny going on with this version (as in previous) with a clip showing 49d16h40m40s length good things take time

yep. 5.2.8.2 -> no rectangles on BI3 plus looks like a few other fixes still only sub-streams on BI3 though

I use two of these cameras for LPR (OpenALPR), zoomed in to maximum, and because they are at max zoom, they have focus problems if left to switch by themselves (even with reflective tape as an IR auto-focus point), so I use "schedule" and drop to black&white 40 - 50 minutes before they would...