Logic Pro 9 Logic 9 Core Load Distribution Problem

R

redember

Logician
Hi i am getting core overload on one out of 8 cores because of an instance of Kontakt4 (with multiprocessor support switched on at 7 cores) running Abbey Road Drums in Logic 9. (at the suggestion of apple help pages --> even when i tried to distribute the effects plugins (including waves CLA) to bus channels the load is visibly all still stacked onto the same core that is carrying the kontakt channel load.
hence getting overload messages/stops on what is a very simple track compared to others i've done.

i tried switching to 256k buffer - no effect. switched Kontakt multiprocessor support to different values - no effect i'm wondering what is the point of that is then🙁

can anyone suggest anything?


3.2ghx mac quad with 8gb ram 10.6.4osx, logic 9.1.3
 
Sort by date Sort by votes
Try opening the buffer out further til the problem stops. Also, dont leave that track highlighted during playback, click on some low grade audio track with no plugs...
I also find when the CPU craps out that stopping, hitting return a couple of times and selecting another track kinda clears it sometimes. HTH
 
Upvote 0
FYI the multiprocessor setting in Kontakt is for when it is being used as a stand alone, not as a plug-in.

As for Kontakt causing one core to overload with Abbey Road Drums on it, especially with a 3.2 GHz cpu, it isn't that causing the overload, it has got to be something else. You are correct in thinking it's a single core being used.

Try this:

Make a new audio track, don't put anything on it, and set it to record. then look at your CPU meter. It should be lower, because that track is now set to live input, not your Kontakt track.

How are things when you try this?
 
Upvote 0
One thing that is a killer is having several live inputs on at the time so make sure that your Kontakt channel is the only live input channel on.
 
Upvote 0
thanks so much for the feedback <was taken ill, hence my late reply>
a few of those tricks i know but some i am implementing like the buffer which ive never touched! i have resorted to freezing other tracks which is working to an extent. i agree that this shouldn't be happening with the speed on the computer. i've tried to repeat the issue with another fresh track and no problems so i'm thinking its a 'bug' in this specific project/one of those weird combinations of loaded plugins that don't like each other 🙂 Cheers
 
Upvote 0
Have the same problem (which is what led me to this forum in the first place).

The inability to control what is going on with the cores or even to understand why everything is inexplicably camped on to one core is incredibly annoying.

I have tracked some of this down to bugs in virtual instruments. On other occasions, nothing seems to help or shed any light on why some cores are over-utilized and others are left absolutely alone.

I have resorted to dumping tracks to audio just to get through a project. Not cool.

Apple? Help?
 
Upvote 0
yeah frustrating in its randomness. an obvious thing maybe.... but as well as freezing.... i am disabling the plug in that is causing the spike whilst i work and then re-enabling for the final bounce (offline mode).
 
Upvote 0
Did you look in Activity monitor how is your load ?
Logic can display wrong load !!

Solution 1 :

Use Standalone Kontakt with IAC
For rooting the sound back to Logic either do it with your hardware or you have software to do it (I cannot remember it's name)

Solution 2 ;
Some user have been putting K4 into VE pro (but I have not tried this)

Solution 3 :
Get a 12 core 2.93 ghz 24 GB like I did

best

Cyril
 
Upvote 0
I have notice core audio overload with no load on logic (2 proc with 3 bars) just adjusting the 5.1 general output while it is playing about 25 midi tracks to VSL VE PRO server
 
Upvote 0
I had a load of CPU load distribution issues when working with my template (I have a default template which I load before every session). The symptoms were that one core would be spiking or at best seeing heavy use, whilst the remaining 11 would be practically dormant.

The template is big (many hundreds of tracks) and uses a lot of VI's - lots of Kontakt 4 and VE Pro instances, drawing audio from multiple network systems as well as the host. However, the spikes were happening even when the session was pretty much empty.

About 4 weeks ago I totally rebuilt my template from scratch. Same track and instrument configuration etc., but just rebuilt using the latest build of Logic. The first thing I noticed was that as soon as I fired it up, the CPU activity monitor showed low and evenly spread usage across ALL cores. It was like winning the lottery - all of a sudden Logic is using all my system's resources evenly and properly. Sure I sometimes still get spikes on one core as projects evolve, but these are due to genuine overloads caused by lots of plugins on a specific track etc. and can easily be worked around or avoided.

I guess the implication is that Logic is constantly evolving as a platform, and in my case taking a song through multiple iterations of the software was not good for it - somewhere down the line, Logic lost the ability to manage resource distribution correctly.

Maybe your session needs to be rebuild, environment imported (if not in whole then perhaps in part) or rebuilt, MIDI files re-imported etc. using a fresh song, and that will most likely fix any corruption in your existing session.

Don't know if this helps at all.

Jules
 
Upvote 0
Trailerman said:
The template is big (many hundreds of tracks) and uses a lot of VI's - lots of Kontakt 4 and VE Pro instances, drawing audio from multiple network systems as well as the host. However, the spikes were happening even when the session was pretty much empty.

Jules
Click to expand...

Hello Jules

It is not a good idea to have VI into Logic;
It is better to have a VE pro server with a few VE
Best

Cyril
 
Upvote 0
Cyril

I use VE Pro Servers for the bulk of my instruments, but some I need/choose to host in Logic. Works fine here.

The point that's relevant to this thread is that a large template can run fine in Logic and avoid single-core spikes, as long as it's constructed properly, and ideally using the most recent Logic build.

Jules
 
Upvote 0
Trailerman said:
Cyril


The point that's relevant to this thread is that a large template can run fine in Logic and avoid single-core spikes, as long as it's constructed properly, and ideally using the most recent Logic build.

Jules
Click to expand...
Hello Jules

Great to know that you are using VE PRO SERVER, do you use Vienna Suite or do you do your correction in Logic

My Logic song that is used for template is about 5 year old 😀

This Dolby 5.1 song connect to 8 xVE that are containing 100 VI loaded with L2 patches
It has also 16 x K4, 2 x QL Choir and 1 omnisphere and there is hardly any load on Logic and on my Macpro 12 core 2.93 Ghz 24 GB

But I re-organize the song memory from time to time

:thmbup:

Best

Cyril
 
Upvote 0
Wow... 5 years old. I wonder how everything is working properly. I have had so many issues with Logic 7 (and even sometimes Logic 8) templates that, when a client has ghost routing issues, or bad DSP issues, making a new template is the first thing I try.

I do understand that for some it's a massive undertaking, but in the end Logic seems like a whole new app to them (in fact it is really, since all the internal wiring of Logic has been upgraded since V8).
 
Upvote 0
Couldn't agree more George. I don't doubt that Cyril knows what he is doing, but it is prudent to make anyone reading this aware that using old templates is one of the classical methods of asking for trouble.

kind regards

Mark
 
Upvote 0
Markdvc said:
Couldn't agree more George. I don't doubt that Cyril knows what he is doing, but it is prudent to make anyone reading this aware that using old templates is one of the classical methods of asking for trouble.

kind regards

Mark
Click to expand...

do you re-organize song memory from time to time ?
If you have trouble with a song ; importing it can solve most of the problems :hippy:
 
Upvote 0
It's not about reorganizing memory and importing things, it's about the fact that Apple rewrote the audio code. If you have been lucky enough to not have any problems, good for you, but I can assure you, for some people it has been a real nightmare.

I do allot of mixing, and I have received older Logic song files, loaded them, and discovered things like sends going to multiple places, and parts where I routed them to an aux, going to 2 or 3 at a time, including phantom ones.

So, in order to be 100% confident that things are up to date and working as required, rebuilding is the best way I know how to be confident everything is going to work.

As always, anyone is completely entitled to do whatever they wish, right... I do it like this, you do it like that.
 
Upvote 0
You must log in or register to reply here.
Back
Top