WriteBlueAlert no no bitmap 0 - new error

dimammx

Getting the hang of it
Joined
Apr 9, 2015
Messages
78
Reaction score
35
I am on 5.5.1.16 and error is still there unless setting of "pre-trigger video buffer" is un-checked.
Even with the box un-checked I occasionally do get the error (once every few days).

1635797819795.png
 

erkme73

BIT Beta Team
Joined
Nov 9, 2014
Messages
1,256
Reaction score
1,003
i was seeing them again, but on the same camera over and over. After carefully looking at all the camera variables, I found that I had mismatched specs between the main and substream on the camera gui. specifically, main was set to h264 and the sub was h265. Once I change them both to h265, the error stopped an has not returned.
 

dimammx

Getting the hang of it
Joined
Apr 9, 2015
Messages
78
Reaction score
35
Strange, I do not use sub stream at all and was getting the error.
 

erkme73

BIT Beta Team
Joined
Nov 9, 2014
Messages
1,256
Reaction score
1,003
Yeah, I would think this is a combination of triggers. I got it on another camera now, almost non-stop:

Line 49164: 2 11/1/2021 5:30:08.649 PM a185 WriteBlueAlert no bitmap 0
Line 49175: 2 11/1/2021 5:30:20.488 PM a185 WriteBlueAlert no bitmap 0
Line 49179: 2 11/1/2021 5:30:31.968 PM a185 WriteBlueAlert no bitmap 0
Line 49196: 2 11/1/2021 5:30:53.003 PM a185 WriteBlueAlert no bitmap 0
Line 49204: 2 11/1/2021 5:31:06.113 PM a185 WriteBlueAlert no bitmap 0
Line 49209: 2 11/1/2021 5:31:23.986 PM a185 WriteBlueAlert no bitmap 0
Line 49224: 2 11/1/2021 5:31:47.995 PM a185 WriteBlueAlert no bitmap 0
Line 49225: 2 11/1/2021 5:31:48.583 PM a185-clone WriteBlueAlert no bitmap 0
Line 49230: 2 11/1/2021 5:31:59.070 PM a185-clone WriteBlueAlert no bitmap 0
Line 49231: 2 11/1/2021 5:31:59.398 PM a185 WriteBlueAlert no bitmap 0
Line 49236: 2 11/1/2021 5:32:09.723 PM a185 WriteBlueAlert no bitmap 0
Line 49244: 2 11/1/2021 5:32:18.398 PM a185-clone WriteBlueAlert no bitmap 0
Line 49245: 2 11/1/2021 5:32:22.516 PM a185 WriteBlueAlert no bitmap 0
Line 49260: 2 11/1/2021 5:32:41.941 PM a185 WriteBlueAlert no bitmap 0
Line 49269: 2 11/1/2021 5:32:56.942 PM a185 WriteBlueAlert no bitmap 0
Line 49276: 2 11/1/2021 5:33:13.931 PM a185 WriteBlueAlert no bitmap 0
Line 49278: 2 11/1/2021 5:33:18.087 PM a185-clone WriteBlueAlert no bitmap 0
Line 49281: 2 11/1/2021 5:33:27.464 PM a185 WriteBlueAlert no bitmap 0
Line 49283: 2 11/1/2021 5:33:28.546 PM a185-clone WriteBlueAlert no bitmap 0
Line 49290: 2 11/1/2021 5:33:40.054 PM a185 WriteBlueAlert no bitmap 0
Line 49299: 2 11/1/2021 5:33:53.309 PM a185 WriteBlueAlert no bitmap 0
Line 49304: 2 11/1/2021 5:34:04.974 PM a185 WriteBlueAlert no bitmap 0
Line 49316: 2 11/1/2021 5:34:28.928 PM a185 WriteBlueAlert no bitmap 0
Line 49325: 2 11/1/2021 5:34:41.150 PM a185 WriteBlueAlert no bitmap 0

