Okay guys!
So I am making a patch which should be able to play many files with certain random functions.
Before I used readanysf~ library to do that, but it has weird artefacts during playback at times, so I decided to try another approach and use tabplay.

Tabplay works out fine as far as playback goes, I was able to put together the patch pretty quickly. However, another problem arose - when you load files into sample players during playback, 50% of the time a click, when all audio stops momentarily, would occur. This, of course, is not what you need during a performance.

I have been pointed to this topic:
http://puredata.hurleur.com/viewtopic.php?pid=5382#p5382

I did attempt to use block~ with read and soundfiler commands, but the effect was actually worse - without a block 50% of the time I get no clicks, with block~ I get it 100% of the times, although I must admit, often the click is less noticeable.

I cannot load files in advance, because the whole point of this patch is to do spontaneous music, load samples and loops as it goes. Because I see that using readanysf~ produces no clicks whatsoever, I am sure the problem is somehow solvable, but I am not sure what to do at this point. Any advice would be welcome.

I submit the patch for your inspection.

http://www.pdpatchrepo.info/hurleur/TapeLoops_tabplay.zip

I'm afraid this won't be an easy one. You don't get clicks with readanysf~ because it streams the audio from disk. The soundfiler object reads the entire content into a table, which causes the dropout. Have you tried the readsf~ object, but I'm not sure if it has the same weird artefacts you're talking about?

Did not try readsf~ yet, should do it of course as well.

Is it possible to somehow process file load in the background? I wouldn't mind it being much slower in time but not cause disruptions in the audio stream.

What about using switch~? Might it allow to turn dsp off in looper, load file, turn it on?

can you guys help on my post its right under this one

[readsf~] just plays files from beginning to end, so it's not really going to work for random slicing. You'll have to load the file into and array or

@Maelstorm said:

[readsf~] just plays files from beginning to end, so it's not really going to work for random slicing.

you can send an offset of "sampleframes" (i think that means "samples") along
with the open message, and readsf~ will play from that position. according to the help-file, there might be up toi a few seconds delay between open and
playback start, but in my test-patch i had no audible delay.

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

Two things:

1: The "method" is basically the command you give to the object. What you want is to open the file, so you have to make your message [open <filename>(. It says "no method for '03)'" because "03)" doesn't mean anything to [readsf~]

2: Message boxes separate elements in a list by spaces, so even if you put "open" first, it's just looking for a file called "03)" and ignoring the rest. It doesn't consider it to be one long symbol, it considers it a list of symbols. There are two solutions: first is to just use files that don't have spaces. The second is to convert the space-separated list into one long symbol. You can do this with the [list2symbol] object.

[03) Nine Inch Nails - The Frail.wav(
|
[list2symbol]
|
[open $1( <-- $1 is a variable that gets replaced by the incoming symbol
|
[readsf~]

Yeah, that's what I was saying. You can't get random slicing with [readsf~]. You'll have to load it into a

@harrywood said:

ye man now i get it seems so obvious now got my patch here fully set up and working similar to the one you showed me before. dont really get how i can randomly slice it so i can get it to play at different positions in the song at the moment even when i adjust the numbers in the message box it is always starting from the beggining at every point.

the numbers are way too small. 2000 is just 0.04whatever seconds (44100 is 1 second), so hardly noticeable, especially with a complete song. i have just checked with a 13 min 32bit wav file , and it worked fine. i am not sure if i would actually want to use this for beatslicing (i think it depends much on the system), but it is definately good enough for cueing to different positions in a song. maybe it is also a os- and pd version issue: i am using 0.43.0 vanilla on ubuntu lucid.