sorry, i cannot catch what your problem is the outlet~ of the 256-window produces a stream. one 256-sample vector covers 5,8 ms (at 44,1 kHz). and the 64-window gets that stream and handles it in 4 parts (each 64 samples, each 1.45 ms). there is no loop at all. in each (block)window there is a kind of "trigger-point" until then all calculations of a vector have to be done. and at that point the result is copied to what ever (eg. the soundcard). in a 64 block this is done all 1,45 ms (depending on the samplerate). a larger blocksize has less of those "trigger-points" and does calculations on larger data. - at least thatŽs how I understand the whole thing. sme.
----- Original Message ----- From: "J. Scott Hildebrand" jshildebrand@ucdavis.edu To: "marius schebella" marius.schebella@chello.at Sent: Friday, August 30, 2002 1:09 AM Subject: Re: [PD] outputting samples
ok i see what you're saying, but this is only converting blocksizes. would it just take 64 samples and send that, and then send the next 64 a couple more times? how do the samples actually get to the soundcard?
scottOn Fri, 30 Aug 2002, marius schebella wrote:
do this: have the block~ 256 in a subpatch and in this subpatch there
should
be a outlet~ object to which you can connect the signal-stream. the
outlet
on the objectbox of your subpatch should then have a connection to a
dac~
object. (the parent patch has the (default) 64-sample-vector-size).
outlet~s
and inlet~s is the best way of converting between different blocksizes. sme.
i now know that the output array is hardcoded to 64
blocksize. if
i
have an array of 256 inside my perform function, how do i create a
loop to
output the whole thing? i guess a better question would be; is the
output
finally sent to the soundcard when there is a whole pass through
the
entire external, or when leaving the perform function? thanks!
"640K ought to be enough for anybody." -- Bill Gates, 1981
-
marius schebella