i'm expiriencing audio sutters when i trigger audisamples at a constant rate. its like sometimes my computer is thinking to slow, but its a really easy to handle patch i'm talking about so that couldn't be the problem.
i think i'm triggering the sample the wrong way letting pd searche for it ever time it has to be triggered. but i don't know how to manage the sample triggering process otherwise(i'm just new). or maybe i should somehow make some buffers in my patch. maybe its something totally else.
i attahed the patch so you can see:
http://www.filefactory.com/file/081078/n/dram_pd
(you'll have to load your own samples to hear anything).

even this won't stay steady after a while and stutters:
http://www.filefactory.com/file/017178/n/nbtd_pd
(you'll have to load your own samples to hear anything).

(sorry for the upload sites uploading on the forum doesn't work)

Ok, here you are using readsf~ which isn't the most efficient way of doing things.
It's a problem because you have to continually reload the files before playing.

You will want to look into using arrays to store audio in.
Like in this example here. By having something in an array, it's already loaded, so your computer only needs to read the data.

Arrays become better again when you start using tabread4~ or even just in the example here, where you can specify a starting point by changing that 0 at the top to whatever sample you want to start on.(or in the case of tabread4~, speed, direction and start and stop points)

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