Yes, I've seen this "flip-flop"-ing happening on winXP too. And I
*think* (not know) the flipflopping of Csound processing from one core
to another will have an impact on realtime performance, creating the
possibility for a dropout during the switchover time.

Oeyvind


2008/3/8, Anthony Kozar <mailing-lists-1001@anthonykozar.net>:
> This probably means nothing for WinXP with Intel Dual Core, but my Dual G4
> PPC Mac running OS X 10.2 does an excellent job of balancing tasks between
> processors.  When I run Csound with top running in another terminal, I can
> clearly see Csound using nearly 100% of one processor while the other
> processor runs the GUI ("TrueBlueEnv" I think it is called).  (I don't think
> Csound always stays on the SAME processor -- the tasks sometimes flip-flop,
> I believe).
>
> Anthony
>
> Oeyvind Brandtsegg wrote on 3/8/08 10:02 AM:
>
> > The thing Michael states about getting a "clean" core for Csound, one
> > that does not have to deal with OS, graphics and housekeeping is very
> > much valid. But this does not happen automatically (at least not on
> > winXP).
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>