hi Thomas,
- (yet another workaround:) -- with a combination of oversampled
[switch~] and a [bang~] you may set the (logical) speed of dsp processing in a window. This speed may be up to 8192 times the realtime (or more, if [switch~] is dynamically created) -- I think this is sufficient in most cases... test the attachment.
- This reminds me of my old (and rather modest?) proposal for using
Pd in batch processing of sounds stored on disk. The needed changes are: minor editing of Pd's scheduler, and an addition of a startup option.
- ``Filling large arrays with audio data'' is one of the aims of
my vexing library. I can send you the sources, if you wish.
Krzysztof
Thomas Grill wrote: ...
is there any means (or will there be a possibility in the future) to steer a part of a signal network (e.g. a subpatcher) in a way that it doesn't run in real-time but rather uses the full cpu power available? This would be good for filling large arrays with audio data.
#N canvas 168 255 505 276 12; #N canvas 0 0 450 300 graph1 0; #X array t 524288 float 0; #X coords 0 1 524287 -1 200 140 1; #X restore 269 51 graph; #X obj 61 227 tabwrite~ t; #X obj 21 21 bang~; #X obj 21 131 switch~ 524288 1 8192; #X msg 95 56 1; #X msg 21 92 0; #X obj 21 56 t b b; #X obj 24 174 noise~; #X obj 95 21 loadbang; #X connect 2 0 6 0; #X connect 4 0 3 0; #X connect 5 0 3 0; #X connect 6 0 5 0; #X connect 6 1 1 0; #X connect 7 0 1 0; #X connect 8 0 4 0;