[Config Support]: FFMPEG Errors After Switching to GO2RTC with Annke NCD800 #10041
Replies: 8 comments 7 replies
-
|
I have this camera but the hikvision version. The problem is that your hardware doesn't support that high of a resolution. you'll need to use the sub stream for detection |
Beta Was this translation helpful? Give feedback.
-
|
I am using the sub stream for detection. And it was working with the same hardware and full resolution using this config: ffmpeg: front:
|
Beta Was this translation helpful? Give feedback.
-
|
Those aren't correct urls for annke / hikvision. The sub stream would be |
Beta Was this translation helpful? Give feedback.
-
|
Yes, if you look at my current config in the first post above, you'll see that is what I am using currently and it isn't working. But the one from my previous config (the incorrect URLs as you stated) actually did work. |
Beta Was this translation helpful? Give feedback.
-
|
Your logs show that you're are pulling 5120x1440, this is not the resolution of the sub stream. The ffprobe is interesting, seems this camera may be buggy or you just need to use the other url. My hikvision works without issues (but my hardware also supports decoding 5120x1440 hevc |
Beta Was this translation helpful? Give feedback.
-
|
This Annke supports HEVC as well. And GO2RTC works perfectly with both as you can see from the VLC screenshots I posted above. Detect should be using: rtsp://[------]:[------]@front-ipcam.home.lab/channels/102 which is what is in the config. When I pull that up in VLC I get: |
Beta Was this translation helpful? Give feedback.
-
|
I am not talking about Annke, your server does not support decoding 5120x1440 whether it is h264 or h265. Looks like your screenshot is missing but your vlc screenshots above show both streams as 5120x1440 which is wrong for the sub stream. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I pulled the image because I didn't hide user/pass. The server did support 5120 x 1440 up until I changed the config. If I put back the old config, it works in H.264 at 5120 x 1440. This is the substream in current config. The resolution is not 5120 x 1440. It is the substream.
Also, I did notice the H.265 substream was choppy and dropping frames and have switched back to the H.264 substream. H.265 substream dropping frames. H.264 substream clean. |
Beta Was this translation helpful? Give feedback.
-
|
Vaapi doesn't support 5120x1440 at h264 (in fact, neither does Nvidia decode). They both max out at 4096 in either dimension. H265 supports greater dimensions. |
Beta Was this translation helpful? Give feedback.
-
|
If I use this: And this It works. But is that because I am not using VAAPI on that camera? Both cameras seem to be using the same amount of CPU. |
Beta Was this translation helpful? Give feedback.
-
|
It's weird because it was failing both H.265 and H.264 on the new config despite GO2RTC not having any issues. And on the old config it IS working in H.264 at full resolution. |
Beta Was this translation helpful? Give feedback.
-
|
UPDATE: Changing the detect stream from:
to
is what breaks it. |
Beta Was this translation helpful? Give feedback.
-
|
Also, it looks like for whatever reason
is causing frigate to detect from the main stream at full resolution even though when I use the same rtsp link in VLC, it pulls up the correct sub stream. It was doing the same on my rear camera as well so I have reverted both detect streams to the "incorrect" format of:
for the time being. |
Beta Was this translation helpful? Give feedback.
-
|
This is most likely a bug in the camera, potentially because vlc uses udp by default meanwhile frigate uses tcp by default. This behavior does not exist on my hikvision variant of this camera. |
Beta Was this translation helpful? Give feedback.
-
|
I've just noticed the Annke AC800 has the same behavior as the NCD800 when using
for the detect sub-stream. It seems to get redirected to the main stream. And this AC800 camera has been flashed with Hikvision FW. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
Running into an FFMPEG issue after updating config to use GO2RTC with one of my two cameras, the Annke NCD800. My other camera, the Annke AC800 works fine in the new config. I suspect this is related to the resolution of the NCD800 being 5120 x 1440 (as discussed here: Issue 6678) but even after switching to H.265, it still occurs. Some more observations:
Version
0.13.2
Frigate config file
Relevant log output
Frigate stats
Operating system
HassOS
Install method
HassOS Addon
Coral version
USB
Any other information that may be helpful
VLC confirmation of GO2RTC streams:
Prior config that worked had these settings for FFPMEG and the rstp stream with the camera set to H.264:
ffmpeg:
hwaccel_args: preset-vaapi
output_args:
record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
rtmp: -c:v copy -c:a aac -f flv
front:
ffmpeg:
inputs:
- path: rtsp://[------]:[------]@front-ipcam.home.lab:554/H264/ch1/sub/av_stream
roles:
- detect
- path: rtsp://[------]:[------]@front-ipcam.home.lab:554/H264/ch1/main/av_stream
roles:
- record
Beta Was this translation helpful? Give feedback.
All reactions