Alejandro Barreiro

Since it is a Ryzen processor with integrated graphics, I would recommend checking the NootedRed repository. Judging by the image, the issue lies with the graphics.

Good morning, Daniel @MaLd0n. Sorry for the delay in replying. I thought you were asking for the CoreAudio log extracted from the Console—my apologies... Here is the information you requested. HDAUniversal-Fast-Diagnostics-2026-10-14_10-08-17.zip

@MaLd0n I did what you mentioned, but while testing, I realized that CoreAudio has the same problem we had at the beginning: it can't handle the rear line-in (rear light blue) and the front microphone input (front pink) at the same time. Can this be fixed? AudioLog.txt.zip

Good morning, Daniel @MaLd0n: Well... checking in again. It’s working well... There is some noise, though I’m not sure if it’s a defect in the cables, the jacks, or the controller, so I’ll keep testing for a few more days. However, there is one thing that isn't working, and I don't know why. In macOS Tahoe's "Audio MIDI Setup," the onboard audio, USB interface, and HDMI all appear correctly and function properly. However, the "Aggregate Device" feature—intended to centralize input and output operations—doesn't work after setup. It fails with any device: onboard audio, the (generic) USB interface individually, or even when grouping the two devices. There is no audio input or output. I want to try restoring AppleHDA.kext to see if I encounter the same problem without AppleALC.kext, but I can't seem to install it. Do you have any idea why the "Aggregate Device" issue might be happening? I tried using MyKextInstaller to install AppleHDA.kext, but it won't install. I can't use OCLP forks because I need the official version to enable my Polaris graphics, given my processor's lack of AVX2 instructions. Is there a tool that can successfully install AppleHDA.kext on Tahoe? Thanks, as always...

Good morning, Daniel @MaLd0n. I have to reiterate what I said in my previous comment: YOU ARE A GENIUS!!! Everything is working correctly so far. I still need to run audio quality tests and try it out with Logic Pro or some mixing software to see if everything can be used simultaneously—the way I do with AppleALC.kext, though without the rear line-in (light blue) port. It seems that with your new driver, this should be possible without major issues by setting up an aggregate device in macOS's Audio MIDI Setup. Now, I have a few questions: 1- Is this package you sent me specific to my hardware, or can anyone with my codec get it working the same way? 2- Is this package only for the ALC887, or does it also include solutions for other codecs? 3- Do you release updates for this driver, like the developers of other drivers do? Here is the information generated by the last package we tested. Tomorrow, I’ll send you the results of the tests I run with a DAW—I’ll likely use Logic. This work will be published online with the appropriate credits. A million thanks... HDAUniversal-Fast-Diagnostics-2026-10-11_09-40-09.zip

@MaLd0n Okay... it works and the names don't change, but the behavior is strange. It’s as if the line-in and the front microphone can't work at the same time. If I select the front microphone, the line-in stops working—and no matter what I do, it won't work—so I have to select the rear microphone and then the line-in to get it active again. But then the front microphone deactivates and won't work even if I select it; I have to select the rear microphone and then the front one to get that working, and so on. Basically, whenever I switch between them, one of them always ends up not working. I’m going to be out of town for a few days and will be back on Sunday, so I’m leaving this info here and will get back in touch with you on Sunday or Monday. You're a genius!!! Best regards HDAUniversal-Fast-Diagnostics-2026-10-09_12-30-30.zip

Good morning, Daniel @MaLd0n . In this version, the line-in works, but selecting it changes the name of the front microphone, and the microphone stops working. This behavior is shown in the attached video. Both the front microphone and the line-in change names when one or the other is selected; what I am looking for is to have three separate stereo inputs (Rear Speakers, Headphones, Rear Microphone, Rear Line-in, and Front Microphone). The video is inside the ZIP file. Audio Tahoe 3.zip HdaCodecDump-Clover.zip

