Intel-Media-SDK / MediaSDK

The Intel® Media SDK
MIT License
933 stars 458 forks source link

[windows] RKL-S low power encoding not supported? #2784

Open mikk9 opened 3 years ago

mikk9 commented 3 years ago

We are currently testing RKL-S and noticed that the HEVC low power mode does not work for RKL-S on Windows 10. Testing the same on TGL-U no issue. I thought both are based on Xe LP, is there a technical reason why low power isn't working for RKL-S. This is tested on driver build 9864 and Handbrake as well as QSVEnc.


[20:00:16] + encoder: H.265 10-bit (Intel Media SDK)
[20:00:16] + preset: quality
[20:00:16] + options: ref=6:b-pyramid=1:tu=1:force-cqp=1:cqp-offset-i=2:cqp-offset-p=5:cqp-offset-b=10:lowpower=1
[20:00:16] + profile: main10
[20:00:16] + level: auto
[20:00:16] + quality: 28.00 (ICQ)
[20:00:16] + color profile: 9-16-9
[20:00:16] + mastering display metadata: r(0.6800,0.3200) g(0.2650,0.6900) b(0.1500 0.0600) wp(0.3127, 0.3290) min_luminance=0.000100, max_luminance=1000.000000
[20:00:16] + content light level: max_cll=825, max_fall=118
[20:00:16] * subtitle track 1, Deutsch [PGS] (track 1, id 0x3, Picture) -> Passthrough, Default
[20:00:16] * audio track 1
[20:00:16] + name: Surround 5.1
[20:00:16] + decoder: Deutsch (AC3) (5.1 ch) (640 kbps) (track 1, id 0x1)
[20:00:16] + bitrate: 640 kbps, samplerate: 48000 Hz
[20:00:16] + AC3 Passthru
[20:00:16] sync: expecting 3712 video frames
[20:00:16] qsv: integrated qsv adapter with index 0 has been selected
[20:00:17] qsv_hevc_make_header: MFXVideoCORE_SyncOperation failed (-17)
encqsvInit: qsv_hevc_make_header failed
Failure to initialise thread 'Quick Sync Video encoder (Intel Media SDK)'
[20:00:17] vfr: 0 frames output, 0 dropped and 0 duped for CFR/PFR
[20:00:17] vfr: lost time: 0 (0 frames)
[20:00:17] vfr: gained time: 0 (0 frames) (0 not accounted for)
[20:00:17] ac3-decoder done: 0 frames, 0 decoder errors
[20:00:17] hevc_qsv-decoder done: 0 frames, 0 decoder errors
[20:00:17] sync: got 0 frames, 3712 expected
[20:00:17] Finished work at: Fri Sep 10 20:00:17 2021
[20:00:17] libhb: work result = 3

# Job Failed to Initialise. Check log and input settings (3) 

QSVEncC (x64) 6.01 (r2458) by rigaya, Sep 6 2021 12:55:13 (VC 1929/Win)
OS Windows 10 x64 (19043) [UTF-8]
CPU Info 11th Gen Intel Core i5-11500 @ 2.70GHz [TB: 4.19GHz] (6C/12T) <Tigerlake>
GPU Info Intel UHD Graphics 750 (32EU) 350-1300MHz [65W] (30.0.100.9864)
Media SDK QuickSyncVideo (hardware encoder) FF, 1st GPU, API v2.04
Async Depth 3 frames
Buffer Memory d3d11, 38 work buffer
Input Info avqsv: H.265/HEVC, 3840x2160, 24000/1001 fps
AVSync cfr
Output HEVC(yuv420 10bit) main10 @ Level 5 (high tier)
3840x1600p 1:1 23.976fps (24000/1001fps)
Target usage 1 - best
Encode Mode Constant QP (CQP)
CQP Value I:29 P:32 B:37
QP Limit min: 22, max: 63
Trellis Auto
Ref frames 6 frames
Bframes 3 frames, B-pyramid: on
Max GOP Length 240 frames
VUI matrix:bt2020nc,colorprim:bt2020,transfer:smpte2084,chromaloc:topleft
MasteringDisp G(0.265000 0.690000) B(0.150000 0.060000) R(0.680000 0.320000)
WP(0.312700 0.329000) L(1000.000000 0.000100)
MaxCLL/MaxFALL 825/118
Ext. Features WeightP WeightB QPOffset
MFXENCODE: EncodeFrameAsync error: device operation failure..
Break in task MFXENCODE: device operation failure..
encoded 1 frames, 0.41 fps, 0.00 kbps, 0.00 MB
encode time 0:00:02, CPULoad: 0.8
QSVEncC.exe finished with error!

