-
Notifications
You must be signed in to change notification settings - Fork 339
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
[Bug]: VA_RC_ICQ not available in AV1 encoder on DG2 #1597
Comments
Auto Created VSMGWL-60768 for further analysis. |
Is there any way we can see or be informed of the status/progress of VSMGWL-60768 ? |
Is there any update to this? |
Hi, can someone please provide an update on this issue? Is there a fix in the works? Will it be addressed? Is there an expected timeline? Anything? |
@channeladam It seems Intel haven't figure out the AV1 ICQ support on DG2 platforms, including the next gen MTL, which is being actively developed in their new code path "media_softlet". HEVC ICQ on DG2 might just be a capability reporting bug (if DG2 and Gen12 share the same code path), while AV1 ICQ doesn't seem to be implemented yet as I can't find it anywhere. @Jexu may be able to provide more progress on this. |
Thank you @nyanmisaka, I appreciate your response and you creating this issue. I bought my Intel Arc A770 reasonably expecting/assuming HEVC & AV1 ICQ to be working since H264 ICQ does... I guess I was either foolish or misled. It would be nice to hear from someone at Intel to understand if AV1 ICQ will happen & when, or not... Thank you in advance. |
@channeladam I also bought the A380 for VP9/AV1 video encoding (VP9 appears to have the same issue BTW). It would be great to get some kind of communication on this issue. |
The RC modes of VP9 are correct even though I don't use it.
|
#1630 ONLY fixes the HEVC ICQ. |
Yet it doesn't work for me. Maybe it's user error or one of my packages it outdated, idk. When you try running it yourself does it work? |
What ffmpeg command did you use? |
Just a basic ffmpeg command. Basically the same as in OP only with vp9_qsv. I also tried running -crf and -qp. I then tried to use vp9_qsv with peertube in VBR. av1_qsv works fine in VBR. The 30 minute VP9 output works for 2-3 minutes and then seeking stops working and the video corrupts. There were no errors listed during transcoding. |
Confirmed the VP9 ICQ is also broken (device failed -17) on DG2 even if the driver reports VA_RC_ICQ. |
Can also confirm ICQ broken for AV1. |
I see this is now in progress. Is this just for AV1 or will VP9 also receive ICQ support? (I really just care about AV1 though) |
Hey, I noticed this had been placed in progress on July 20th. It's currently August 17th. Do you have any progress updates you can share? Thank you. |
We are now working on final quality tuning. The patch will be online soon. |
I noticed it was downgraded to priority 2. Does this mean it's ready for release? |
Thanks all of you. I'm closing this issue now. Please feel free to re-open for any other concerns or issues. |
It appears to work from initial testing. ffmpeg does throw this error with a simple command: [av1_qsv @ 0x55dc9d895880] Warning in encoder initialization: incompatible video parameters (5) ffmpeg -i "test.webm" -c:v av1_qsv -global_quality 20 -pix_fmt p010le -c:a libfdk_aac -profile 1 "output.mp4" |
av1_qsv works for me without this warning.
|
Hi @vid-bin |
Hi, QVBR doesn't seem to be working with this.
|
Doesn't seem to be implemented yet.
|
I see. Well, this works with h264_qsv on Linux so I was hoping this would add support for av1_qsv for it as well. EDIT: There seems to be references to QVBR within the media-driver code for AV1 so maybe this is an issue upstream? |
Hi @BlakeB415 |
I tested it, it works perfectly. |
Does this not include the LookAhead functionality? (i.e. icq_la). |
Nice to hear that! |
Currently, we didn't include LookAhead functionality. |
@leyu-yao you will already know what this next question will be... :) Is Look Ahead going to be implemented, and if so, what is the timeline? I'm sure almost everyone here would agree that the genesis of this issue was for targeting the purpose of storage/archival, and LA_ICQ is the recommendation by Intel for that... thank you. |
https://github.com/intel/media-delivery/blob/master/doc/quality.rst#enctools-and-extbrc https://github.com/oneapi-src/oneVPL-intel-gpu |
so... last comment here was september last year... any update? |
During the last few months, we did have some discussion on av1 LA_ICQ, but till now we haven't decided to implement it... For torage/archival usage, currently we recommend ICQ or VBR. I will update here if we got any implementation plan. |
Which component impacted?
Encode
Is it regression? Good in old configuration?
No, this issue exist a long time
What happened?
ffmpeg -f lavfi -i "testsrc2=s=1920x1080,format=nv12" -c:v av1_qsv -global_quality 25 -g:v 120 -f null -
What's the usage scenario when you are seeing the problem?
Transcode for media delivery
What impacted?
ICQ rate control is not available in AV1 encoder on DG2 on Linux.
Cannot use the
-global_quality
option in FFmpeg.Debug Information
I tried ICQ rate control with AV1 on Windows and it works just fine with FFmpeg.
Do you want to contribute a patch to fix the issue?
None
The text was updated successfully, but these errors were encountered: