A380 6GB hardware transcoding issues

[bandit8623 48]

transcoding regular 1080p and lower files work fine hardware.  going to 4k there are freezes for 200ms then plays fine again.  consistently does it around every 4 to 5 seconds.  doesnt matter what resolution i force it too still does the freeze.  ive tried with tonemapping on and off.

cpu and gpu are not being taxed above 20% .  transcoding directory is a ram drive. 

i normally dont transcode these large files but i have a few users with less than 5meg internet .  so i figured i would get the arc card to help them out.

e5-2695v4 cpu

sparkle A380 6gb

 

thanks

ffmpeg-transcode-failed-hardware_1.txt ffmpeg-transcode-working_1.txt embyserver (9).txt ffmpeg-transcode-tonemapping-freezeevery5 sec_1.txt

Edited April 6 by bandit8623
added tonemapping info

[Happy2Play 8296]

Something is not right as you should have more than DX11VA

But you are decoding in hardware and encoding in software.  And software encoding chokes and can not process fast enough (speed=0.289x)

>>>>>>  Hardware Decoders for hevc
        [X] DX11VA Intel Arc A380 Graphics - H.265 (HEVC)

>>>>>>  Selected Codecs
Decoder DX11VA Intel Arc A380 Graphics - H.265 (HEVC)
        Adapter #0: 'Intel(R) Arc(TM) A380 Graphics' Id:22181 (Driver: , Vendor: 32902)
        Max Bitrate: 117 Mbit/s - Frame Sizes: max 8192x8192
        Color Formats: NV12, YUV420P, P010 - Bit Depths: 8, 10
        Profiles: Main Profile (Level 6.1), Main 10 Profile (Level 6.1)

Encoder x264
        Max Bitrate: 781 Mbit/s
        Color Formats: YUV420P, YUVJ420P, YUV422P, YUVJ422P, YUV444P, YUVJ444P, NV12, NV16, NV21, YUV420P10, YUV422P10, YUV444P10, NV20, GRAY8, GRAY10 - Bit Depths: 8, 10, 12, 14
        Profiles: Baseline Profile (Level 6.2), Main Profile (Level 6.2), High Profile (Level 6.2), High 10 Profile (Level 6.2), High 4:2:2 Profile (Level 6.2), High 4:4:4 Predictive Profile (Level 6.2)

What drivers do you have installed?

Initialize MFX session: API version is 1.35, implementation version is 1.255

 

[bandit8623 48]

14 minutes ago, Happy2Play said:

Something is not right as you should have more than DX11VA

But you are decoding in hardware and encoding in software.  And software encoding chokes and can not process fast enough (speed=0.289x)

>>>>>>  Hardware Decoders for hevc
        [X] DX11VA Intel Arc A380 Graphics - H.265 (HEVC)

>>>>>>  Selected Codecs
Decoder DX11VA Intel Arc A380 Graphics - H.265 (HEVC)
        Adapter #0: 'Intel(R) Arc(TM) A380 Graphics' Id:22181 (Driver: , Vendor: 32902)
        Max Bitrate: 117 Mbit/s - Frame Sizes: max 8192x8192
        Color Formats: NV12, YUV420P, P010 - Bit Depths: 8, 10
        Profiles: Main Profile (Level 6.1), Main 10 Profile (Level 6.1)

Encoder x264
        Max Bitrate: 781 Mbit/s
        Color Formats: YUV420P, YUVJ420P, YUV422P, YUVJ422P, YUV444P, YUVJ444P, NV12, NV16, NV21, YUV420P10, YUV422P10, YUV444P10, NV20, GRAY8, GRAY10 - Bit Depths: 8, 10, 12, 14
        Profiles: Baseline Profile (Level 6.2), Main Profile (Level 6.2), High Profile (Level 6.2), High 10 Profile (Level 6.2), High 4:2:2 Profile (Level 6.2), High 4:4:4 Predictive Profile (Level 6.2)

What drivers do you have installed?

Initialize MFX session: API version is 1.35, implementation version is 1.255

 

well the cpu can actually handle software just fine if set to software.  its a beefy cpu.  passmark 19699

but i have it set to gpu  

if i have tonemapping off it gives me a warning that i have tonemapping in software disabled.  

drivers 5330  and latest 5382 same thing happen.

