[Support]: Camera feed corrupting/turning green #13559
-
Describe the problem you are havingI am having and issue where when I view a camera feed in Frigate it will be choppy/turn green/corputed. When I view directly thougth Reolink web portal it looks just fine. The camera is a RLC-510WA Version0.14.1 Frigate config filemqtt:
host: 192.168.1.xxxx
topic_prefix: frigate
user: xxxxx
password: xxxxx
detectors:
coral_pci:
type: edgetpu
device: pci
# cpu1:
# type: cpu
# num_threads: 3
go2rtc:
streams:
front_porch_camera:
- rtsp://admin:xxxxxx@192.168.1.xxx:554//h264Preview_01_main
back_yard_camera:
- rtsp://admin:xxxxxx@192.168.1.xxx:554//h264Preview_01_main
birdseye:
enabled: false
record:
enabled: true
retain:
days: 7
mode: motion
events:
retain:
default: 30
mode: motion
snapshots:
enabled: true
retain:
default: 30
cameras:
#**************************
# BACK YARD
#**************************
back_yard_camera:
ffmpeg:
inputs:
- path: rtsp://admin:xxxxxxx@192.168.1.xxx:554//h264Preview_01_main
roles:
- record
- path: rtsp://admin:xxxxxxx@192.168.1.xxx:554//h264Preview_01_sub
roles:
- detect
onvif:
host: 192.168.1.xxx
port: 8000
user: admin
password: xxxxxx
detect:
enabled: true
width: 640
height: 480
fps: 10
max_disappeared: 30
stationary:
interval: 10
objects:
track:
- bird
- person
filters:
person:
threshold: 0.75
mask:
- 480,60,480,180,390,165,390,60
#**************************
# FRONT PORCH
#**************************
front_porch_camera:
ffmpeg:
inputs:
- path: rtsp://admin:xxxxx@192.168.1.xxx:554//h264Preview_01_main
roles:
- record
- path: rtsp://admin:xxxxx@192.168.1.xxx:554//h264Preview_01_sub
roles:
- detect
detect:
enabled: true
width: 640
height: 480
fps: 7
max_disappeared: 30
stationary:
interval: 10
objects:
track:
- person
- car
filters:
person:
threshold: 0.75
car:
mask:
- 417,0,418,49,342,49,343,0
zones:
road:
coordinates: 417,38,158,89,0,141,0,109,190,43,415,0
driveway:
coordinates: 0.411,0.181,0.236,0.188,0.042,0.274,0.362,0.233,0.784,0.28,0.785,0.201
inertia: 3
loitering_time: 0
front yard:
coordinates: 0,138,0,480,73,480,179,417,457,142
front_door:
coordinates: 1,0.323,0.799,0.321,0.322,1,1,1,1,1
inertia: 3
loitering_time: 0
motion:
mask:
- 0.355,0.431,0.362,0.613,0.191,0.625,0.183,0.444
- 0.252,0.283,0.273,0.475,0.233,0.494,0.216,0.285
version: 0.14Relevant Frigate log output2024-09-04 13:55:22.047315337 [h264 @ 0x7fb954282b80] error while decoding MB 41 27, bytestream -7
2024-09-04 13:55:42.072266065 [h264 @ 0x7fb95423d400] cabac decode of qscale diff failed at 112 37
2024-09-04 13:55:42.072269869 [h264 @ 0x7fb95423d400] error while decoding MB 112 37, bytestream 186177
2024-09-04 13:55:42.104429563 [h264 @ 0x7fb95423d400] error while decoding MB 51 54, bytestream -5
2024-09-04 13:55:52.040660504 [h264 @ 0x7fb954203c80] cabac decode of qscale diff failed at 34 66
2024-09-04 13:55:52.040746820 [h264 @ 0x7fb954203c80] error while decoding MB 34 66, bytestream 57686
2024-09-04 13:58:42.415654635 [h264 @ 0x7fb95401c440] error while decoding MB 17 57, bytestream 148048
2024-09-04 13:58:42.438283684 [h264 @ 0x7fb95401c440] error while decoding MB 92 18, bytestream -5
2024-09-04 13:58:52.303106539 [h264 @ 0x7fb95423d400] left block unavailable for requested intra4x4 mode -1
2024-09-04 13:58:52.303529886 [h264 @ 0x7fb95423d400] error while decoding MB 0 39, bytestream 201624
2024-09-04 13:59:02.276438084 [h264 @ 0x7fb954359340] error while decoding MB 105 43, bytestream -7
2024-09-04 13:59:12.156772297 [h264 @ 0x7fb954359340] left block unavailable for requested intra mode
2024-09-04 13:59:12.156855521 [h264 @ 0x7fb954359340] error while decoding MB 0 26, bytestream 208879
2024-09-04 13:59:12.226323066 [h264 @ 0x7fb954359340] error while decoding MB 118 13, bytestream -5
2024-09-04 13:59:22.177854488 [h264 @ 0x7fb95400f980] left block unavailable for requested intra mode
2024-09-04 13:59:22.178017077 [h264 @ 0x7fb95400f980] error while decoding MB 0 67, bytestream 62481Relevant go2rtc log output2024-09-04 13:45:07.086430995 [INFO] Preparing new go2rtc config...
2024-09-04 13:45:07.611367652 [INFO] Starting go2rtc...
2024-09-04 13:45:07.755316701 13:45:07.755 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-09-04 13:45:07.755513581 13:45:07.755 INF config path=/dev/shm/go2rtc.yaml
2024-09-04 13:45:07.756047434 13:45:07.756 INF [rtsp] listen addr=:8554
2024-09-04 13:45:07.756328334 13:45:07.756 INF [webrtc] listen addr=:8555/tcp
2024-09-04 13:45:07.757125409 13:45:07.757 INF [api] listen addr=:1984
2024-09-04 13:45:17.084621966 [INFO] Starting go2rtc healthcheck service...
2024-09-04 13:47:10.971386865 13:47:10.970 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url=rtsp://admin:xxxxxx@192.168.1.xxx:554//h264Preview_01_main
2024-09-04 13:49:14.298280277 13:49:14.298 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url=rtsp://admin:xxxxxx@192.168.1.xxx:554//h264Preview_01_mainFrigate statsNo response Operating systemOther Linux Install methodDocker Compose Object DetectorCoral Screenshots of the Frigate UI's System metrics pagesAny other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Answered by
hawkeye217
Sep 4, 2024
Replies: 1 comment 1 reply
-
|
If these are Reolink cameras, you should use the recommended Reolink config for stability. |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
NickM-27
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


If these are Reolink cameras, you should use the recommended Reolink config for stability.