Logic Pro X is slow after installing SSD

Well, that's a good advice, let's just install the worst, least reliable, most buggy, ugliest, most catastrophic OS Apple has ever released

 

I've been using Logic Pro X on Mavericks since Mavericks came out, I really doubt it has to do with that. I'm really scared it is a hardware problem, and the Apple service would probably cost a big amount of money.

Well, that's a good advice, let's just install the worst, least reliable, most buggy, ugliest, most catastrophic OS Apple has ever released

 

I've been using Logic Pro X on Mavericks since Mavericks came out, I really doubt it has to do with that. I'm really scared it is a hardware problem, and the Apple service would probably cost a big amount of money.

 

Look, you can either exhaust all your options in trying to troubleshoot this problem, or you can ignore obvious advice from a few of us. You're talking about spending money to fix a hardware issue but you haven't even tried a system update yet. Like it or not, it is a possibility.

Well, does anyone else recommend installing Yosemite?

Okay I installed it, problem still here.

 

We'll never solve this… should I just get a new Mac?

 

The problem is that Logic behaves weirdly. Some other audio stuff(*1) behaves weirdly as well. Here's how Logic behaves:

 

The app (Logic Pro X) opens up instantly. When loading projects(*2), the beach ball appears and it takes a while (*3) to load. (longer than it should!(*4)) As if Logic was frozen for a short time. Projects close instantly as well. Quitting Logic however takes quite a while (*3) - again, the beach ball appears, everything seems to freeze, only after 30 seconds it quits successfully. I never needed to force quit Logic.

 

You'll have to be more specific on some points.

(*1) What audio stuff? And how does it misbehave. And also: what audio stuff does not misbehave?

(*2) Describe the project in (much) more detail: sample frequency; how many tracks; how many of them VI's; which VI's; how many and which EXS24 and/or Kontakt instruments; how many audio tracks; how many MB's of audio files; are all, some or no tracks automated?; how many buses and auxes are used?

(*3) How long exactly (in seconds)?

(*4) How do you know how long it should be?

 

Also, it might help to watch Activity Monitor while you quit Logic, sort the list by CPU activity, maybe processes spiking during those "hesitations" could provide a clue.

Another thing to try is to do the quitting sequence again, bui this time first make sure your Mac is disconnected from the internet. See if that makes a difference to any of the "too long" processes.

(*1) Actually this problem (or these problems) are solved, they had nothing to do with that. So I won't bother explaining them because I believe it will bring up too much confusion; it's already complicated enough and I believe it's difficult to keep track also.

 

(*2) Forget the project – because I believe it has nothing to do with that. The reason for that is because it happens when I quit Logic also. With no project open at all. Imagine I started Logic, and then decided to simply quit it again. Without opening any project. The problem would occur while quitting Logic.

 

(*3) I've just counted now, it took me around 9-10 seconds until the spinning beach ball was gone and Logic finally quit itself.

 

(*4) I remember what it was like before.

 

Logic always used to quit instantly. Apparently it is a core audio problem, but I have no idea how to update it or whatever. Apparently the core audio is a driver on Mac, that's what I read.

 

I've checked Activity Monitor already, and Console too. Nothing abnormal. Actually, I just checked console again, and now under Yosemite it did give me something.

 

11.04.15 14:48:01,958 spindump[372]: Saved spin report for Logic Pro X version 10.1.1 (3683.37) to /Library/Logs/DiagnosticReports/Logic Pro X_2015-04-11-144801_Times-Mac-Pro.spin

 

I clicked on "Open report" and it showed me this:

 

Date/Time: 2015-04-11 14:47:55 +0200

OS Version: 10.10.3 (Build 14D131)

Architecture: x86_64

Report Version: 21

 

Command: Logic Pro X

Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X

Version: 10.1.1 (3683.37)

Build Version: 3

Project Name: MALogic

Source Version: 3683037000000000

App Item ID: 634148309

App External ID: 811655126

PID: 38707

 

Event: spin-lite

Duration: 6.20s (process was unresponsive for 2 seconds before sampling)

Steps: 63 (100ms sampling interval)

 

Hardware model: MacPro5,1

Active cpus: 24

 

Fan speed: 799 rpm

 

Heaviest stack for the main thread of the target process:

63 start + 1 (libdyld.dylib + 13769) [0x7fff95cdb5c9]

63 ??? (Logic Pro X + 6704117) [0x107d7abf5]

63 NSApplicationMain + 1832 (AppKit + 13140) [0x7fff8ec9d354]

63 -[NSApplication run] + 711 (AppKit + 552040) [0x7fff8ed20c68]

63 ??? (Logic Pro X + 6941147) [0x107db49db]

63 ??? (Logic Pro X + 6941258) [0x107db4a4a]

63 ??? (Logic Pro X + 6920230) [0x107daf826]

63 -[NSMenu performKeyEquivalent:] + 359 (AppKit + 2439597) [0x7fff8eeed9ad]

63 _os_activity_initiate + 75 (libsystem_trace.dylib + 3287) [0x7fff8f81ccd7]

63 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 114 (AppKit + 2443900) [0x7fff8eeeea7c]

63 -[NSMenuItem _corePerformAction] + 382 (AppKit + 2444622) [0x7fff8eeeed4e]

63 ??? (Logic Pro X + 6703375) [0x107d7a90f]

63 ??? ( + 832328) [0x10b5be348]

63 -[NSApplication sendAction:to:from:] + 452 (AppKit + 2445233) [0x7fff8eeeefb1]

63 _os_activity_initiate + 75 (libsystem_trace.dylib + 3287) [0x7fff8f81ccd7]

63 ??? (Logic Pro X + 6703244) [0x107d7a88c]

63 -[NSApplication terminate:] + 1759 (AppKit + 3672671) [0x7fff8f01aa5f]

63 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66 (Foundation + 31185) [0x7fff950109d1]

63 _CFXNotificationPost + 3140 (CoreFoundation + 67124) [0x7fff901a1634]

63 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12 (CoreFoundation + 1180764) [0x7fff902b145c]

63 ??? (Logic Pro X + 6879136) [0x107da57a0]

63 ??? (Logic Pro X + 1940423) [0x1078efbc7]

57 ??? (Logic Pro X + 4792370) [0x107ba8032]

57 ??? (Logic Pro X + 730140) [0x1077c841c]

57 ??? (Logic Pro X + 722226) [0x1077c6532]

57 ??? (Logic Pro X + 724248) [0x1077c6d18]

57 ??? (<6773F937-75FF-3031-AEC9-A7476D519C36> + 227308) [0x10b2617ec]

57 ??? (<6773F937-75FF-3031-AEC9-A7476D519C36> + 161117) [0x10b25155d]

57 Delay + 70 (CarbonCore + 590233) [0x7fff8d648199]

57 mach_wait_until + 10 (libsystem_kernel.dylib + 71166) [0x7fff8b8875fe]

*57 ??? (kernel + 1220912) [0xffffff800032a130]

 

Binary Images:

0x107716000 - 0x1088a7fff com.apple.logic10 10.1.1 (3683.37) /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X

0x10b22a000 - ??? ??? <6773F937-75FF-3031-AEC9-A7476D519C36>

0x10b4f3000 - ??? ???

0x7fff8b876000 - 0x7fff8b893fff libsystem_kernel.dylib (2782.20.48) /usr/lib/system/libsystem_kernel.dylib

0x7fff8d5b8000 - 0x7fff8d89ffff com.apple.CoreServices.CarbonCore 1108.6 (1108.6) <8953580E-7857-33B2-AA64-98296830D3A8> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore

0x7fff8ec9a000 - 0x7fff8f81bfff com.apple.AppKit 6.9 (1347.57) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit

0x7fff8f81c000 - 0x7fff8f822fff libsystem_trace.dylib (72.20.1) <840F5301-B55A-3078-90B9-FEFFD6CD741A> /usr/lib/system/libsystem_trace.dylib

0x7fff90191000 - 0x7fff90529fff com.apple.CoreFoundation 6.9 (1153.18) <5C0892B8-9691-341F-9279-CA3A74D59AA0> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation

0x7fff95009000 - 0x7fff9533afff com.apple.Foundation 6.9 (1153.20) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation

0x7fff95cd8000 - 0x7fff95cdbfff libdyld.dylib (353.2.1) <9EACCA38-291D-38CC-811F-7E9D1451E2D3> /usr/lib/system/libdyld.dylib

*0xffffff8000200000 - 0xffffff80009fffff kernel (2782.20.48) <4B3A11F4-77AA-3D27-A22D-81A1BC5B504D> /System/Library/Kernels/kernel

 

So apparently my duration of 9-10 seconds was wrong, it says (if I understood this correctly) that it was somewhere around 6-7. I had different values when trying again, but it's always between 6 and 7.

 

Can anyone conclude something from this report? I hope it doesn't contain sensible/personal data. I hope we're a step closer now

 

Edit:

 

I had reinstalled Mavericks twice (fresh install), but it was from a USB flash installer. Could it be that something went wrong with making that installer, and thus both versions of Mavericks I installed were faulty and caused this error? I made a thread about it recently: viewtopic.php?f=10&t=116088&p=596107#p596107

