Frequently Asked Questions

What do I need to do with my previous sound modifications?
You must remove any of them. All the other changes including modified AppleHDA.kext, VoodooHDA.kext, HDAEnabler.kext, AppleHDADisabler.kext, realtekALC.kext, CodecCommander.kext, bootloader kext patches if any, patches in DSDT/SSDT if any, etc. are to removed.
The provided codec modification does not work for me, what can I do?
AppleALC was originally designed to be configured and built specifically for each user. However, a number of codecs were added by various people for their own needs. Consider these additions to be usage examples, because in no way they guarantee that the changes are meant to work on your configuration.
Why do I get a number of warnings when compiling AppleALC in Xcode?
Ask Apple why Mac policy is still not considered KPI, and why the linkage issue is unfixed after a long while. These two can be safely ignored.
Why do I have no sound in Recovery HD?
There is a hotplug bug on certain codecs, which allows only (front panel) phones work after booting to Recovery.
How do I build AppleALC for 10.7 or 10.8?

You need to have the 10.7 SDK installed
Copy usr/include/mach-o/fat.h and usr/include/mach-o/nlist.h to System/Library/Frameworks/Kernel.framework/Versions/A/Headers/mach-o/
Set the Base SDK project property to 10.7

Why does AppleALC deal with audio patches only, it can modify other kexts? AppleALC requires a number of kexts to be loaded before it is able to apply any memory changes due to the nature of its kext/kernel patcher. These kexts generally include HDD, USB, and Network stuff, making it practically useless for side kext patching. Moreover, the bootloaders offer the necessary patching as a convenient and reliable option, which AppleALC has no reason to interfere with.
If you still want to use AppleALC for this kind of work, you may do this in private at your own risk.

Provide feedback