Apple Logic Pro /LogicExpress Discussion

> 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.

It's not as simple as synchronising clock frequencies. Making both a G4
and G5 work efficiently on the same motherboard would require such a
complicated design (in the hardware and in OSX) that it would probably
be more expensive than a dual G5.

> 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.

Logic cannot tell OSX what processor to use. Especially since
OSX already has a dozen tasks runnning before you can even start Logic
and you can be sure they'll be spread across both processors.

How multiprocessing generally works (I don't know the specific's in
Logic's case) is that in a multithreaded application, threads can be
spread across two processors. It's likely that every plugin in Logic has
it's own thread and so it can easily spread the plugins over the two
processors (which would be much more efficient than the entire OS and
MIDI, both of which use hardly any power at all, on one processor and
the audio engine, using almost all required power, on the other). This
does mean that if you use only one really heavy plugin, you'll see more
load on one processor than the other. A single thread cannot be spread
over two processors.

Maurits.