- Joined
- Dec 25, 2019
- Messages
- 15
- Motherboard
- Gigabyte Z390 Designare
- CPU
- i9-9900K
- Graphics
- RX 5700 XT
Hey @Chevron I know someone else who had Logic Pro X crash on startup on his build. Did you happen to work at a large recording studio in Bermondsey, London? I am sure you have tried all the things here https://support.apple.com/en-us/HT200260 The fact it is working fine on your backup suggests that it is something conflicting or got corrupted on your main system as the hardware and clover config will be identical.Awesome thanks for the info. I too had a 2008 Mac Pro (2008 till 2014) then a 2010 Mac Pro until this year, when I built this machine. It's the best computer I have ever had.
My only ongoing issue is that Logic Pro crashes immediately on startup, it's no biggy as I don't use it anymore - but might need it for the occasional client project. I've removed all the plug ins, plugin database, trashed Logic preferences, and it still crashes hard before starting up.
My minty fresh bootable back up is fine with Logic Pro.
Sure, please try the modified NVM 50 for GC-Titan Ridge attached here. Because I don't currently own Thunderbolt monitors, I cannot say whether this will work.@CaseySJ
So I have restored my dual monitor setup by going back to un-modified NVM 23 on GC-Titan Ridge. While I haven't tested this, I believe I could go back to un-modified NVM 43 or 50 and still have dual monitor support. I have read that Clover has had issues over the last few releases, I was on 5108, I have since updated to 5114. No issues booting on either one.
Some questions:
You mentioned having a newer NVM 50 release that you were getting better results with. Is that something I can try?
Have you tried flashing the Designare NVM 33 to your GC-Titan Ridge?
Have you been able to pass 2 monitors over your TR card?
What I keep going back to is I don't understand why the patched firmware would affect running monitors directly off the GPU? I feel like I'm missing something.
Sorry for many questions.
@smashdownbabylon hi, just wondered how your getting on with the UAD? I've got the Apollo 8 TB2/3 - Quad satellite TB2 and an 8Core PCie.. I've had a more stable OS and Hack in the past - however after updating last year to newer OS and Clover updates etc I've been having a few niggles with the Apollo not being recognised, audio stuttering once or twice.. Hotplug now and then.. So I thought it may have been the updates I'd done etc. and have been trying to find a new solution, Opencore was one recent 'project', now looking to flash the onboard TB via the Pi route.. after just reading over your post I'm even more optimistic.Yes, system audio was spotty, and only worked at low sample rates. Daisy chaining was also spotty and while hot plug seemed to work in terms of connecting the interface to the comp, audio wouldn’t work properly. On the fly sample rate changing worked but resulted in massive audio distortion. The only sample rate that did work was 44.1khz, I think because thats sort of the default rate that most things would use anyway. Occasionally channel mapping was screwy and generally unusable. The IO tree before the update had the UAD driver on a completely different section than the TB controller, and the TB controller was not recognized in System Info. It was like the computer could see the device and the driver knew what to do, but they weren’t speaking the same language in terms of syntax, ie bussing.
With the firmware update, all of these aforementioned issues seem to have been solved. Of note, turning on the device on the end of the chain, waiting for it to initialize, and so on down to booting the computer seems to be the way to go, although hot plugging does also seem to be functional once everything has been booted properly once (see note at bottom). The UAD hardware reset was necessary, having the TB cables unplugged while doing it. I did not have to do the whole “unplug all power, disconnect all cables, let it sit for ten minutes” thing described elsewhere, which frankly i think is a load of hooey,lol. Just make sure the TB cables are unplugged when resetting and turn the devices on from last to first, and then the comp PSU (because the TB controller is powered without the comp being booted). I can’t think of anything else, but if anyone has any questions with regard to getting a UAD device working I’d be happy to help!
Note: HotPlugging seems to advance the ch count in Console by 2 every time, ie 1-2 becomes 3-4 and so on with each hotplug reinstatement of the audio session.
Sure, please try the modified NVM 50 for GC-Titan Ridge attached here. Because I don't currently own Thunderbolt monitors, I cannot say whether this will work.