Some feature requests

Hello,

First of all thank you for this excellent software. As a new non-experienced user I ran with some problems in my first build and I think it would be helpful for some other users like me to include the following options:

1) Option to install OptioMemoryFix.efi instead of OsXAptioFix3Drv64.efi.
2) Option to uninstall drivers and also to show what drivers are already installed
3) When selecting audio driver (for example ALC1220) have a warning message displayed saying to be sure to install first the 100 / 200 / 300 series Audio Support and/or audio device ID patch.

1) Already implemented in latest standalone Clover installer.
2) We've investigated doing this but it's not a simple thing to do
3) This is noted in announcement thread and in descriptions for each option.

MacMan said:

3) This is noted in announcement thread and in descriptions for each option

Click to expand...

Macman,

congratulations on MultiBeast 10.4, especially new AppleALC audio option (works great for Realtek S1220A )!

Are you planning to add any footer notes to AppleALC option such as:
- Use patch to rename HDAS to HDEF /Volumes/EFI/EFI/CLOVER/config.plist. (this is included under Realtek ALCxxx ...)

Finally a solution to the audio nightmare.

Thanks a million!

Yes, I forgot to add that.

I've updated the announcement post with that information.

MacMan said:

Yes, I forgot to add that.

I've updated the announcement post with that information.

Click to expand...

Great!

Considering that the Installation Guide states "It requires no experience and all of the basic installation and post-installation tools are available on tonymacx86.com" - seems like people new to this will need some hand holding to correctly patch config.plist.

Could the HDAS ->HDEF patch be included in the AppleALC option (same as in the Realtek options)?

In next version of MultiBeast we are looking to move HDAS ->HDEF patch to the root of Audio since it's now appropriate for AppleALC or Toledo's.

MacMan said:

In next version of MultiBeast we are looking to move HDAS ->HDEF patch to the root of Audio

Click to expand...

Makes sense. Also, it might be worth adding some discussion about the correct sequence to install audio and help de-mystify the process, which must be one of the single most-difficult things for NOOBs (that would be me trying to get audio working).

Macman,

Some thoughts on helping first time builders:

Unlike the Unibeast process, which is a fairly straight forward check list, MultiBeast requires builders to really identify the components of their system and make correct decisions about choosing and installing drivers, especially audio.

People doing a first build might have an easier time with audio if some of acronyms and terminology were explained, for example:

ALC – automatic level control is a technology to control power output to the speakers

Realtek ALC – drivers for Realtek audio chipset ICs as found on motherboards in the Tonymacx86 Buyer’s Guide

Codec – hardware or programs for encoding/decoding digital audio signal data

…..

As an audio NOOB, I would have benefited from some discussion like this:

Getting audio working on your new build takes some work. Before you start, be aware that:

1. MultiBeast audio drivers are designed for systems with an HDEF address
2. Some motherboards will have HDEF out of the box. If not, you have to apply a patch to the config.plist file to convert
HDAS to HDEF. Look for this patch in MultiBeast Audio.
3. A new AppleALC kext may greatly simplify the configuration of audio on your new build.
4. Alternatively, you can use a Realtek ALCXXX driver to match the audio on your motherboard
5. You can’t easily undo a MultiBeast customization. Before launching MultiBeast, make a backup of the macOS drive using Carbon Copy Cloner or Superduper. If you have a problem getting audio to work, boot the backup macOS and use it to erase your internal drive, and then clone your backup macOS to the internal drive. Now you have a clean install again.

MacMan said:

since it's now appropriate for AppleALC

Click to expand...

The AppleALC/Lilu audio option from MultiBeast 10.4 also worked for OSX Sierra on a 9 series system (Z97-A) that has an HDEF address. Not perfect, however, as this 9 series system with AppleALC/Lilu lost audio after sleep. Does Toleda troubleshoot AppleALC?

Is there a possibility of working out a baked-in SSDT, etc to address Thunderbolt? This issue is in regard to no hot-plug support and the current limit of only a single Thunderbolt 3 port available on dual-port add-in cards? (All of this works in Windows 10.) Please and thank you.