thanks for all the replies.
and yes, something similar you posted, frank, is what i had in mind.
i couldn't remember the block-quantisation, but it makes sense now.
in G05.execution.order it says: "DSP sorting in Pd follows the
hierarchy of subpatches"
hierarchy of subpatches means top to bottom or simply outlet to inlet?
thanks,
volker.
On 19.01.2010, at 13:05, Frank Barknecht wrote:
Hallo,
Frank Barknecht hat gesagt: // Frank Barknecht wrote:
Mike Moser-Booth hat gesagt: // Mike Moser-Booth wrote:
If I'm not mistaken, I believe the trick to getting this to work
is to
make sure the array size is a multiple of the block size.
[tabwrite~]
conforms to block boundaries, to if you bang it in the middle of a
block, it won't begin writing until the end of the block. That's
probably where the clicks are coming from.
The actual size of the array doesn't matter: If you have for
example an array
of size 300, you could record and playback only the first 256
samples (4*64)
with block-quantized objects. Just ignore the last 44 samples.
Anyway, attached is a tabwrite~-based looping recorder. I use a
[bang~] based
metro to start recording there, and some DSP order forcing to make
sure, the table
is written before it is read to be able to get a delay time of zero
as well.
Ciao
--
Frank
<table-looper.pd>_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