Sorry, Daniel @MaLd0n; I'm resending the message and attaching the information. No... ID 170 shows a name change. "Internal Speakers" are renamed to "Line Out," but everything works the same way. What we are looking to do is activate "Line In." Audio Sonoma.zip Audio Tahoe 2.zip HdaCodecDump-Clover.zip

No... ID 170 shows a name change. "Internal Speakers" are renamed to "Line Out," but everything works the same way. What we are looking to do is activate "Line In."

@MaLd0n Here is the codec dump extracted with Clover.HdaCodecDump-Clover.zip

I'll send it to you as soon as I can... Please wait a bit for me...

Thanks a lot, Daniel @MaLd0n, great work, as always! Everything works just like with AppleALC.kext. The only thing left is to test the sound quality, which I'll get to today. And well... the "Line In" (the light blue rear port) still isn't working; it would be fantastic if that could be fixed, but if not, it's fine as is.

Hi Daniel @MaLd0n ... Well, I managed to install macOS Tahoe 26.7.1 (25G241) on Ivy Bridge. Hardware: Processor: i5-3330 3.0 GHz Motherboard: GA-H61M-S1 Graphics: AsRock Phantom Gaming RX 570 4GB The motherboard's audio codec is ALC887; across macOS versions from High Sierra to Sequoia, I’ve always used layout-ID 11. This allows me to have two stereo "pink" inputs (which I split into four mono inputs) and two stereo "green" outputs (which I can also split into four mono outputs if I wish). Both audio outputs appear when expanding the menu bar menu, allowing for manual selection; the rear output shows up as "Internal Speakers," while the front output initializes as "Headphones." The only downside to this ID is that the "light blue" line-in port doesn't work. In macOS Tahoe, using HDAUniversal with the boot argument "alcid=11" results in the same initialization, but the front "Headphones" output doesn't work when selected in "System Settings," nor does it appear in the menu bar selection list. No matter what changes I make, audio always plays through the rear output. I’m sending you the codec info extracted from Sonoma (where it works with AppleALC.kext) and the info extracted from Tahoe (using HDAUniversal.kext) to see if there’s a solution. It would also be fantastic if we could get the rear "light blue" line-in port working. Audio Sonoma.zip Audio Tahoe.zip

Big Sur

MaLd0n Excellent tutorial !!! Thanks.

For which version of MacOS?

See if someone can help me with Monterey Clover. I'm trying to install legacy kext, but I can't enable writing, it remains read-only Attached image... Captura de Pantalla 2021-08-02 a la(s) 10.08.46.zip