here is ffmpeg log for tonemapping off

ffmpeg-transcode-a3689fab-3e0c-4d01-954d-f96a69191ac1_1.txt

Edited April 6 by bandit8623

[Happy2Play 8296]

1 minute ago, bandit8623 said:

well the cpu can actually handle software just fine if set to software.  its a beefy cpu.  passmark 19699

but i have it set to gpu  

if i have tonemapping off it gives me a warning that i have tonemapping in software disabled.  

drivers 5330  and latest 5382 same thing happen.

 

here is ffmpeg log for tonemapping off

ffmpeg-transcode-a3689fab-3e0c-4d01-954d-f96a69191ac1_1.txt 41.72 kB · 0 downloads

Devs will have to comment.

But you could try change this setting but hdr will bring most cpus to there knees but still need to get your hardware figured out as I suspect drives per the api error.

 

Will look at other topics as ARC has a few most all with Driver issues.

[Happy2Play 8296]

Can you post your hardware detection log also.

[bandit8623 48]

8 minutes ago, Happy2Play said:

Devs will have to comment.

But you could try change this setting but hdr will bring most cpus to there knees but still need to get your hardware figured out as I suspect drives per the api error.

 

Will look at other topics as ARC has a few most all with Driver issues.

no option for that on my system.  weird

Edited April 6 by bandit8623

[Happy2Play 8296]

5 minutes ago, bandit8623 said:

no option for that. on my system

I meant enable Software setting, but per your setup Emby does not see your hardware Encoders.

But maybe @softworkzcan provide a little more insight.

Edited April 6 by Happy2Play

[bandit8623 48]

5 minutes ago, Happy2Play said:

Can you post your hardware detection log also.

hardware_detection-63848017182.txthardware_detection-63848017122.txthardware_detection-63848013304.txt

[Happy2Play 8296]

But per the log encoder query fails but devs will have more insight. 

2024-04-06 14:20:49.416 Info QuickSyncDx11CodecProvider: ProcessRun 'ffdetect_qsvencdec' Process exited with code -1 - Failed

As I have no idea why you only have DX11VA and not QuickSysc Intel.

[bandit8623 48]

2 minutes ago, Happy2Play said:

But per the log encoder query fails but devs will have more insight. 

2024-04-06 14:20:49.416 Info QuickSyncDx11CodecProvider: ProcessRun 'ffdetect_qsvencdec' Process exited with code -1 - Failed

As I have no idea why you only have DX11VA and not QuickSysc Intel.

ok thanks for taking a look!  much appreciated.  hopefully the devs will know why.

[Happy2Play 8296]

Have you tried an older drivers?

An old discussion on A380.

 

[bandit8623 48]

25 minutes ago, Happy2Play said:

Have you tried an older drivers?

An old discussion on A380.

 

i havent.  i just did a ddu of the drivers and reinstalled. same issue

[Happy2Play 8296]

Is this a headless setup?

Hardware Acceleration on Windows | Emby Documentation

[bandit8623 48]

hyper-v.  this is running on a vm.  380 pci passed through dedicated to only this vm.

 

Edited April 6 by bandit8623

[Happy2Play 8296]

3 minutes ago, bandit8623 said:

hyper-v.  this is ruinning in a

Not sure if it will work at all but the devs will have to comment.  Or if anyone has truly got it working.

 

[softworkz 3339]

6 minutes ago, bandit8623 said:

hyper-v.  this is running on a vm.  380 pci passed through dedicated to only this vm

I don't think that this can work inside Hyper-V. Can you install the latest Intel drivers inside the VM?
Without those drivers there's no HWA possible.

Edited April 6 by softworkz

[bandit8623 48]

1 minute ago, Happy2Play said:

Not sure if it will work at all but the devs will have to comment.  Or if anyone has truly got it working.

 

it should work as the host system no longer has accessto the gpu.

the pci device has been reasigned direct and only to this vm running emby.  drivers install just like on a baremetal system. to get the vm to boot had to install a dummy hdmi stick to make the gpu know there was a display connected

[bandit8623 48]

14 minutes ago, softworkz said:

I don't think that this can work inside Hyper-V. Can you install the latest Intel drivers inside the VM?
Without those drivers there's no HWA possible.

yep installs just like on bare metal system. the pci device is directly assigned to the vm. 

