Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

A quick checklist for updating to VirtualSMC 1.0.7:
  • Replace the VritualSMCkext and sensor kexts.
    • If replacing them in /Library/Extensions folder, run Kext Utility to rebuild kernel cache (required).
    • If replacing them only in CLOVER/kexts/Other, no need to rebuild kernel cache.
  • Replace VirtualSmc.efi in the drivers64UEFI folder (for Clover 4xxx) or drivers/UEFI folder (for Clover 5xxx).
Remember that VirtualSMC consists of:
  • Kexts
  • EFI driver

Yes, dit it twice to check if I made a mistake..
not shure why it is not working :(
 
@NoiseCoalition are you still running an Apollo x8? OP lists you as confirming it works.
I'm using one I just purchased. Generally very good performance except:

In Pro Tools, if I set the playback engine buffer to 64 or lower my entire system freezes up when I arm a track for recording. The display status frozen and input devices are unresponsive for about 15 sec on, 15 sec off, until the team is disarmed. This may not be an issue because headphone latency is surprisingly tight at 128sample buffer but I wondered if you'd run into the same issue.

EDIT: If this isn't relevant enough to this thread I can start a new one. I'll leave that to your discretion, @CaseySJ.

@JingleDjango


I mainly use the Apollo x8p for extra inputs then send via ADAT to the Orion 32HD. That said, I set the Apollo as my main driver and was able to record / playback a large session at 32 samples and 64 samples via thunderbolt with no problems. I don't use Protools so these tests were done in Cubase 10 and Ableton 10. It was interesting to see how much higher the input latency for the Apollo was compared to the RME HDSPE MADI card that I mainly use.

Maybe it's a problem with Protools? Do you have any other DAWs installed on your computer to test? Unfortunately I let my Protools subscription expire recently.

Screenshot 2019-08-17 11.28.20.png

Screenshot 2019-08-17 11.28.36.png

Screenshot 2019-08-17 11.28.26.png

Screenshot 2019-08-17 11.28.30.png



Screenshot 2019-08-17 11.21.13.png

Screenshot 2019-08-17 11.21.01.png
 
The latency values with your HDSPE are quite good. Are you sure the actual converter latencies are reported too? What did you have hooked up to the MADI port of your RME?

The Apollo has its more elaborate UAD mixer that is has to compensate for, the RME has the more simple (but still great)TotalMix.
 
The latency values with your HDSPE are quite good. Are you sure the actual converter latencies are reported too? What did you have hooked up to the MADI port of your RME?

The Apollo has its more elaborate UAD mixer that is has to compensate for, the RME has the more simple (but still great)TotalMix.

I'm not sure if the converter latencies are reported. I kind of assumed they always were. It doesn't really matter that much to me because I mostly record using hardware monitoring so I can technically set my buffer to 2048 and be fine while tracking. I'll bring the buffer down to 32 or 64 if I'm doing something with soft synths / midi.

I have an Orion 32HD connected via MADI to the RME HDSPE MADI. The the Apollo x8p is feeding 8 more channels via ADAT to the Orion 32HD. Both the RME HDSPE MADI and Apollo x8p are clocked by the Orion.
 
Thanks for looking into it, @NoiseCoalition. I'll see what happens if i try lower buffers in Ableton or Logic the next time I'm at the studio.

Even still, roundtrip latency is perceptibly tighter with the Apollo x at 128 samples than with the HD Native PCIe card.
 
Last edited:
Is Apple Watch unlock working right after waking up from sleep? I have to wake first then press ESC and hit keyboard again to unlock with watch. I am using darkwake=0.
FYI. I found that darkwake=10 is the solution. Takes a bit longer to wake from sleep but unlocks with my Apple Watch every time now.
 
any1 succeeded to connect iMac(2018+) display as 2nd monitor via TB3???
This requires Thunderbolt Target Display Mode which, like Target Disk Mode and Thunderbolt Local Node, does not work on any Hackintosh at the moment. We're not sure when, if ever, these features can be made to work. There is, however, a lot of interest in solving this final piece of the puzzle.
 
You just pointed us to 2 very good peripherals:
  • A 3-pole umbilical antenna. I’ll purchase one myself! [update: order placed]
  • A PCIe x4 SATA card with Mac compatibility. In the build guide you will see that the suggested SATA cards are all x1, so I’ll add this to the list.
I didn’t had any problems with the Fenvi T919. Only some lag with the Apple mouse, but after some reading this was probably because the 2,4Ghz WiFi band. To improve the signal, I used the antenna which came with the Designare and connected it to the 2 middle screws on the Fenvi card (2 middle screws for no particular reason). Connection is perfect and no mouse lag, but at the same I time changed the settings in my router to not combine 2,4 and 5Ghz, but both separate. So don’t know exactly what did it that the mouse lag went away. My Hackintosh is standard connected to the 5Ghz and lan cable. So no need for me to buy additional antenna's.
 
Thanks for the guide! I used this for a similar setup, except I updated Clover to r5045 and eliminated the drivers64uefi directory from my EFI partition. I removed the -64 from the kext filenames, and I placed them in the drivers/UEFI directory. I followed the supplemental information to switch from FakeSMC to VirtualSMC as well. I haven't done anything for graphics other than the headless patch, haven't noticed any fan issues on 10.14.6 with the Vega56 after running Cinebench or LuxMark.
 
Last edited:
Back
Top