I disabled substream completely - played with resolution, bitrate, vbr/cbr, and none of it stops the errors. I do have pre-trigger enabled, with a value of 2 seconds. I really do want the pre-trigger, so I didn't try it disabled. I will now, but if that does solve the issue, that's not a very practical workaround. I sent an email to Ken again just a few min ago.
 

Tinman

Getting comfortable
Joined
Nov 2, 2015
Messages
793
Reaction score
628
Yeah, I would think this is a combination of triggers. I got it on another camera now, almost non-stop:

Line 49164: 2 11/1/2021 5:30:08.649 PM a185 WriteBlueAlert no bitmap 0
Line 49175: 2 11/1/2021 5:30:20.488 PM a185 WriteBlueAlert no bitmap 0
Line 49179: 2 11/1/2021 5:30:31.968 PM a185 WriteBlueAlert no bitmap 0
Line 49196: 2 11/1/2021 5:30:53.003 PM a185 WriteBlueAlert no bitmap 0
Line 49204: 2 11/1/2021 5:31:06.113 PM a185 WriteBlueAlert no bitmap 0
Line 49209: 2 11/1/2021 5:31:23.986 PM a185 WriteBlueAlert no bitmap 0
Line 49224: 2 11/1/2021 5:31:47.995 PM a185 WriteBlueAlert no bitmap 0
Line 49225: 2 11/1/2021 5:31:48.583 PM a185-clone WriteBlueAlert no bitmap 0
Line 49230: 2 11/1/2021 5:31:59.070 PM a185-clone WriteBlueAlert no bitmap 0
Line 49231: 2 11/1/2021 5:31:59.398 PM a185 WriteBlueAlert no bitmap 0
Line 49236: 2 11/1/2021 5:32:09.723 PM a185 WriteBlueAlert no bitmap 0
Line 49244: 2 11/1/2021 5:32:18.398 PM a185-clone WriteBlueAlert no bitmap 0
Line 49245: 2 11/1/2021 5:32:22.516 PM a185 WriteBlueAlert no bitmap 0
Line 49260: 2 11/1/2021 5:32:41.941 PM a185 WriteBlueAlert no bitmap 0
Line 49269: 2 11/1/2021 5:32:56.942 PM a185 WriteBlueAlert no bitmap 0
Line 49276: 2 11/1/2021 5:33:13.931 PM a185 WriteBlueAlert no bitmap 0
Line 49278: 2 11/1/2021 5:33:18.087 PM a185-clone WriteBlueAlert no bitmap 0
Line 49281: 2 11/1/2021 5:33:27.464 PM a185 WriteBlueAlert no bitmap 0
Line 49283: 2 11/1/2021 5:33:28.546 PM a185-clone WriteBlueAlert no bitmap 0
Line 49290: 2 11/1/2021 5:33:40.054 PM a185 WriteBlueAlert no bitmap 0
Line 49299: 2 11/1/2021 5:33:53.309 PM a185 WriteBlueAlert no bitmap 0
Line 49304: 2 11/1/2021 5:34:04.974 PM a185 WriteBlueAlert no bitmap 0
Line 49316: 2 11/1/2021 5:34:28.928 PM a185 WriteBlueAlert no bitmap 0
Line 49325: 2 11/1/2021 5:34:41.150 PM a185 WriteBlueAlert no bitmap 0

I disabled substream completely - played with resolution, bitrate, vbr/cbr, and none of it stops the errors. I do have pre-trigger enabled, with a value of 2 seconds. I really do want the pre-trigger, so I didn't try it disabled. I will now, but if that does solve the issue, that's not a very practical workaround. I sent an email to Ken again just a few min ago.
One thing about yours, when you get the error you REALLY get the error ! wow
 

erkme73

BIT Beta Team
Joined
Nov 9, 2014
Messages
1,256
Reaction score
1,003
You are correct, my apologies. I misread the number. It is 5.5.2.

As a work around, turning off the pre-trigger buffers on the trouble cameras (across all profiles) stopped my errors. But I'm going to add them back as I do like that functionality.
ETA: After adding the pre-buffers back, I have had zero errors. This fix appears to have solved the issue (for now)...
 
Last edited:
Top