Notifications
Clear all

Big Sur VP9 support on NAVI eGPU  

  RSS

Margio
(@margio)
New Member
Joined: 2 months ago
 

Hi everyone, I want to start by thanking this community for the awesome guides and support you provide. I lurked around a lot for my bootcamp setup but now I need to ask for help directly.

 

Does anyone know if VP9 (hardware) support is enabled for NAVI eGPU on MacOS Big Sur? I can’t make it work and use the eGPU in chrome or safari, it only works when I enable the software option which uses the CPU.

To be clear, the eGPU is detected by chrome and if i go to chrome: //gpu i can see it list but only support h264 HA, i also tried using Chrome Canary and enabling the experimental flags regarding the VP9 videotoolbox.

 

My setup:

2016 15” Macbook Pro (touchbar)

Razer Core X

AMD 5600XT

 

Thanks again,

any info or advice is appreciated.

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
oo.viper.oo
(@oo-viper-oo)
Active Member
Joined: 4 months ago
 

I'm running Chrome 87.0.4280.67 in Big Sur 11.0.1 (20B29) on Macbook Pro 16 with integrated Radeon Pro 5300M (Navi?) and external RX Vega 56. I can see Google Chrome Helper (GPU) on all three GPUs (internal Intel, internal 5300M and external Vega).

chrome://gpu/ shows only h264 in Video Acceleration Information section.

Mac Mini 2018 + Blackmagic eGPU Pro


ReplyQuote
Margio
(@margio)
New Member
Joined: 2 months ago
 
Posted by: @oo-viper-oo

I'm running Chrome 87.0.4280.67 in Big Sur 11.0.1 (20B29) on Macbook Pro 16 with integrated Radeon Pro 5300M (Navi?) and external RX Vega 56. I can see Google Chrome Helper (GPU) on all three GPUs (internal Intel, internal 5300M and external Vega).

chrome://gpu/ shows only h264 in Video Acceleration Information section.

Just to verify if it's a eGPU problem and since i read somewhere that Vega GPUs don't support VP9, maybe you can try disconnecting the eGPU, disabling automatic switching (from battery settings in apple preferences) and enabling both and from chrome://flags

Can you see the vp9 deconding under chrome://gpu video acceleration section now?

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
oo.viper.oo
(@oo-viper-oo)
Active Member
Joined: 4 months ago
 

Ok, did what you asked and now it shows VP9:

Video Acceleration Information

Decode h264 baseline 16x16 to 4096x4096 pixels
Decode h264 extended 16x16 to 4096x4096 pixels
Decode h264 main 16x16 to 4096x4096 pixels
Decode h264 high 16x16 to 4096x4096 pixels
Decode vp9 profile0 16x16 to 4096x4096 pixels
Decode vp9 profile2 16x16 to 4096x4096 pixels

Edit: The only needed switch is VideoToolbox VP9 Decoding

This post was modified 2 months ago

Mac Mini 2018 + Blackmagic eGPU Pro


ReplyQuote
Margio
(@margio)
New Member
Joined: 2 months ago
 
Posted by: @oo-viper-oo

Ok, did what you asked and now it shows VP9:

Video Acceleration Information

Decode h264 baseline 16x16 to 4096x4096 pixels
Decode h264 extended 16x16 to 4096x4096 pixels
Decode h264 main 16x16 to 4096x4096 pixels
Decode h264 high 16x16 to 4096x4096 pixels
Decode vp9 profile0 16x16 to 4096x4096 pixels
Decode vp9 profile2 16x16 to 4096x4096 pixels

Edit: The only needed switch is VideoToolbox VP9 Decoding

Happy for you! For me that doesn't work, probably because I'm trying to use an eGPU to decode VP9.

Just to help me troubleshoot, what card you see active under the driver information section? The Vega or the Navi?

 

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
oo.viper.oo
(@oo-viper-oo)
Active Member
Joined: 4 months ago
 
Posted by: @margio

Happy for you! For me that doesn't work, probably because I'm trying to use an eGPU to decode VP9.

Just to help me troubleshoot, what card you see active under the driver information section? The Vega or the Navi?

GL says following even when I'm typing this in Chrome on screen attached to Vega eGPU:

GL_VENDOR ATI Technologies Inc.
GL_RENDERER AMD Radeon Pro 5300M OpenGL Engine
GL_VERSION 4.1 ATI-4.0.47

Anyway, I would not expect this to be directly related as judging from the Chrome flag name, we're enabling VideoToolbox VP9 decoding and VideoToolbox is, I guess, completely different library and API than OpenGL. What I mean is that the fact that Chrome talks to one GPU via OpenGL does not necessary mean the VideoToolbox would use the same GPU.

Out of curiosity, why are you bothered with VP9 in Chrome? My Chrome plays 4K and 5K YouTube even with VP9 disabled and Safari in Big Sur plays 4K YouTube (though not 5K). And 8K falls back to CPU in both cases and is unusable.

 

Mac Mini 2018 + Blackmagic eGPU Pro


ReplyQuote
Margio
(@margio)
New Member
Joined: 2 months ago
 

@oo-viper-oo, for me Safari doesn't play videos in 4k unless I enable VP9 software decoding in developer tools, and by doing that it uses the CPU which for me doesn't provide a smooth playback and it uses a lot of CPU resources. Since I have an eGPU capable of decoding VP9 I want to use that. My dGPU is not capable of decoding 4k.

 

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote