Brian H.

I'm having some issues organizing the flow of my patches. One thing that would really help is the ability to control a single [sfplay~] object from elsewhere in the patching heirachy. This is a simple open file play/pause, and there are no other cues, so there really doesn't seem to a need for [sflist]. I suppose I could use [send/receive] I'd rather not add even more of them to the patch if I can avoid it.

Can the name argument be used to refer to an [sfplay] by *other* [sfplays]? Didn't seem to work in the experiment below, but maybe there is something?

Hi,
I'm having some issues organizing the flow of my patches.  One thing that would really help is the ability to control a single [sfplay~] object from elsewhere in the patching heirachy.  This is a simple open file play/pause, and there are no other cues, so there really doesn't seem to a need for [sflist].  I suppose I could use [send/receive] I'd rather not add even more of them to the patch if I can avoid it.

Can the name argument be used to refer to an [sfplay] by *other* [sfplays]?  Didn't seem to work in the experiment below, but maybe there is something?

sfplay-instances-control

Sorry. sfplay~ doesn't work that way - I expect you might be thinking of some other MSP objects that take the name of a buffer~ object to which they refer (i.e. whose' content they play back). Take a look at the helpfile or MSP tutorial 16 for the skinny on sfplay~ (sfinfo~ will give you some data that might be useful to you in terms of playing the file from disc).

If you're looking for ways to address a single point from various locations, you might want to look at the pvar object. If you don't like sends and receives (and I don't, generally speaking), you can always encapsulate and route data via patch cords to known locations you can see.

[sfplay~] instances & control