My oldest camera, when in daylight mode, causes several errors fairly consistently.
W(1/Backyard): Skipping problematic audio stream: pcm_mulaw with 1 channel (causes muxer initialization failure)
W(1/Backyard): Unsupported audio codec pcm_mulaw for recording, disabling audio stream (camera: pcm_mulaw)
W(1/Backyard): Got out-of-order dts=4794084000 while last was 4794084000 on stream 0, adjusting timestamp
W(1/Backyard): No frame rate information available for stream 0, using default 30fps
W(1/Backyard): Likely timestamping error. Ignoring.
W(1/Backyard): Last message repeated 158 times!
This is a camera issue, however the “Got out-of-order…” message appear to be lining up with file corruption and stop playing of that camera in the Web page Live View page. I can reselect the camera and resume playing, however this is a constant issue.
The out of order seems to be tied to some issue or limitation in the camera, nothing to do with bluecherry. What I’m hoping is there is some setting in bluecherry that will allow the live view to coast through the errors and not require manual intervention to recover playback.
I’ve looked to switching to the web page live view as the client does not allow window size adjustments and still seems to be subject to memory leaks.
For reference, I’m using Bluecherry 3.1.13 on 24.04.1-Ubuntu
Can you try 3.1.14? I made several changes to audio, if we can’t support the stream or the stream causes problems we eject it but continue.
Loaded up 3.1.14, can see the altered audio error message. Took a while to get the “Out of order” error as in IR mode then camera does not generate the bad frames as often. Once the error came out, the live view of that camera image had the file corruption error and the image stopped. Only way to get it back is to reselect that camera.
The live view does not appear to be able to ride through an out of order frame sequence. The main problem is being caused by my cheap camera, was just hoping there was a way to have the live view ignore errors and keep displaying.
Positive, the 3.1.14 appears to have reduced the amount of log flood that was happening when using the client.
2025-09-11T22:50:28.537645-07:00 cameras bc-server[1873008]: I(1/Backyard): Last message repeated 1121 times!
2025-09-11T22:50:28.540761-07:00 cameras bc-server[1873008]: I(1/Backyard): Motion detected
2025-09-11T22:50:28.547822-07:00 cameras bc-server[1873008]: W(1/Backyard): Discarding problematic audio stream: pcm_mulaw with 1 channel (causes muxer initialization failure)
2025-09-11T22:50:28.548019-07:00 cameras bc-server[1873008]: I(1/Backyard): Audio stream discarded due to compatibility issues, recording video only
2025-09-11T22:50:28.585012-07:00 cameras bc-server[1873008]: W(1/Backyard): Likely timestamping error. Ignoring.
2025-09-11T22:50:33.743006-07:00 cameras bc-server[1873008]: W(1/Backyard): Last message repeated 63 times!
2025-09-11T22:50:33.743674-07:00 cameras bc-server[1873008]: W(1/Backyard): Got out-of-order dts=641685780 while last was 641685780 on stream 0, adjusting timestamp
2025-09-11T22:50:33.755430-07:00 cameras bc-server[1873008]: W(1/Backyard): Last message repeated 1 times!
2025-09-11T22:50:33.755585-07:00 cameras bc-server[1873008]: W(1/Backyard): No frame rate information available for stream 0, using default 30fps
2025-09-11T22:50:33.878990-07:00 cameras bc-server[1873008]: W(1/Backyard): Likely timestamping error. Ignoring.