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

Feb 14, 2013 1:17 PM in response to Mark Lindsey

I have been experimenting with so many things. I have tracks and aux returns coming up all over the place, tracks with one name and number in the Arrange Window and differnt name and numbers in the Mixer. It is CRAZY!!! I'm working with three user accounts. The lag is gone in one. One project crashes in another.


I have Bounced all my tracks into two folders, one with automation and plug-ins and the other without, just to protect the projects.


Every day one or more projects gets more scrambled. I keep reassigning the returns. Sometimes the changes stick. The Sends seem to be stable. Regions in certain tracks are silent (but are ok in another user).


How about creating a New Track, let's say plain mono audio. And instead of a new normal track number is has copied a Track Name from an exisitng track, and it has borrowed another's Channel Strip Settings. Apparently these settings are stored in a user folder somewhere. It is random and crazy!


Here's my reason for bouncing tracks. I have no idea what will happen with a new OS version or Logic version. I truly belevie Apple ought to come up with a FIX for those who would not or cannot buy a new Logic version (after all this). But with several projects that have value, assuming a new version moves us forward, then we can open existing projects / sessions and forget all of this. If not, maybe import or load the tracks into another DAW.


For me, Cubase 7 would be that DAW. It's really great to work with. I still like a lot about Logic for some work, but for music Cubase is a far superior platform in so many ways. I hope we get the option to chose.


I'm thiking about sitting at the desk waiting for the playback to stop, wondering if Logic will crash. It seems like months ago- but then all these other crazy issue started and the "lag" just became one of many. It is nuts!!

Feb 14, 2013 1:18 PM in response to Mark Lindsey

It looks like the post by WindowsME was already removed and I don't want to be a party-pooper, but let's keep this thread positive and not a witch-hunt talking about legal action, etc. I'm sure that violates the terms of discussion forums, and it's not productive in this venue. If you want to do something like that, you should probably create your own website. 🙂


Since I started this thread, I guess I should provide an update. I'm using the latest versions of everything, and only experience the lag problem (which is much less severe in ML now - maybe 2-4 sec of stall) when trying to real-time edit a "heavy" plugin like Waves Z-Noise. I've only been doing simple podcast mixing/mastering gigs lately, so I'm not hitting Logic anywhere near as hard as I would with a music production project. As well, the window focus trick works for me on the occassion that I need to get control back.


I feel bad for those that have it worse and I don't blame you for jumping ship. I do think Apple has really dropped the ball on this one, having not made any communication to the pro market (although when have they ever done so before) - it has always been "push" support, unless you contact them and get some follow up. Back in the day, I would email Steve Jobs and then magically, a week later, someone's head would roll and I'd get some attention, but it's a new Apple these days.


I hope we all get some relief soon, and I hope this doesn't signal the death of pro apps and the beginning of Garage Band Pro X. 😉 (Although I really like FCP Pro now, but there was a lot of pain during that transition and many jumped ship - I hope Apple learned from it.)


Good luck!


-M

Feb 14, 2013 2:12 PM in response to Mark Lindsey

Mark Lindsey wrote:


It looks like the post by WindowsME was already removed and I don't want to be a party-pooper, but let's keep this thread positive and not a witch-hunt talking about legal action, etc.


I completely agree, the fact is Logic is working perfectly well for most people Seems the operating system has outdistanced the application, old code is getting broken. I can't say I agree with the direction operating systems are heading.. Apple is guilty of the practice MS used to be accused of, heavy handed code that takes ever more powerful systems to run. The amount of background processes running in ML is staggering. On three client's machines every install of ML created problems however, only one went back to Snow Leopard. Apple pushes forward and many Mac users (not many from this group) have been trained to upgrade, problem is with Pro apps, that's not always the best idea. Applle has to support more and more hardware these days so the concept of upgrading to the latest & greatest as soon as it's released is not always the best plan.

Feb 14, 2013 3:21 PM in response to Pancenter

Great points Pancenter. My problem is that I also use the same machine for my general business/leisure use, so while in the old days of SoundTools/ProTools I would be a generation or two behind (mostly due to Digi in those days, not Apple), these days, it's like candy to me, so I early adopt and pay the price sometimes. For example, the lack of a **** Calendar snooze time option killed my previous workflow - not fun having to transition to new apps or modify your workflow on every update. Now if I can just get this yellow vertical line off my machine for 5 minutes after I wake from sleep, I'd be happy - just popped up out of nowhere. :/

Feb 14, 2013 3:26 PM in response to Pancenter

Apple don't have to support much hardware. They have a rolling 5 year support pattern, release new hardware at the most yearly and release a new OS every year. That means if they released new Macs in every single configuration every single year and you discounted RAM, CPU (aside from SMP) and screen size (apart from Retina which may need different drivers) differences and they would have to support a total of 12 versions of 5 new Macs a year, if you want to be generous:


(I counted the following from the current generation.The only thing I think is missing is the optional Graphics Cards for the Mac Pro: Mac Pro Quad, Mac Pro 8/12 core, 27in iMac 675MX, 27in iMac 660M, 21in iMac 650M, 21in iMac 640M, Mac Mini (All configs use the same driver set), MBA (All configs use the same driver set) ,13in MBP, 13in MBP Retina, 15in MBP, 15in MBP Retina)


Thats 60 Macs max. Mountain Lion currently supports around 30 (I count 29 but many of them could be revisions). Nothing compared to the average roster of, say Dell, especially considering that combining it with Microsoft still wouldn't net you a company with the financial clout or net worth of Apple.


