Is it my Mac or Logic X or something else?

Hi,

having some issues with Logic X at the moment, I keep getting the "system overload" message all the time & my CPU meters are spiking, having no issues with the HD meters though.

Even right now I'm working on a beat which currently has 8 tracks open (couple loaded with Nexus 2 and the rest is Logic plugins) but even on this small project I'm getting the overload message!

It is really becoming quite annoying... literally every 20-30 seconds BAM "System Overload"

I have nothing else running in the background - Just using Logic X

I have also tried everything - Freezing tracks (works a little bit) however i hear certain guys are running way more than 8 tracks on Logic X and still running smoothly

I have also messed with the buffer settings and still nothing helps.

I literally don't know what to do next

Current Set Up: (in case its needed)

iMac: late 2009 model

OSX Version: 10.9.3

Processor: 2.66 GHz Intel Core i5

Memory: 16GB 1067 MHz DDR3

M-Audio Profire 610

Have I missed anything?

Has or Is anyone having this problem? How did you solve it?

Thanks

Are you running everything off your one internal hard drive?

If so that could be your problem right there. Running the Os, Logic, and reading and writing to the same internal hard drive is very taxing on a system. Especially the stock hard drives that come in an IMac. Try moving at least your recording folder and samples to an external hard drive.

Also, are you sure that you third party plugins are up to date?

Logic comes with a fairly taxing demo called "The Numbers Game". If you don't have it you can download it from your logic menu, install additional content. Run that off your internal hard drive and see what you get. If it works fine and plays then you know it's a 3rd party problem.

Wayne

Have you tried raising your audio buffer?

yeah i have... still no luck

Are you running everything off your one internal hard drive?

 

If so that could be your problem right there. Running the Os, Logic, and reading and writing to the same internal hard drive is very taxing on a system. Especially the stock hard drives that come in an IMac. Try moving at least your recording folder and samples to an external hard drive.

Wayne

