Kim Cascone

I ran across a behavior I don't remember experiencing in Max/MSP 4.5:

- open a patch 'foo1' containing [sfplay~ name kim1]-->[dac~]

- sfplay~ loads sample1.aif and is sent [1] to play and [loop 1]

- the dac~ is sent a [startwindow] command

- open patch 'foo2' also containing a [sfplay~ name kim2]-->[dac~]

- sfplay~ is playing sample2.aif and sent [1] to play and [loop 1]

foo2 patch opens with the dac~ running although no [start] or 

with foo1 and foo2 open I can use [startwindow] or [start] commands 

to have either -or- both patches running at the same time...

...but is it possible to load another patch containing a dac~ and 

- I'm assuming this is possible since you can send [startwindow] to 

one patch containing a dac~ and have the other patch containing a 

- open a patch 'foo1' containing [sfplay~ name kim1]-->[dac~]
- sfplay~ loads sample1.aif and is sent [1] to play and [loop 1]
- the dac~ is sent a [startwindow] command
- it plays the file

- open patch 'foo2' also containing a [sfplay~ name kim2]-->[dac~]
- sfplay~ is playing sample2.aif and sent [1] to play and [loop 1]

foo2 patch opens with the dac~ running although no [start] or  
[startwindow] command was sent to it

with foo1 and foo2 open I can use [startwindow] or [start] commands  
to have either -or- both patches running at the same time...

...but is it possible  to load another patch containing a dac~ and  
have it  *not*  play when loaded?

- I'm assuming this is possible since you can send [startwindow] to  
one patch containing a dac~ and have the other patch containing a  
dac~ not play


behavior-dac-in-separate-patches

eureka! I think I answered my own question:

- sending an [enable 0] command with a loadbang will load an instance 

    - suggestion: the dac~.help fine should contain this very useful tidbit

On Oct 18, 2006, at 8:58 AM, Kim Cascone wrote:

> I ran across a behavior I don't remember experiencing in Max/MSP 4.5:

> - open a patch 'foo1' containing [sfplay~ name kim1]-->[dac~]

> - sfplay~ loads sample1.aif and is sent [1] to play and [loop 1]

> - the dac~ is sent a [startwindow] command

> - open patch 'foo2' also containing a [sfplay~ name kim2]-->[dac~]

> - sfplay~ is playing sample2.aif and sent [1] to play and [loop 1]

> foo2 patch opens with the dac~ running although no [start] or 

> with foo1 and foo2 open I can use [startwindow] or [start] commands 

> to have either -or- both patches running at the same time...

> ...but is it possible to load another patch containing a dac~ and 

> - I'm assuming this is possible since you can send [startwindow] to 

> one patch containing a dac~ and have the other patch containing a 

eureka! I think I answered my own question:
- sending an [enable 0] command with a loadbang will load an instance  
of the dac~ but not running
	- suggestion: the dac~.help fine should contain this very useful tidbit

> I ran across a behavior I don't remember experiencing in Max/MSP 4.5:
>
> - open a patch 'foo1' containing [sfplay~ name kim1]-->[dac~]
> - sfplay~ loads sample1.aif and is sent [1] to play and [loop 1]
> - the dac~ is sent a [startwindow] command
> - it plays the file
>
> now...
>
> - open patch 'foo2' also containing a [sfplay~ name kim2]-->[dac~]
> - sfplay~ is playing sample2.aif and sent [1] to play and [loop 1]
>
> foo2 patch opens with the dac~ running although no [start] or  
> [startwindow] command was sent to it
>
> with foo1 and foo2 open I can use [startwindow] or [start] commands  
> to have either -or- both patches running at the same time...
>
> ...but is it possible  to load another patch containing a dac~ and  
> have it  *not*  play when loaded?
>
> - I'm assuming this is possible since you can send [startwindow] to  
> one patch containing a dac~ and have the other patch containing a  
> dac~ not play


behavior: dac~ in separate patches