Sorry, I skimmed that first email too quickly.
Delaywrite~/read~ objects would definitely be a decent alternative if you want to avoid clicking sounds. It is possible to tap a delay from multiple patches, as long as it is not named with a $0 at the beginning. I would use this approach unless you for some reason would want to save the internals of the delay buffer, which seems unlikely.
~Kyle
On Mon, Jan 18, 2010 at 2:26 PM, Kyle Klipowicz kyleklip@gmail.com wrote:
It would also be possible to do this using [delay~] objects instead of arrays.
~Kyle
On Mon, Jan 18, 2010 at 10:15 AM, volker böhm vboehm@gmx.ch 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