Logic Pro X 10.2.1 update system overload problem

Upgraded from 10.2 as well with these specs:

MacBook Pro Retina ''15 Middle 2014 / 2.5Ghz / 16GB / Quad-Core i7 / UAD-2 Satellite Quad, Custom Bundle

I got the same CPU Overload message on one core as well what completely ruins the workflow, literally it's just the same as earlier Logic Pro on Lion with an i3 processor. Yes I'm using busses, and I don't seem to have any "bad habbits" in mixing so forth.

No.. but again, its just an example of how different setups may be affected by certain changes, than others

While this is correct, still how can 10.2 run smoothly, and 10.2.1 run as a piece of youknowwhat?

These new Apple updates like El Capitan, and now Logic make my i7 laptop behave like I'm on Windows Vista. How can an actual upgrade downgrade the overall performance is a mystery to me. And I can't seem to find any explanation besides the Apple's Marketing Plan on selling more fresh top end computers. I know Apple executives don't read the support threads, which is disappointing to me, so I need to tell it somewhere lol.

I am experiencing the exact same issue. However I'm getting it just using the stock plugins from Logic/Alchemy. I do have NI Komplete 9 Ultimate installed as well but the message comes whether or not I'm using them. The latest issue is just starting a track with 3 logic instruments and I get the message. Would love to know of a fix or whether they plan to push out an update for it.

I don't think my computer is the issue. Late 2013 Mac Pro 8-Core 3.0ghz processor, 32gb ram (Apple Factory) 2xD700 graphics cards, 1tb PCI flash drive (Apple) running 10.10.5. This computer has eaten up and spit out anything I can throw at it like its a light snack, I swear I can hear it ask me "Is that all you got?"

I haven't added anything new since updating to LPX 10.2.1

After updating Logic from 10.2 to 10.2.1 and Logic Remote on my iPad, then finding 10.2.1 is too buggy for me to use (performance issue documented here), I rolled back to 10.2. however now Logic Remote will not work with 10.2. Is there a way to roll back the version of Logic Remote on the iPad?

Plexus wrote:

however now Logic Remote will not work with 10.2. Is there a way to roll back the version of Logic Remote on the iPad?

No.. unless you made a hard backup of your device via iTunes.. and the older version of the app is stored on your Mac.... Then you can manually restore that version.

Luckily I had the ipa for the previous version of Logic Remote. I was able to transfer it to my iPad and it works fine now with LPX 10.2.

I hope apple is going to respond to the various issues with 10.2.1 especially the over-load issue. Then again, there have been a bunch of other bugs reported with 10.2.1 beyond performance. sad.

I hope apple is going to respond to the various issues with 10.2.1 especially the over-load issue.

...and again, for what it's worth..

Im running LPX 10.2.1 under 10.10.5, 10.11.3 and 10.11.4b on a variety of different Macs (2011 iMac, 2015 iMac 5K, 2015 Mac Pro, 2011 Mac Mini Server 2Ghz..) and no such overload issues here at all...

What overload issues I have seen, have all been related to 3rd party plugins that aren't fully compatible and needed removing or when possible, updating to function correctly... or conflicting 3rd party applications installed... or the usual culprits in regards to poorly written Audio/midi drivers ... (Digidesign/Avid/M-Audio etc..) that always seem to have issues once OS X and/or Logic is updated..

The other thing I've noticed is apparently, the lack of proper optimization /updated drivers for certain Mac hardware itself.. Some older graphic cards found in older Mac Pros or MBPs... for example.. seem to have problems coping with the newer graphic routines used by OS X and Logic...leading to CPU overloads and GUI sluggishness...

That's fantastic that your systems are so stable. But please don't discredit the rest of us with issues. Your assertion that the performance issue is related to "3rd party plugins that aren't fully compatible" implies that Apple changed something in 10.2.1 to make plugins that worked in 10.2 to fail in 10.2.1. This implies that Apple purposely did this - that 10.2.1 has some feature not in 10.2 that is now making plugins incompatible. If this were the case, one would expect some note about this from Apple as well as some kind of check built into 10.2.1 that informs the user of this incompatibility.

There have been some reports of people removing a plugin and getting better results with 10.2.1 however this is not proof that the issue is related to "incompatible plugins". In fact, based on the failure, it sounds like 10.2.1 has been made incompatible with plugins that otherwise worked fine - this is a bug in 10.2.1.

If someone has some kind of note from Apple about 10.2.1 causing issues with plugins and requiring the plugins to be updated, I'd love to see this! I know of no plugin devs that are saying their plugins needs to be updated to work with 10.2.1.

Plexus,

You appear to be missing my point entirely.....and because of such, have apparently found my post offensive, in some way to you...

Giving such offense was never my intention.

