you know we wouldnt flame you!! we is passinately tollerant!!!
in PD you can give it a string in the config prefs where you can tell it to look in all sorts of pathes, most the time those pathes are going to libs that you need for your abstractions.
in SC3 this is soo frekin much easier! the heirearchy makes too much sense!
it all goes to 1 folder called /sounds
in max/msp it explodes all over your hd! making a folder in your user putting all kinds of shit. that would be much nicer an Cleaner if they just kept it in the F’n folder! i dont think i have max/msp installed (open mac… nope not there)
hmm i bet i have it on another hd(lets see… nope)
hmm i install with default settings…
make object filein, rclick help
hmm it say “read or spool with argument specifies a file in Max’s search path”
wait, why not use sfplay~?
“sfplay~ plays AIFF, SD II, NeXT/SUN(.au), WAVE, and Raw Data files of 1-8 tracks from disk. To play a file, you send sfplay~ the open message, then send it a 1 to start and a 0 to stop. open takes an argument to specify a filename in the search path. You can also create additional cues with the preload message. These can reference other files, all of which are simultaneously accessible. The open message sets the “current” file: the one that plays back from the beginning when 1 is sent and is used as the default for the preload message. sfplay~ can also connect to the cues defined in an sflist~ object. Since multiple sfplay~ objects can reference the same sflist~, this allows you to store a global list of cues. See the sflist~ help file for more details. (be sure to open the “new features” sub patch to find out about variable speed playback, looping, triggering cues with audio signals, and more)”
then you could use sflist~ too
seems much more apt at doing more. but after thinking about it more i see that you might not want to use sfplay the way its been made.
i notice this tho "open takes an argument to specify a filename in the search path. "
maybe the arg: getnamed yourfile