NickM-27
commented
9 months ago if this is the same camera then it seems like the main paths are wrong. But in any case could try using ffmpeg: on the go2rtc camera that is having trouble
Closed jonwilliams84 closed 8 months ago
NickM-27
commented
9 months ago if this is the same camera then it seems like the main paths are wrong. But in any case could try using ffmpeg: on the go2rtc camera that is having trouble
jonwilliams84
commented
9 months ago if this is the same camera then it seems like the main paths are wrong. But in any case could try using
ffmpeg:on the go2rtc camera that is having trouble
Huh? The paths are right aren't they?...I probably needed to add that everything seems to be still working, regardless of the errors in the logs...I have only included config lines for the camera generating the errors.
Do you mean like this?: front_main:
If so, I tried this and only 2 of 4 cameras worked.
NickM-27
commented
9 months ago rtsp://REDACTED:554/Streaming/Channels/103
Is hikvision sub stream
rtsp://REDACTED:554/Streaming/Channels/101
Is what hikvision main stream is
jonwilliams84
commented
9 months ago rtsp://REDACTED:554/Streaming/Channels/103
Is hikvision sub stream
rtsp://REDACTED:554/Streaming/Channels/101
Is what hikvision main stream is
Yes - They work, but so do the ones I am currently using
gregewing
commented
9 months ago Just wanted to add that i'm new here, and I get these errors too. I came looking to see if this was an explanation for why object detection does not work at all for me.
XMaarten
commented
8 months ago I am experiencing exactly the same issue with also a Hikvision camera,
gregewing
commented
8 months ago I wanted to update that I am 50% confident that forcing TCP streaming from within frigate has stopped these messages appearing in my logs. certainly I don't see them during run, but only occasionally at startup.
It was not obvious to be how to force tcp streaming, but I figured it out while resolving broken images issues with UDP streaming. I did this by adding ffmpeg input args to each camera as per the screenshot.
NickM-27
commented
8 months ago You are overriding input args incorrectly. You are putting hwaccel args under input which is entirely wrong
jonwilliams84
commented
8 months ago I am experiencing exactly the same issue with also a Hikvision camera,
Update: I have updated the FW on the cameras affected to V5.5.801 build 211105 from V5.3.xxx and the errors have disappeared.
Frigate has been stable since making this firmware change on the camera.
jonwilliams84
commented
8 months ago I wanted to update that I am 50% confident that forcing TCP streaming from within frigate has stopped these messages appearing in my logs. certainly I don't see them during run, but only occasionally at startup.
It was not obvious to be how to force tcp streaming, but I figured it out while resolving broken images issues with UDP streaming. I did this by adding ffmpeg input args to each camera as per the screenshot.
If this helps, here is my config:
ffmpeg:
hwaccel_args: preset-vaapi
input_args: preset-rtsp-restream
output_args:
record: preset-record-generic
birdseye:
# Optional: Enable birdseye view (default: shown below)
enabled: False
go2rtc:
streams:
back_main:
- rtsp://REDACTED@10.32.99.6:554/ch1/main/av_stream
back_sub:
- rtsp://REDACTED@10.32.99.6:554/ch1/sub/av_stream
back_detect:
- rtsp://REDACTED@10.32.99.6:554/Streaming/Channels/103
cameras:
back:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/back_main
roles:
- record
- path: rtsp://127.0.0.1:8554/back_detect
roles:
- detect
detect:
...You are overriding input args incorrectly. You are putting hwaccel args under input which is entirely wrong
Granted, i'm new to this, and I take on board your feedback.
However, my intention is to modify the behaviour of ffmpeg when it connects to the camera, not what it does with output streams. I'm not using go2rtc, though maybe I should be...? My cameras all support multiple streams, and I'm using a RTX3060 for hardware decoding (and detecting), so I don' think go2rtc offers me an advantage. Please set me straight if I am wrong, I certainly don't have this instance performance tuned quite yet.
NickM-27
commented
8 months ago there are multiple problems.
hwaccel_argspreset-nvidia-h264preset-rtsp-genericusing go2rtc has absolutely nothing to do with the advice above
gregewing
commented
8 months ago Interesting... Looks like i've misunderstood something... I got that straight out of the documentation.
I'll re-read.
gregewing
commented
8 months ago Still some work to do, configuring it your recommended way (@NickM-27 ) results in UDP being used to capture video from the cameras, and I get random image corruptions. I'll tried adding in my fix to the hwaccel_args, but still no dice.
How should I be adding this kind of custom configuration for ffmpeg to force it to use TCP to talk to the camera(s)?
NickM-27
commented
8 months ago if you are using preset-rtsp-generic for input args then udp is not used, as tcp is forced by default
gregewing
commented
8 months ago Ok, so I've spent a little more time with the docs today and I appear to have a stable config, with input, output and hwaccel args in the right places. I'm using the presets as you recommended, and having them all set globally works for my camera types. No need to finagle the ffmpeg command structure to force tcp...
So thanks for pointing me in the right direction @NickM-27
Describe the problem you are having
Have been running frigate for a couple of years now and had no issues to report up until I upgraded to 0.13.1 from 0.12.
Now I keep getting logs like this ever 10 secs.
It appears to be only happening for one of my cameras (I have 3 of the same model). (HIK-VISION)
Version
0.13.1-34FB1C2
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Other Linux
Install method
Docker Compose
Coral version
M.2
Network connection
Wired
Camera make and model
hikvision
Any other information that may be helpful
No response