It was on 10.9.5. I then decided to install 10.9.4, which I installed directly from the existing system 10.9.5. The issue was still here. I then jumped from 10.9.4 to Yosemite, but like you see, still here. So the last two were not fresh installs, they were based on my 10.9.5 installation. And if this installation was "faulty", then that could be the reason?

Edited April 11, 2015 by Revs

So the only problem left is a quit time of less than ten seconds where you'd want less than 1 second? To be honest, I'm pretty sure I could easily live with such a "disaster".

I believe a "spindump" is created when an app has been force quit.

Also, here's a good explanation of what the "beachball" actually is.

http://en.wikipedia.org/wiki/Spinning_pinwheel

It's not really that much of a pain (unless working with many projects at once and switching between them) but it is hinting that something is wrong here, and that is what bothers me. Also, it does also appear when opening projects, not just quitting Logic. The reason why I was saying that it is most likely unrelated to projects is because it also happens when quitting Logic, changing the sound output, or changing preferences in Logic. (and then additionally, in the last two cases, a "initializing core audio" message appears and it takes even longer). And it happens with small projects too. This is not normal, it's a 12 core Mac Pro and everything is on an SSD.

I don't see also why it should force to quit Logic, it's just weird if you ask me.

 

PS: I edited my post above.

Did a fresh install of Yosemite. (last time was only an update)

 

I downloaded it again, made a bootable USB flash drive with createinstallmedia, downloaded Logic again, downloaded the content again that you need to download in order to start Logic – problem still here.

 

Maybe it's installing OS X from the Internet vs. installing with a flash drive that makes the difference. I simply do not understand where this issue comes from. Does anyone else have this at all? Perhaps it's even normal… or does Logic quit instantly for you? I can't even say if it's a hardware or software problem. Or a compatibility problem. I could install an older version of OS X but I couldn't install an older version of Logic Pro X, that's what sucks. Or is there a way? It will always download the latest version as far as I know (from the App Store). And I don't own Logic 9 anymore. What a frustrating story.

 

PS: In the Logic preferences, when I deactivate the core audio, Logic gets the same "spin lite" problem (short spinning beach ball) report in the console. When reactivating it, however, it happens instantly and Logic doesn't freeze.

Hey Revs, I might have some info that may or may not help you...

 

I recently installed a 250gb SSD into my 2009 17'' MacbookPro running OSX Yellowstone. I mean Yosemite.

It replaced my 500gb HDD, which I put into the Optical drive area.

 

When I started using Logic, I noticed that my system would overload pretty frequently when running on the SSD.

When I moved the project file to my HDD, and loaded the project file from there, I didn't run into any issues.

It runs just like it did before.. which is sort of a shame considered I desired an "Upgrade" But it still runs well!

 

My point is, try a different hard-drive. See if you have any issues running it from there. Have a good one man!

Hey Revs, I might have some info that may or may not help you...

 

I recently installed a 250gb SSD into my 2009 17'' MacbookPro running OSX Yellowstone. I mean Yosemite.

It replaced my 500gb HDD, which I put into the Optical drive area.

 

When I started using Logic, I noticed that my system would overload pretty frequently when running on the SSD.

When I moved the project file to my HDD, and loaded the project file from there, I didn't run into any issues.

It runs just like it did before.. which is sort of a shame considered I desired an "Upgrade" But it still runs well!

 

My point is, try a different hard-drive. See if you have any issues running it from there. Have a good one man!

 

Exaclty, try that other hard drive you have with nothing on it.

 

That way you can test if the issue is the SSD.

Thanks guys, I've actually already done this before after someone suggested it (page 1 me thinks) So sadly, it is not the SSD I guess. Which means the title of the thread is wrong too now

I could install an older version of OS X but I couldn't install an older version of Logic Pro X, that's what sucks. Or is there a way?

 

Have you ever done a Time Machine backup?

 

If you have Logic 10.0.7 somewhere, you can just drag that app over and use it with Mountain Lion for example.

I just tried it, and the problem is still present, but I didn't try it on Mavericks or Mountain Lion. I just dragged it to my Yosemite desktop.

 

I think this is a compatibility problem between the version of Logic, the version of OS X and my hardware. They don't test every Mac for that I believe.

 

We'll see if it's present on an older OS X then. But I tried a version of Logic Pro 9 (I think) on my eMac, it does the same thing there. But well, that's one very old Mac. I was just curious. I believe it does it for other reasons than my Mac Pro.

 

I'm pretty sure it didn't do this on my iMac (2011) last year.