-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protools unsupported on macOS Mojave and Catalina. #11
Comments
I haven't tried Pro Tools yet but I can confirm Cubase crashes immediately when opening the control centre. I'm not an expert by any means but I genuinely wonder if it's something to do with the way that the DRM works - PT uses metafortress and it wouldn't surprise me if some differences in architecture cause it to not work correctly. Out of curiosity, have you tried any other DAWs? Do they work as expected? Would want to rule out an unrelated audio issue first. |
Hello JoeINichols well yes I installed studio one and it works great. I'm coming from and Intel mackintosh to AMD and on Intel hight Sierra with protools functioning perfect. I've read people with AMD and high sierra running protools just fine. so I'm not shore what's going on but I need protools I do all my work there thanks for answering |
Thanks for updating - I don't have time right now to test but I will investigate when I've got some free time. Can you confirm which version of Pro Tools you're running exactly? |
Ok thanks I’m using protools 2019.6 it’s the latest one on the Avid website |
Right so apologies for taking a week to get back to you on this but as it turns out real life is important too. I'm going to test on an Intel Mac running Catalina shortly but I genuinely suspect the issue is actually down to a 32-bit Quicktime dependency in Pro Tools, rather than some inability to get it working on AMD. |
Update: The solution in your case is either to switch to an AMD kernel (i.e. rather than vanilla patches) or wait until Avid updates Pro Tools for Catalina, removing the 32-bit dependencies in the process. |
Thanks for taking the time out I appreciate it |
Do let me know what happens - I haven't had a chance to play with 2019.10 yet but it does seem possible as it could fix the issue. To give a bit more detail, the crashing in 2019.6 was actually caused by the audio / video engine - it's trying to use a 32-bit QuickTime dependency, which Apple killed in Catalina (and wouldn't work on an AMD hackintosh without a custom kernel due to the lack of IOMMU). 2019.10 does indeed appear to include improvements to the AVE so I do wonder if they may have removed this dependency. As an aside, for anyone who finds themselves here from Googling, I was able to fix the issue with Cubase by removing the surroundpanner.vst3 file from Cubase.app/Contents/VST3/. |
So update I deleted all files of protools 2019.6 and installed protools 2019.10 and I’m still having the same issue sucks |
Very well said @JoelNichols I will add your Cubase suggestion to our known fixes lists, of course crediting you for it. Only slight nitpick would be that it's the lack of OPEMU, not IOMMU, but great information nonetheless. As for Protools 2019.10 @el1nd1o it would be very helpful if you could attach any available crashlogs. |
Ok I will post a crashlog soon thanks |
this is my protools log guys hope this can help Process: Pro Tools QuickTime Server [2065] Date/Time: 2019-10-06 18:09:01.424 -0400 Time Awake Since Boot: 550 seconds System Integrity Protection: disabled Crashed Thread: Unknown Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Termination Signal: Illegal instruction: 4 Backtrace not available Unknown thread crashed with X86 Thread State (32-bit): Logical CPU: 0 Binary images description not available External Modification Summary: System Profile: |
That crash log does indeed point to a 32-bit dependency that hasn't been removed from Pro Tools yet. Interestingly I have noticed a few places where I'll get EXC_BAD_ACCESS on my AMD hackintosh - notably Cubase when surroundpanner.vst3 isn't removed and also the Slate Raven Cubase overlay. Crash log is included:
|
I have a raven too. I have not installed it yet because of protools not opening I hope there’s a fix soon for both of us and everyone else |
I should clarify that the Raven works perfectly with Logic Pro, just it crashes immediately with Cubase for some reason, which I find strange. I haven't tested with Pro Tools because well, Pro Tools won't launch at all, though I suspect that's still an issue that'll likely be fixed with a future Pro Tools update. |
I understand now definitely it has something to do with Cubase |
FL studio is work?? |
Unfortunately I don't know (it's the one DAW I don't own). Your best bet is to try it and report back. |
yes FL studio is working perfect on my end
…-----Original Message-----
From: Joel Nichols <[email protected]>
To: AMD-OSX/AMD_Vanilla <[email protected]>
Cc: el1nd1o <[email protected]>; Mention <[email protected]>
Sent: Tue, Nov 26, 2019 4:19 am
Subject: Re: [AMD-OSX/AMD_Vanilla] Protools unsupported on macOS Mojave and Catalina. (#60)
FL studio is work??
Unfortunately I don't know (it's the one DAW I don't own). Your best bet is to try it and report back.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Worth mentioning that the latest version of the Raven software (3.7.1) works absolutely fine with Cubase now. |
So Pro Tools has had an update that brings Catalina support. Anyone tried it yet? |
Ok thanks I will be Checking it out I will let you know 🙏🙏🙏 |
Hello I have a 3900x ryzen with a x570 phantom gaming 4 motherboard 64g ram GPU vega 56 8g
500g ssd for now switching to m.2 soon Running Mojave 10.14.6
Everything seems to work fine but my protools app. it’s installed but won’t open it says it’s not responding and I have the latest update to protools and it works fine on a regular IMac with Mojave 10.14.6
I have other apps running fine as well
Is anyone having this issue or with any other program and is there a driver or kext I can put please help anyone 🙏 thanks
The text was updated successfully, but these errors were encountered: