Jump to content


Just Joined
  • Content Count

  • Joined

  • Last visited

About Haive_Music

  • Rank
    InsanelyMac Protégé

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Haive_Music

    Success with 8700K, Aorus Gaming 7, Thunderbolt

    Your build is very similar to that of my own. Do you have Hotplug working for thunderbolt per chance?
  2. Today I ended up re-enabling my front case ports (USB 2.0 ones) and trying to use those with the original version of the AppleUSB kext. Problem definitely seems improved, and I can utilize the USB input. For some reason, the problem seems to revolve around using the USB 3.0 ports on the board.
  3. Interesting idea. I haven't tried this yet and just did. Initial results are mixed. It seems that it resolves the audio dropout error issue I was having. However, it's introduced a side effect in doing so. I personally don't notice this issue much anymore after switching to the Thunderbolt Interface, the issue is that it still affects other aspects of the audio sub system. For instance, if I stream to Twitch using OBS, even though I'm hearing stutter-free audio, the audio feed sent out to Twitch is now (instead of doing random drop outs), it's almost like it records and streams cleanly for 2-3 seconds, and then it starts almost looping/delaying back into it self "click click click click click" and the clicking noises progressively get faster and louder as time goes on. It's like a backfeed or something. It's interesting. The problem itself seems directly related to the USB Audio subsystem of OSX. It's really annoying.
  4. Sadly, no. I take it you must be experiencing the same issue too? Sad. I really wish I knew what was causing this issue. I did however, semi-work around this issue (note, semi-workaround). I built this machine specifically for audio production, so it sucked dealing with it. I finally gave up, sold my USB interface, and actually went back to a Thunderbolt interface. I managed to get a thunderbolt add-on card that was compatible with my motherboard working just well enough to support the Thunderbolt audio interface. Overall, the problem is resolved to the point where I can actually reliably work in my DAW without experiencing dropouts. However, often, if I go into any other application while the audio in the DAW is running (say, chrome or something), the audio starts to drop out and have issues. I'm really not sure what the underlaying problem that causes these types of issues is, but I *never* had these problems on my real mac, working on the exact same thunderbolt interface, on the exact same project files, and sadly, this Hackintosh is far more powerful and in every way superior hardware wise to that of my legit 2013 Mac Pro. My guess is, there's still some kind of a underlaying driver issue, or perhaps something within Clover that still isn't tweaked properly, although I've tried everything I could think of for months before going back to a Thunderbolt interface. As I said though, it's not without it's issues. For one, the issue technically still is there when switching apps. Sometimes audio does weird things on my system. The other thing is I gave up having hotplug Thunderbolt support AND an otherwise perfectly functioning Sleep. Both my computer and my audio interface now remain turned on 24/7, which....truly isn't ideal. However, I'll take those workarounds over going back to older legit Mac Hardware, having the ability to dual boot, and otherwise having a mostly perfectly functioning Hackintosh.
  5. Haive_Music

    ThunderBolt Drivers

    Cool. Well, I think I'm just going to have to accept the fact that the computer and thunderbolt devices need to be left on 100% of the time, at least until perhaps I decide to upgrade the motherboard and jump to an i9, which I don't see any point to doing just yet. Thanks for all your help and attempts at getting this to work man. Truly appreciate it.
  6. Haive_Music

    ThunderBolt Drivers

    I think we're getting closer. That seemed to get NHI working. Hot plug still doesn't however. So weird. Should I have the thunderbolt header cable plugged in or unplugged with this? I do have to ask, why is it when I enable the _DSM -> XDSM patch in Clover, that most of my PCI section items disappear? IOReg.zip
  7. Haive_Music

    ThunderBolt Drivers

    I appreciate you trying. I've tried all I can think of. Not sure why it's not working.
  8. Haive_Music

    ThunderBolt Drivers

    You're right. That's gone now too. With the other SSDT I was messing with, the 'NHI' driver was showing up. Now it's definitely not. I think BIOS settings are okay. I've attached some pictures of the various sections: The Thunderbolt Enumeration Mode is set to 'Legacy'. I tried to include a picture of that, but ran out of space on this post.
  9. Haive_Music

    ThunderBolt Drivers

    That definitely did something. My Alpine Ridge now shows up as a Titan Ridge (although, that may just be cosmetic). My PCI section is definitely different/shorter. Unfortunately, hotplug still does not work. Here's a new IOReg (with both those .amls applied), my EFI folder, and my PCI Screenshot. I had to remove the files in the 'APPLE' folder from my EFI. They were huge for some reason (24mb)? IOReg.zip EFI.zip
  10. Haive_Music

    ThunderBolt Drivers

    Sure, here you go. I included a copy of the SSDT as well. Maybe you will know why hotplug isn't working for me. *fingers crossed* IOReg.iojones SSDT-TB3.aml
  11. Haive_Music

    Gigabyte Aorus Gaming 7 Bios F5e

    Interesting. I just saw the F10 bios was released too. I'm anxious to try it, not that it probably adds anything significant unless they're running an i9 processor.
  12. Haive_Music

    ThunderBolt Drivers

    No, it wouldn't have accomplished anything. If BIOS is unable to detect the card, nothing past it on the OS side is going to detect it either. Windows showed no reference to the card being detected, nor did my devices I tried at a raw hardware level. Yes, I'm currently using the Alpine Ridge card - which works great under Windows. Under OSX it works, but ...I have no hotplug support. I basically lost sleep and always have to leave the computer and the thunderbolt devices on 24/7 now. I don't mind giving up sleep - I expected to lose that, but it'd be great to be able to turn my audio interface on and off. It works perfect on a real mac, and also under Windows with the Alpine Ridge. There has to be something I'm missing with my SSDT. That's interesting you tried the other 2 cards without success. I read a lot of reviews saying the Alpine Ridge just simply worked "better", so that was what I went with and the only one I tried. I'd be very interested in trying your SSDT to see if it fixes my hotplug issues since it sounds like you have the same board as me? Perhaps there's something wrong with my DDST and/or Clover config as well? I wish I knew more about these, but... still trying to learn. You wouldn't mind sharing your Clover config, DDST, and hotplug SSDT with me to try would you?
  13. Haive_Music

    ThunderBolt Drivers

    No dice on getting the Titan Ridge to work on my Gigabyte Aorus Gaming 7 motherboard. It isn't detected at all under Bios. Sad. I had high hopes to finally get hotplug working. Really wish I could get it working on my Alpine Ridge.
  14. Haive_Music

    ThunderBolt Drivers

    Hmmm... very interesting. I didn't realize that (and, more-so, that I had my supported chipsets mixed up). I very well may have to give this Titan Ridge card a shot on the Z370 and report back. It would be nice to see if I can get hotplug working with it, since...so far, I've been unsuccessful in my attempts with the Z370 and the Alpine Ridge * Edit - Just ordered up a Titan Ridge card to try. Hopefully it works, fixes hotplug, and also works under Windows. Will report back with further details when it comes.
  15. Haive_Music

    ThunderBolt Drivers

    I too was curious if my Z370 Gaming 7 would support the Titan Ridge card. However, my understanding of it was that the z370 only supported the Alpine Ridge and not the Titan Ridge card, and that the x299 was required to support the Titan Ridge chipset? Maybe I'm incorrect in this assumption? I'm definitely curious to know if it works on this motherboard or not.