Hi,

Does anyone know how to turn example B.16.long-varispeed.pd into a seamless looper? Meaning, I just want to loop a long .wav file, with varispeed control, and not have it make any pops or clicks when it loops.. I have modified the patch to loop, but it always clicks at the loop point, and I made sure to check that my .wav loops seamlessly with no clicks or pops in audacity. Thanks!

Thank you for the reply. By windowing do you mean enveloping with a fade in & fade out? If so I'm trying to avoid doing that. My loops are edited so that they loop seamlessly (in a daw) without any pops or clicks and without the need of enveloping or ending/starting at the zero crossing.

I'm looking for away to sample accurately loop the file. This works fine with smaller files using Tabread4~ and Phasor~. And it works with larger files, but for the larger files you get the nasty artifacts if you just simply run your phasor into a multiplier and then into a Tabread4~. That's why i really like the B.16 Example, it gets rid of the artifacts by polling the phase. Any help in figuring out how to build a sample accurate loop component into this patch without enveloping would be much appreciated! Thanks!

@flagpuppy Hello..... I imagine that you need to reset the phase of the phasor (the message [0,01( ...) as the loop wraps.........
David.

Not sure, but maybe B15.tabread4~-onset.pd might be helpful.

Yeah I have tried to reset the phase of the phasor by sending a bang to the message 0.01. I've also tried changing that to 0.0, but I still get the click as the loop wraps. The problem is that I am monitoring the accumulated onset, since that is the only way to tell where in the array index I currently am at (that I know so far). The problem with this approach is, it isn't sample accurate. In fact, the accumulated onset is triggered every 100ms from the snapshot~ metro object. I could try to make the metro faster, but I still don't think that will work. Maybe I have to convert all of the Non-signal Logic into Signal Logic, in order to get sample accurate wrapping. But if anyone can help me figure out how to do that I would greatly appreciate it, as I'm not a pure data expert. I've also read the B15.tabread4~ onset.pd and it doesn't really help with the problem I'm trying to solve. I don't fully understand how onset is working with phasor~ signal input in B16, and how to use that to sample accurately loop the file. I think this functionality though would be super useful to PD users if we can come up with a solution. Thanks!

Hey just poking to see if anyone could help provide a solution for this, or let me know if this can't or shouldn't be done this way in PD. I haven't had any luck coming up with anything that doesn't make a pop unfortunately. Any help would be greatly appreciated. Thanks

@flagpuppy Hello........ You could certainly solve the problem like this........
B16.long-varispeed-modded.pd
although you might need to use [delay] instead of [pipe] in vanilla..........
David.

@whale-av [pipe] is Vanilla as cake! It even takes lists and symbols these days.

@whale-av Sorry I haven't had a chance to check out the patch, but I finally did and it doesn't seem to work. I load in a wave and then click .5 or .01 to start the sound, and it doesn't loop. Also I noticed you implemented a VLINE object. I am trying not to use envelopes at the beginning and end of the wave file to get rid of the pops.

Instead, my goal is to loop a wave file, of any length, seamlessly. So the wave file will be edited beforehand to loop seamlessly, and I need pure data to play that file back without artifacts, and without envelope fades. Does this make sense? I'm happy to provide a wave file for testing. I am able to do this in Max MSP or PD Extended using the Count~ Object. But I want to do this in PD Vanilla as cleanly as possible. Maybe I need to make an external?

Thanks!

If you have the time to process the sample, you could just count all the zero crossings, set the loop points you'd like to be perfectly zero instead of the +/- 1-6e they usually are, and record those indices in another array. You'd have to be sure that the four point interpolation in tabread4 doesn't mess you up though. Hadn't played with that math before.