[Solved] Video playback broken on Vega 56

[darkmonk]

Hey guys. Wondering if anyone can chime in here-

I just finished tweaking all other aspects of this build, and it's running great (Mojave 10.14.2). Except for my Vega.

It's a reference Vega 56 (PowerColor). It worked great oob (at least I thought it did), but shows up as "Radeon RX Vega 64 8176 MB" instead of Vega 56. Then I tried to do video decode. In VLC or other 3rd party players the video plays, but then if you try to skip around to different parts of the video they all freeze to the point of needing a force quit. I also cannot load videos into the video player in Logic or Studio One for scoring. Black screen in both (I believe both rely on Apple/quicktime for the playback engine). Quicktime itself gives me an unknown error (-101) on both 1080p and 4k files (h264/.mov), which should be redflag number one.

I get 28k opencl score in Luxmark. Which seems quite good. Final Cut is a little delayed on timeline skimming in 4k, but Resolve works like a dream. I'm not too worried about encode since I expect to cpu encode here anyway (no quicksync on the xeons and VCE is not impressive), but if it helps to know hw_encoder shows true for h.264 but HEVC does not in videoproc.

I'm wondering, do I need to do the FB rename to the old Kamarang or something? I'm already running a custom dsdt for cpu names and ssdt for cpu PM tables, as the 2667 v2's are an unsupported cpu. I tried installing lilu/whatevergreen (not very familiar with it, last hack was a 280x system), and doing radeondeinit=true. Neither has helped so far. The only issue I have right now is this video playback issue, well other than the expected loud fan.

Any ideas would be much appreciated. Thanks

 

[darkmonk]

Small update - I didn't want to do another manual custom SSDT for FB rename, so I tried the lazy Clover Configurator select FB method by typing in Kamarang into the FB name box under graphics for the config.plist. No idea if that is even supposed to work. I also removed whatevergreen and lilu, unchecked radeondeinit. So far the problem is still there across all affected apps.

 

[darkmonk]

Guess what, it was the lack of system audio. Sometimes you just work so hard at something, you get lost in your work, get fatigued, and then miss the obvious...

I put off moving my audio interface over until after I fixed my video issues. Forgot that I never setup any integrated audio (I never use mobo audio and only use dedicated interfaces which are easy to install on macos, plus this is a server mobo so it never even crossed my mind). OOPS

This system is AWESOME.

Time to try and fix that annoying fan...