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.
.mmb
volker böhm wrote:
thanks for your suggestions, guys.
sorry, if i wasn't clear, but i'm not looking for (cross)fades.
i'd like to perform circular recording into an array, constantly
overwriting what has been recorded before.
so if you put the playhead a little behind (or before - as it's
circular it depends on your view) you get a simple delay.
as the trigger to start recording with tabwrite~ is not sample
accurate, i can't get a constant recording without clicks at the
trigger points - at least not with my limited understanding of pd.
but i think i've just found a solution using poke~ (which seems to be
the same as in max).
thanks,
volker.
On 18.01.2010, at 11:46, João Pais wrote:
how do you read the array? just fast, I'm thinking of adding a fade
in + fade out. you can put it either before the recording, or after
reading it. just depends where it's easier to detect the array's
writing/reading point going from xxx to 0.
I don't know if Grill's xsample library can help you, I don't know it
myself - http://puredata.info/Members/thomas (not included in Pd-ext).
João
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