What I am trying to get across is that there are several possible reasons for suddenly getting overloads in conjunction with Logic Pro X 10.2.1...

Those are the reasons I listed as obviously there has been some changes in 10.2.1 that are causing or triggering such behavior and with the right troubleshooting some of the negative end results of these changes.. can be eliminated or reduced.

As can be seen from the 10.2.1 change log there have been many tweaks and changes made to LPX, some of which may be at the root of such issues... but not necessarily ones that will be fixed by a further update to Logic itself.

Instead, as just one possible scenario... it may well be that certain 3rd party plugins (or hardware drivers.. or whatever else) will need to be updated so they work smoothly within the new libraries, routines and frameworks in OS X that Logic now appears to be using... as again, it obvious not all systems and setups are being affected to the same degree by the update.

This leads to the possibility of the specific causes i listed, as being part of, if not wholly so, of the problem and if one looks at such possibilities you might be able to eliminate/minimize the overload issue yourself...

In every case to date, that I have consulted on with my clients.. I have identified such issues as i listed that once fixed, again either eliminated or reduced the overload issues to the point the systems became quite usable again.

My own systems are all stable now, yes. This is not to discredit anyones else's reports.... Its simply a fact that has to be taken into account as again, its part of the troubleshooting process... If it were an issue that affects everyone.. that would indicate with much more reliability, that it would take a fix from the Logic Devs or to OS X.. to resolve such issues. The fact it doesn't affect everyone, changes the playing field, so to speak and so such resolutions may need to come from other sources depending on the specific causes found through proper troubleshooting.

It's also worth noting that in the past such performance issues were also identified to only affecting certain people because of the specific workflows they were using... Examples.. leaving multiple EQ's in 'analyze' mode... or using certain combinations / orders of certain plugins in their projects that for some reason became a less optimal setup after an update to Logic. Tweaking their workflows improved the performance of their system by some degree.

Anyhow..

if you choose not to troubleshoot the possible issues yourself but instead either roll back to earlier combinations of OS X and/or Logic or wait for some indeterminate period of time.. for some possible fix.. from whatever source, thats entirely up to you. I'm simply saying that with a bit of work on your own behalf, you could be back up and running.. without any such delays.. Note: I said could be.. not will be...

Again, the choice is yours as always.

Cheers..

Nigel

I know of no plugin devs that are saying their plugins needs to be updated to work with 10.2.1.

Celemony and Melodyne 4.0.2... would be one prime example...

Developer Logs:

Issue:

Clicking the Library tab for a software instrument track crashes Logic Pro X 10.2.1 if the project includes an audio track with the Melodyne plugin loaded. The issue has been identified as being caused by an improper library call within the Melodyne plugin that will require an update from Celemony to resolve this issue.

I think we will all agree we shouldn't be afraid to update our systems and our DAWs...

and...

It is the best time ever to be making music, but we seem to have forgotten the main point is stability to stimulate creativity!

I agree.... But here's the thing..

Users shouldn't ever update OS X nor Logic... until everything is fully tested and confirmed as working..

This is becoming a real issue.

Actually, its been like this for years now... Users are treated as unpaid beta testers.... and so they should be fully aware of this and take the much needed precautions..

I and others have posted this advice repeatedly here and yet, users just charge ahead and update anyhow because they want the latest and greatest.... and then wonder why things break.... especially when they do so mid project! (And it still amazes me how few do so without making any form of backups to roll back to if /when updates invariably have issues)

From the User tip found here...

El Capitan 10.11.3 / Logic Pro X 10.2.1 Compatibility information

For anyone, for whom working with Logic is important... and who is thinking about updating their current version of OS X....

Don't!!!!

At least not until it has been fully tested with different hardware/software/drivers etc.... and after ensuring that your current hardware is compatible with the version of OS X that you wish to upgrade to.. and has the appropriate drivers, where applicable.. that work and have been fully tested with that new version of OS X

If you really want to try out a new version of OS X then install that OS X version on to an external Hard Drive, install Logic Pro on that drive along with any drivers/plugins etc... and then boot to that. and test thoroughly.... leaving your current configuration alone and working...

or...

Make a full clone backup of your current system drive using something like Carbon Copy Cloner or SuperDuper! (My personal choice) to an external drive before you update to Yosemite and then if things don't work out you can quickly and easily revert back to your current config with ease..

Note: The sole use of Time Machine as a clone backup is not recommended as not all files will be restored correctly and you may find you have to do a great deal of manual tweaking/fixing/re-registering to get everything back to normal. TM is great for individual file restoration but for full cloned restores, not so good!