English Good. As always, to begin with, a very special thank you to this great community, and to the Administrators and developers who post their experiences on this site, an even bigger thank you. As you will see in my profile, my hardware is made up of: Motherboard: GA-H61M-S1 Micro Threader: Intel Core I3-3220 (Ivy Bridge G3 with HD Graphics 2500) Dedicated graphics: MSI Geforce GT 710 2Gb DDR3 I have tried all the tutorials that can be found on the Internet, on how to activate Hardware Decoding, and the only one that worked for me was this guide in which I am commenting, but with a detail, the recommendations in this guide say: Ivybridge IntelGFX 0x01628086 Ig-platform-id 0x01620007 IntelGFX which refers to the Clover section of the FakeID, for this quality to work, it is necessary to have the FakePCIID.kext loaded and secondly use the Hardware ID 0x01628086, although it activates the Decoder, it does not work correctly in Final Cut, a when Transcoding, Rendering or Sharing, since its performance is very low and slow. Coincidentally by mistake, I found the solution! In my case, for my Hardware, instead of placing the IntelGFX 0x01628086, I changed it to the original one that corresponds to the integrated graphics that I have, which is IntelGFX 0x01528086. The result was amazing !!! Processes that took up to 2 hours to complete now take approximately 15-20 minutes. It seemed important to me to share this experience, given that the information found on the Web, for reasons of language and others, is not absolutely clear. I want to add a special thanks to MaLd0n, for having attended me in my numerous inquiries a few days ago. Thanks. Português Bom. Como sempre, para começar, um agradecimento muito especial a esta grande comunidade, e aos Administradores e desenvolvedores que postam suas experiências neste site, um agradecimento ainda maior. Como você verá em meu perfil, meu hardware é composto de: Placa-mãe: GA-H61M-S1 Micro Threader: Intel Core I3-3220 (Ivy Bridge G3 com gráficos HD 2500) Gráficos dedicados: MSI Geforce GT 710 2Gb DDR3 Tentei todos os tutoriais que podem ser encontrados na Internet, sobre como ativar a Decodificação de Hardware, e o único que funcionou para mim foi este guia no qual estou comentando, mas com um detalhe, as recomendações deste guia dizem: Ivybridge IntelGFX 0x01628086 Id-plataforma-Ig 0x01620007 IntelGFX que se refere à seção Clover do FakeID, para que essa qualidade funcione, é necessário ter o FakePCIID.kext carregado e em segundo lugar usar o Hardware ID 0x01628086, embora ative o Decodificador, ele não funciona corretamente no Final Cut, a durante a transcodificação, renderização ou compartilhamento, pois seu desempenho é muito baixo e lento. Coincidentemente por engano, encontrei a solução! No meu caso, para o meu Hardware, em vez de colocar o IntelGFX 0x01628086, mudei para o original que corresponde aos gráficos integrados que tenho, que é IntelGFX 0x01528086. O resultado foi incrível !!! Processos que levavam até 2 horas para serem concluídos agora levam cerca de 15 a 20 minutos. Pareceu-me importante partilhar esta experiência, visto que as informações encontradas na Web, por razões de linguagem e outras, não são absolutamente claras. Quero acrescentar um agradecimento especial a MaLd0n, por ter me atendido em minhas numerosas consultas há poucos dias. Obrigado. Español Buenas. Como siempre, para empezar, un agradecimiento muy especial a esta gran comunidad, y a los Administradores y desarrolladores que publican en este sitio sus experiencias, un agradecimiento aún mayor. Como verán en mi perfil, mi hardware se compone por: Motherboard: GA-H61M-S1 Microprosesador: Intel Core I3-3220 (Ivy Bridge G3 con gráficos HD 2500) Graficos dedicados: MSI Geforce GT 710 2Gb DDR3 He probado con todos los tutoriales que se pueden encontrar en Internet, sobre como activar de Decodificación por Hardware, y la única que me funciono, fue esta guía en la que estoy comentando, pero con un detalle, las recomendaciones en esta guia dicen: IvyBridge IntelGFX 0x01628086 Ig-platform-id 0x01620007 IntelGFX cual hace referencia al apartado en Clover del FakeID, para que funcione esta cualidad, hace falta tener cargado el FakePCIID.kext y en segundo lugar usar el ID de Hardware 0x01628086, si bien activa el Decodificador, no funciona correctamente en Final Cut, a la hora de Transcodificar, Renderizar o Compartir, dado que su rendimiento es muy bajo y lento. Casualmente por error, encontré la solución! En mi caso, por mi Hardware, en vez de colocar el IntelGFX 0x01628086, lo cambié por el original que corresponde a los gráficos integrados que poseo, que es IntelGFX 0x01528086. El resultado fue asombroso!!! Procesos que tardaban hasta 2 horas, en llevarse a cabo, ahora tardan aproximadamente 15 o 20 minutos. Me pareció importante compartir esta experiencia, dado que la información que se encuentra en la Web, por cuestiones de idioma y demás, no es absolutamente clara. Quiero agregar un agradecimiento especial a MaLd0n, por haberme atendido en mis cuantiosas consultas hace unos días. Gracias.

