Logic 9's UI extremely laggy - any fixes?

I've been a pretty happy Logic user since 2004, but lately version 9 has been really cheezing me off. It seems that whenever I'm playing my current project, the user interface becomes completely unresponsive to key commands and mouse clicks, which will be delayed for many seconds, or ignored entirely.


This is a fresh install of Logic Pro 9.1.4, 32-bit, on one of the new Mac minis (dual 2.7GHz i7, 4GB RAM, stock 500GB hard drive), with a PreSonus FireStudio Project. However, this was also happening on my previous system, a 2008 15" unibody MacBook Pro. It was happening a little bit on Snow Leopard but it's gotten much worse under Lion. My MacBook had aftermarket RAM (8GB) and an aftermarket SSD, but everything in the Mini is stock.


It's happening even if I only have one or two tracks, although it seems to be worse if I have any of the various metering plugins running and open, or ChanEQ with the analyzer turned on. I wonder if maybe those plugins aren't handling UI updates correctly, or something.


Just to be clear, I have absolutely no third-party AudioUnits installed, and it's neither a CPU nor an I/O issue (both gauges are pretty much empty, and Activity Monitor shows Logic as taking about 10% of one CPU), and yet it takes anywhere from 3-10 seconds for a simple mouse click to go through.


This is getting EXTREMELY frustrating, especially since the lag seems to always happen at the worst moments (i.e. I'm trying to turn down the volume on a track which suddenly got really loud, and the lack of responsiveness means my ears get blasted and I have to take a break for them to recover before I can start mixing again).


Has anyone else been experiencing this and found a workaround? Is anyone at Apple even paying attention to these issues? I feel like it's the same problem that was being discussed in this thread, which was never resolved: https://discussions.apple.com/thread/2396951


Message was edited by: robert113

Mac mini, Mac OS X (10.7), 2.7GHz i7, 4GB RAM, 500GB HDD

Posted on Jul 30, 2011 7:31 PM

Reply
516 replies

Jan 26, 2013 12:13 AM in response to Mark Lord

Yep, I've been trying out lots and lots of DAWs, and while many of them may be more stable and reliable than Logic, none of them have an interface that's as remotely usable and no-nonsense. Live, Studio One, Rebirth, Renoise, Cubase, ProTools LE... all seem to have interfaces that are designed to show off how impressive their graphic designers are, and not how easy they are to use. They all have some good IDEAS, but their implementations are all lousy.


If it weren't for the Logic GUI lag problem I'd have no reason to look for anything else. Hopefully with 10.8.3 it'll finally be usable enough, even if it isn't as silky-smooth as it was on 10.6.


Also I hope that the Logic team just haven't been sitting on their ***** all this time; maybe there's a Logic X in the works, and maybe it'll be worth upgrading to (even if it's an even more substantial UI reboot than 8 was).

Jan 26, 2013 1:59 AM in response to buddhistmarty

Haha - if only... Now if all DAWS could load sessions completly from other DAWS that would keep the manufacturers on their toes...


Fluffy - that's a shame - I was kinda hoping Studio One was going to be the one to change that. Still, I have heard good reports from some pros so it might still be worth checking out. I believe the new 2.5 update brought a lot features and user requests to the table...

Jan 26, 2013 2:18 AM in response to Mark Lord

Yeah, Studio One is a good start, but it's far from usable at this point. For example, I have multiple MIDI inputs (keyboard, drum kit, a few other miscellaneous controllers), and while it lets me set up multiple inputs and everything, it will only route my keyboard to anything. Not useful when I'm trying to record drums. It's also very fiddly to get working with Presonus' own hardware, and the user interface is kind of weird in terms of how it handles tracks vs. instruments and whatnot. It also shows a lot of information about what's available but no clear way to make that available stuff into in-use stuff.


The timeline itself is pretty good, but it's basically a clone of Logic in that regard. Which isn't a bad thing, of course. Although one major difference between it and Logic is that parameter automation is done as a separate track rather than it being attached to the track itself. It seems like it might actually be better in general - one of my big frustrations with Logic is being unable to easily separate automation data from the parameter that's being automated (say, if I want to copy one parameter to another, or I want to rearrange my plugins on the control strip or whatever). I didn't play with it too much, though, since it just seemed like finding more good features in it would make me even more upset that basic things (like MIDI input routing) weren't working. 🙂


Basically, Studio One feels like how Logic and Cubase felt 10 years ago - fiddly, weird, and inconsistent.

Jan 26, 2013 3:09 PM in response to Pancenter

Pacenter, I totally agree!


About other DAWs.. I read somewhere that ProTools isn't 64 bit, which is obviously a game changer. What I'm going to be trying out as an alternative app is Digital Performer. I have a lot of good friends who love this app, and say it's very stabile.


