[sc-users] Re: Background server processing

[Item State <itemstatechanged@xxxxxxxx>]

how should that work? on the server, everything runs
in realtime, so there's no "priority" (except for
asynchronous commands like /b_read), every synth has
to calculate 44100 or so samples per second, otherwise
you'd get glitches. i'm not sure if you can assign
priorities to threads on the language (client) side.

you could monitor the CPU load by looking at
aServer.avgCPU and "stutter" background synths if you
need CPU. by stutter i mean you could pause them in
intervals when CPU is needed for more "audible"
synths.

you could try to run a second server in NRT
(non-realtime) mode for processing stuff in the
background ...

best, -sciss-


--- sc-users-request@xxxxxxxxxxxxxxx wrote:
> Message: 11
> Date: Fri, 3 Mar 2006 13:02:12 +0100
> From: Andrzej Kopec <akopec@xxxxxxxxxxxxx>
> Subject: [sc-users] Background server processing
> To: SuperCollider users mailing list
> <sc-users@xxxxxxxxxxxxxxx>
> Message-ID:
> <17416.12356.513235.246179@xxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=us-ascii
> 
> Hi,
> Is there any possibility to run some processes
> (synths) on server with lowered priority,
> eg. for processing recorded buffers during
> performace (so that sound is generated by other
> synths).
> 
> Any ideas/hints?
> 
> TiA
> /ak/



		
____________________________________________________ 
Do you Yahoo!? 
Never miss an Instant Message - Yahoo! Messenger for SMS
http://au.mobile.yahoo.com/mweb/index.html