Major UI Lag in Logic Pro 9.1.7 on OS 10.8?

Hi,


I've just completed my first session in Logic 9.1.7 on a Mac Pro Quad Xeon 2.6 after upgrading to Mountain Lion 10.8. I got through it, but experienced the following new bug (as compared to running in Lion 10.7.4:


I noticed that if Logic is currently playing when I double click on a plugin in the channel strip, and then try to stop the playback (keyboard or by clicking the transport in the arrange window), I will get from a 5-45 second lag before the app responds and actually stops. No mouse or keyboard commands seem to work while it's hanging up.


Workaround: Only open plugin windows when playback is stopped, and then playing and stopping works fine (although maybe a little more laggy than in the former OS still).


Is anyone else experiencing this or have any better workaround ideas?

Mac Pro, Mac OS X (10.7), Quad 2.66GHz, 16GB, 18TB HD / RAID

Posted on Jul 26, 2012 1:43 PM

Reply
905 replies

Oct 23, 2012 9:44 AM in response to ndrdj

Unfortunately...me too.


Because of this blatant lack of importance and attention by Apple, ProTools has been on my radar for the past four weeks. Been doing a lot of research on it. Now I've begun budgeting for it. Have a few professional friends in the "sound business" that live by it. I have found that, for the most part, ProTools is the industry standard for "professionals."


I really love what Logic Pro is....or was. But the bottom line is I've got to keep up with the industry if I'm to stay competitive. So I have to choose tools that are doing the same. Logic used to but I guess that was the past.


All things said and done, as many complaints as I and other have about this issue, there's still just ONE thing that's terribly troubling to me. This problem started immediately after installing Lion. It didn't take a few hours, days or weeks. It was as soon as I rebooted from the system update. Then Mountain Lion made it worse. The same scenario for many, many, many other users. So....if that's a fact...


Logic wasn't REALLY ever tested on L or ML by anyone at Apple. It simply couldn't have been. If so the problem would have been noticed...IMMEDIATELY. Surely the issue wasn't noticed but dismissed with a, "We'll figure it out later" mentality was it? What's that say about Logic Pro's importance/future/pro users to the "powers that be" at Apple? Not much.

Oct 23, 2012 9:48 AM in response to MadDog15

MadDog15 wrote:


If so the problem would have been noticed...IMMEDIATELY.


I can't agree. I have seen the problem here and there, but it has been extremely rare for me. The problem doesn't appear for everyone, and for those that don't have it, it can be very hard to reproduce. Nobody seems to know exactly what causes it, but certain install configurations seem more likely to have it.


Thankfully it looks like Apple finally has more info from users and is able to reproduce the problem, so hopefully we'll see a fix sooner rather than later.

Oct 23, 2012 10:05 AM in response to Mike Connelly

I sure hope you're right. I really do.


As a check list here's what I've done to date to remedy the issue:


1. Rebuilt Permissions

2. Rebuilt ACLs and Permission for Utility partition

3. Uninstalled and reinstalled logic from scratch....every thing disk by disk.

4. Called Logic support.

5. To date, spent a total of about 5.5 hours on the phone with Logic tech's

6. Have contact with Senior Logic tech person and personal e-mail address

7. Bought a brand new Mac Pro 5,1 (Quad core 3.3Mhz, 32GB of RAM, Three, 2TB hard drives, etc etc.)

8. After 5 weeks of same thing...wiped the drive completely and reinstalled everything fearing Migration Assistant could have brought over bad files. (Everything from System, all other applications, widgets, fonts etc. etc.)

9. Reinstalled Logic from scratch again.

10. Preformed all required and necessary updates

11. Rebuilt permissions and ACL's after massive reinstall of everything

12. Made milk and cookies, cried then went to bed.

Oct 23, 2012 10:31 AM in response to TokyoD

Did a full system update and Logic's non-stopping in the middle of a sequence happens a lot less, but there is still a problem with lag/delayed stopping of a sequence.


Looked at the system Console app and saw this:


10/24/12 2:18:23.192 AM Logic Pro[18654]: DTUninstall(), the current deferred task 0x6eccb3c4 being removed is also currently executing its dtAddr routine, so unexpected things may result ( Radar #4555679 ).

Oct 23, 2012 10:37 AM in response to Mike Connelly

I think it was poor or minimum in-house testing, Apple has enough "different" machines out there with varied firmware that they need either a more competent or comprehensive test team that uses a wide variety of users. Apple is supporting more machines than they ever have... their "Pro" applications should be thoroughly

tested, especially since this was reported to Apple under Lion.


I'm not weighing in on the FinalCutX -> Garageband comparison but if you followed the release of FCX you know it was released in a Alpha/Beta condition and that Apple used paying customers as beta testers. No one, even the most die-hard Apple fans disagrees with that. It's not that it was missing features, it was that half the advertised features didn't work correctly. Many users got their money back after trying to use it for a week or two. If Logic users are wary of new releases and how well their tested, they may have cause.

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.

Major UI Lag in Logic Pro 9.1.7 on OS 10.8?

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