I am having a hard time trying to figure something out.

I have a looping system i cobbled together that got its timing information from a vline~ whose value was sent to 8 loopers. this has been cool and stable but i want to time stretch the audio so i decided to swap it out for a phasor~.

It kinda sorta works. i clear the table, then i use a timer to set the loop length in ms and use that to calculate the sample size (ms/100*samplerate) and use this number to ride the phasor and read the index in tabread4~. i play something into it and it loops and i have control over the speed of the phasor~ using a slider, but its distorted and grainy and eventually fades away.

I think i've left something out but i cant figure out what. any help would be highly appreciated!

onyx

http://www.pdpatchrepo.info/hurleur/looperexperimentor.pd

your [r~ vline] receives the phasor~ signal multiplied by the loopsize...so it's going from 0 to loopsize every cycle.

BUT, then you're using [wrap~], which just wraps that signal ridiculously fast into 0 to 1 range. I have a feeling if you remove the loopsize multiplication from after the [phasor~]. you might get a better result?

thanks for the reply.

it stops working if i take that away because it uses that to index the the table, if i understand this correctly.

the part of the patch that is on the right side of th screen works really well when getting its index info from vline~ with the ms and samplesize packed and sent as a message. i will try packing the number streams into a message. maybe its a formating issue.

any further insights?

i had another look, and yeah...quite weird.

sorry, i just dislocated my elbow and have it in a brace for a few days, so can't do much patching....but it looks like there are timing issues that differ between a [phasor~] and a similar vline~ construction. In particular, it looks to me like they have some different effect on s~ / r~ pairs. if you remove those, and directly connect the phasor~ to the looper, the distortion seems to go a bit. but, for some reason, [phasor~ 1] doesn't give me the same result as [metro 1000] connected to vline~

sorry, i'm still baffled as well.

ah, cool. at least i'm not crazy. maybe the loop length isnt being calculated properly, since it is based on the ms from the timer and not the actual filesize. i did notice that the snapshot i placed after the [+ 1] object shows two different numbers when the metro bangs the beginning of the loop, but i dont know why.

thanks for checking. i will do the direct connection and play around with it some more.