luraplitmur

Q: Logic Pro X 10.2.1 update system overload problem

I have been using Logic Pro X for two months on my new MacBook Pro with 16gb of RAM with no major problems. Just after updating to the 10.2.1 version, the programme cannot cope with a 26 track jingle I had been working on and constantly issues the "system overload" message. The LCD display shows CPU use at 50% when 5 to 10 tracks are being used and it's overwhelmed when the rest come into play for the Chorus. This had never happened before.

 

Checking the Activity Monitor while playing the song  shows the computer is using ONLY 7GB of RAM of the 16GB I have (and this while having Safari open with many tabs and other Apps) and the CPU use is ONLY at 20%!

 

What has happened and how can I fix this? I need to work on this project urgently!

 

I may have learned the lesson never to update the software while working on a project whose deadline is fast approaching.

 

Disappointed.

MacBook Pro (Retina, 13-inch,Early 2015), OS X Yosemite (10.10.5)

Posted on Jan 22, 2016 5:42 AM

Close

Q: Logic Pro X 10.2.1 update system overload problem

  • All replies
  • Helpful answers

first Previous Page 4 of 4
  • by Dominique.Cologne,

    Dominique.Cologne Dominique.Cologne Mar 18, 2016 5:57 AM in response to markorozco
    Level 1 (8 points)
    Audio
    Mar 18, 2016 5:57 AM in response to markorozco

    As i said, i read the entire 3 pages,  i have tried a higher increasing the buffer size and the multithreading to only playback, to no avail.

    I m using a Macbook pro (late 2011) I7 2.7 , 16gb Ram and Samsung 850PRO SSD drive.

    I can only partly justify what you say about the nature of computers and software. Of course i won't be able to run efficiently the latest OSX with a 10 years old machine, but here we are talking about an update (a "technical" improvement) on the same software ... and the result is unacceptable..

    The workflow of my machine has been massively compromised since this last update, and it is only because of the update,  the machine has little installed and nothing has changed since the previous version of Logic.

  • by Pablo Logic,

    Pablo Logic Pablo Logic Mar 24, 2016 3:07 PM in response to Dominique.Cologne
    Level 1 (14 points)
    Mar 24, 2016 3:07 PM in response to Dominique.Cologne

    I have the same CPU issues since updating to 10.2.1 with other problems like drop-outs.

     

    Removing all the Logic-related .plist files from my preferences folder solved it.  You have to re-set your preferences though afterwards.

     

    I must profess that 10.2.1 is more CPU heavy than 10.2.0 but unfortunately my Time Machine HD died just before I updated so I couldn't revert to the previous version; but if I could I would.

     

    My hunch is the problem relates to the new vector-based plug-in GUIs, possibly complicated by 3rd party plug-ins that use the same expandable out vector GUIs, like Fabfilter ProQ2...and perhaps my graphics card not being good enough to handle them.

  • by Dominique.Cologne,

    Dominique.Cologne Dominique.Cologne Mar 24, 2016 6:50 PM in response to Pablo Logic
    Level 1 (8 points)
    Audio
    Mar 24, 2016 6:50 PM in response to Pablo Logic

    which ones are the .plist that you have deleted? i ve tried with the main one but i think the problem s still there

    D.

  • by tortosise180,

    tortosise180 tortosise180 Jul 31, 2016 1:08 PM in response to luraplitmur
    Level 1 (8 points)
    Desktops
    Jul 31, 2016 1:08 PM in response to luraplitmur

    I have a mac and use reaper. I am thinking of getting a new MBP and logic with it, so thank you for this thread - forewarned, but….

     

    I can tell you that i have upgraded reaper versions 3 times in the last two years and each version has not slowed down my little old MBA ( only 4 gb RAM, 1.7 ghz i5 dual core, SSD so very sensitive to any resource hogging ) or increased cpu usage for same projects ( certainly not to the point of noticing higher cpu )  although granted, Reaper does circumvent more detailed GUI resource issues due to its simple utility graphics.

     

    Many of you may already know this but to those who have knocked back the buffer setting ( latency ) for logic as part of a solution to reduce the problem, unless something very odd has happened , doing so is just opening up resources via the delay induced. The longer the buffer, the more power is available to process. This is a standard trick when mixing. i.e. when recording time sensitive things ( real time VI's for example ) you need very low latency, but when mixing you need power for plugins instead so you knock it back to its maximum setting ( e.g. 1024 ). A buffer of 256 samples will introduce noticeable latency when recording using virtual instruments.

     

    As mentioned, 3rd party plugins can be very problematic. cheers

  • by Pancenter,

    Pancenter Pancenter Jul 31, 2016 1:48 PM in response to tortosise180
    Level 6 (9,913 points)
    Audio
    Jul 31, 2016 1:48 PM in response to tortosise180

    Reaper was coded from the beginning to be fast and efficient. Some of Logic's code dates back 10-15 (or more) years. It's gets slower and more problematic with every OSX update.

  • by tortosise180,

    tortosise180 tortosise180 Aug 5, 2016 4:54 AM in response to Pancenter
    Level 1 (8 points)
    Desktops
    Aug 5, 2016 4:54 AM in response to Pancenter

    Ah ok, i will have both soon anyway so i will be able to decide based on efficiency. I know reaper likes to see only one thread per core and i think all tracks use cpu but logic only uses cpu on used tracks (?) and can use two threads per core. On this basis logic should be more efficient than reaper on osx and some tests and users over on the reaper forum seem to suggest this. However, at higher used track count with more plugins apparently reaper is as or more efficient. I look forward to finding out on my projects.

     

    However, my main problem with reaper on osx has been 3rd party plugin compatibility. It is not good over all as can be seen by the huge sticky thread on reaper osx forum. I am hoping logic will fair better in this respect. Compatibility and efficiency are both really important to me. cheers

first Previous Page 4 of 4