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

[zipb]

I am thinking of getting rid of all the speedstepping options in the BIOS, and also maybe hyperthreading just to see if this will help with stability and sheer CPU power for DAW usage. I know for a fact that Pro Tools Ultimate on PC needs this to work properly.
I have reasons to believe MacOS may misinterpret the way audio buffers(with their short bursts of high activity) work and will step down the CPU because of this.

Will this cause problems on a Hack? You can't really adjust these settings on a real Mac, and I wonder if MacOS will work properly if I do this in the BIOS.
I also remember there was this kext that made your Hack run at full throttle all the time. Forgot the name, it was quite some time ago.

 

[zipb]

I'm having a hard time using a network disk as a time machine backup. All good with my mojave macbook, but here I don't know if it's a normal issue for high sierra or the build has problems doing that

I have been using several QNAP NAS units for timemachine and CCC backups for years to good effect.

 

[jdlux]

Hello @jdlux,

"Pre-noob"?

This may be a USB 3 port stability issue that a number of our audio professionals have faced recently. Please have a look first at this post and we can go from there:

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

I have that same card and a brand new unopened Magic Mouse 2. I'll test it out tomorrow. I connected the mouse with the computer with the lightning-to-USB cable and it works now!!!! Thanks all!

www.tonymacx86.com

thank you will do!

 

[interobang]

Okay, some interesting updates. Always good to have such a device in the house!

• There appears to be a problem in Apple's implementation of IOUSB-to-IOSCSI.
• When we insert one drive, it mounts.
• When we insert a second drive, everything ejects first and then both drives mount. This leads to a "Disk Not Ejected Properly" warning.
• When we safely eject one of the two drives, the ejected drive remains in IOReg. It's as if the drive was not ejected.
• When we safely eject the second drive as well, still both drives remain in IOReg.
• When we then physically pull a drive out of the dock, both drives disappear from IOReg, but the drive that was not physically removed gets reconnected and remounted.

So in summary:

• MacOS seems to be treating these dual-bay docks as a single-bay dock when it comes to eject and mount.
• The only way to avoid the warning is to mount both drives before powering on the system and to eject both drives before physically removing either one.
• We can also mount one drive, then eject it (but not physically remove it), then insert the second drive. Now both drives will appear on the desktop without warning.

This was tested on an Apple MacBook Pro 13" 2020 model.

Wow, that is annoying. So no truly practical workaround then. But now if you've tested this on a MacBook Pro model, then that basically makes this device technically incompatible with even a legitimate a Mac. So I am tempted to simply return the device, and get a simple SATA to USB dock, for way cheaper, and start saving up for a NAS.

I short addendum to this issues various problems, is that if my computer goes to sleep then the drives disconnect as well.

Thanks for your in-depth look into this.

 

[kromuh]

Hey again @CaseySJ! Hope you're well. Everything's going swimmingly over here thanks to your assistance

Only issue I'm facing is my Fenvi T919 card seems to be significantly slower than I anticipated.
My hack gets 9mb/s Download on an internet speed test, while my phone consistently gets 75+mb/s on the same network in the same location.

Any recommendations on a better card for Mojave?

 

[oopsmybad]

On Mojave we've had a Jekyll and Hyde relationship between OcQuirks/OpenRuntime and OcQuirks-4/FwRuntimeServices. It seems the latter is better suited for Mojave.

I might mention that I've encountered two variations of OcQuirks/OpenRuntime -- the one you built and is included in the May 2020 Catalina Fresh Install zipfile, which uses OcQuirks.plist. Then there's the one that the Clover installer started providing in version 5120, which uses Clover's regular config.plist for configuration of the boot quirks.

The former (your) version has always worked wonderfully for me on Mojave... but, since 5120, the Clover installer squashes your version with its own every time I upgrade (say, from 5120 to 5121). If you don't remember to save a copy of the working (OcQuriks.plist) variants and replace them after the Clover upgrade, your system may not boot.

I don't think that's exactly what's happening here, but I thought it was worth mentioning...

Anyway, this finally pushed me into using OpenCore 0.6.0 (for Mojave), which has worked equally well as Clover.

 

[Rag]

Looks like you've put the labor back in Labor Day! Will work on 0.6.1 EFI soon for both Z390 Designare and Z490 Vision D.

@CaseySJ looking forward to your new version !!!! thank you

on the official page does it say 0.62? what would it be ?

GitHub - acidanthera/OpenCorePkg: OpenCore bootloader

OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.

github.com

 

[CaseySJ]

OpenCore 0.6.1 Released:

Releases · acidanthera/OpenCorePkg

OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.

github.com

@CaseySJ looking forward to your new version !!!! thank you

on the official page does it say 0.62? what would it be ?

GitHub - acidanthera/OpenCorePkg: OpenCore bootloader

OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.

github.com

** OpenCore 0.6.1 EFI ZIP has been Added **​

Please see this post:

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

OpenCore 0.6.0 VirtualSMC 1.1.5 Lilu 1.4.6 WhateverGreen 1.4.1 AppleALC 1.5.1 NVMeFix 1.0.3 With NVMeFix 1.03 , my system can't boot , neither with OC or Clover, but NVMeFix 1.02 seems ok

www.tonymacx86.com

It is necessary once again to copy the following values into one of the new config files:

• Serial Number
• Board Serial Number
• System UUID

These are easily copied-and-pasted from Hackintool:

 

[jdlux]

Cubase Pro 10.5.x has been less stable than previous versions, now at 10.5.20 it is sort of usable. I don't think Cubase alone is to blame, there are toxic combinations of 3rd party plug ins (of which I have quite a lot) that will cause crashes and weird behaviour.
A new shorter elicenser dongle helped a bit. I often rescan my plug ins in the VST manager. And I am still on Mojave.
I have less crashes with Logic Pro and even less with Bitwig, but I prefer Cubase for some stuff.

Thanks. do you enable multi-processing and asio guard?

I think Casey just changed my whole world so Cubase hopefully goes back to minimal crashing. I was beta-testing studio one I think that had a lot to do with it, and it's inability to play nice with 3rd party plugins (I have 600 or something). Bitwig is so solid! A bit clumsy compared to ableton to me but I dig it. Logic is great but I don't use it much anymore.

 

[jdlux]

@CaseySJ you absolute legend-I went through the usb steps and I'm on a whole machine. THANK YOUUUUUUU! Sorry...but I was desperate and frustrated, you are doing god's work haha-big thanks to all who worked out that solution I had no idea wow...

Is there a list of best settings overall for bios? I've been switching around so much. I think it's good with turbo disabled and stuff now per UAD but haven't seen specifics about that here, and would obviously prefer it run as fast as possible...

Also-not sure where to add info if it's helpful but I tried an antelope audio Discrete four last week and it would not be recognized via tb3, usb was fine...