-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[h264_vaapi @ 0x55c0c2379240] No usable encoding profile found #366
Comments
go2rtc doesn't have a quick go2rtc:
log:
exec: trace
format: text
streams:
voordeur:
- "exec:ffmpeg -hide_banner -avoid_negative_ts make_zero -fflags nobuffer -flags low_delay -strict experimental -fflags +genpts+discardcorrupt -use_wallclock_as_timestamps 1 -c:v mjpeg -i http://admin:<password>@10.69.55.228/pbhelper/stream.mjpeg -c:v h264_qsv -g 50 -bf 0 -profile:v high -level:v 4.1 -user_agent -user_agent ffmpeg/go2rtc -rtsp_transport tcp -f rtsp {{output}}" |
Oh, I was not aware I could use a syntax like that :) |
for some reason part of the command got clipped off so make sure to recheck what I have |
I think main problem with "maybe incorrect parameters such as bit_rate, rate, width or height". PS. You can restream your source as MJPEG. So no CPU usage at all. |
I think this is fixed in the latest master version |
Hi,
Trying to switch my frigate setup to go2rtc
The above command produces the following ffmpeg exec in the logs:
Which is all VAAPI based... Something i never got to work in my old configuration either...
Here is a snip of the log file
This is my working config:
Any idea what i am doing wrong here?
The text was updated successfully, but these errors were encountered: