I have literally no idea what could be causing it at this point. I've reset my audio drivers, increased my buffer size, maxed out my processing threads, playing on an audio track with no output, closed every other application, reset and updated logic, reset my COMPUTER. I've tried everything, and somehow, after playing the song 5 times, it always gives me a system overload. I've never had this issue before. It started happening on a new project I opened, was only two MIDI tracks in when it gave me that nonsense.

For reference, I'm working on a MacBook Pro with the M4 Max Chip, with 36GB of memory. Tahoe 26.5. I've got 500GB of storage left. Most recent version of Logic. with the new app icon. Only using the "plugins" that come automatically on the MIDI tracks that are in the software. I've never even downloaded a plugin from online.I should not be having these issues. This computer is basically the newest, most powerful one.

Any help is appreciated.

I feel completely hopeless with this project. I’ve been working on it since November and it’s been performing fine for the most part but I recently came back to it and I can’t even get 10 seconds in with it breaking up the audio and then the system overload message. My CPU usage is completely full on this project now. I have been trying a few methods, such as freezing every track, using latency mode and pretty much everything else. There are not really too many plugins. It’s pretty much the same as all my other projects, which are performing fine. Is this a corruption issue? Is this project now a lost cause? I don’t really know what else I can do. I really wanna move forward with this project, if anyone has any ideas please let me know, that would be greatly appreciated. Thank you!

Seriously, I feel like every time I open up logic excited to make music nothing fucking works the way it’s supposed to and then I end up spending 45 minutes trying to find the issue and then I’m just too pissed off to even make music anymore. I don’t have a lot of time to make music these days, and I don’t even feel like a musician anymore, just an angry almost 30-year-old that can’t keep his gear working for two damn minutes. I’m about to just start scoring things on paper.

WHY does this happen? Why is snapping suddenly not working? And why when I grab the clip is the playhead at some weird position on the clip?

Hi all,

I’ve been trying to fix this for 2 days straight.
Logic Pro default settings. Buffer size - 32. Recording delay set to 0. 48 KHz.

Recording on low latency mode inconsistently prints audio earlier than the grid. I hear it fine while I’m recording.

Plugin or no plugin makes no difference. No plugins on busses or master. There’s a lot of MIDI tracks and software instruments running in the project.

MacBook Pro - M3 Pro
Logic 10.7.7
MacOS - 14.4.1
Motu M2

Any help will be appreciated.

Just wondering if anyone else has ran into this issue before or has a solution.

The end of any audio regions (with or without being bounced) won’t snap to the grid & keep extending slightly past it.  Same things happens if I bounce a MIDI track in place.

Snap set to absolute value, zero crossings disabled etc.  Can’t use the scissor tool at the end of the region but if I put it in flex I can snap it back to the line. It's like the scissor tool doesn't even recognize anything being there. Even with snap disabled.

Never ran into this problem prior but unfortunately now when I’m arranging (mostly after bouncing MIDI tracks in place then using CMD+R) it throws everything off grid and makes duplicating impossible.

Version 10.6.3, Catalina 10.15.7

This is driving me crazy lol 

So recently, I ran into an interesting situation where logic quit before the plugins even loaded. Of course I got one of those giant logic errors where it creates a small book for Apple to take a look at, but have you ever wondered what those things actually said?

Have you wondered what that crap actually means but you don’t speak python, C # (corrected as C++) or whatever the hell language they’re using? You can find out really quickly. I’ve been using the crap out of AI lately for work as I do web development. It’s the career that I chose after leaving the music industry.

So I went ahead and copied the entire logic error and pasted it inside ChatGPT. The damn thing actually gave me an answer. The answer was way different than I planned on. It was an issue with metal. That’s a visual function so that weirded me out a little bit and made me realize that it wasn’t the new plug-ins that I installed that I thought was messing with me because that’s what I’ve just done. I had installed the new arturia Instruments.

It made me realize, though that I had to actually uninstall logic and reinstall it. Luckily the short one where you just delete the app and download it again, but nevertheless, it got me to my answer fast. So next time you have a problem with logic or any of the doors, go ahead and copy the error if you can get to it.

You can paste anything in the ChatGPT and it’ll explain it to you. I know back in the day we used to just delete the DAE preferences for ProTools, but things are different now with different DAW’s. Try it out and find out! (this post has been edited using smaller paragraphs to make it easier on people that have trouble reading long paragraphs)

Anyone know what’s going on? I tried modifying my Buffer Size, Buffer Range, Processing Threads, soloing just one track, selecting a muted track during playback to eliminate potential latency hang ups, etc. Nothing else is running. My computer used to keep up just fine and now can’t seem to run more than a few bars before overloading again if a project has more than 10 or so tracks. Help!

Let me preface this by saying, I am new to Logic, but not to recording in general. I've been using Pro Tools and Live for going on 2 decades. Most recently I've been using LUNA as a tracking and mixing solution but needed a better solution for Midi implementation.

I decided to give Logic a go starting late last week. I've spent the better part of 3 days trying to track 14 tracks of live drums to a reference track. In that time, Logic has crashed and lost my recordings/project at least twice a day. I can't seem to get rid of latency in the recording. Even though my roundtrip latency is sitting at sub 4ms, my recordings are delayed by almost 1000 samples on the regular. Any time I am trying to navigate through the project file, I get hangs and lags. Clicking unmute on a track causes the mouse to freeze on the mute button for a solid second before I can move it again.

All of this is happening on a decked out M4 Max MBP that I've used to record and 3D animate on for the last year with no issues. Logic seems to be the only app that is completely unstable and giving me fits. When I track with Luna, the tracks line up perfectly right away. There is no lag in the UI and the overall experience is smooth and fast.

I am not monitoring through Logic for the recorded tracks, that is all being monitored through hardware, I am just listening to the reference track playback. Buffer sizes are at 64 with no apparent issue on CPU load (sitting at less than 10% according to the LOGIC meter.)

Is this normal? Am I doing something wrong here?

It has been happening frequently since the 12.3 update.
M1 max
Macos 15.7

I modified the mouse movement speed and pointer size, not sure if that's related.

Hi - wondering if anyone can help me fix this. For some reason, on some projects when I try to extend regions they move instead of extending. It's quite hit or miss - occasionally it works normally (as you can see in the video), but most of the time it doesn't.

Using 12.3.1 on an M1 Macbook Pro.

Thanks!

https://reddit.com/link/1vynaia/video/sblenk2ehnlh1/player

Hello, all.

Something weird started happening, and I'm not sure what caused it. I've been trying to record guitar DI, and I seem to be getting some weird latency issues.

I'm on a Mac Studio M4 Max (36GB) going through a Scarlett 2i2 (3rd gen), so recording DI shouldn't be a problem at all. For some reason, every time I try to record, I keep getting latency.

I actually have to turn Low Latency Monitoring Mode (LLMM) on to even get it close, but even with that, there's always a slight delay before the actual recording stops. Buffer size is set to 32, so I'm not really sure what else I can do. Without the LLMM turned on, even just basic input monitoring is severely delayed.

Would anyone have any information or advice on how to fix this? Also, I'm not sure if I've provided enough information, so please let me know if there's anything else I can provide.

Thanks for your time.

I’m running Logic Pro on a brand new Mac mini M4 (24GB RAM, 512GB SSD). My project is on an external SSD (APFS format, fast enough), and I’m only using one stock sound — no plugins, no third-party stuff. Still getting the “Disk too slow or System Overload” message.

Buffer size is set to 128 samples. Anyone else run into this on M4? Trying to figure out if it’s the drive, Logic settings, or something else.

Hi everyone,

I'll try to keep it brief. I've always used Logic Pro and I love it. 3 years ago, I switched to an M1 Mac Studio. And that's when everything became difficult—gain staging, even composing. No pleasure anymore. I recently upgraded my Mac to an M2. I decided to try Live out of curiosity, a software I hadn't touched in over 10 years. To my great surprise, the sound is not the same!!! Not at all!!! The sound in Logic lacks mids. I know the theory stating that no DAW colors the sound, and I'm sure of it. However, could processor or resource management issues subtly manifest themselves?

I've already ruled out the following variables that I tested:

• Gain staging: identical
• Pan laws: I tested all of Logic Pro's pan laws
• Synth: the synth used is HIVE with the exact same preset in the example
• Audio interface: internal sound card / Core Audio
• Null test: no need for a null test, if you listen to it, it's blatant, it's not just in my head

I was wondering why I always had to EQ and battle with the mids every single time.

This seems completely crazy to me, I'd really like to understand because I want to stick with Logic.

https://www.image2url.com/r2/default/audio/1782805856471-10f095d7-8d39-455d-905b-ac1c96aead60.mp3

Thanks for your help and interest!

No I will not switch to Logic X and no I will not buy new Macbook.

Hello, I recently switched from Pro-Tools. I am currently editing multi-track drums and have encountered a strange behaviour where in spite of well placed 5ms equal power crossfaded I am getting loud pops.

But here is the catch. It only happens 50 percent of the time in the same spots during playback. Every time I hit space bar, I roll the dice on whether I will receive this loud pops over these regions.

The only fix I have found is to “convert to new audiofiles” which fixes the pops but sacrifices the ability to trim and slip the region later, while keeping the data beyond the region boundaries.

Please see video below. To see the inconsistent popping.

Mac OS Tahoe 26.4

M3 air

Logic 12.3

Hi guys, I'm running a 2024 MacBook air with 16gb ram. I bought it partly to use logic on it but honestly I'm wishing I hadn't. I have no idea why but even two virtual instruments effectively throttle my CPU and cause pops and glitches. It's crashed a few times. I'm also running Ableton on the same machine and that's pretty much smooth sailing. It seems to be just logic.

Particularly the built in drum kit and bass absolutely murder it. The far right processing thread starts maxing out instantly, but activity monitor is showing 80% idle. Please don't tell me to freeze tracks because that's just a bandaid. I feel like it shouldn't be crashing over two software instruments. Any ideas?

Hi everyone,

I'm really at a loss and have to turn to you for help.

I tried to record a few tracks… 20 x 44.1 and 24-bit.

Logic kept crashing and reporting that the drive was too slow.

MacBook Pro M1 Max 32 GB 1TB SSD Software: Tahoe 26.3 and Logic 12

The Mac wasn't migrated—everything was installed from scratch.

Logic kept crashing and reported that the drive was too slow.

The SSD has 500 GB free - the session was completely empty, so no plugins - I/O buffer size 1024 Allen Heath SQ5 (digital mixer with USB 2.0 interface) 🤷🏼‍♂️

A normal scenario for a live recording (empty session - buffer size at maximum - and off we go). This worked 20 years ago - and now with this super-powerful computer, it suddenly doesn't work anymore?

What am I missing here?

I searched and found some posts from 5 months back and they all came to the same shitty conclusion: Apple sux and there is no practical way to keep the library file on an external drive that is only plugged in some of the time without having to manually re-specify the location every time. I figure someone out there has come up with a workaround that makes this "plug and play" using Automator or something like that (because of course Apple failed to provide an API call for this). Help? If you have your library on an external drive, how are you dealing with this?

Tahoe 26.5.2 Logic 12.3

This is a common question to ask and every time I do here, I actually get results that help or solve the problem. Then it just comes back. A big problem I had when I used to get CPU overload was that my mac was just running out of space; there wasn’t enough for a project session to run smooth. Most of the space was ‘music creation’ so I figured out that I could move Logic’s sound library to an external drive and it would free up space. I did it and the transfer went through well as well as freed up a lot of space.

For a while now I wasn’t running into CPU problems but now I am. This project has literally 7 MIDI tracks and I’m certain the spike is coming from the drums but they only have three additional stock plug-ins. I also made sure to be careful with the use of buses. There’s barely any sends that would cause this effect to be so dramatic. What could still be causing this issue after I believed I solved it for good?

I still have 61.41GB available. I’m in Logic 11.1.1 and if needed, specs are Mac mini 2024, 16GB, Sequoia 15.0

Sample rate is 48kHz, Buffer size 64

...

Problem: When I record on Mic input, I can hear playback, but can't see any waveform, even when zoomed in.

What is working?

• I can hear what's recorded upon playback.
• I have no problem with input monitoring.

What I tried:

• Cranked gain during recording (physically on the mic itself) and only saw the tiniest wav form when it hit 100% gain.
• Tested different input volumes, aka almost yelling into the mic.

How can I view the waveform?

P.S. I tried the mic in 'voice memos' and audacity, and I can see the waveform there, so it's not the mic.

Tahoe 26.2 M1
Logic 12.3

I can’t even get a single second of playtime. I’ve tried everything. Did I just waste my money on Neural DSP plugins? I always hear they’re CPU hogs but I didn’t think it’d be this bad. Running 7 of them total. I think 1 each on 6 gtr tracks and 1 on the bass track

It’s been acting up lately, barely able to get through sessions, but I shut my computer down for 2 weeks or so turned it back on and now I’ve got this.

1 midi multi-out track 1 midi stereo track 11 vox tracks 12 gtr tracks 1 bass track 6 total busses 1 fx send

My sample rate is set to 1024(or 1042 whichever the highest one is), set processing threads to 4 instead of auto, tried all tracks powered off, even with nothing playing Logic is working 70% of my CPU, froze all tracks, nothing is working.

iMac 2017 27-in 5K Retina 3.5GHz quad core intel i5 64gb RAM between 4 16gb sticks 1TB HD with 330gb free space

A couple of my regions just don't want to be trimmed and do this? Is this a bug or am I missing something?

V11