Category: Logic crashes

  • Logic Pro 10.7.7 Crashing – Fixing Plug-in Conflicts on macOS Monterey

    Logic Pro 10.7.7 Crashing – Fixing Plug-in Conflicts on macOS Monterey

    Audio Support provides independent, one-to-one technical help for Logic Pro users worldwide — solving crashes, latency, and workflow problems quickly and clearly.

    Founded by Paul Andrews, a technician and educator with over 20 years’ experience in music technology, the service helps musicians and producers get their systems running smoothly so they can focus on making music.

    This case study article is part of our Logic Pro Support series, sharing real client stories and practical fixes discovered through remote troubleshooting.

    Learn more about Logic Pro Support

    Joe, a professional composer, contacted Audio Support after Logic Pro began crashing repeatedly. His system included:

    • MacBook Pro (M1, 2020)
    • macOS Monterey
    • Logic Pro 10.7.7
    • Toontrack EZdrummer 3 and other third-party plug-ins

    Each time Joe opened a project and clicked the track containing EZdrummer 3, Logic Pro crashed immediately. Sometimes a crash report appeared; sometimes it didn’t.

    He also described a visual glitch where Logic would play back audio but the playhead stayed frozen — frustrating and unpredictable behaviour that made composing impossible.

    At first glance, his setup appeared consistent: an M1 Mac running macOS Monterey with Logic Pro 10.7.7 — all released around 2020–2021.
    However, EZdrummer 3 was a newer release designed for later versions of Logic Pro and macOS. This created subtle incompatibilities between his host software, operating system, and updated plug-ins.

    I confirmed via Activity Monitor that Logic Pro was running natively, not under Rosetta, so Intel translation wasn’t causing the problem.

    Re-creating the crash made the cause clear. Logic Pro failed whenever it tried to activate EZdrummer 3 on project load.
    Inside File > Project Settings > General, Joe had enabled:

    “Load plug-ins only when needed.”

    This setting deactivates unused plug-ins at startup and reloads them when a track is selected.
    In Joe’s session, EZdrummer 3 wasn’t truly “unused” — it already contained MIDI data. When Logic attempted to reload the instrument mid-session, the DAW crashed instantly.

    After disabling this setting, saving a new version of the project, and reopening it, Logic Pro loaded normally. Selecting the EZdrummer 3 track no longer caused a crash.

    With the immediate crashing resolved, we investigated the playback glitch.
    That issue wasn’t related to any specific plug-in; it pointed to graphics and timing behaviour that Apple addressed in later versions of Logic Pro and macOS.

    I recommended Joe update his system to ensure full compatibility:

    • macOS → Sonoma (or at least Ventura)
    • Logic Pro → 11.x series

    While it’s wise to be cautious with updates, Apple Silicon machines like Joe’s M1 handle recent releases very reliably. The most significant compatibility risks I see today involve newer software on older Intel Macs, not the other way around.

    Joe followed my advice, updated to macOS Sonoma and Logic Pro 11.2.3, and later emailed to confirm:

    “Everything’s working beautifully — no crashes, no glitches, just smooth playback. Thank you for your help and reassurance.”

    This case highlights how Logic Pro stability depends on harmony between macOS, the DAW, and third-party plug-ins. Joe’s hesitation to upgrade was sensible — many professionals delay updates to protect active projects — but sometimes staying too far behind introduces the very instability you’re trying to avoid.

    Knowing when it’s safe to update, especially on Apple Silicon, comes from real-world experience. That’s what Audio Support offers: practical, human troubleshooting informed by years of hands-on audio engineering.

    By combining diagnostic insight with empathy for the creative process, we find not just quick fixes but sustainable solutions.

    When Logic Pro starts crashing or acting erratically, it’s rarely a single bug. It’s the interaction of versions, drivers, and plug-ins — the delicate ecosystem of modern production.
    At Audio Support, I provide one-to-one remote troubleshooting for Logic Pro users worldwide, helping composers and producers eliminate technical roadblocks so they can focus on making music.

    Author Credit

    Paul Andrews is a provider of expert music technology support

    Case study by Paul Andrews, Founder of Audio Support.

    No automated tickets, no waiting queues — just one-to-one help from an experienced music technology specialist. I’ll connect to your system remotely, identify the issue, and guide you through the fix.

    Recent problems solved for real clients.

    Optimising Logic Pro CPU Usage for Large Orchestral Mixes

    Client’s Question

    Why does Logic Pro keep crashing when I add plugins to my tracks?

    Session Result

    CPU load drastically reduced; mix workflow stabilised via bus routing.

    Read Full Case Study Report: Logic Pro 10.7.7 Crashing – Fixing Plug-in Conflicts on macOS Monterey
    Preparing for a Studio Hardware Installation

    Client’s Question

    What cables do I need to connect my hardware synths to my mixer?

    Session Result

    Equipment audited, cable inventory confirmed, site visit planned.

    Read Full Case Study Report: Logic Pro 10.7.7 Crashing – Fixing Plug-in Conflicts on macOS Monterey
    Mono Microphone Only in Left Speaker Fix in Logic Pro

    Client’s Question

    Why is my mono mic input only coming out of the left speaker in Logic Pro?

    Session Result

    Mono input successfully centred by changing Logic Pro track format from Stereo to Mono.

    Read Full Case Study Report: Logic Pro 10.7.7 Crashing – Fixing Plug-in Conflicts on macOS Monterey
    Managing Native Instruments Komplete Libraries in Kontakt

    Client’s Question

    How do I hide unwanted libraries in the Kontakt side pane?

    Session Result

    Unused libraries hidden, visual clutter removed.

    Read Full Case Study Report: Logic Pro 10.7.7 Crashing – Fixing Plug-in Conflicts on macOS Monterey
  • Solving Logic Pro Dropouts for a Singer Using Scarlett Solo and Rode NT1-A

    Solving Logic Pro Dropouts for a Singer Using Scarlett Solo and Rode NT1-A

    Audio Support provides independent, one-to-one technical help for Logic Pro users worldwide — solving crashes, latency, and workflow problems quickly and clearly.

    Founded by Paul Andrews, a technician and educator with over 20 years’ experience in music technology, the service helps musicians and producers get their systems running smoothly so they can focus on making music.

    This case study article is part of our Logic Pro Support series, sharing real client stories and practical fixes discovered through remote troubleshooting.

    Learn more about Logic Pro Support

    A singer contacted Audio Support because Logic Pro kept freezing and stopping mid-recording. Their setup included:

    Logic Pro running on M2 Macbook

    Rode NT1-A Microphone

    Focusrite Scarlett Solo

    Wired headphones

    Despite contacting Apple Support who suggested reinstalling drivers and testing other microphones, my client’s problem persisted — dropouts, glitching playback, and recording interruptions. They found Audio Support through Google and booked me for an hour’s remote support.

    Once we were connected and I was remotely viewing my client’s Mac I investigated the situation. At first glance, the system looked fine — nothing unusual in Logic or the Focusrite configuration.
    But after digging deeper, I noticed something subtle:

    • Logic’s input device was set to the Focusrite.
    • Logic’s output device was set to the Mac’s system default output (which, in this case, was the 3.5 mm headphone jack).

    This mismatch meant Logic was sending playback through the Mac’s internal hardware, while recording through the Focusrite. This configuration can work, but is not how the Scarlett Solo is designed to be used. With this setup, the client is unable to use the Focusrite’s direct monitoring feature and there will be more latency introduced into the system than necessary. 

    As we were moving the headphones from the Mac to the Scarlett, the client told me that sound was only coming from the left-hand headphone. Also, moving and wiggling the cable was causing crackling sounds. 

    This was the crucial piece of information that told us the reason for Logic’s dropouts. 

    My client’s damaged headphone lead was causing occasional momentary disconnects. This caused the Mac to switch output devices on the fly. Logic interpreted these as hardware changes and stopped recording instantly.

    I explained that both input and output should ideally use the same audio device for stability. We used a 3.5 mm to 6.35 mm adapter to connect the headphones to the Focusrite’s headphone output.

    The damaged headphone cable needed to be replaced. 

    We ordered a new, balanced a pair of studio headphones — and as a temporary measure, I suggested the client could secure the existing cable by folding it over and using a piece of tape to prevent movement.

    The dropouts disappeared. The client was relieved — they’d spent hours updating software and swapping microphones, but the root cause turned out to be a simple physical connection issue that only surfaced through careful observation.

    This session shows how human technical support goes beyond “update your drivers.”
    Real problem-solving in audio means understanding the interaction between hardware, software, and real-world use.

    No automated tickets, no waiting queues — just one-to-one help from an experienced music technology specialist. I’ll connect to your system remotely, identify the issue, and guide you through the fix.

    Recent problems solved for real clients.

    Optimising Logic Pro CPU Usage for Large Orchestral Mixes

    Client’s Question

    Why does Logic Pro keep crashing when I add plugins to my tracks?

    Session Result

    CPU load drastically reduced; mix workflow stabilised via bus routing.

    Read Full Case Study Report: Solving Logic Pro Dropouts for a Singer Using Scarlett Solo and Rode NT1-A
    Preparing for a Studio Hardware Installation

    Client’s Question

    What cables do I need to connect my hardware synths to my mixer?

    Session Result

    Equipment audited, cable inventory confirmed, site visit planned.

    Read Full Case Study Report: Solving Logic Pro Dropouts for a Singer Using Scarlett Solo and Rode NT1-A
    Mono Microphone Only in Left Speaker Fix in Logic Pro

    Client’s Question

    Why is my mono mic input only coming out of the left speaker in Logic Pro?

    Session Result

    Mono input successfully centred by changing Logic Pro track format from Stereo to Mono.

    Read Full Case Study Report: Solving Logic Pro Dropouts for a Singer Using Scarlett Solo and Rode NT1-A
    Managing Native Instruments Komplete Libraries in Kontakt

    Client’s Question

    How do I hide unwanted libraries in the Kontakt side pane?

    Session Result

    Unused libraries hidden, visual clutter removed.

    Read Full Case Study Report: Solving Logic Pro Dropouts for a Singer Using Scarlett Solo and Rode NT1-A
  • M2 Mac Performance Fix: Eliminating Logic Pro 11.1.2 Plug-in Errors After Migration

    M2 Mac Performance Fix: Eliminating Logic Pro 11.1.2 Plug-in Errors After Migration

    Hi Paul. I have an M2 Mac with Logic Pro and am struggling with lag and slow performance. I would like to book a session with you. – OB

    I received the above message from a new client and we arranged a time to connect for a remote support session. Once we were speaking via WhatsApp voice chat and had connected our screens via AnyDesk my client explained his situation in more detail.

    My client had been using Logic Pro on his Macs for many years and had recently purchased a new M2 Mac Studio. He had used Apple’s migration assistant to move the contents of his old mac to his new one. The process seemed to have been successful, but now Logic Pro wasn’t working smoothly. Sessions were slow to load and Logic was throwing up the vague “An Audio Unit Has Reported A Problem” error. I had seen this error before so I had some ideas on where to start the troubleshooting process.

    I had a look at my client’s Mac’s plug-in library, folder structure and activity monitor to see what was going on in OSX while Logic was running.

    I could see some clues to the likely source of Logic’s problems, so I started working through resolving them.

    Removing Incompatible Audio Units

    Logic Pro’s error messages had told us that Audio Units were an issue, so I started the investigation there. I manually moved AU components in and out of my client’s Audio Plug-in Library to identify which ones were failing validation during Logic’s startup. During that process, we found a number of old plug-ins which were failing validation and my client didn’t want on his system any more. Many were demos which he had installed but were no longer required. I uninstalled the unwanted plug-ins.

    Updating Old Audio Units

    Some plug-ins were passing validation, but were old versions that were coded to run on Intel Macs. I explained that we needed to update these plug-ins to the Apple Silicon coded versions to allow them to run at maximum efficiency on my client’s M2 Mac.

    I helped my client log in to the manufacturer’s websites and download the correct updates to his plug-ins. Once installed I checked that the old versions were removed and used Activity Monitor to check the AUHostingService processes and confirm no Intel Audio Units were running in his Logic project.

    Removing Logic Projects From iCloud

    My client was storing many of his Logic Projects and audio files on his desktop. iCloud was automatically moving some of these folders into my client’s cloud storage and removing the files from my client’s Mac. This is a useful feature for many Apple users but can be a major problem for pro audio users. If files are in the cloud, when Logic tries to access them they can’t be downloaded fast enough and Logic crashes. I showed my client how to select a non-iCloud location on his Mac to store his files and set up aliases to make the new location as easy to access as his desktop.

    Organising Large Sample Libraries

    I could see that my client was using a number of large sample libraries from East West, Native Instruments and Spitfire Audio on his system. He told me that he had bought a massive 20 TB external SSD to store all his files. When I checked the file paths of my client’s sample libraries, I found duplicated locations and that many sample libraries were stored on my client’s Mac’s Operating System drive.

    My client and I discussed how he wanted his new filing system to look like, and I helped him start the process of transferring files. Since the transfer of large files from one SSD to another can take many hours, I didn’t want to waste my client’s money by spending my time watching a progress bar. I gave my client a list of what he needed to copy and where, and then we arranged to connect the next day once it was all finished.

    Once all the files were copied to their new locations, I deleted the unwanted copy from the Mac’s drive. I then used Native Access to repair the libraries by setting the new path.

    I used the library manager Apps from Spitfire Audio and East West to repair my client’s other libraries.

    Results

    The issues took a number of remote sessions to resolve, but once everything was finished my client was very pleased to see that his Logic Pro projects were now opening quickly and with no error messages.

    After our sessions, my client very kindly took the time to leave me this nice review:

    Excellent guy, brilliant service, knows all about music and plugins and what can go wrong inside your computer. Highly recommended.

    Thanks, Owen!

    Happy to help with any other music technology related problems in the future. If anyone reading this has a similar issue and would like to hire expert support, please Get in Touch.

    Categories: , , , , , , , , , , , ,

    No automated tickets, no waiting queues — just one-to-one help from an experienced music technology specialist. I’ll connect to your system remotely, identify the issue, and guide you through the fix.

    Recent problems solved for real clients.

    Optimising Logic Pro CPU Usage for Large Orchestral Mixes

    Client’s Question

    Why does Logic Pro keep crashing when I add plugins to my tracks?

    Session Result

    CPU load drastically reduced; mix workflow stabilised via bus routing.

    Read Full Case Study Report: M2 Mac Performance Fix: Eliminating Logic Pro 11.1.2 Plug-in Errors After Migration
    Preparing for a Studio Hardware Installation

    Client’s Question

    What cables do I need to connect my hardware synths to my mixer?

    Session Result

    Equipment audited, cable inventory confirmed, site visit planned.

    Read Full Case Study Report: M2 Mac Performance Fix: Eliminating Logic Pro 11.1.2 Plug-in Errors After Migration
    Mono Microphone Only in Left Speaker Fix in Logic Pro

    Client’s Question

    Why is my mono mic input only coming out of the left speaker in Logic Pro?

    Session Result

    Mono input successfully centred by changing Logic Pro track format from Stereo to Mono.

    Read Full Case Study Report: M2 Mac Performance Fix: Eliminating Logic Pro 11.1.2 Plug-in Errors After Migration
    Managing Native Instruments Komplete Libraries in Kontakt

    Client’s Question

    How do I hide unwanted libraries in the Kontakt side pane?

    Session Result

    Unused libraries hidden, visual clutter removed.

    Read Full Case Study Report: M2 Mac Performance Fix: Eliminating Logic Pro 11.1.2 Plug-in Errors After Migration
  • Logic Pro 10.8.1 Error Message Using Kontakt- Solved

    Logic Pro 10.8.1 Error Message Using Kontakt- Solved

    Hello Paul. I would be pleased to hire you if you know how to solve this issue: “Audio Unit plug-in reported a problem which might cause the system to become unstable. Please quit and restart Logic Pro”. I am on Mac Sonoma 14.3 – M1 chip using Logic 10.8.1.

    I received the above message from Tim and we arranged a time to connect for a remote support session later that same day. At the start of the session, I called Tim via WhatsApp voice chat and we set up a remote connection between our computers using AnyDesk.

    I asked Tim to load up Logic on his Mac and show me the problem occurring. Tim explained that the error message didn’t appear all the time, but only sometimes when he opened certain Kontakt sample libraries.

    Tim loaded up Logic Pro and tried to load one of his Kontakt sample libraries. Logic threw up the same error message and needed to be restarted. I opened Native Access to check details of the Kontakt installation.

    Looking through Native Access I could see that the library files were installed on an external hard disk that wasn’t currently shown as connected to the Mac. I asked Tim about this and he double-checked the USB-C connection to the external disk.

    Once the USB cable had been reconnected, the disk now appeared on the desktop. We re-opened Logic Pro and checked the plug-in again. This time Kontakt opened the library without any issues. Problem solved!

    I spent the remainder of the hour with Tim checking over his system and making sure everything else was installed and running smoothly. Tim and I had a chat about his music and I gave him some tips on some of the latest features of Logic Pro.

    Tim was very happy that he now understood why his Kontakt library problem occurred and how to avoid it in the future. Although the solution turned out to be simple, he was grateful to have a professional look at his system and solve it for him. After the session, he took the time to write me this nice review:

    Thanks, Tim!

    , , , , , , ,

    No automated tickets, no waiting queues — just one-to-one help from an experienced music technology specialist. I’ll connect to your system remotely, identify the issue, and guide you through the fix.

    Recent problems solved for real clients.

    Optimising Logic Pro CPU Usage for Large Orchestral Mixes

    Client’s Question

    Why does Logic Pro keep crashing when I add plugins to my tracks?

    Session Result

    CPU load drastically reduced; mix workflow stabilised via bus routing.

    Read Full Case Study Report: Logic Pro 10.8.1 Error Message Using Kontakt- Solved
    Preparing for a Studio Hardware Installation

    Client’s Question

    What cables do I need to connect my hardware synths to my mixer?

    Session Result

    Equipment audited, cable inventory confirmed, site visit planned.

    Read Full Case Study Report: Logic Pro 10.8.1 Error Message Using Kontakt- Solved
    Mono Microphone Only in Left Speaker Fix in Logic Pro

    Client’s Question

    Why is my mono mic input only coming out of the left speaker in Logic Pro?

    Session Result

    Mono input successfully centred by changing Logic Pro track format from Stereo to Mono.

    Read Full Case Study Report: Logic Pro 10.8.1 Error Message Using Kontakt- Solved
    Managing Native Instruments Komplete Libraries in Kontakt

    Client’s Question

    How do I hide unwanted libraries in the Kontakt side pane?

    Session Result

    Unused libraries hidden, visual clutter removed.

    Read Full Case Study Report: Logic Pro 10.8.1 Error Message Using Kontakt- Solved
  • Logic Pro Disk Overload on Mac Mini M2 – Solved

    Logic Pro Disk Overload on Mac Mini M2 – Solved

    Hi Paul, I hope you can help me solve an issue. I use Logic Pro and my Macbook kept crashing every time it reached a certain point in a song. It said System Overload or Disk Too Slow. I changed the buffer size and a whole a bunch of things in system preferences. After days of going back and forth I decided my 2015 Macbook needed upgrading. I’ve bought a Mac Mini M2 with 16GB of RAM but I’m still having the same problem.

    Dom

    I received this message from a new client by email and we arranged a time to connect the next day. Once we had the remote desktop connection sorted on his Mac, I asked him to show me the problem occurring in Logic. He opened his most recent Logic Project file and Dom showed me that every time playback reached a certain point in the track, the above error would flash up.

    My initial thought was that it might be the connection to his external drive. I tested this by moving his Logic Project to the internal SSD of the Mac Mini and reopening it. We played the song through again, but it didn’t make a difference. The crash still occurred in the same place.

    I asked my client how he had moved his apps and files from his old MacBook to his new Mac Mini. He told me he had used the Time-Machine backup method. This gave me another idea. It was likely old Preference files from the MacBook had been copied over to the new Mac Mini and Logic was running in an older mode.

    I closed Logic and navigated to the users/client/library/preferences folder. I removed all the Logic .plist files and put them into a temporary folder on the desktop.

    When I restarted Logic it was behaving as if it had been freshly installed. I had to do a couple of steps like turning off my client’s unused plugins and switch Logic back to Advanced Mode. Once Logic was ready, we opened the previously unplayable song.

    The song now played through without any disk overload messages. The Performance Meter window was now showing minimal activity rather than maxing-out.

    The operation had been a success. Dom was now able to take advantage of all the processing power available on his Mac Mini. I finished the session by tidying up the old preference files and deleting them from the desktop.

    Dom was kind enough to write me a nice review after our session:

    Logic pro X kept crashing (system overload, disk too slow) every time it reached a certain point in the session. After doing everything i could on my end i came to the conclusion my 2015 macbook pro needed an upgrade. I decided to go for the Mac Mini M2 Pro 2023 and still had the same issue! (As you can imagine i was a broken man) Paul is an absolute god send! Efficient and knows his stuff well. I will definitely be using his services again. – Domonic Jackson

    Categories: , ,

    About the Author

    PAUL ANDREWS

    I’m the owner and lead technician for Audio Support, a small company based in London, UK that connects remotely with clients worldwide to help them with their music technology issues. I’ve run Audio Support since 2005 and in that time I’ve seen and solved thousands of recording studio problems. 

    Outside of Audio Support, I run music workshops at a local school, play bass in a 90s tribute function band and perform modular synth jams with friends on Twitch.


    Get support for similar problems:

  • Logic Pro X not opening – ‘Bundle Error’ – solved

    Logic Pro X not opening – ‘Bundle Error’ – solved

    Connected remotely with a client in Switzerland. His problem was that Logic crashed immediately when loading. The diagnosis was that an incompatible plugin (Miroslav Philharmonik by IK Multimedia) was causing the crash as Logic was scanning the AU components folder. Removed the plugin from the AU components folder and Logic was able to open again.

    Went onto the IK Multimedia site to download the latest versions of their software and got the client’s plugins working again. 


    About the Author

    PAUL ANDREWS

    I’m the owner and lead technician for Audio Support, a small company based in London, UK that connects remotely with clients worldwide to help them with their music technology issues. I’ve run Audio Support since 2005 and in that time I’ve seen and solved thousands of recording studio problems. 

    Outside of Audio Support, I run music workshops at a local school, play bass in a 90s tribute function band and perform modular synth jams with friends on Twitch.


    Get support for similar problems: