-
Notifications
You must be signed in to change notification settings - Fork 100
Open
Description
Which component impacted?
Encode
Is it regression? Good in old configuration?
No, this issue exist a long time
What happened?
- Linux 6.15 + FFmpeg 7.1.1
- libva 2.22.0 + gmmlib 22.7.2 + media-driver 25.2.3 + vpl-gpu-rt 25.2.3
- Run
ffmpeg -extra_hw_frames 40 -init_hw_device vaapi=va:/dev/dri/renderD129 -init_hw_device qsv=qs@va -filter_hw_device qs \
-hwaccel vaapi -hwaccel_output_format vaapi -i <INPUT> -an -sn -dn -vf hwmap=derive_device=qsv,format=qsv -c:v av1_qsv \
-preset veryslow -low_power 1 -b:v 6M -rc_init_occupancy 12M -bufsize 24M -bf 7 -g 240 -extbrc 1 -look_ahead_depth 40 \
-b_strategy 1 -adaptive_i 1 -adaptive_b 1 -strict -1 -async_depth 4 -y <OUTPUT> -v verbose- See error in about 5 seconds
[av1_qsv @ 0x55eaaf135a80] Invalid FrameType:0.
[vost#0:0/av1_qsv @ 0x55eaaf137b00] Error submitting video frame to the encoderThe error will occur only if both of these conditions are met: lookahead > 8 + async_depth > 1
What's the usage scenario when you are seeing the problem?
Transcode for media delivery
What impacted?
Using AV1e EncTools with lookhead enabled to improve video quality.
https://github.com/intel/media-delivery/blob/master/doc/quality.rst#av1
Debug Information
- libva 2.22.0 + gmmlib 22.7.2 + media-driver 25.2.3 + vpl-gpu-rt 25.2.3
- Yes.
03:00.0 VGA compatible controller [0300]: Intel Corporation DG2 [Arc A380] [8086:56a5] (rev 05) - vainfo.log.txt
- libva_trace.log.zip
- No GPU hang in dmesg.
Do you want to contribute a patch to fix the issue?
None
Metadata
Metadata
Assignees
Labels
No labels