is it a feature that the dual g5 mac uses only once processor when bouncing audio to disc? or is there a way to make it use both, which would be nice. (logic 7.2.0) any thoughts?

--- In logic-users@yahoogroups.com, "max Richter" <forums@...> wrote: > > Message posted by max Richter <max.richter@...>: > > is it a feature that the dual g5 mac uses only once processor when bouncing > audio to disc? or is there a way to make it use both, which would be nice. > > (logic 7.2.0) > > any thoughts? I'm not sure that it really is using only one. My impression (from memory only) was that during an offline bounce, the indicator just maxes out in a way that's meant to indicate it's not actually indicating to you at the present time :) I could be wrong but that's the impression I got the first time I ever did it, and I'd never thought about it again since til you mentioned it.

> I'm not sure that it really is using only one. My impression (from > memory only) was that > during an offline bounce, the indicator just maxes out in a way > that's meant to indicate it's > not actually indicating to you at the present time :) I could be > wrong but that's the impression > I got the first time I ever did it, and I'd never thought about it > again since til you mentioned > it. That's not completely true, though it's very possible that the fact that only one meter registers the load is a bug. :o) But apart from that, the maxing out you see is accurate. In realtime, the core audio system has to process a sample in the time it takes to play a sample. If it finishes the processing before the time runs out, it can wait for the next sample. The amount of time the processor spends waiting, is the measure for the processor load. (This is a slightly simplified story since it really works in buffers but for the sake of the argument it'll do). :o) In an offline bounce, the processor processes each next sample as soon as it's finished with the previous one. This means a constant load of 100%, as far as that means anything. But the cpu meter registers correctly that there is no wait time left. What you also may have noticed is that the cpu (-and other) meters update extremely slowly. That is because they are only updated when the processor has nothing else to do, and in an offline bounce this is only when a block of data is written out to disc (because the disc dma takes care of that on its own but the processor does have to wait for it to finish). (So actually the load is _almost_ 100%). :o) So you only see everything getting updated when a block of audio data is being read or written. This does make the meters pretty useless during an offline bounce, the only reason they work is because the same routines are used for online and offline bouncing and it would only mean extra programming to not make them work. But as for the original question.. no idea. It could be that the second meter just doesn't get updated, or that the distribution amongst the cpu's is based on timing algorythms that have no meaning during an offline bounce. Maurits.