Logic 9's UI extremely laggy - any fixes?

Logic Pro bug update: I received word a few days ago that the Mountain Lion crew had figured out a fix for the Logic Pro lag issue, which is actually a major Core Audio problem that has effected many other apps as well. So, yay! He said the update should be coming out sometime in January or February and apologized for the continued wait. Just wanted to pass that on to other Lion and ML Logic Pro users.

Hm, none of those fix'es work for me.. I have a new MacBook Retina 15 and it's UI is laggy as ****, for example, i can't scroll in safari without pictures to start flicker and logic is just, gaaah!

When i have like 4-5 instruments and one open - the meters are lagging as **** like i try to push the computer way to far andgd when i try to pause logic agwith spacebar, nothing happens. When i go to mission control, press a window in there, then all my commands from keyboard or/and mouse is coming in to logic.

I mean, i have a 13 MacBook C2D and it's working like 100 times better machine than this 2000dollar machine.

Im sorry if this message is writthejn with some glitches, because when i write in this window some text suddenly dissapears (retina bug).

I hate my new machine.

EDIT: I have also tried all methods in retina lag UI thread and nothing helped me.

Does the activity monitor or console log show anything interesting? (both those apps reside in Applications>Utilities)

No offense to the Apple guys but they really did not think on thier feet when developing these last two OS. I am a PRO user of Logic and between Apple and Tascam, I dont know who I am more dissappointed in. To solve EVERYTHING EVERYONE is talking about on here, I simply re-installed the original SNow Leopard 10.6.8 and have had not one problem. I will again wait until I see EVERYONE use this update and see it working for all in Logic.

CHEERS!

Same here on a MB Air only a year old. Open the EQ, turn on the spectrum analyzer and... goodnight. The EQ window can be moved around smoothly, CPU use is low but Logic itself accepts no standard input anymore. Cannot stop the track, close the EQ window etc.

Sometimes it will suddenly "catch up" registering dozens of clicks after I switch to another app, but it usually requires a force kill on Logic and I get to lose my work. EQ + analyzer seems to make it happen 100% of the time although I have noticed this a few times a day at other times when the EQ is closed.

Since I'm new to Logic and this bug looks to be over a year and a half old, going to go ahead and try the ableton demo that came with my midi keyboard instead. Particularly for creative stuff, the last thing I want to do is waste time "fighting" with software.

Hi Seugmatis,

It is definitely a well-known problem and Core Audio is the culprit. Right now a fix has been discovered by the Mountain Lion team, but we just have to wait for them to release it. In the meantime.... be patient. You do not have to kill Logic to get it to stop. It will stop eventually, even if it's 2 minutes later. I know this isn't a great comfort, but at least you don't have to lose your work!

Fredo Viola wrote:

Hi Seugmatis,

It is definitely a well-known problem and Core Audio is the culprit. Right now a fix has been discovered by the Mountain Lion team, but we just have to wait for them to release it. In the meantime.... be patient. You do not have to kill Logic to get it to stop. It will stop eventually, even if it's 2 minutes later. I know this isn't a great comfort, but at least you don't have to lose your work!

And how do you know it's been discoverd and that a fix will come?

Because I wrote a letter to Tim Cook, a very long one, and as a professional curtesy Apple had somebody very high up in the staff at Logic Pro write to me. We have had a lot of communication, even as they were trying to get the Mountain Lion staff take the problem seriously, as it is clearly not something that could be fixed with a Logic update. He wrote to me just before Christmas saying that the team had found the problem and fixed it, but we'd now have to wait for the release of the Mountain Lion update.

The most wierd thing is the fact that my rMBP has started to work now together with Logic, without any glitches and very few GUI lags.

What i did? I turned on only the dedicated graphic card in rMBP. Now my mac seems to be as quick as my old one.

Logic has some GUI lags here, but very few, it happens when i try to modify this plugins:

Fxpansion GURU

Xfer Tools LFOTool

All the Logic stock plugins, like EQ and analyzer on many EQs at the same time, all working.

Don't know if this is just that it will be working for now - but it has worked now for about 1 week.

Tnx.. Well 10,8.3 dev preview should fix it then.. Any one tryed it?

I have very similar days, km9898. Some days I don't have a single problem. others (like this morning) anytime I open channel eq terrible lag. Glad to hear you've got a possible fix for yourself though!!

Ahhh, I just saw that up higher in the thread. It isn't too bad otherwise, maybe a couple times a day but on chapter 9 of Dave Nahmani's pro logic training book (which is *great* btw) there is the whole section on EQ ... that is where it bit really hard. Otherwise the software is amazing! A lot of time already invested in learning logic, so I'll just keep this in mind when using the EQ analyzer and look forward to the bugfix. Thanks for the tip!

ususally if you just disable analyzer it won't have the lag.

Yeah, i know because it was the same lag at my iMac and the only solution was to downgrade to SL and then all worked perfectly. If i had the choice to downgrade this rMBP to SL, i would do it! But i can't and, well, it works for me right now but i know that it will go back to that terrible lag some day. Just tried to be as happy as i can for this problem hehe 🙂

My MBP i7 2.0ghz 8GB RAM suffered this problem after a recent software update... then I found someone claiming that if you manually install the Garage Band update it fixes the issue. THIS WORKED FOR ME. I am currently mixing a 80 track hiphop tune and structuring a live project without any issues... In fact the 80 track project is only tickling 4 bars on the CPU meter compared to a maxed CPU meter on a 5 track project before the Garageband workaround.

From reading some posts on this thread, I wonder whether it has anything to do with those of you who have HD screens... as my MBP has the basic screen (mid 2011)...

Best of luck to you all.