Apple Logic Pro /LogicExpress Discussion group photo

Yahoo Groups archive

Apple Logic Pro /LogicExpress Discussion

Index last updated: 2026-04-28 23:06 UTC

Thread

LOG7 - System Performance window help

LOG7 - System Performance window help

2005-03-01 by Todd Gys

I'm running L7 on a G4 dual 500 with 640mb RAM.

I was maxing out my CPU last night and opened up that system
performance window within Logic. In it, there are two levels for CPU
load and 2 levels for HD I/O. When my CPU was maxing out, I noticed
that only the left level for the CPU area was "clipping"...the other
one was at a very low level. Do those 2 levels for the CPU represent
each of my G4 processors? If so, is there a way I can balance the
load between the two?

I assumed that L7 would recognize dual processors and make use of
them automatically...is there something I need to set up to make this
happen? The only thing I had running in my session was a single
Sculpture synth running a preset. I know my mac isn't top of the
line, but it seems like it should be able to handle at least that!

Thanks for your help.

gys

Re: [Logic_Cafe] LOG7 - System Performance window help

2005-03-01 by GAmoore@aol.com

I was maxing out my CPU last night and opened up that system
performance window within Logic. In it, there are two levels for CPU
load and 2 levels for HD I/O. When my CPU was maxing out, I noticed
that only the left level for the CPU area was "clipping"...the other
one was at a very low level. Do those 2 levels for the CPU represent
each of my G4 processors? If so, is there a way I can balance the
load between the two?


I have a dual processor G5 and the performance meter only shows one meter for CPU, the other is for hard disk access. That would be a good idea though - perhaps suggest it to apple.

The only thing I had running in my session was a single
Sculpture synth running a preset.



Sculpture is a CPU hog so its not surprising. And its almost surely being used on a single processor. Maybe if you opened two plugs they would distribute.

I think you are in a similar situation to where I was at with my G4/1.2 - you can use logic 7, and by using the freeze function, bouncing to audio, offline bouncing, you can get it to work - however it seems to be pressing the system hard - and its not that stable of a system (either X or Logic itself) and so it will break - that is crash. I think the answer is to get a dual g5 - and thats why i forked over the cash.

In the meantime, I think you should get your sculpture track fixed then bounce it rather than freeze it. Then disable the plug and use the bounced audio. That will then come purely from the hard disk and free up your cpu(s) to do more work.

Re: [Logic_Cafe] LOG7 - System Performance window help

2005-03-01 by Howard Lipp

What I  found in Logic
is when I run a processor heavy track the left load indicator jumps up
if i stop and restart it goes down.
Freezing tracks eliminates the load.
I believe the multiprocessing algorithm is handled by the operating system not by logic.
It's one of those many things that hasn't been addressed in ver 7!
H-
Show quoted textHide quoted text
----- Original Message ----- 
From: 
To: Logic_Cafe@yahoogroups.com
Sent: 3/1/2005 10:51:14 AM 
Subject: Re: [Logic_Cafe] LOG7 - System Performance window help


I was maxing out my CPU last night and opened up that system
performance window within Logic. In it, there are two levels for CPU
load and 2 levels for HD I/O. When my CPU was maxing out, I noticed
that only the left level for the CPU area was "clipping"...the other
one was at a very low level. Do those 2 levels for the CPU represent
each of my G4 processors? If so, is there a way I can balance the
load between the two?



I have a dual processor G5 and the performance meter only shows one meter for CPU, the other is for hard disk access. That would be a good idea though - perhaps suggest it to apple.


The only thing I had running in my session was a single
Sculpture synth running a preset. 




Sculpture is a CPU hog so its not surprising. And its almost surely being used on a single processor. Maybe if you opened two plugs they would distribute.

I think you are in a similar situation to where I was at with my G4/1.2 - you can use logic 7, and by using the freeze function, bouncing to audio, offline bouncing, you can get it to work - however it seems to be pressing the system hard - and its not that stable of a system (either X or Logic itself) and so it will break - that is crash. I think the answer is to get a dual g5 - and thats why i forked over the cash.

In the meantime, I think you should get your sculpture track fixed then bounce it rather than freeze it. Then disable the plug and use the bounced audio. That will then come purely from the hard disk and free up your cpu(s) to do more work.


Yahoo! Groups Sponsor
ADVERTISEMENT






Yahoo! Groups Links

To visit your group on the web, go to:
http://groups.yahoo.com/group/Logic_Cafe/
  
