Major UI Lag in Logic Pro 9.1.7 on OS 10.8?

Ok I had this problem and fixed it.

Basically the UI lag had got so bad that I could sometimes not even stop logic using my mouse. I could not also click on items in the mixer and so on.

Here's what I did to fix it.

I deleted the Novation Automap files completely from my computer.

http://www.novationmusic.com/answerbase/en/article.php?id=468

Then I edited my MIDI preferences in Logic to remove the Automap midi configuration because that was still there.

I then downloaded the latest update to my MOTU Ultralite Mk3 soundcard.

I restarted my machine and now Logic works fine with no UI lag.

Sounds like some kind of internal MIDI feedback loop, that type of lag is exactly what happens during a loop situation.

I don't know anything about the Automap software, but I've noticed that it does seem to have come up in an awful lot of problems on numerous other forums.. mmm, don't really know though, but it wouldn't be exactly encouraging to me if I were considering using it.

That's one of the ML/Logic bugs I had - output to the Mackie Control would work sometimes, but input (i.e. faders) never worked. Downgraded to Lion, and all is well (mostly).

Pete

Guess what!

I just switch Logic 9.1.7 to 64-bit.

And then switch back to 32-bit again.

And it starts to act normally!

Am I the first person on earth that cure this problem (by accicent)?

Sorry....

it went back to the same problem again just now...

sigh~

Monbaza from Taiwan

Ok so im having the same issues on a Mac Pro xeon 8 core, running ML, Logic 9 and automap and I have discovered not so much a workaround more a reset.

What you need to do is when you notice the lag click and hold the logic icon in the dock to bring up the submenu and select 'show all windows'. Then click on your project window that shows up and Logic should 'catch up'. I found this is successfull 99% of the time for me.

Thank you! It sure did help... otho not not all the time.

In my case it solves 30%.

hypnotik wrote:

To summarize a bit the problem, and keep a trace (video)

(just a mouse driver, razer icon in my menubar - it doesn't cause any issue to the system/Logic)

I also have a mouse driver showing up in System Preferences ("Mouse Locator"), + Apple QMaster, Flash Player, Flip4Mac WMV, Growl and VoddlerNet. Which mouse driver do you have? I wonder if any of these extensions could be part of the problem.

one of the ways I stop playback now is by attaching a MIDI keyboard/controller and pressing Stop on that..

It's often hard to find a solution to a problem if the problem has mor ethan one cause. Maybe this problem has thre causes: the new OS needs a more powerful graphics card (256 MB may not be enough) to work properly, som drivers may not be 100% compatible with mLion/Logic, and 'something' in the system causes Logic to respond well to MIDI messages but not to mouse actions or key commands... Plus, there's a change in how audio is buffered. I'll check if I can get back the audio-won't-stop problem when pressing stop, and see in the transport bar if Logic is actually running or if audio is just playing after Logic has stopped. I found this problem in Safari as well, under mLion: audio from certain URLs continued to play even after I had closed that window, eg by clicking on some tabbed bookmarks.

I'll start by disabling the Mouse Locator and see what happens. But wait... how do I disable it?

I'll start by disabling the Mouse Locator and see what happens. But wait... how do I disable it?

Found it - just use the installer. What will I miss if I disable Growl? I don't remember why I have that product in there...

so Apple just released 10.8.1. Wonder if that helps any of our GUI problems or will we only see it in the .2 release since they apparently just seeded 10.8.2 to developers 😟

Just testing it and so far so good!

I pretty much had the problem all the time, but no issue as yet. I've tried really messing with the EQ and compressor with analyser on, during a complex arrangement. *breathes out*

They didn't mention anything it in the release notes / fixes, just something about thunderbolt audio...

looks like it's working there too, i can't reproduce the problem with an empty session and one plugin + channel eq loaded whatever the analyzer resolution.

thx battlegimp for your feedback, could you please stress a bit more logic interface and give us your experience there ? i must install my plugins and drivers on my ML partition...so it could be very very long....

It seems fine here on 10.8.1, running a song with 30+ tracks and some automation. I just opened 5 EQs, enabled the Analyzer on all of them in high resolution mode, and things still work fine. There's maybe a half-a-second lag, but nothing like the issus I originally had. When leaving Logic to go to the Finder or some other app, there's sometimes some waiting - it seems that Logic somehow makes itself ready to work the way it wants to work, but that's fine. Jumping to new locations in the song, by clicking in the bar rules with the mouse, never takes more than half a second before the music starts playing from the new location. That's with 5 channel EQs open w/ analyzers. The song has maybe 60-70 plugins.

But then again, I removed some drivers and startup items I didn't need earlier today and couldn't get the problem back before I went 10.8.1 either, so I can't really tell what fixed it. I think part of the problem was having two screens with two different sizes/resolutions. I even found that it helped to open a window (on another screen?), and that this possibly helped even after I closed it again. At any rate, if you already are using Mountain Lion, I doubt that there are any reasons not to install the .1 update, which is only a few megabytes.

What I found in the midst of all this is that there are background operations not shown as Preference extensions in the Preference window, or as login/startup items on my account. Evernote, for example, has a feature called "Start Evernote helper" in it's preferences - which doesn't show up any of these places. So look in your menu bar for possible background troublemakers if you still have the problem.

Anyway - I was looking forwad to do some more troubleshooting tonight based on my findings, but now I can't even recreate the problem. Very disappointed. 😟

🙂