And about the 'heavy handed' code bloat, where even Windows ends up looking good in comparison. At least when Vista came out MS listened and made 7 faster. 8 is even faster believe it or not, making it run faster than XP did back in 2003. That sounds like the OS Apple would make in my wet dreams, and if MS can do it, I honestly think that Apple is not doing it deliberately. Only one reason I can think of; Planned Obsolescence.


EDIT: Also, the post above makes an important point about Digi and how it always used to hold us up on updating due to compatibility. That point is that if there was an incompatibility, or things were buggy, Digi told us, and often had version checks in the program that refused to run on the suspect newer versions of the code until updates were released. Still no word from Apple...

Feb 14, 2013 3:58 PM in response to gen_

gen_ wrote:


Apple don't have to support much hardware. They have a rolling 5 year support pattern, release new hardware at the most yearly and release a new OS every year. That means if they released new Macs in every single configuration every single year and you discounted RAM, CPU (aside from SMP) and screen size (apart from Retina which may need different drivers) differences and they would have to support a total of 12 versions of 5 new Macs a year, if you want to be generous:


My point being, there's several different Intel chipsets involved as well as a variety of USB 2&3/Firewire chipsets, graphics/graphics configurations, Thunderbolt, MB Air, Pro, Firmware...etc


It's a definitely more than they used to support 10 years ago. Maintaining optimum performance across the board is not something I think Apple is that interested in, they would rather you be purchasing more recent hardware.

Feb 15, 2013 12:08 PM in response to Alexander One

I reported that one on day 1.I'm surprised more people haven't complained - do people not use skip-cycle so much?



Alexander One wrote:


Sincerely I don't know how many of you installed the 9.1.8 because the new skip cycle bug they introduced with this upgrade was another hit in my stomach as I use it quite often when building up song structure.


try to skip cycle a region and see what happens with 9.1.8!

Feb 16, 2013 12:42 PM in response to Pancenter

I agree, however I manually counted how many unique models they have to develop drivers for. There are between 29-37+ variants of 5 machines that currently work for ML, depending how you look at the modifcation options of the Mac Pro.


(Note that I did this by going throigh the model listings for each type of Mac in wikipedia, and discounting any models with non driver related differences to other models. Differently clocked CPUs within the same model of Mac and CPU type don't count, RAM and HDD size differences don't count, Retina does count as a seperate model but otherwise screen size doesn't count. GPU differences count and model refreshes always count.)


That's at the very most, between 3 and 4 times the amount of Macs as Apple maintained 10 years ago, but it's being handled by a company that is now 50 times the size. A company that's worth more than everyone in Sweden makes in a year. I don't think it's beyond thier scope to have fixed this bug a long time ago, and made sure it wasn't a problem well before Lion, I just think that they can't be bothered to.


I don't know if that counts as slander as I've tried to make my points as factual and well formed as possible. The fact is that the company has grown far more than it's model base has grown and easily has the money needed to throw at this issue to make it go away. (Hire contractors in if need be.)


It's coming up to 2 years since this problem first presented itself, and ther are numerous other ignored problems thing Logic that have existed right from 6 and 7. I think Apple don't want to do anything about them.

Feb 16, 2013 1:59 PM in response to gen_

gen_ wrote:


I agree, however I manually countedhow many unique models they have to develop drivers for. There are between 29-37+ variants of 5 machines that currently work for ML, depending how you look at the modifcation options of the Mac Pro.


(Note that I did this by going throigh the model listings for each type of Mac in wikipedia, and discounting any models with non driver related differences to other models. Differently clocked CPUs within the same model of Mac and CPU type don't count, RAM and HDD size differences don't count, Retina does count as a seperate model but otherwise screen size doesn't count. GPU differences count and model refreshes always count.)


That's at the very most, between 3 and 4 times the amount of Macs as Apple maintained 10 years ago, but it's being handled by a company that is now 50 times the size. A company that's worth more than everyone in Sweden makes in a year. I don't think it's beyond thier scope to have fixed this bug a long time ago, and made sure it wasn't a problem well before Lion, I just think that they can't be bothered to.



gen_


I'm with you 100%, as others have noted, I'm a Logic fan but not an Apple fan.

No matter the size of the company their main focus is not highly efficient code and support of their professional users. It's obvious that Logic hasn't been thoroughly beta tested with Lion & ML, and definitely not on the range of machines still supported. As you know.. most third party beta testers (pros running Logic) are no longer used. A product can't be beta tested on paper, it takes many users with a wide variety of hardware to do a through job. Apple is not only supporting the hardware you mentioned but also three different operating systems.. Snow Leopard is still considered a supported system... yes? Right now it's all about bottom line and investors.. and how many new iphones and ipads can be put into play.


However... I'm still looking forward to see what Logic X brings to the table, I just wish it was cross-platform, I would be using it all the time instead of just for my own use.

Feb 16, 2013 4:55 PM in response to Alexander One

Alexander One wrote:


The only reason stopping me doing for now that is called Logic Pro,

So I don't really need a bootcamp Ableton & Plugins are working fine also on here.


I was responding to this comment of yours...


so I decided when the upgrade time will come, my next machine will be a PC.


...and I was simply pointing out, you don't need to purchase a PC.. just use Bootcamp with your existing hardware,....

Feb 16, 2013 5:17 PM in response to The Art Of Sound

I didn't got that quick, sorry.


Actually I meant when the time will come to upgrade the hardware of my mac pro (8 core early 2011),


It will be worthless investing a huge amount of money to upgrade a system where my main daw (logic) it's being treated like this by apple.


I will, instead:

work with ableton 9 or cubase 7 on a windows system, as PC are now more powerful, more upgrade-friendly and cheap than every mac on planet earth.


It's all about Logic for me,

and what its future will be.

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.