Anyway, very very disappointing about Apple. I agree that a healthy Steve Jobs would not have let this happen to their professional app. But keep in mind, it's a Mountain Lion issue that shows it's ugly effects not only in Logic, but I've also heard Reaper and Garage Band. And boy am I tired of having to turn off and on my Ensemble when the software crashes under Mountain Lion. The tech support at Apogee recently recommended as a fix that I install Snow Leopard!


Still can't wait for this update, and I hope it fixes all these problems. My sinking suspicion is it won't though. 😟

Jan 26, 2013 3:39 PM in response to Fredo Viola

Fredo Viola wrote:


Pacenter, I totally agree!


About other DAWs.. I read somewhere that ProTools isn't 64 bit, which is obviously a game changer.


The Protools boards seem concerned (obsessed) with ProTools catching up to 64-bit Nuendo which now uses a RAM cache to load most of the project into RAM, (if you have the memory) for incredible performance. Protools is losing some to the Nuendo camp. I guess the Nuendo audio engine is spectacuar, I'll soon get to see the new version as the University and local PBS studios are upgrading their systems soon.


If anything, Logic users should be concerned that the Logic engineering team had to convince the OSX developers there was a problem. That doesn't bode well. OSX is no longer a lean/mean operating system and it seems the eye candy just keeps getting piled on while performance drops. I don't know enough about programming but it seems Retina support has added considerable graphics overhead.

Jan 26, 2013 11:41 PM in response to Pancenter

I think you've both hit the nail on the head there - it's an OSX issue rather than a Logic issue per se; which is actually even more worrying - as the chance of them getting those billions of lines of code sorted seems even less likely. I remember when Windows XP came out (using Logic 5.xx - as someone else said, still probably the most stable version ever produced) and the first thing we all did was go into control panel and turn on all the pointless eye candy and new looks to get back the lost performance, and have a clearer interface. Lion and Mountain Lion seem so un-apple in so many ways to me. Their whole history has been built on practicle, clear GUIs that are a pleasure to use - and now we have icons that are grey, grey and grey, loads of stuff we are really need and want missing, and loads of crap we don't clutering the place up and draining overhead.


Soon (no, make that now!) , we're going to need one of those clever programmers back from the windows days - who would work out loads of hacks and mods to turn off all the crap we didn't want and that got in the way of the the music software that was running... What a sad that of affairs. And to think, on the strength of 10.4 my one MacBook has become 2 Mac Pros, MacBook Pro, MacBook, iPAD and 3 iPhones... Sad... I might have to go a say 100 hail-mary's but has anyone used Windows recently??

Jan 27, 2013 12:52 AM in response to Mark Lord

I have a single quad-core processor Mac-Pro (Snow Leopard) & A Quad core PC I built running windows 7, they are lightpiped together 8 channels going either way depending on what machine I use as a master. I still have a rack of hardware synths and a MIDI patch bay. I'm mostly back to playing these days but I had a great run with PBS & NPR 1993-2003.. then funding dried up. I still do some things but nothing like before.. it's not as fun now anyway, plus I'm closing in on retirement age and it's too expensive to keep everything current.


Windows 7 is wonderful for Audio/MIDI use, I can use less I/O buffer and still have more efficient CPU use. I fear Win-8 will be another do-all OS loaded down with a slew of background processes.


My only experience with Lion and ML was upgrading on two different client's machines, they're both back with Snow Leopard.


There's a program on Win that allows one to check the DPC Latency of their machine, using this program I tweaked Win-7 until it's extremely efficient with real-rime tasks.


User uploaded file

The 13 number is extremely low showing this machine has been optimized for audio video... it never burps.


The operating system maintains DPCs scheduled by device drivers in a queue. There is one DPC queue per CPU available in the system. At certain points the kernel checks the DPC queue and if no interrupt is to be processed and no DPC is currently running the first DPC will be un-queued and executed. DPC queue processing happens before the dispatcher selects a thread and assigns the CPU to it. So, a Deferred Procedure Call has a higher priority than any thread in the system.


Note that the Deferred Procedure Call concept exists in kernel mode only.

Feb 19, 2013 8:54 AM in response to fluffy

EVERYONE! I have found something that worked for me. I recently upgraded to Mountain Lion (in hopes that all bugs would be fixed) only to find that it pretty much rendered my Logic Pro useless with lag. So, after a good deal of forum searching, I found this link that tells you how to start Logic as a Root instead. It's very easy to do and I haven't had any major lag issues yet. I suggest, if you are still having this problem, giving this a shot.


http://osxdaily.com/2013/02/06/how-to-run-gui-apps-as-root-in-mac-os-x/?utm_sour ce=feedburner&utm_medium=feed&utm_campaign=Feed%3A+osxdaily+%28OS+X+Daily%29



To simplify the instructions... go to you your Applications. Right click on Logic Pro. Select "Show Package Contents." Go to contents/MacOS/Logic Pro. The "Logic Pro" should be an executable (exec). Double click on that. It'll run a terminal which will boot up Logic. Done deal. I then made an alias of the executable and put it on my desktop.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Logic 9's UI extremely laggy - any fixes?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.