Based on past experiences.. as seen by the many 100s of posts made in the Logic Pro forum after the release of Lion, Mountain Lion, Mavericks and Yosemite...there could well be incompatibility issues that will rear their ugly heads upon the launch of the next new OS X version... so be warned!

So again... as always when OS X or Logic Pro is updated... Take your time and let others find the bugs/issues etc before you install it yourself.. or if you insist on doing so.. make proper clone backups first... to save a lot of wasted time and effort later.

The exact same advice applies to any and all Logic updates too....

Some of the regulars here like myself.. still use LP9.1.6 and Snow Leopard 10.6.8 as our primary working systems.. because that is to date, still the best performing and most stable combo of Logic and OS X.... I also happen to run testbed systems here.. (10.10.5, 10.11.3 and 10.11.4b along with the current versions of Logic..) so I can troubleshoot and test out new updates... as they happen.. but I would never use any of those testbed setups... as my prime working setup.. until I knew them inside out, quirks, bugs and all...and it worked as I wished... on my primary working rig.

However, you do get the feeling that, generally, it is more about being able to sell your product as fancy and spectacular rather than promising a stable system, a 4x4, heavy-duty, versatile workspace that remains functional regardless of all of those different circumstances.

Please bear in mind.. we are not Apple here.. We are all just users like yourself.... Apple has no real presence in the community except for moderation and maintenance duties for the most part..

Why doesn't Apple answer the questions that we ask about Logic Pro?

Cheers..

Nigel

100% agree. I've been using this code since 1988 with CLAB Notator. This app was the most stable elegant software I've used. Until Apple got their hands on it. But to be fair, even through LP 9 it was pretty stable. But in the early days on the Atari, it dead stable - no crashes in years of use. We pay good money for this stuff. Back when it would cost you $1500 for what you get now for $200, well, it had better be rock solid. But what, because Apple discounted the price they should get more tolerance for bugs and lack of stability? I'd rather pay $1500 and have it stable thank you very much.

Expecting the user to troubleshoot bugs introduced by Apple, is absurd. Sure, you do it if you have to and if you can. In my case, I can not. I do not have time to troubleshoot this list of plugins, all which work fine in 10.2. http://theplexus.com/pluings/plugin_list.png

Apple dropped the ball. Logic Pro 10.2.1 is a fail. Too many people have the same issue with performance forcing them back to 10.2 or to troubleshoot and unable to use plugins they've likely paid good money for. We deserve better.

I've been using this code since 1988 with CLAB Notator.

Likewise.. Supertracks in 86, Creator in 87 and then Notator in 88...

But what, because Apple discounted the price they should get more tolerance for bugs and lack of stability? I'd rather pay $1500 and have it stable thank you very much.

Couldn't agree more with this statement... but then again, I don't often upgrade my stable working system... because I need its stability more than I need fancy new features that I may or may not actually want or use in reality...

The 'once a year' major updates to OS X... and Logic.. leaving users as unpaid betas testers.. is absurd... but I suspect its as much to do with market driven expectations these days (see new iPhones and iOS update policy) and the need to sell newer hardware... which users have to buy so their Macs can handle the higher demands placed on the Mac's sub systems.. to provide for.. for example... higher resolution screens. (that my poor, aging, eyesight really cannot benefit from..).......... more than anything else...

Ill stick with my primary 10.6.8 and LP9.1.6 setups here as my main working rigs, for as long as I can, thank you.. and you can keep all the new stuff... as again for me... reliability, stability and performance far outweighs anything else for my personal workflow.... and sanity!

I do not have time to troubleshoot this list of plugins, all which work fine in 10.2

You probably forgot about the U-HE issues with the missing UI that initially started after LPX 10.1.... as one example... of something that broke (in other DAWs not just Logic it should be noted) and needed fixing by the U-he dev... because Urs was still compiling his plugins using an out of date SDK.... which then broke when Logic and other Daws... were updated to use the new SDK routines.. (A common cause of issues after OS X or Logic/DAW updates.. when Devs fail to recompile their plugins after SDK changes or updates so they break in unexpected ways..and users think its the update to OS X or the DAW that is causing it..)

Luckily Urs was on the ball and the fixes came out in beta initially, very quickly. The final versions of the fixes were released after 10.2 came out... Unfortunately not every plugin Dev is as diligent....

8th October 2015

Host/DAW issues:

- The "Missing UI" in Logic and Studio One is fixed.

You raise a good point - why not roll back to LP9? I don't really use most of what Logic has to offer. I keep my workflow very basic. But 3rd party plugin heavy. Was 9 the earliest version that supports 64 bit plugins? I think I have it on disk somewhere?... no wait... I skipped 9. I have 8. I think 8 is 32 bit only right? I can google all this, no worries. but 10.2 works ok for me too. so I am happy on 10.2 and leave it at that. 🙂