Bom dia MaLd0n. Eu segui este guia ao pé da letra e o VDADecoder funciona bem, mas o Hackintool mostra "Metal Low Power = No" e "Metal Headless = No", e não sei se isso é uma limitação do meu hardware ou se algo está faltando no minha configuração. Aqui estão meus resultados. iHack.zip Só quero saber se com meu Hardware posso ativar essas funções ou não! Infelizmente, não estou em posição financeira de mudar nada, então se é tudo o que pode ser feito, o que está feito, é assim que permanecerá. Muito obrigado novamente pela sua presença ... Ingles Good morning MaLd0n. I have followed this guide to the letter and VDADecoder works fine but Hackintool shows "Metal Low Power = No" and "Metal Headless = No", and I don't know if this is a limitation of my hardware or if something is missing in my configuration. Here are my results. iHack.zip I just want to know if with my Hardware, I can activate these functions, or not! Unfortunately, I am not in a financial position to change anything, so if it is all that can be done, what is done, that is how it will remain. Thank you very much again, for your presence ... Español Buen día MaLd0n. He seguido al pie de la letra esta guía y VDADecoder funciona bien pero Hackintool muestra "Metal Low Power = No" and "Metal Headless = No", y no se si esto es una limitación de mi hardware o si falta algo en mi configuración. Aquí están mis resultados. iHack.zip Unicamente quiero saber si con mi Hardware, puedo activar estas funciones, o no! Lamentablemente no estoy en condiciones económicas para cambiar nada, por lo que si es todo lo que se puede hace, lo que está hecho, así quedará. Muchas gracias otra vez, por tu prestancia...

MaLd0n, thank you very much for answering This I already solved it. It was that I had badly configured the graphics, although I would like to know if with my hardware full compatibility with Metal can be activated, since Hackintool shows "Metal Low Power = No" and "Metal Headles = No". Español MaLd0n, muchas gracias por contestar Esto ya lo solucioné. Era que tenia mal configurados los gráficos, aún que me gustaria saber si con mi hardware se puede activar la compatibilidad total con Metal, dado que Hackintool muestra "Metal Low Power=No" y "Metal Headles=No".

First of all, I want to greet this great community, in which a great deal of information is shared for people who want to learn; And it is worth adding an even greater thanks to the administrators of this site. I also want to apologize for my English, just in case, since Google translated what I expose. As you can see, the title of the publication says MSI NVIDIA GT 710 and in my profile it says "XFX GeForce GT 240 1024 MB", this is because I am changing the graphics of my Hack. The truth is that the change gave me a lot of joy since Final Cut works much better and faster when using the VDADecoder, but I am having the problem, that I cannot see the PDF files, open but appear black or multi-colored pixelated. This is only with PDFs, even though I also see the image on my monitor much sharper, but it is not smooth ... I attach images in ZIP. I hope you can help me... Thank you... Idioma Español Ante todo quiero saludar a esta gran comunidad, en la que se comparte gran cantidad de información para personas con ganas de aprender; y vale agregar un agradecimiento aún mayor, para los administradores de este sitio. También quiero pedir disculpas por mi Ingles, por las dudas, ya que Google tradujo esto que expongo. Como verán, el titulo de la publicaciónDice MSI NVIDIA GT 710 y en mi perfil dice "XFX GeForce GT 240 1024 MB", esto se debe a que estoy cambiando los gráficos de mi Hack. La verdad que el cambio me di mucha alegría ya que Final Cut funciona mucho mejor y mas rápido a la hora de usar el VDADecoder, pero estoy teniendo el problema, de que no puedo ver los archivos PDF, se abren pero se ven en negro o pixelado de varios colores. Esto es solo con los PDF, aún que también veo mucho mas nítida la imagen de mi monitor, pero no es suave... Adjunto imágenes en ZIP. Espero puedan ayudarme... Mil gracias... Archivo 2.zip

I am pleased to report that Catalina 10.15.7 works perfectly with this hardware configuration for now. I need to test the operation of Logic Pro, Final Cut and Motion. Some applications like Crome and Microsoft Office need repair, otherwise they won't work. I am attaching a ZIP, with some screenshots I will update information Imagenes.zip