This is what I've ended up doing too (tabplay~ and tabwrite~ with bangs for each) - I think maybe the devs will add the voltage control to tabwrite~ in the distant future. Maybe a tabwrite4~ if possible?
Thanks again for your help.
Kevin
On 12/27/06, Peter Plessas <plessas@mur.at> wrote:
Hi Kevin,
Aha, in my looper, i used tabwrite~ and tabplay~, triggered by messages.
This works fine, but doesn't allow for speed changes. I also do not
reverse the read/write direction when i want backwards sound, but i
reverse the table content with vasp.
sorry for the confusion.
cheers, P
Kevin McCoy wrote:
>>
>> So you would have to write into an array cyclically (phasor~ is your
>> friend here), and read at the same position, feeding back the audio
>> signal from the tabread to tabwrite, thus creating a loop.
>
>
> Order forcing is giving me headaches right now but that's OK - but what
> I am
> wondering is: is there a way to *write* cyclically to an array based on a
> signal input? This would save me a lot of trouble here syncing/dividing
> [metro]s and messages, which is really complicating the
> overdub/play/stop/start process. I wish it could just be driven by a
> [phasor~] - is this possible somehow?
>
> [snapshot~] is impractical here unless I can get it to sync on the sample
> level.
>
> Kevin
>
--
"[D]aily life [is] a theatrical landscape in which 'everyone has their price,' God (via televangelism) and happiness (smile buttons) become commodities, radio stations say they love you, and detergents have compassion for your hands.