Start: 05:46:35
End: 05:46:46
Duration: 00:00:10
aidan2020sh commented 3 years ago

hi, can you try the case with RC6 disabled in BIOS? i am afraid it's the same as a known issue which has been resoloved but the fix is still under the release flow.

mikk9 commented 3 years ago

I'm afraid there is no RC6 option, we can't disable RC6 in the bios.

aidan2020sh commented 3 years ago

@mikk9 this issue looks similar to https://github.com/Intel-Media-SDK/MediaSDK/issues/2684. the ww33 IFWI fixed a R2R GPU hang issue, Could you update the IFWI to latest and have a try?

mikk9 commented 3 years ago

IFWI is a bios part or is there a standalone firmware?

aidan2020sh commented 3 years ago

In my understanding, BIOS is part of IFWI.

pacuro78 commented 2 years ago

the ww33 IFWI fixed a R2R GPU hang issue, Could you update the IFWI to latest and have a try?

Hi folks. What is ww33 ? Is it some kind of gpu bios version? Here comes the spring 2022 and I still can't have RKL ff encoding enabled while eu encoding works fine. Which part of my below bios should be updated?

EFI GOP Driver TigerLake - 17.0.1058 EFI GOP Driver SKL-CML - 9.0.1111 -> found 9.0.1112 update RAW GOP VBT TIGERLAKE - 240 RAW GOP VBT SKYLAKE - 231 OROM VBIOS IceLake - 1003

aidan2020sh commented 2 years ago

@pacuro78 hi, ww33 means "work week 33". There was an IFWI update in work week 33, 2021(about in Mid August, 2021). You just need update the IFWI(including BIOS) to the latest version with a tool named "Dediprog". Other customers reported similar issue and now those issue were gone after IFWI update. I am not sure from who you get those RKL boards and whether they can provide any platform support .

dmitryermilov commented 2 years ago

@pacuro78 , I'm trying to find some Intel contacts who can (at first internally) clarify RKL-S IFWI release process to me. I'll come back to this email thread if get some news.

pacuro78 commented 2 years ago

@aidan2020sh thanks for explaination. I run my cpu on Asrock H570M-ITX and have last bios update issued before mentioned date. This is not a problem as I am familiar with spi programmar and have changed several bios modules manually (intel z270). So I have replaced efi gop driver to new version within bios but stuck one step before flashing - there is, new for me, ultra tiny spi connector on this motherboard instead of regular pins connector. I have asked Asrock support to release new bios version for my mobo. Keep fingers crossed. @dmitryermilov thanks for your effort.

pacuro78 commented 2 years ago

Asrock support team answered in 24h after submitting the issue. Nice leadtime. +1 for folks in Asrock. They send me alpha bios with "some" fix. Unfortunatelly it did not fix ff encoding so I decided to replace microcode in this alpha bios for the last version "50" and flashed such an image. It helps! Now ff encoding works like a charm. 320 fps in fhd instead of poor 80 fps in eu mode.

mikk9 commented 2 years ago

You only changed the microcode?

pacuro78 commented 2 years ago

Asrock did something in alpha release bios and it didn't not fix the problem. They didn't tell me what they have changed. So I have upgraded microcode in their alpha and after that ff started working.