with ALC898. you can try any of these layouts with AppleALC:
1, 2, 3, 5, 7, 11, 13, 65, 66, 98, 99, 101
Native macOS HD audio for not officially supported codecs - acidanthera/AppleALC
github.com
Thanks for the layouts list
@Feartech, however I think I have quite a bit of work before I can start testing layout IDs.
The card doesn't show up as a Realtek ALC898 by default. Do you or any of the audio expers like
@toleda know if AppleALC connects to any HDA device regardless of Vendor/Device ids? Or does it only look for/connect to those that it knows/supports? I ask in an effort to obtain a better understanding of how the process works; been doing allot of reading, but not quite sure where to start, or if it's even doable. But there's no fun if there's no hacking lol.
I'm thinking of trying one of these:
1. Try and spoof the Audigy FX card to act like the Realtek ALC898 controller that it uses. It currently shows up in Hackintool as a creative card, see data below. I'm wondering if spoofing the card would allow AppleALC to make a direct connection to the chip/codec and I can then try the layout-ids you mentioned.
2. Try creating a native AppleALC layout for the card/codec as is? This is why I'm wondering about how AppleALC detects devices, would it detect the card if a proper codec entry is added? I know creating these is not easy, but I found a guide that seems to be recent, and a pin configurator tool by
@headkaze that may prove to be use in this endeavor.
But my first obstical is that neither the Audigy FX or its ALC898 are listed under HDEF in IOReg (only the Intel audio controller is — but no kexts are attached). I was under the impression that this (HDEF rename) is required in order to get AppleHDA working? Thus I'm trying to figure out how to get AppleAlc to possibly recognize/interact with the card and do the renaming automatically, or perhaps I'll have to do the rename manually with a DSDT; or maybe adding the proper Vendor ID and device ID to AppleALC would do the trick...
For the sake of completion, here's the Hackintool PCI data for the Audigy FX card, reformatted for readability:
Vendor ID: 1102
Device ID: 0012
Subvendor ID: 1102
Subdevice ID: 0010
ASPM: Disabled
Vendor Name: Creative Labs
Device Name: Sound Core3D [Sound Blaster Recon3D / Z-Series]
Class Name: Multimedia controller
SubClass Name: Audio device
IOReg Name: P08@1C,7/PXSX@0
IOReg IOName: pci1102,12
Device Path: PciRoot(0x0)/Pci(0x1C,0x7)/Pci(0x0,0x0)
I also have a codec dump from Clover if anyone might be interested or if it may get us some better answers.
Finally, when viewed in Windows, the Vendor ID shows 10EC (Realtek) and the device was 0899 (ALC899 = rebranding?), so it seems that the HDA connection may be direct to the ALC898 chip and not a creative processor. The codec dump also lists it as 0899, though the chip on the card itself is labeled as ALC898.
[edit: While checking the revision ID of the supported ALC898 codec in AppleALC's supported codec list, I noticed it says "ALC898/899"; and the revision listed in my codec dump (0x00100003) appears to be the same as in the supported list "100003".]
I had some time to work on this tonight, so using the device properties section of OC's config I was able to change the vendor and device IDs and they showed up in Hackintool, but no luck with AppleALC so far. I've not figured out the names/values for the other properties to spoof them as well, but I should have more time to test this weekend, so will test those and see. I think one of my older boards uses an ALC898 chip, so will try to fire it up and try to get the data off of it. If that doesn't work then it may be time to roll up the sleves and try building a codec entry for AppleALC
