hi, i am trying since a few hours to make my audiofilplayer working. but my patch plays my loaded audiosample only once. it seems, the datas are after playing not present anymore. my patch is connected as follows

bang---openpanel---open $1-----readsf~ -----dac~

the readsf~ object is connected with a start-message box too, to play the sample.

so i would like that one version of the patch plays the audiofole in loop and one version only one shot via bang.

i have no ideas anymore,

you would save my day for any ideas, that fix my patch

thanks
rookie

The included patch should do the trick. You might consider adding a [spigot] object to stop triggering the next play.

Cheers,

Domien

http://www.pdpatchrepo.info/hurleur/sfread.looper.pd

@domien said:

The included patch should do the trick. You might consider adding a [spigot] object to stop triggering the next play.

Cheers,

Domien

thank you domien for your help.
that is nearly what i looked for

you saved the day...

hi domien again,

i thougt the >t b b< ( trigger bang bang, isn´t it?) object solved the problem, but it doesn`t.
your patch is very close, what i am looking for. I builded a patch for a while. I could start play the sample in loopmode with it a start message and stop with stop message. also was a little variation from that patch able to play a sample one time triggered via bang drum samples vor example)
I made those patches for a while, but i cant find it anymore, probably deleted. I try the whole day to rememeber, it seems i have lost my mind. I started with pd in september last year and had a little break with the program. it seems you have to work every day with pd
have you got one more idea

thanks in advance

if they are just samples you are using, and less than a minute long or whatever, it's best to load them into arrays ( check the help file for [soundfiler] ) and then use [tabplay~ ] or [tabread4~ ] to play them back

hello hardoff, thanks for posting. i would like play short drum samples in one patch version, not looped but triggerd with a bang. the other should play audiosamples, most of them less than a minute. i had that patch in the past selfconstructed, it was very simple. only a few objects. my actual not finished patch plays the loaded sample only one time (see the construction above) if i like to play the sample again, i have to reload it via openpanel. it seems, the sampledata is not present after on time playing. domiens patch loops the loaded files and its working fine, but there is also a very little other aproach. the point is, those patches are the beginning of my planned chain. i try your hint with [tabplay~ ] or [tabread4~ ]. thanks so far, i have to construct now. i hold contact with the status of building.

yeah. you definitely want to load your samples into arrays first and then play them back.

i think the best way to do this is to use the http://www.pdpatchrepo.info/hurleur/simpleplayer.pd

hi hardoff, jesus, that is the luxus version. it works fine and looks very pretty.
so i can start now with the more interesting step number two. deconstructing the samples.

thanks a lot...

hi hardoff again. i played with your patch arround and tryed to understand, what you did and how it works. if you like to answer two questions? what does the dollarsigns exactly in the messageboxes do and what is the argument "s" and "f" in the pack object meaning.

i cant proof it to you (because, i cant find my old patch anymore) but i bet you, there is a way without arrays. very simple. i try it out in my next free time. because of the minimum-maximum principia in programing

[pack s f f s] == [pack symbol float float symbol] (exactly the same, but shorter to type)

$1, $2, etc in a "message box" are parts of the incoming list message:

"list with at least 3 elements"
|
"$3 blah $1 blahblah $2"
|
"least blah with blahblah at"

$1, $2, etc in an [object box of an abstraction] are useable inside that abstraction to access the creation arguments.

$0 in abstractions is special, it is unique to that instance, so you can use it to make local name - like [delwrite~ $0-delay] - so that if you have more than one instance of an abstraction, the names don't clash.