To unsubscribe from this group, send an email to:
Logic_Cafe-unsubscribe@yahoogroups.com
  
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Re: [Logic_Cafe] LOG7 - System Performance window help

2005-03-01 by GAmoore@aol.com


In a message dated 3/1/05 1:57:42 PM, digitalwizzard@... writes:

I believe the multiprocessing algorithm is handled by the operating system not by logic.


There are different types of multi-processing. I think that Photoshop might actually take a task and split evenly among the processors. But what little I know of Logic's implementation, they split major tasks to separate processors - e.g. OS X and midi on one, audio on the other.

I always wondered why they had to have symetrical multiprocessors. Why not use a G4/1.4 for the OS, and a G5 for Audio and soft synths.

Re: [Logic_Cafe] LOG7 - System Performance window help

2005-03-02 by Howard Lipp

they have to match because the hardware on board for the G4 and G5 is clocked and timed differently
that would actually slow the machine down
memory access is different
refresh happens at different times
lots of other hardware reasons why it couldn't happen
dual CPU motherboards still share memory and CPU clocks or things couldn't happen in synchronicity


its not that there are different types of multi-processing
think about the fact that photoshop doesn't have to happen in real time
it's done when it's done and you get the result when it's done
with audio eventually everything has to be sent to the d/a in time for real time uninterrupted
audio to result so timing is critical.


H-
Show quoted textHide quoted text
----- Original Message ----- 
From: 
To: Logic_Cafe@yahoogroups.com
Sent: 3/1/2005 3:27:28 PM 
Subject: Re: [Logic_Cafe] LOG7 - System Performance window help



In a message dated 3/1/05 1:57:42 PM, digitalwizzard@... writes:


I believe the multiprocessing algorithm is handled by the operating system not by logic.



There are different types of multi-processing. I think that Photoshop might actually take a task and split evenly among the processors. But what little I know of Logic's implementation, they split major tasks to separate processors - e.g. OS X and midi on one, audio on the other. 

I always wondered why they had to have symetrical multiprocessors. Why not use a G4/1.4 for the OS, and a G5 for Audio and soft synths.


Yahoo! Groups Sponsor
ADVERTISEMENT






Yahoo! Groups Links

To visit your group on the web, go to:
http://groups.yahoo.com/group/Logic_Cafe/
  
To unsubscribe from this group, send an email to:
Logic_Cafe-unsubscribe@yahoogroups.com
  
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Re: [Logic_Cafe] LOG7 - System Performance window help

2005-03-02 by GAmoore@aol.com

they have to match because the hardware on board for the G4 and G5 is clocked and timed differently
 that would actually slow the machine down memory access is different

Imagine a G4 at 1 ghz and a G5 at 2 ghz, and system buss at 1 ghz. I am sure that could be synced. And if it saved me $500 with virtually no performance hit, I think it would be something I would be buying.

 its not that there are different types of multi-processing

Imagine two cooks trying to cook a meal together. One guy could cut 6 onions,
while the 2nd one rinses blueberries. Or else they could both cut 3 onions each, and
then both rinse blueberries.

I think photoshop "cuts three onions each"... it takes a big job, then divides it and each processor
does a different part. I think Logic "cuts 6 onions while the other rinses blueberries" - at least this
is the way it was implemented when dual processor macs first came out. One side was for OS and
"rock solid" midi and the other for audio.


 think about the fact that photoshop doesn't have to happen in real time
 it's done when it's done and you get the result when it's done
 with audio eventually everything has to be sent to the d/a in time for real time uninterrupted
 audio to result so timing is critical.


Since you can access dozens of tracks at once, the audio doesn't seem to be too much of a strain.

I read on the Garritan site somewhere that to get it to use both processors you need to instaniate
at least two instances of the Kontact player - which seems to indicate that separate tracks may be
handled by separate processors.

And perhaps the "node" deal is taking this one step further - the other nodes are other processors - but they are tasked with clearly separate tasks.


Re: [Logic_Cafe] LOG7 - System Performance window help

2005-03-02 by Dave Shirk

Logic has no control over what processor does what under OSX!
It is all decided by the OS.

Dave S
Show quoted textHide quoted text
On Mar 2, 2005, at 2:50 AM, GAmoore@... wrote:

>
>  I think photoshop "cuts three onions each"... it takes a big job, 
> then divides it and each processor
>  does a different part. I think Logic "cuts 6 onions while the other 
> rinses blueberries" - at least this
>  is the way it was implemented when dual processor macs first came 
> out. One side was for OS and
>  "rock solid" midi and the other for audio.
>
>
>

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.