We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Encode
No, this issue exist a long time
When setting "- extbrc 1- restrict -1", the output bitrate, md5, psnr are the same CBR: $ffmpeg -v verbose -hwaccel qsv -qsv_device /dev/dri/renderD128 -f rawvideo -pix_fmt yuv420p -s:v 1024x768 -r 30 -i 1024x768.yuv -frames:v 500 -c:v hevc_qsv -b:v 600000 -maxrate 600000 -extbrc 1 -strict -1 -vsync passthrough -y output.h265 VBR: $ffmpeg -v verbose -hwaccel qsv -qsv_device /dev/dri/renderD128 -f rawvideo -pix_fmt yuv420p -s:v 1024x768 -r 30 -i 1024x768.yuv -frames:v 500 -c:v hevc_qsv -b:v 600000 -maxrate 1200000 -extbrc 1 -strict -1 -vsync passthrough -y output.h265
my test env: OS:22.04 kernel:6.2.0-26-generic platform:DG2 (A380) maybe is platform-common
media-stack: libva:intel/libva@63d2b22 gmmlib:intel/gmmlib@5fb4180 media-driver:intel/media-driver@a9f2724 libvpl:intel/libvpl@2274efc vpl-runtime:852fa9f ffmpeg:FFmpeg/FFmpeg@3047f05
I think this should be unrelated to the format of the output , and AV1 and AVC should also have the same problem.
Others
No response
Removing any one of "-extbrc 1 -strict -1 " would result in a different outcome, which is expected. CBR: $ffmpeg -v verbose -hwaccel qsv -qsv_device /dev/dri/renderD128 -f rawvideo -pix_fmt yuv420p -s:v 1024x768 -r 30 -i 1024x768.yuv -frames:v 500 -c:v hevc_qsv -b:v 600000 -maxrate 600000 -extbrc 1 -vsync passthrough -y output.h265 VBR: $ffmpeg -v verbose -hwaccel qsv -qsv_device /dev/dri/renderD128 -f rawvideo -pix_fmt yuv420p -s:v 1024x768 -r 30 -i 1024x768.yuv -frames:v 500 -c:v hevc_qsv -b:v 600000 -maxrate 1200000 -extbrc 1 vsync passthrough -y output.h265
None
The text was updated successfully, but these errors were encountered:
@dvrogozh could you take a look whether it's expected or not?
Sorry, something went wrong.
dvrogozh
No branches or pull requests
Which component impacted?
Encode
Is it regression? Good in old configuration?
No, this issue exist a long time
What happened?
When setting "- extbrc 1- restrict -1", the output bitrate, md5, psnr are the same
CBR:
$ffmpeg -v verbose -hwaccel qsv -qsv_device /dev/dri/renderD128 -f rawvideo -pix_fmt yuv420p -s:v 1024x768 -r 30 -i 1024x768.yuv -frames:v 500 -c:v hevc_qsv -b:v 600000 -maxrate 600000 -extbrc 1 -strict -1 -vsync passthrough -y output.h265
VBR:
$ffmpeg -v verbose -hwaccel qsv -qsv_device /dev/dri/renderD128 -f rawvideo -pix_fmt yuv420p -s:v 1024x768 -r 30 -i 1024x768.yuv -frames:v 500 -c:v hevc_qsv -b:v 600000 -maxrate 1200000 -extbrc 1 -strict -1 -vsync passthrough -y output.h265
my test env:
OS:22.04
kernel:6.2.0-26-generic
platform:DG2 (A380)
maybe is platform-common
media-stack:
libva:intel/libva@63d2b22
gmmlib:intel/gmmlib@5fb4180
media-driver:intel/media-driver@a9f2724
libvpl:intel/libvpl@2274efc
vpl-runtime:852fa9f
ffmpeg:FFmpeg/FFmpeg@3047f05
I think this should be unrelated to the format of the output , and AV1 and AVC should also have the same problem.
What's the usage scenario when you are seeing the problem?
Others
What impacted?
No response
Debug Information
Removing any one of "-extbrc 1 -strict -1 " would result in a different outcome, which is expected.
CBR:
$ffmpeg -v verbose -hwaccel qsv -qsv_device /dev/dri/renderD128 -f rawvideo -pix_fmt yuv420p -s:v 1024x768 -r 30 -i 1024x768.yuv -frames:v 500 -c:v hevc_qsv -b:v 600000 -maxrate 600000 -extbrc 1 -vsync passthrough -y output.h265
VBR:
$ffmpeg -v verbose -hwaccel qsv -qsv_device /dev/dri/renderD128 -f rawvideo -pix_fmt yuv420p -s:v 1024x768 -r 30 -i 1024x768.yuv -frames:v 500 -c:v hevc_qsv -b:v 600000 -maxrate 1200000 -extbrc 1 vsync passthrough -y output.h265
Do you want to contribute a patch to fix the issue?
None
The text was updated successfully, but these errors were encountered: