Apple Logic Pro /LogicExpress Discussion group photo

Yahoo Groups archive

Apple Logic Pro /LogicExpress Discussion

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

Message

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.


Attachments

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.