Gigabyte B550 Vision D (Thunderbolt 3) + AMD Ryzen 7 3700X + AMD RX 5600 XT

[JimmakoS]

@CaseySJ Thank you so much for this guide. I build one for a friend of mine with the following specs.

CPU : AMD Ryzen 3600
GPU : RX 5700 XT
RAM : 16 GB
WIFI: DW1560 on board

The only problem is with UAD Arrow with sound (choppy, crackling)

 

[CaseySJ]

@CaseySJ Thank you so much for this guide. I build one for a friend of mine with the following specs.

CPU : AMD Ryzen 3600
GPU : RX 5700 XT
RAM : 16 GB
WIFI: DW1560 on board

The only problem is with UAD Arrow with sound (choppy, crackling)

@JimmakoS: Nice build!

@xtreem.p: I believe you faced the same choppy audio problem with UAD. Were you able to solve it?

 

[xtreem.p]

@JimmakoS: Nice build!

@xtreem.p: I believe you faced the same choppy audio problem with UAD. Were you able to solve it?

No...not on my B550 Vision D build, works great on the Asrock X570 and 5950X using Beta Bios 2.72

However, buildzoid suggested to disable global c-state to fix USB issues. I have not been able to test it myself

 

[xtreem.p]

@CaseySJ Thank you so much for this guide. I build one for a friend of mine with the following specs.

CPU : AMD Ryzen 3600
GPU : RX 5700 XT
RAM : 16 GB
WIFI: DW1560 on board

The only problem is with UAD Arrow with sound (choppy, crackling)
View attachment 500001View attachment 500002View attachment 500003

Nice build. But shouldn’t your RAM be in slots 2 and 4?

 

[JimmakoS]

No...not on my B550 Vision D build, works great on the Asrock X570 and 5950X using Beta Bios 2.72

However, buildzoid suggested to disable global c-state to fix USB issues. I have not been able to test it myself

The problem with the sound from speakers through UAD arrow also exist in Windows 10. I don't know if it is Thunderbolt issue or a problem with UAD arrow.
I read from the manual that two sticks of ram should be placed at 2 and 4 slots.

 

[xtreem.p]

The problem with the sound from speakers through UAD arrow also exist in Windows 10. I don't know if it is Thunderbolt issue or a problem with UAD arrow.
I read from the manual that two sticks of ram should be placed at 2 and 4 slots.

I dont have issue with with sound on Windows10, only in macOS.
Have you tried disabling Global C-State?

You are completely correct.. 2 and 4 it is! I must be getting old to not see clearly on the pictures Good job!

 

[Gigamaxx]

The problem with the sound from speakers through UAD arrow also exist in Windows 10. I don't know if it is Thunderbolt issue or a problem with UAD arrow.
I read from the manual that two sticks of ram should be placed at 2 and 4 slots.

Ryzen 5000 series
There is a fix for the Audio. It works for me, at least.

I made my own ALC887 for my Gigabyte Aorus B550 Pro AC.

It requires the latest ALC.kext, OC 0.6.4, and SSDT-5.aml (generated from Hackintool).

I have all my port line-outs working and in synch, Headphones, 5700XT (HDAU), and even tested Airplay.
The only remaining issues are the microphone inputs. Sleep/wake works with audio working normally after wake.

Obtaining the Audio Codec raw.
Use a USB with Clover 4988 No kernel patches or config edits. Hit F8 at Clover menu and go to Clover/misc./ALCXXXX files, and drag a copy of the ALCXXXX.bin to the desktop. Open PinConfigurator then go to File and select Desktop/ALCXXXX.bin file. Save the ALCXXXX.text file for editing later it has names and locations of the ports for testing and confirming.

Pin Configurator App.
headkaze/PinConfigurator: HDA Audio Codec verb ... - GitHubgithub.com › headkaze › PinConfigurator


Open a copy AppleALC.kext by right clicking and selecting "Show Package Contents". Right click on the info.plist and open with Propertree or other plist editor. Propertree and Xcode are the easiest for cut and paste.
corpnewt/ProperTree: Cross platform GUI plist editor ... - GitHubgithub.com › corpnewt › ProperTree


Save the info.plist edits and place the edited AppleALC.kext in OC/Kexts folder. Make your SSDT-HDAU.aml using Hackintool Utilities section. It should be labeled SSDT-5.aml. Add SSDT-HDAU.aml to OC/ACPI folder. Make sure to run Propertree/OC-Snapshot after adding or replacing SSDTs and kexts.

Boot up and test your Audio and open up Pin Configurator and go to File/Import/IOregistry.

The ALC layout should appear.

You can test ports and edit this then hit the "Get ConfData" tab and get a new set of Data.
Repeat the process from above and cut and paste the new values in the info.plist of the AppleALC.kext.

Below you can double click on devices and edit, ports types, internal/external, color etc..


After finalizing your configuration and testing, save the data and make a final edit to the ALC.kext info.plist.

I noticed that the AppleALC.kext has over 250 layout IDs, So I did a little experiment and removed them all then copied over a few of the relevant versions that may be used on AMD systems.



Give it a test, you may have to adjust or correct your EFI and use parts of this solution.
Add your own serials etc...

 

[JimmakoS]

Ryzen 5000 series
There is a fix for the Audio. It works for me, at least.

I made my own ALC887 for my Gigabyte Aorus B550 Pro AC.
...

Do you believe that with this process can fix the sound also from Thunderbolt 3 connection? Because I try to play sound trough UAD Arrow - Speakers connected via Thunderbolt 3 cable.

 

[Gigamaxx]

Do you believe that with this process can fix the sound also from Thunderbolt 3 connection? Because I try to play sound trough UAD Arrow - Speakers connected via Thunderbolt 3 cable.

It may help, you can also try using the midi audio tool to set bit rate and frequency of audio.
Go to top tool bar and select GO/Utilities/MidiAudio. Try setting the frequency 24-96MHz. There are a few options you may find one that solves it.
For me it is 32Bit 96MHz for mobo audio match.

It would be nice to create your own Codec it may include the Thunderbolt audio.

 

[xtreem.p]

Do you believe that with this process can fix the sound also from Thunderbolt 3 connection? Because I try to play sound trough UAD Arrow - Speakers connected via Thunderbolt 3 cable.

Have you tried to disable Global C-State in BIOS?