beepsilver
Getting comfortable
If at any time you changed the resolution of that camera including adding or removing VPP, you'll wipe your motion zones. Not saying you did that, just putting it out there.
Version 5 bugs and issues
- Thread starter Apollo
- Start date
If at any time you changed the resolution of that camera including adding or removing VPP, you'll wipe your motion zones. Not saying you did that, just putting it out there.
- Jul 31, 2016
- 54
- 14
It also happens when changing hardware acceleration from Intel to No which is necessary to eliminate the bottom border pixelation on a cloned camera.
Even attempting to restore these cameras from a backup seems to lose all motions settings for other profiles.
Looks like this is due to missing registry entries. I was able to manually fix my other profiles by adding an empty string called "camsync" and a dword called "sync" set to 0 on the relevant profiles for the cameras in the registry. Also reported the issue to Ken.
- Jul 31, 2016
- 54
- 14
V. 5.0.0.55 x64 seems to have some serious issues. The motion zones on one of my cameras was messed up (again), but in a different way than usual. When I cleared it to recreate the masks (again), it did not completely clear. There were two lines of random yellow and red boxes. When I saved the setting and clicked elsewhere in the app, the app hung.
Code:
Fault bucket 1382262686394385707, type 5
Event Name: FaultTolerantHeap
Response: Not available
Cab Id: 0
Problem signature:
P1: BlueIris.exe
P2: 5.0.0.55
P3: 5D02D006
P4: ffffbaad
P5:
P6:
P7:
P8:
P9:
P10:
wepee
Getting the hang of it
- Jul 16, 2016
- 255
- 59
Seeing that.....the small updates version of BI v5 does have some software bugs (in every minor release of BI v5.0.0.x.)
Would it be wise to follow the rule of thumb: We suppose to disable the automatic updates,
and wait for a few weeks, until the teething buggy problem is iron out before we start installing?
Previously, this rule of thumb applied to every minor updates on the earlier generation: BI v4.x.x.x
Would it be wise to follow the rule of thumb: We suppose to disable the automatic updates,
and wait for a few weeks, until the teething buggy problem is iron out before we start installing?
Previously, this rule of thumb applied to every minor updates on the earlier generation: BI v4.x.x.x
Yes, you shouldn't use automatic updates. And keep waiting a bit longer before upgrading to BI5 if you haven't yet. There are still things that need to be ironed out.
Yeah, mine seems to be triggering outside of the zones I have set as well in this version. Haven't tried editing the masks though.
Happy to report that 5.0.0.55 has fixed all my issues with remote management and UI3 hanging when switching profiles that are making cams active or inactive.
When trying to view alerts and clips on another computer using Firefox I am getting video stream was lost errors as attached. It doesn't happen with all files. Strangely I notice if you look at the properties of the clip it shows the Real time as 1 second and play time as 0.51. I can download the file and it plays ok.
If I look on my android phone the files I get this error on have a green arrow in the top LH corner and will open in my android photo app and not in the blue iris app. Other previous clips clips from the same camera open within the Blue Iris app. I made no changes to Blue Iris during the period it's changed.
EDIT- It seems all the files affected have been moved to my storage folder but I can't understand why these are there as earlier files are still in the AUX1 folder. I think update 56 has reset all my storage folders to 'new' from eg aux1, aux2 etc. My 'new' folder is only small and from there files would be moved to stored. But this doesn't explain why other files both earlier and later are stored in the correct folder.
If I look on my android phone the files I get this error on have a green arrow in the top LH corner and will open in my android photo app and not in the blue iris app. Other previous clips clips from the same camera open within the Blue Iris app. I made no changes to Blue Iris during the period it's changed.
EDIT- It seems all the files affected have been moved to my storage folder but I can't understand why these are there as earlier files are still in the AUX1 folder. I think update 56 has reset all my storage folders to 'new' from eg aux1, aux2 etc. My 'new' folder is only small and from there files would be moved to stored. But this doesn't explain why other files both earlier and later are stored in the correct folder.
Last edited:
5.0.0.56 fixes the BI4 import issue according to Ken also also resolved my issue with triggering outside of the defined motion zones.
Going through where all my clips are stored and correcting the locations solved it for me.
tech101
Known around here
I found one of my PTZ cameras stopped recording any motion / alerts immediately after the 5.0.0.59 update. It's a ptz camera that had 'override motion zones' set up on it. My others, that are the same, but didn't have override motion zones were not effected.
Unticking 'override motion zones' got it recording motion/alerts ok.
Unticking 'override motion zones' got it recording motion/alerts ok.
pelermon
Young grasshopper
- Sep 30, 2014
- 35
- 1
IAmATeaf
Known around here
pelermon
Young grasshopper
- Sep 30, 2014
- 35
- 1