not the exact guide i used but this is just basics. https://devblogs.microsoft.com/scripting/passing-through-devices-to-hyper-v-vms-by-using-discrete-device-assignment/

 

no to be confused with gpu-partitioning

Edited April 6 by bandit8623

[softworkz 3339]

5 minutes ago, bandit8623 said:

yep installs just like on bare metal system. the pci device is directly assigned to the vm. 

Do any of the built-in features work, like screen capture?
You might need to connect a real monitor for this.

Also, ARC cards are very sensitive to BIOS settings on bare metal systems, most importantly the requirement for the "Resizable Bar" setting in the BIOS. I don't know whether Hyper-V can emulate this properly. 

[bandit8623 48]

3 minutes ago, softworkz said:

Do any of the built-in features work, like screen capture?
You might need to connect a real monitor for this.

Also, ARC cards are very sensitive to BIOS settings on bare metal systems, most importantly the requirement for the "Resizable Bar" setting in the BIOS. I don't know whether Hyper-V can emulate this properly. 

i have a dummy stick plugged in. thats the only way the vm will start. without it the vm crashes.  arc needs a display connected

it cannot emulate rbar properly,  but most cases its not needed. (just see less than 100% performance)   my buddy has the a750 no rebar and everythjing works fine

[softworkz 3339]

On my system, even the BIOS UI get corrupted without ReBar enabled, neither does the OS start.
 

Your hw detection log indicates a crash during the QuickSync detection without any specific log output from this run at all. I don't remember that I've ever seen that - there's always a log, even when it doesn't work.

The dummy plug doesn't tell you whether it's working, you can't assume that just because the VM start. 
That's why I'm suggesting to connect a real display first.

Emby is something that comes just at the end of the chain - when everything else is working.

[bandit8623 48]

20 minutes ago, softworkz said:

Do any of the built-in features work, like screen capture?
You might need to connect a real monitor for this.

Also, ARC cards are very sensitive to BIOS settings on bare metal systems, most importantly the requirement for the "Resizable Bar" setting in the BIOS. I don't know whether Hyper-V can emulate this properly. 

none of the arc control feature captures work it says no displays are plugged into an intel adapter.  broacast and capture only 2 things not working.

i can however see all other info like usage temp vram and such

 

[bandit8623 48]

Just now, softworkz said:

On my system, even the BIOS UI get corrupted without ReBar enabled, neither does the OS start.
 

Your hw detection log indicates a crash during the QuickSync detection without any specific log output from this run at all. I don't remember that I've ever seen that - there's always a log, even when it doesn't work.

The dummy plug doesn't tell you whether it's working, you can't assume that just because the VM start. 
That's why I'm suggesting to connect a real display first.

Emby is something that comes just at the end of the chain - when everything else is working.

i just connected a real display and the vm boots but still no capture or broacast option.  

without anything connected the vm wont start.

[Happy2Play 8296]

I guess milage may very as the card doesn't support Virtualization.

https://www.intel.com/content/www/us/en/support/articles/000093216/graphics/processor-graphics.html

https://community.intel.com/t5/Graphics/Intel-ARC-A380-questions/m-p/1522997/highlight/true#M122239

Found this interesting

Quote

In regard to the first question, the Intel® Arc™ A-Series GPUs do not support virtualization, hence the ability to install the driver on a VM through DDA is not tested nor supported by Intel.

 

[softworkz 3339]

15 minutes ago, bandit8623 said:

i just connected a real display and the vm boots but still no capture or broacast option.  

without anything connected the vm wont start.

I think these cards are just not made to work in this environment. For once, they are targeted at the consumer market, and even though there's a range of models for datacenter operation, that still doesn't mean that they can run virtualized. Unlike with pure GPU solutions like Nvidia or AMD, Intel's architectures have always been around iGPUs with shared memory - where they can do memory remapping instead of copying between system and GPU memory. My suspicion is that this is the reason why Intel cannot easily support virtualized environments.
For example, Nvidia have pretty early provided drivers for WSL (you can in fact use Nvidia HW acceleration when running a Linux version of Emby Server on WSL).
That was two years ago and (at least until recently) Intel does not provide driver support for this.

You really need to check back with Intel whether this is supposed to work in some way.   

Edited April 6 by softworkz