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

[memomemonline]

Thankfully you're already on OpenCore! Which version of OpenCore do you have at the moment? And was it downloaded from this thread?

H @CaseySJ, I never upgraded, and now I have to. My version of OpenCore is 2.43.0.0, and of course, it was downloaded from this thread, but now it is asking me to update it. Thanks

 

[jiffyslot]

When using a DAW(Logic, Cubase), I see an uneven CPU load. There's always one core that is loaded much more than the others, and if this core peaks I hear a glitch. That's the way the DAW software is designed at the moment.
So I would like to have one core running as fast as possible when loaded, and the others not so much to avoid unnecesary high temps.

If you have a PC, there's lots of stuff that can (and should be adjusted) in the BIOS with a clear result on DAW use.

Does anyone have an idea how does works on our hacks? I tried adjusting BIOS settings(hyperthreading, speedstepping, EIST etc are a bad idea using a DAW), but they don't seem to have a clear effect.
Results(glitches at a certain load) are more or less the same whatever the settings.

Where do the BIOS settings stop and MacOS takes over?

Anyone found optimal settings for DAW use with a Z390 Designare board?

I have hyperthreading enabled. Basically, a gentle overclock, all cores at 4.9 GHz, etc. I think the core priority has to do with the software. I no longer think a KS is worth it, but it's fine. FWIW, even when using Process Affinity in Windows 10 Pro, my hacks run Pro Tools and VEP7 much better in MacOS.

 

[zipb]

And how did you exactly sync your cores @ 4.9 gHz?

BTW, why sync Logic to Pro Tools?

 

[CaseySJ]

H @CaseySJ, I never upgraded, and now I have to. My version of OpenCore is 2.43.0.0, and of course, it was downloaded from this thread, but now it is asking me to update it. Thanks

You may be confusing OpenCore Configurator with OpenCore itself. If you run Hackintool and select the Boot tab, you will which version of OpenCore is installed. OpenCore version numbers start with 0, such as 0.6.6 or the latest 0.7.9.

 

[Itshuta]

Hi everyone,
I tried the new Hackindrom 2.10.0 to update my EFI and received this error.
I do not know what is the meaning of borked.

Kernel->Add[14] discovers CpuTscSync.kext, but its ExecutablePath (Contents/MacOS/CpuTscSyn) or PlistPath (Contents/Info.plist) is borked!
CheckKernel returns 1 error!

Completed validating /var/folders/_x/rs6tt7494qzdn1s89ft1tvgr0000gn/T/HackinDROM/standalone/EFI/OC/config.plist in 1 ms. Found 1 issue requiring attention.

 

[Inqnuam]

Hi everyone,
I tried the new Hackindrom 2.10.0 to update my EFI and received this error.
I do not know what is the meaning of borked.

Could you please upload your old EFI

 

[Itshuta]

Could you please upload your old EFI

Here it is.
Thanks Inqnuam

 

[Inqnuam]

Here it is.
Thanks Inqnuam

Theres a typo in your config.plist Kexts > Add > CpuTscSync.kext > ExecutablePath should be 'Contents/MacOS/CpuTscSync' instead of 'Contents/MacOS/CpuTscSyn'

 

[jiffyslot]

And how did you exactly sync your cores @ 4.9 gHz?

BTW, why sync Logic to Pro Tools?

Ahh, it's because it's the KS, so all cores can be overclocked to the same value:
Sometimes I sync Logic to PT because I need that fat-n-squishy Alchemy synth. I can print the synth audio from Logic into audio tracks via the UAD virtual channels. I use Pro Tools because it's more MIDI friendly crazy than Logic for using the Vienna Ensemble Pro stuff with a remote machine. Until VSL gets their Logic implementation out of Beta, that's where I'm at.

 

[Itshuta]

Theres a typo in your config.plist Kexts > Add > CpuTscSync.kext > ExecutablePath should be 'Contents/MacOS/CpuTscSync' instead of 'Contents/MacOS/CpuTscSyn'

Thanks Inqnuam.