I was thinking this Wayne BUT (and correct me if I'm wrong please) if this was the issue wouldn't my HD meter be spiking and not the CPU meter?

All my plugins are up to date too. hmmm.

UPDATE OF TONIGHTS ACTIVITY

Been in the studio since 8pm - uk time (not that it matters) everything was working fine, made a new song and also touched up some other projects... the time now is 10:30pm and Logic CPU meter is now spiking again.

I close all projects (nothing else running in the background either) and open a new empty project, I load up 1 plugin, yep just 1 and its spiking already.

INFACT: As i type this right now Logic is idle.... no sounds being played and nothing being recorded its just sitting there, however the CPU meter is still by itself spiking...

I have no idea what is going on at all.

very strange activity

Sounds like something is up.

Have you tried a computer restart?

Sounds like something is up.

Have you tried a computer restart?

I have just done that now... Logic seemed ok for about 1 minute and now spiking again.

could it be Maverick OS?

http://i61.tinypic.com/2607n84.png

Could be the M-Audio driver that is causing this issue.

What happens if you choose Preferences > Audio > Devices and change the In and Output to the built in interface instead?

Click this link to your signature and add your system information:

• Logic version and sub-version (e.g. Logic 10.0.7)

• OS X version and sub-version (e.g. OS 10.9.4)

• Computer (e.g. MacBook, Mac Pro, iMac)

• Processor (e.g. 2.2 GHz Intel i7)

• Memory (e.g. 8GB)

• Audio interface manufacturer and model (e.g. RME Babyface)

(most of that information can be found by choosing Logic Pro X > About Logic Pro X, and  > About This Mac)

Could be the M-Audio driver that is causing this issue.

What happens if you choose Preferences > Audio > Devices and change the In and Output to the built in interface instead?

The same thing happens.. CPU spikes. I have downloaded and properly installed the latest update for my M-Audio too.

Click this link to your signature and add your system information:

• Logic version and sub-version (e.g. Logic 10.0.7)

• OS X version and sub-version (e.g. OS 10.9.4)

• Computer (e.g. MacBook, Mac Pro, iMac)

• Processor (e.g. 2.2 GHz Intel i7)

• Memory (e.g. 8GB)

• Audio interface manufacturer and model (e.g. RME Babyface)

 

(most of that information can be found by choosing Logic Pro X > About Logic Pro X, and  > About This Mac)

done.

NOTE

In the time it has taken me to fill out my signature and reply to you it is no longer spiking... everything is running smoothly again. I know it will happen again in due time.

its just very odd that it does this.

For your information: The Profire 610 driver is not officially supporting Mavericks.

PROFIRE 610 with thunderbolt adapter on OS X 10.9.3

For your information: The Profire 610 driver is not officially supporting Mavericks.

PROFIRE 610 with thunderbolt adapter on OS X 10.9.3

looks like M-Audio have done me nicely. lol. Thanks for this info.

but that wouldn't make the internal In/Out spike though would it?

No, it would not.

What happens if you change to the built in interface, close Logic and then restart?

Thanks for updating your signature.

No, it would not.

What happens if you change to the built in interface, close Logic and then restart?

 

Thanks for updating your signature.

no problem.

ok I'm going to do everything you just suggested... I will then sit down and play with Logic for few hours and see what happens.

will keep you updated.

thanks again.

TEST ONE UPDATE:

I unplugged my M-Audio interface and switched on my mac.

set audio In/Out to the internal system, opened Logic and had it running for 3-4 hours without one single spike. All seemed to work smoothly and well.

so at this stage I'm guessing it was my M-Audio Profire610 interface causing the problems.

Just to be 100% sure I will run a couple more tests in the next few days and see what results I get.

Will update this thread with the info.

Thanks for the update.

At this stage it really seems that you should be looking for an alternative to the M-Audio.

Thanks for the update.

At this stage it really seems that you should be looking for an alternative to the M-Audio.

I would agree.

However i done some more tests tonight... so same as before M-Audio unplugged, switch on Mac, open Logic & make music.

Again as last night Logic running fine for few hours and then suddenly I'm starting to get CPU spiking again. http://i58.tinypic.com/1zlyobc.png

I really thought it was the M-Audio interface but from tonights test it seems it may be something else, although I have to admit the matter is extremely worse when the M-Audio is in use. (so will defo look at replacing it)

BUT I'm still confused as to why this is still happening even with my interface unplugged. Hmmm

Eric - you have been very helpful so far, Thank you.

Do you have any other suggestions?

or is anybody else experiencing such problems or have any suggestions?

I am experiencing more spikes than usual under the latest combination of OSX and LPX. At first, I thought it was only the new STank3 causing it, but now I am not so sure. I have a 'CPU saver' track, which is an audio track with no designated input and turned off, but that doesn't help when trying to play an actual software instrument. Logic 10.0.6 seems to not do this as often.

YMMV.

Eric - you have been very helpful so far, Thank you.

 

Do you have any other suggestions?

 

or is anybody else experiencing such problems or have any suggestions?

You're welcome MB.

What kind of 3rd party instruments do you use?

Does quitting Logic and reopening it again fix it for a longer period?

Eric - you have been very helpful so far, Thank you.

 

Do you have any other suggestions?

 

or is anybody else experiencing such problems or have any suggestions?

 

You're welcome MB.

 

What kind of 3rd party instruments do you use?

Does quitting Logic and reopening it again fix it for a longer period?

I only ever use Nexus 2 and the stock Logic plugins.

I have quit an re opened Logic and the problem still occurs.

I am experiencing more spikes than usual under the latest combination of OSX and LPX. At first, I thought it was only the new STank3 causing it, but now I am not so sure. I have a 'CPU saver' track, which is an audio track with no designated input and turned off, but that doesn't help when trying to play an actual software instrument. Logic 10.0.6 seems to not do this as often.

 

YMMV.

I have no idea what is going on with this Logic X - some very weird behaviour.

Now the dreadful question:

Same behavior without Nexus?

Now the dreadful question:

 

Same behavior without Nexus?

Hi Triplets,

I ran Logic X tonight without using Nexus to see what would happen and the same thing happens.. Logic X CPU spikes and I'm getting "System Overload" message.

very strange... as of tonight I've also been getting another message pop up... its something like "sample rate 44278 conflict" or something like that, can't remember exactly but it has popped up a couple times tonight along with the "System Overload" message

I'm starting to think that maybe it could be Maverick.. I'm just not sure.

The sample rate conflict is an issue with the interface.

thanks Triplets - maybe i do still need to look into buying a new interface.

still confused about my main issue though.

Mmm, M-Audio interface and Mavericks... Loads of my customers have problems with Mavericks and their older M-Audio interfaces. There is no official driver for your 610 and 10.9...

Blink

Mmm, M-Audio interface and Mavericks... Loads of my customers have problems with Mavericks and their older M-Audio interfaces. There is no official driver for your 610 and 10.9...

 

Blink

Yes...

For your information: The Profire 610 driver is not officially supporting Mavericks.

PROFIRE 610 with thunderbolt adapter on OS X 10.9.3