Strange problem with Logic on Mountain Lion

I have the same issue.

Lion worked fine ... but ... Mountain Lion seems to really not like the Real Time Analyzer in the EQ.

The interaction with the program goes away (all control is lost) then many seconds later, every click I made while I was trying to control "anything" suddenly starts to happen on it's own. It's as if the part of the program that accepts the user input goes away and everything is kept in a buffer until finally that part of the program comes back and everything stacked in the buffer is released ...

I tried lowering the buffers but it seem to have no effect.

I hope there's a fix for this REAL SOON!

There is Nothing that Mountain Lion offers the is worth having a cripple Logic ...

Im having the same issue here, but the problem extends to alot of the more heavy duty third party audio units that i use..some of which are vital.

Many au's seem to not trigger this issue either and some make the computer unresponsive for longer than others, it seems the more memory and CPU the plugin is using, the more likely it is that logic will become unresponsive.

If other people are having the same problem then please come forward so a fix can be issued.

Hey!

I'm having the same issue aswell. I upgraded to an 8GB ram (i thought it was that) then I did a clean install of Mountain Lion and the problem still continues.

Its getting really really annoying and so far the only 'fix' I've found, other than waiting it out, is to right click Logic in the dock and click on the current project. It seems like everytime I open a plug-in, Logic sort of goes into the background.

Its really confusing and annoying. Apple seriously needs to release an update with a fix.

Report this via Logic Feedback on this website and call tech support to complain (if you still have phone support available., that is). Apple needs to see how widepsread the problem is.

It should also be noted that this is not happening on every system running ML and Logic 9.1.7. There seems to be some kind of third thing required... it most probably has something to do with the changes in grpahics handling from Lion to Mountain Lion, and can apprently be triggered by a number of situations.

For example, I had this same behavior until I removed the Mackie Control control surface install from Logic, tossed the .cs preferences and restarted the Mac. I can put Logic back into the same tailspin by reinstalling that control surface profile. OSC controllers work fine and don't affect Logic's transport reponse. MC in = trouble, MC out = no trouble. But this isn't the only trigger.

So I agree that Apple needs to address it. But since it's not reproducible on every system, you have to yell extra loud to make sure they get it.

Different problem, but definitely related to Mountain Lion, as nothing else in my setup changed from OS 10.7 to 10.8.

My setup is this: iMac i7 8gb sdram. Apogee Ensemble interface. None of the rest of my setup should matter because this happens most often after recording, not during!

I am getting a slow disk or system overload message. Could be in the middle of recording, but usually is in playback. And what is really strange is it happens sometimes after I've muted some tracks, and try to listen to the rest.

Typical scenario...perhaps 6-8 audio tracks, and as many software instrument tracks. Can be playing just fine until I do something different, such as muting some tracks or soloing tracks. I did start using my firewire drive to record to again, something I had to do when using my previous G5 Mac, but hasn't been a problem until now with my iMac.

So I too would urge, beg, demand of Apple this be resolved. I'm using pro equipment, all guaranteed to work and play well together, have plenty of RAM, and have an issue which NEVER happened using OS 10.6 or 10.7

So

Call Apple, posting here will do you no good, sending feedback is advisable but who knows how long the cue is or if it gets read at all. By calling and getting bumped up a level in tech support you can be sure your voice is heard, plus....they will have a database of support related problems and may even have a suggestion that helps. I've beta tested for two major companies (Steinberg being one) .... a call carries much more weight, trust me.

Same problem here! I'll get onto calling up on Sunday and hopefully get some good feedback, if anyone rememdies it earlier be sure to let us know!

sI

I am at my wits end with this! Logic is currently unuseable for me . . . a big shame really as Logic has been my DAW of choice since the beggining. Same problems that are well documented, slow unresponsive GUI, logic going to sleep and not responding for up to 45 secs then 'waking up'! It was bad in Lion - hoped Mountain Lion would sort it but its worse, much worse! Also experiencing the odd random crash in 32 and 64 bit modes, totally unacceptable for 'professional software'. Have been running a session in Pro Tools 10.2 for a few days now, and its been a total joy. Am I thinking of turning to the dark side (Pro Tools) you bet I am!

Same problem here. Seems very wide spread based on the forum posts. How can that slip through beta testing.

The interesting thing is that when Logic can't be stopped with the space key or onscreen buttons, it reacts promptly to the Navigation controls on from my EUphonix MC Control. However a few seconds later (when ML pays attention), it fires up all those ignored commands. - very annoying to say the least.

Edgar Rothermich

www.DingDingMusic.com/Manuals/

Has anyone spoken to apple yet about this? I plan on ringing then this week, just if anyone has any other info from them on it it would be helpful on the call.

I post back here to once I've called them.

sI

Its Fixed!!

I reported the problem a few days ago and have been in discussion with apple over the past week, sent my report in and gave all the information. Looks like a few other people might have done recently too as a ML update came out today which has fixed the problem! I am now happily running several EQ's with the analyser on with out lags.

The update mentions a fix in regards to a probem with running audio through a tunderbolt display which I'm guessing is what the EQ analyser uses.

Update and be happy people! :-)

Strange. I'm still facing that problem even after the update.

The thunderbolt display is an external display.

I honestly don't know why people do this to themselves, especially audio professionals in the middle of paying sessions.

I mean I know this won't help out those who already have but... Always leave a major OS upgrade for at least a couple of months so the software bugs are ironed out.

Ah really? Weird, Not sure as to why it's sorted mine then :-s

Have you reported it to Apple? Mines currently being escalated.

Ah right, I was jumping to conclusions about the thunderbolt display over the excitment! lol

Yup, first time I've done it and I've definitely learned my lesson! ⚠