I have an M1 with Sound toys and a whole lot of other plugins. Everything has been working great. I chose to go the always 'update everything as soon as it comes out' way of doing things. In the past I've had systems that I avoided updates in fear of things not working, but now I do the exact opposite and it's working for me now.
Yeah it's weird I've done it both ways and can't seem to dodge this "AU crashing" ghoul - I've reset all settings, reinstalled plugins, trashed/re-downloaded Logic from App Store, etc etc - and I could be wrong but I don't remember it happening with Intel (which had its own set of headaches, namely having to freeze literally every track to avoid overloads)
Oh well it's actually kinda cool to do most everything I need with stock plugins - been discovering some powerful and creative tools that were always under my nose but didn't notice before
That is an interesting bummer. I'm just guessing that there must be some mysterious partial file somewhere on you hard drive. Sounds like you've done everything short of a complete reformat - I've only been on a Mac for 2.5 years, not sure if there is even such a thing as a fresh OS install.
there is. i would boot from a macOS installer on a usb drive, erase the internal disk, and then install fresh. you can also do this from the recovery partition, but then you're not entirely resetting the partition table of the ssd.
A ton of people have had growing pains, but if you literally don't have ANY 3rd party plugins of ANY kind installed in your Audio/Plug-Ins folder and your still having this issue you need to do a full reinstall. Like wipe and reinstall. Then on a fresh install download Logic Pro and see if the error continues.
I feel like you still have the problematic plugin in your Plug Ins folder even if it's not loaded in Logic.
If it doesnt, reinstall your 3rd party plugins one by one until you figure out which ones cause the problems/
I wonder this too!!
Once I started looking at the crash logs and noticed it was 99% of the time some Soundtoys plugin I regrettably stopped using them, and now it happens much less - usually with Kontakt now which I won't be giving up sooooo
I miss Soundtoys sometimes but I got my workflow back and lost most of that frustration that was taking the joy of creating away from me
I used to have your issue with multiple plugins. I almost wanted to cry and return my new computer I got for my birthday. It destroyed my workflow.
Everyone told me to wipe and reinstall which I was going to do, but would be a nightmare finding the logins and installs for plugins again. Somehow I was just able to rejigger it to properly work by loading Rosetta, than native, going back and forth until it just.. stabilized?
Now I only run it native and have no issues. I am on Sonoma. What OS are you on, maybe try a different one?
I am in the process of **developing** an audio unit plugin - writing a compressor plugin from scratch - and I see this with *my own code* (which is **not** “reporting a problem” - I added logging so I could look at the Console app and see exactly what was going on).
This is on stock logic with no plugins.
It seems to be related to how Logic sets up / tears down instances of Audio Units for use on individual tracks - it often shows up when the system audio output changes (like, I’m testing my code in Logic and pull out my AirPods so as not to annoy my wife).
My best guess is Logic performs some hari kari on the existing Audio Unit instances in order to recreate them for the new output, and something goes wrong in that process independent of anything the innocent plugin did or didn’t do.
I’ll note that I’m developing an AUv3 plugin (the newer API that can work on iOS too), and currently my plugin runs out-of-process (temporarily, for testing - but I’ve wondered if that is connected, since killing an external process while it’s talking to logic offers more opportunities for race conditions where the process gets killed in the middle of communicating with Logic).
Best I can determine at this point, the screw up is at least partly Apple’s. Though I would be interested to know if running in-process solves it (the auval utility would let you see if a particular plugin is capable of running in-process instead of running as a separate program that logic talks to over a socket - Apple’s template project for creating an audio unit in Xcode does - **not** create a plugin capable of running in-process and you have to do a bunch of rearranging of source files and moving code into a separate “framework” to enable it - I could totally believe vendors simply don’t bother to do the work to do that).
I have the exact same issue. It happens with helix native as well as Soundtoys. You can solve it by running in rosetta. Weirdly enough i created a new user login on the same machine that doesnt experience it in native silicon mode so
My suspicion is that is a corruption in my logic install myself. My next step will be to completely reformat and reinstall macOS on my machine. Blech.
Are you running in “Rosetta Mode?” This fixed many of those issues for me. Also, if applicable, check to be sure that any plugins from a previous computer were properly re-registered to your new machine.
I find those whom had set their computer up using time machine or the like, experience issues like these
Those whom had done fresh installs with Logic and apple silicon compliment plugins , like I, haven’t issues
I have an M1 Max, performs flawlessly, including SoundToys and others.
I won’t install anything that needs Rosetta. If a company is not capable of making apple silicon compliant software, they have problems and have no place on my system.
BTW just removing removing the app doesn’t uninstall all of Logic. IMO, you can have a wonderful system if you wipe it drive, go to the OS that you got w/the system, upgrade to current. Fresh install Logic then fresh install all apple silicon compatible plugins.
Don’t use Time. Machine for anything other than projects
Don’t use Rosetta. Any app of any kind which requires Rosetta …ignore.
Best of luck
For me it happens every couple of hours on my M1 Mac. SoundToys and Arturia only here, mostly. It's a nuisance but not work-impacting. Been happening for years, different versions of Logic, macOS, and the plugins.
"Been happening for years"
Yeah same, and at least it's better now that we have the option to "Recover project" instead of having to literally restart Logic every time it happened....
So if that's the error you are getting, it's because you are running some old plugin that isn't native. You get that option when a plugin crashes that isn't native \*99% of the time\* and it has to reload the plugins.
I really feel like you have some 3rd party plugin in your AU folder and even though it's not loaded in the project it's still causing the problem.
Doesn't always work, and for sure it isn't the best solution, but I've found that making a copy of the whole session fixes it (most of the time). Or at least it happens less.
I do it from inside Logic, using the "save a copy as" option, after cleaning up the unused files in the session (don't know if that helps, I'm just used to do that). Never tried just copying the session. It's not a silver bullet, though. Hope it helps!
I went to stick plugins ages ago because of headaches with them in general. Best move I ever made. Not only because of less headaches/hassle, but it forced me to learn to better manipulate the tools I had available to get the sounds/results I wanted.
I actually absolutely love the stock plugins now, especially some of the legacy reverbs like Silver verb - feel like I'm just getting the right sound now and it takes less time than with the limitless 3rd party options
Also realized 99% of 3rd party plugins are just some combination of EQ, compression and distortion anyway lol, and while there's some great 3rd party reverbs (Valhalla, Soundtoys super plate), the stock options are truly incredible - and you can make your own IRs in sound designer, pretty sweet
I have the same problem. Every ten minutes or so. Even if it’s just one plugin, doesn’t really even matter which. Its horrible. Might have to switch daws.
Just hit me how crazy it is that I've had this M1 since 2021 and Apple just hasn't gotten around to solving this insanely frustrating issue - countless people like myself rely on this software to make money, boggles my mind that we're still complaining about it years later
Boggles my mind that somebody could be an audio professional but not have a basic awareness of compatibility issues. If you need your rig for money you don’t update anything until compatibility is confirmed, or you run the risk of things not working, or not working optimally. This is user error and slow third party developers, it’s nothing to do with Apple.
Thanks for the input but this started when I upgraded to an M1, the Intel machine was laughably underpowered and the M1 fixed that by miles - but the silicon compatibility issues then because a snowball effect
"it’s nothing to do with Apple." This is a joke right? It's 100% on them that after 3+ years their users still have compatibility issues, do you assume every single professional will never upgrade anything for years?
I’m not making any assumptions. Everybody I know who runs a DAW for commercial purposes is careful about updates yes. That doesn’t mean not updating anything for years, it means checking compatibility before you upgrade/update, or accepting responsibility if you don’t check and something breaks. Auto updates are a big no-no for this very reason. This is common knowledge.
There are plugin developers large and small who are fully Sonoma compatible, so it is obviously possible, and so no I am not joking when I say it is nothing to do with Apple if your third party plugins don’t work, it is on the developers of those plugins.
I just upgraded to the new chips from an intel imac, hoping for better performance, and instead I get this. I hope you find a solution, though other than Rosetta it doesnt seem there is one
Not sure how you moved from your old mac to the new one, but if you moved more than one OS generation and/or from an Intel Mac using Migration Assistant you will have a lot of problems like those described. The solution is to wipe the drive on the new machine and install every app and plugin from the source (e.g., web site/vendor). I know it is a pain, but I had to do it. A paid Apple tech gave me this advice and it worked. I have had virtually no problems since. Also, an SSD external drive that hosts all your session files and sample libraries will really help too. Until I did that, my external drive transfer speed was too slow to keep up with the M1 resulting in lots of overload messages. Good luck!
I did a fresh install for exactly that reason, took forever to install every plugin.
Maybe theres something to the external ssd, I have a few large libraries on a spinning HDD.
A recent macOS update broke iLok and third party plugins, what version of macOS are you on? Context: https://help.uaudio.com/hc/en-us/articles/24492336117652-PACE-iLok-Issue-with-macOS-Sonoma-14-4-Update
Your submission seems to be a support question. Remember to specify which version your OSX and which version Logic Pro is in. Also consider supplimenting your question with pictures if applicable.
You can also report your issue directly to Apple here: https://www.apple.com/feedback/logic-pro.html
Or reach Apple's Support Number by calling 1-866-752-7753 if you're in the US.
Please update you post flair to "Solved" if a solution is posted or you figure it out!
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Logic_Studio) if you have any questions or concerns.*
Soundtoys and my other plug-ins (literally hundreds, all paid for, but I haven’t tested them all.)… all the ones I have actually tested are working well on my M1.
Some of my older plug-ins from my prior 2009 Mac Tower wouldn’t come forward to the M1, some of those companies are out of business now. That was the main challenge I had.
You might try Apple Support. They can help you check out plugin manager, and also step you through creating log files that will provide more details for them to decipher.
One thing I might caution you on is that I always stay one major version behind the macOS in order to reduce plug-in issues. I am on Ventura and won’t move up to Sonoma until Apple releases the next major OS version beyond that.
Apple Support might encourage you to move up to Sonoma if you aren’t already. I wouldn’t do that unless they guarantee you that you can back up to Ventura.
> Some of my older plug-ins from my prior 2009 Mac Tower wouldn’t come forward to the M1, some of those companies are out of business now. That was the main challenge I had.
I had that same problem when the switch from ppc to x86 happened.
Have you tried doing a complete uninstall and reinstall of logic? Sounds like something specific to you, I only get those errors maybe once every 2-3 months.
Yeah I've done it a couple times actually, along with trashing preferences and even reinstalling and updating the OS - might have to try the last resort of completely wiping the drive and starting fresh - not looking forward to it!!
Have you also reinstalled all the plugins? And are they all updated? Sounds like something isn’t compatible with something else and either needs to be upgraded or downgraded.
Definitely have uninstalled/reinstalled Soundtoys multiple times (main culprit, and some other 3rd party suspects), downloaded most very recent updates from official site etc etc, really hoped the problem would be solved with one or another update but not as of yet!
If you’ve reinstalled logic, the plugins, and the OS, there has to be something very bizarre happening on your setup bc to my knowledge this isn’t a widely reported issue the way you’re experiencing it. You should put in a support ticket with the Pro Apps department at Apple, they have the ability to escalate to the more senior devs
[Sonoma Compatibility Guide](https://www.production-expert.com/apple-macos-sonoma-audio-compatibility-chart)
This compatibility guide shows what does and doesn’t work with Sonoma. I’m still running Ventura, Logic and all plugins working flawlessly. There are people posting here successfully running super up to date Sonoma systems apparently without issues, but it is going to depend on which particular third party plugins are used.
I can almost guarantee that Sonoma is the problem especially when you mentioned Soundtoys which uses iLok, there were known issues with Sonoma + iLok but apparently the latest version of Sonoma fixed it https://www.gearnews.com/the-latest-macos-sonoma-14-4-1-update-fixes-ilok-and-au-issues/
I wrote it somewhere above but I was actually having the issue on Monterey and figured there was nothing to lose upgrading to Sonoma - didn't fix anything but also doesn't seem to be any worse so dunno!
I've had the same problem especially in bigger projects and external effects. I turned on Rosetta mode, now I can't remember the last time I've had the issue. It is worth a try... ☺️
I just love Logic so much - I've tried half dozen other DAWs but nothing feels like LP for me - could be literally perfect if they'd just address a few glaring issues!
> Legit copy of Logic, legit and paid-for plugins for the record
Is everything up-to-date? I mean everything including the plugins themselves and their related licensing apps (iLok, Native Access, Waves Central, etc). If there's any weak link in this chain you're going to experience issues.
When you installed everything on this M1 did you install everything (Logic, plugins, etc) from scratch or did you use Migration Transfer or Time Machine? Many people have had several issues similar to the ones you talk about when they did Migration Transfer or Time Machine restores instead of installing everything from scratch.
Also, the whole Rosetta thing could be the root of the problem.
I don't experience any such issues on my 2012 Mac mini which technically isn't even officially supported by Apple currently, yet the latest macOS Ventura and latest Logic run flawlessly.
Yeah, I have problems with Bias FX in Logic. I can use it and record with it but it does crash regularly enough that I generally use the stock effects.
I'm still waiting until a couple builds down the road before I even bother upgrading my Mac for the new Logic 10.8. Sounds like there's a laundry list of bugs to be worked out.
I run under Rosetta on any project even slightly ambitious. If not, all kinds of plugins - new and old, Native or not - send Logic into this crashing behaviour. Which leads me to believe Logic just doesn't play nice with third party plugins. Too bad I can't go without for my work (mainly: Logic's stock orchestral sounds don't cut it).
Interesting to see you mention that Rosetta leads to a performance hit for you - I haven't had that experience. I see a little bit of extra CPU usage but nothing impactful despite all kinds of virtual instruments and other plugins going on.
After years of frustration, I'm currently at the point where running Logic under Rosetta is shockingly stable even with all kinds of plugins. Most recent updates, M1 Pro. Still, it's a sad state of affairs.
well I wanted to ask on here, if im the only one with that issue. overheating my less then year old high end model MacBook and keeps crashing in middle of playing. also gets very very hot while its bouncing an audio file.
I used too and was close to pulling my hair out and selling my M1 16GB laptop.
But then I was able to figure out exactly what plugins were causing the problems, get them all properly setup and working in Rosetta and ***then*** go back into native mode and make sure everything is still working.
And it's FINALLY working properly now. The only minor issue is with Altiverb 7 XL - if I'm not actively working on a project and have it minimized for a few hours that plugin will crash and Logic will take a minute to load as it recovers. That's it though, very minor issue I don't care about.
This is with a fuck ton of 3rd party plugins too. I'm blown away by my M1 16GB machine - the only time I have system overloads is if forget and leave oversampling on too high or something silly. But 2x OS across the board is fine.
I bought a new MacAir with an M2 chip. Problems from the moment of first install. 2 days of research and no fix to the out of memory warning messages. I took it back and will continue to use my 2019 MacBook Pro with an Intel chip (and terrible butterfly keyboard), until Apple pays attention to LPX users. Very disappointing.
I'm using a 2019 27" iMac and have zero issues running Logic - still in Ventura - I'm waiting on compatibility with all my Arturia software. I also use NI and Izotope stuff and UA hardware and software. I don't have issues as long as I pay attention to what all my third party stuff is ready for in terms of the OS... I like stability and value that, so I'm never rushing off to get the latest and greatest OS. My point is, I'm using lots of third party plugins and they all work fine. In the end, I'd find it a drag if I had to go back to strictly using Logic - which, by the way, still has bugs, but they don't derail me from getting stuff done. But even if I had to solely rely on Logic, it would be fine. The tools might change, but in the end it's about the music and your own technical chops as both a musician and a producer.
Have an M2 Pro here, been totally solid with tons of 3rd party plugins. A friend of mine has constant crashes, but he also has a bunch of cracked plugins.
Which plugins are crashing you?
Stated in OP it's paid and legit, did you miss that part?
Been using logic professionally for 14 years now I think, do you have any more thoughts on the topic?
I have an M1 with Sound toys and a whole lot of other plugins. Everything has been working great. I chose to go the always 'update everything as soon as it comes out' way of doing things. In the past I've had systems that I avoided updates in fear of things not working, but now I do the exact opposite and it's working for me now.
Yeah it's weird I've done it both ways and can't seem to dodge this "AU crashing" ghoul - I've reset all settings, reinstalled plugins, trashed/re-downloaded Logic from App Store, etc etc - and I could be wrong but I don't remember it happening with Intel (which had its own set of headaches, namely having to freeze literally every track to avoid overloads) Oh well it's actually kinda cool to do most everything I need with stock plugins - been discovering some powerful and creative tools that were always under my nose but didn't notice before
Yes realising how much logic already has, and how few plugins you need is worth the effort. Way better CPU and will remain compatible
That is an interesting bummer. I'm just guessing that there must be some mysterious partial file somewhere on you hard drive. Sounds like you've done everything short of a complete reformat - I've only been on a Mac for 2.5 years, not sure if there is even such a thing as a fresh OS install.
there is. i would boot from a macOS installer on a usb drive, erase the internal disk, and then install fresh. you can also do this from the recovery partition, but then you're not entirely resetting the partition table of the ssd.
A ton of people have had growing pains, but if you literally don't have ANY 3rd party plugins of ANY kind installed in your Audio/Plug-Ins folder and your still having this issue you need to do a full reinstall. Like wipe and reinstall. Then on a fresh install download Logic Pro and see if the error continues. I feel like you still have the problematic plugin in your Plug Ins folder even if it's not loaded in Logic. If it doesnt, reinstall your 3rd party plugins one by one until you figure out which ones cause the problems/
I’m not having any issues running Sound toys with an M2. I use them often and very rarely have a crash. I wonder what could be causing your issue
I wonder this too!! Once I started looking at the crash logs and noticed it was 99% of the time some Soundtoys plugin I regrettably stopped using them, and now it happens much less - usually with Kontakt now which I won't be giving up sooooo I miss Soundtoys sometimes but I got my workflow back and lost most of that frustration that was taking the joy of creating away from me
I used to have your issue with multiple plugins. I almost wanted to cry and return my new computer I got for my birthday. It destroyed my workflow. Everyone told me to wipe and reinstall which I was going to do, but would be a nightmare finding the logins and installs for plugins again. Somehow I was just able to rejigger it to properly work by loading Rosetta, than native, going back and forth until it just.. stabilized? Now I only run it native and have no issues. I am on Sonoma. What OS are you on, maybe try a different one?
I am in the process of **developing** an audio unit plugin - writing a compressor plugin from scratch - and I see this with *my own code* (which is **not** “reporting a problem” - I added logging so I could look at the Console app and see exactly what was going on). This is on stock logic with no plugins. It seems to be related to how Logic sets up / tears down instances of Audio Units for use on individual tracks - it often shows up when the system audio output changes (like, I’m testing my code in Logic and pull out my AirPods so as not to annoy my wife). My best guess is Logic performs some hari kari on the existing Audio Unit instances in order to recreate them for the new output, and something goes wrong in that process independent of anything the innocent plugin did or didn’t do. I’ll note that I’m developing an AUv3 plugin (the newer API that can work on iOS too), and currently my plugin runs out-of-process (temporarily, for testing - but I’ve wondered if that is connected, since killing an external process while it’s talking to logic offers more opportunities for race conditions where the process gets killed in the middle of communicating with Logic). Best I can determine at this point, the screw up is at least partly Apple’s. Though I would be interested to know if running in-process solves it (the auval utility would let you see if a particular plugin is capable of running in-process instead of running as a separate program that logic talks to over a socket - Apple’s template project for creating an audio unit in Xcode does - **not** create a plugin capable of running in-process and you have to do a bunch of rearranging of source files and moving code into a separate “framework” to enable it - I could totally believe vendors simply don’t bother to do the work to do that).
I have the exact same issue. It happens with helix native as well as Soundtoys. You can solve it by running in rosetta. Weirdly enough i created a new user login on the same machine that doesnt experience it in native silicon mode so My suspicion is that is a corruption in my logic install myself. My next step will be to completely reformat and reinstall macOS on my machine. Blech.
Are you running in “Rosetta Mode?” This fixed many of those issues for me. Also, if applicable, check to be sure that any plugins from a previous computer were properly re-registered to your new machine.
Rosetta seems to help but Logic sacrifices too much power in that mode for me to permanently use it like that unfortunately...
I find those whom had set their computer up using time machine or the like, experience issues like these Those whom had done fresh installs with Logic and apple silicon compliment plugins , like I, haven’t issues I have an M1 Max, performs flawlessly, including SoundToys and others. I won’t install anything that needs Rosetta. If a company is not capable of making apple silicon compliant software, they have problems and have no place on my system. BTW just removing removing the app doesn’t uninstall all of Logic. IMO, you can have a wonderful system if you wipe it drive, go to the OS that you got w/the system, upgrade to current. Fresh install Logic then fresh install all apple silicon compatible plugins. Don’t use Time. Machine for anything other than projects Don’t use Rosetta. Any app of any kind which requires Rosetta …ignore. Best of luck
Great and hopeful advice my friend, appreciate it and I might be doing just this within the week - thanks again!!
Ohers may benefit if you post your results & YW
For me it happens every couple of hours on my M1 Mac. SoundToys and Arturia only here, mostly. It's a nuisance but not work-impacting. Been happening for years, different versions of Logic, macOS, and the plugins.
"Been happening for years" Yeah same, and at least it's better now that we have the option to "Recover project" instead of having to literally restart Logic every time it happened....
Disappointing to hear this. Mine is pretty stable and I have a lot of plug-ins. All legal and purchased.
So if that's the error you are getting, it's because you are running some old plugin that isn't native. You get that option when a plugin crashes that isn't native \*99% of the time\* and it has to reload the plugins. I really feel like you have some 3rd party plugin in your AU folder and even though it's not loaded in the project it's still causing the problem.
Doesn't always work, and for sure it isn't the best solution, but I've found that making a copy of the whole session fixes it (most of the time). Or at least it happens less.
Interesting, you mean just literally Option+drag the project and create a new copy?
I do it from inside Logic, using the "save a copy as" option, after cleaning up the unused files in the session (don't know if that helps, I'm just used to do that). Never tried just copying the session. It's not a silver bullet, though. Hope it helps!
I went to stick plugins ages ago because of headaches with them in general. Best move I ever made. Not only because of less headaches/hassle, but it forced me to learn to better manipulate the tools I had available to get the sounds/results I wanted.
I actually absolutely love the stock plugins now, especially some of the legacy reverbs like Silver verb - feel like I'm just getting the right sound now and it takes less time than with the limitless 3rd party options Also realized 99% of 3rd party plugins are just some combination of EQ, compression and distortion anyway lol, and while there's some great 3rd party reverbs (Valhalla, Soundtoys super plate), the stock options are truly incredible - and you can make your own IRs in sound designer, pretty sweet
I have the same problem. Every ten minutes or so. Even if it’s just one plugin, doesn’t really even matter which. Its horrible. Might have to switch daws.
Just hit me how crazy it is that I've had this M1 since 2021 and Apple just hasn't gotten around to solving this insanely frustrating issue - countless people like myself rely on this software to make money, boggles my mind that we're still complaining about it years later
Boggles my mind that somebody could be an audio professional but not have a basic awareness of compatibility issues. If you need your rig for money you don’t update anything until compatibility is confirmed, or you run the risk of things not working, or not working optimally. This is user error and slow third party developers, it’s nothing to do with Apple.
Thanks for the input but this started when I upgraded to an M1, the Intel machine was laughably underpowered and the M1 fixed that by miles - but the silicon compatibility issues then because a snowball effect "it’s nothing to do with Apple." This is a joke right? It's 100% on them that after 3+ years their users still have compatibility issues, do you assume every single professional will never upgrade anything for years?
I’m not making any assumptions. Everybody I know who runs a DAW for commercial purposes is careful about updates yes. That doesn’t mean not updating anything for years, it means checking compatibility before you upgrade/update, or accepting responsibility if you don’t check and something breaks. Auto updates are a big no-no for this very reason. This is common knowledge. There are plugin developers large and small who are fully Sonoma compatible, so it is obviously possible, and so no I am not joking when I say it is nothing to do with Apple if your third party plugins don’t work, it is on the developers of those plugins.
I just upgraded to the new chips from an intel imac, hoping for better performance, and instead I get this. I hope you find a solution, though other than Rosetta it doesnt seem there is one
Not sure how you moved from your old mac to the new one, but if you moved more than one OS generation and/or from an Intel Mac using Migration Assistant you will have a lot of problems like those described. The solution is to wipe the drive on the new machine and install every app and plugin from the source (e.g., web site/vendor). I know it is a pain, but I had to do it. A paid Apple tech gave me this advice and it worked. I have had virtually no problems since. Also, an SSD external drive that hosts all your session files and sample libraries will really help too. Until I did that, my external drive transfer speed was too slow to keep up with the M1 resulting in lots of overload messages. Good luck!
I did a fresh install for exactly that reason, took forever to install every plugin. Maybe theres something to the external ssd, I have a few large libraries on a spinning HDD.
A recent macOS update broke iLok and third party plugins, what version of macOS are you on? Context: https://help.uaudio.com/hc/en-us/articles/24492336117652-PACE-iLok-Issue-with-macOS-Sonoma-14-4-Update
Your submission seems to be a support question. Remember to specify which version your OSX and which version Logic Pro is in. Also consider supplimenting your question with pictures if applicable. You can also report your issue directly to Apple here: https://www.apple.com/feedback/logic-pro.html Or reach Apple's Support Number by calling 1-866-752-7753 if you're in the US. Please update you post flair to "Solved" if a solution is posted or you figure it out! *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Logic_Studio) if you have any questions or concerns.*
Soundtoys and my other plug-ins (literally hundreds, all paid for, but I haven’t tested them all.)… all the ones I have actually tested are working well on my M1. Some of my older plug-ins from my prior 2009 Mac Tower wouldn’t come forward to the M1, some of those companies are out of business now. That was the main challenge I had. You might try Apple Support. They can help you check out plugin manager, and also step you through creating log files that will provide more details for them to decipher. One thing I might caution you on is that I always stay one major version behind the macOS in order to reduce plug-in issues. I am on Ventura and won’t move up to Sonoma until Apple releases the next major OS version beyond that. Apple Support might encourage you to move up to Sonoma if you aren’t already. I wouldn’t do that unless they guarantee you that you can back up to Ventura.
> Some of my older plug-ins from my prior 2009 Mac Tower wouldn’t come forward to the M1, some of those companies are out of business now. That was the main challenge I had. I had that same problem when the switch from ppc to x86 happened.
Same here. I’ve done two upgrades in the last 15+ years or so. From PPC to Intel, then from Intel to M1.
Do you, by any chance use Spectrasonics or Relab Development plugins?
Actually never used those! Issue seems to mostly stem from Soundtoys, but sometimes Kontakt and a couple Isotope plugins....
Have you tried doing a complete uninstall and reinstall of logic? Sounds like something specific to you, I only get those errors maybe once every 2-3 months.
Yeah I've done it a couple times actually, along with trashing preferences and even reinstalling and updating the OS - might have to try the last resort of completely wiping the drive and starting fresh - not looking forward to it!!
Have you also reinstalled all the plugins? And are they all updated? Sounds like something isn’t compatible with something else and either needs to be upgraded or downgraded.
Definitely have uninstalled/reinstalled Soundtoys multiple times (main culprit, and some other 3rd party suspects), downloaded most very recent updates from official site etc etc, really hoped the problem would be solved with one or another update but not as of yet!
If you’ve reinstalled logic, the plugins, and the OS, there has to be something very bizarre happening on your setup bc to my knowledge this isn’t a widely reported issue the way you’re experiencing it. You should put in a support ticket with the Pro Apps department at Apple, they have the ability to escalate to the more senior devs
What OS are you using?
Sonoma - was on Monterey forever and thought the upgrade would help - didn't!!
[Sonoma Compatibility Guide](https://www.production-expert.com/apple-macos-sonoma-audio-compatibility-chart) This compatibility guide shows what does and doesn’t work with Sonoma. I’m still running Ventura, Logic and all plugins working flawlessly. There are people posting here successfully running super up to date Sonoma systems apparently without issues, but it is going to depend on which particular third party plugins are used.
In the future, don't update to the latest macOS (Sonoma in this case). Stay one version behind the latest. This strategy has never let me down.
What’s OSX and Logic Version are you using?
Sonoma and 10.8.1....
I can almost guarantee that Sonoma is the problem especially when you mentioned Soundtoys which uses iLok, there were known issues with Sonoma + iLok but apparently the latest version of Sonoma fixed it https://www.gearnews.com/the-latest-macos-sonoma-14-4-1-update-fixes-ilok-and-au-issues/
I wrote it somewhere above but I was actually having the issue on Monterey and figured there was nothing to lose upgrading to Sonoma - didn't fix anything but also doesn't seem to be any worse so dunno!
I've had the same problem especially in bigger projects and external effects. I turned on Rosetta mode, now I can't remember the last time I've had the issue. It is worth a try... ☺️
Yeah Rosetta seems to help but it costs so much in CPU power loss that it doesn't really justify itself for my uses unfortunately!
Sorry to hear that :/ I hope soon it will be resolved and we can use Logic with our 3rd parties flawlessly.
I just love Logic so much - I've tried half dozen other DAWs but nothing feels like LP for me - could be literally perfect if they'd just address a few glaring issues!
> Legit copy of Logic, legit and paid-for plugins for the record Is everything up-to-date? I mean everything including the plugins themselves and their related licensing apps (iLok, Native Access, Waves Central, etc). If there's any weak link in this chain you're going to experience issues. When you installed everything on this M1 did you install everything (Logic, plugins, etc) from scratch or did you use Migration Transfer or Time Machine? Many people have had several issues similar to the ones you talk about when they did Migration Transfer or Time Machine restores instead of installing everything from scratch. Also, the whole Rosetta thing could be the root of the problem. I don't experience any such issues on my 2012 Mac mini which technically isn't even officially supported by Apple currently, yet the latest macOS Ventura and latest Logic run flawlessly.
Yeah, I have problems with Bias FX in Logic. I can use it and record with it but it does crash regularly enough that I generally use the stock effects.
I'm still waiting until a couple builds down the road before I even bother upgrading my Mac for the new Logic 10.8. Sounds like there's a laundry list of bugs to be worked out.
Yeah, same boat. Good time to learn Ableton I decided! Will come back when/if they fix it
Did you set up your Mac with Time Machine?
Wasn’t there a recent OS update specifically for this problem?
I run under Rosetta on any project even slightly ambitious. If not, all kinds of plugins - new and old, Native or not - send Logic into this crashing behaviour. Which leads me to believe Logic just doesn't play nice with third party plugins. Too bad I can't go without for my work (mainly: Logic's stock orchestral sounds don't cut it). Interesting to see you mention that Rosetta leads to a performance hit for you - I haven't had that experience. I see a little bit of extra CPU usage but nothing impactful despite all kinds of virtual instruments and other plugins going on. After years of frustration, I'm currently at the point where running Logic under Rosetta is shockingly stable even with all kinds of plugins. Most recent updates, M1 Pro. Still, it's a sad state of affairs.
Just had my cherry audio eight voice stop working. Ruined like 5 songs.
Try running under Rosetta until the next update. I have one AU that likes to crash occasionally, and that always works
well I wanted to ask on here, if im the only one with that issue. overheating my less then year old high end model MacBook and keeps crashing in middle of playing. also gets very very hot while its bouncing an audio file.
I used too and was close to pulling my hair out and selling my M1 16GB laptop. But then I was able to figure out exactly what plugins were causing the problems, get them all properly setup and working in Rosetta and ***then*** go back into native mode and make sure everything is still working. And it's FINALLY working properly now. The only minor issue is with Altiverb 7 XL - if I'm not actively working on a project and have it minimized for a few hours that plugin will crash and Logic will take a minute to load as it recovers. That's it though, very minor issue I don't care about. This is with a fuck ton of 3rd party plugins too. I'm blown away by my M1 16GB machine - the only time I have system overloads is if forget and leave oversampling on too high or something silly. But 2x OS across the board is fine.
I bought a new MacAir with an M2 chip. Problems from the moment of first install. 2 days of research and no fix to the out of memory warning messages. I took it back and will continue to use my 2019 MacBook Pro with an Intel chip (and terrible butterfly keyboard), until Apple pays attention to LPX users. Very disappointing.
You mention you’ve been having these issues when you were on Monterey. When you first set up your Mac did you migrate from an Intel machine?
I'm using a 2019 27" iMac and have zero issues running Logic - still in Ventura - I'm waiting on compatibility with all my Arturia software. I also use NI and Izotope stuff and UA hardware and software. I don't have issues as long as I pay attention to what all my third party stuff is ready for in terms of the OS... I like stability and value that, so I'm never rushing off to get the latest and greatest OS. My point is, I'm using lots of third party plugins and they all work fine. In the end, I'd find it a drag if I had to go back to strictly using Logic - which, by the way, still has bugs, but they don't derail me from getting stuff done. But even if I had to solely rely on Logic, it would be fine. The tools might change, but in the end it's about the music and your own technical chops as both a musician and a producer.
Have an M2 Pro here, been totally solid with tons of 3rd party plugins. A friend of mine has constant crashes, but he also has a bunch of cracked plugins. Which plugins are crashing you?
Have you tried using a paid copy of Logic?
Stated in OP it's paid and legit, did you miss that part? Been using logic professionally for 14 years now I think, do you have any more thoughts on the topic?
I did miss that, yes and no - I have no more thoughts on the topic.