Peter Ostry

I feel a bit lonely here with my basic questions but I work hard to develop more interesting problems ;-)

But for now: Is there a kind of dummy object available, which I can use to collect and organize my connections? Something that does nothing but passing all kinds of messages through. Or one for audio and one for others.

is-there-a-dummy-object-in-max

[t l] or trigger list (l) does that. Just one in one out. Something like that?

You can also use this very special trick :D

You can even save the trick as an abstraction ;)

Or you could create an abstraction, save as dummy.pat and put it

Or you could create an abstraction, save as dummy.pat and put it
somewhere in your search path.

Quote: Peter Ostry wrote on Thu, 10 April 2008 08:51

----------------------------------------------------

> But for now: Is there a kind of dummy object available, which I can use to collect and organize my connections? Something that does nothing but passing all kinds of messages through. Or one for audio and one for others.

"nothing" is one of the gems of the CNMAT MMJ Depot:

Quote: Peter Ostry wrote on Thu, 10 April 2008 08:51
----------------------------------------------------
>
> But for now: Is there a kind of dummy object available, which I can use to collect and organize my connections? Something that does nothing but passing all kinds of messages through. Or one for audio and one for others.
>
>
----------------------------------------------------

just make an abstraction with an inlet and an outlet that are connected?

> Quote: Peter Ostry wrote on Thu, 10 April 2008 08:51

> ----------------------------------------------------

>> But for now: Is there a kind of dummy object available, which I can 

>> use to collect and organize my connections? Something that does 

>> nothing but passing all kinds of messages through. Or one for audio 

> "nothing" is one of the gems of the CNMAT MMJ Depot:

> || michael f. zbyszynski -- molecular gastronimist

>
> Quote: Peter Ostry wrote on Thu, 10 April 2008 08:51
> ----------------------------------------------------
>>
>> But for now: Is there a kind of dummy object available, which I can  
>> use to collect and organize my connections? Something that does  
>> nothing but passing all kinds of messages through. Or one for audio  
>> and one for others.
>>
>>
> ----------------------------------------------------
>
> "nothing" is one of the gems of the CNMAT MMJ Depot:
>
>
> http://cnmat.berkeley.edu/patch/2530
>
>
> mz
>
> --
> || michael f. zbyszynski -- molecular gastronimist
> || http://www.cnmat.berkeley.edu/
> || http://www.mikezed.com/
>
>
>


>> But for now: Is there a kind of dummy object available, which I can use

>> to collect and organize my connections? Something that does nothing but

>> passing all kinds of messages through. Or one for audio and one for

FWIW, I use [t l] (trigger list), which works for passing anything

Quote: Peter Ostry wrote on Thu, 10 April 2008 08:51
> ----------------------------------------------------
>>
>> But for now: Is there a kind of dummy object available, which I can use
>> to collect and organize my connections? Something that does nothing but
>> passing all kinds of messages through. Or one for audio and one for
>> others.

FWIW, I use [t l] (trigger list), which works for passing anything
through. +~ for audio.

Thank you all, I like the patcher with the inlet and outlet most (at least in a mixed patch) because it works for numbers and signals.

Quote: Peter Ostry wrote on Fri, 11 April 2008 04:47

> Thank you all, I like the patcher with the inlet and outlet most (at least in a mixed patch) because it works for numbers and signals.

Quote: Peter Ostry wrote on Fri, 11 April 2008 04:47
----------------------------------------------------
> Thank you all, I like the patcher with the inlet and outlet most (at least in a mixed patch) because it works for numbers and signals.
>
----------------------------------------------------

Quote: jvkr wrote on Fri, 11 April 2008 09:21

I believe it is better (performance-wise) not to redirect the program through an included patch. This may be not true for Max/MSP, don't know ...

Quote: jvkr wrote on Fri, 11 April 2008 09:21
----------------------------------------------------
> [t l] works for signals too.
----------------------------------------------------

I believe it is better (performance-wise) not to redirect the program through an included patch. This may be not true for Max/MSP, don't know ...


Quote: Peter Ostry wrote on Thu, 10 April 2008 19:47

In certain cases with signals, this doesn't work out the way you might hope. There is a full explanation in nothing.help, (

 but the short version is that inlets do not do any summing. In other words, if you have 10 signals in and 10 signals out to the patcher you describe, than Max will see 100 signal patch cords. If they go through +~, then there are only 20.

Quote: Peter Ostry wrote on Thu, 10 April 2008 19:47
----------------------------------------------------
> Thank you all, I like the patcher with the inlet and outlet most (at least in a mixed patch) because it works for numbers and signals.
>
----------------------------------------------------

In certain cases with signals, this doesn't work out the way you might hope.  There is a full explanation in nothing.help, (http://cnmat.berkeley.edu/patch/2530) but the short version is that inlets do not do any summing.  In other words, if you have 10 signals in and 10 signals out to the patcher you describe, than Max will see 100 signal patch cords.  If they go through +~, then there are only 20.

> FWIW, I use [t l] (trigger list), which works for passing anything

Sorry, it's not true, though it works in many cases:

Joshua Kit Clayton schrieb:
> FWIW, I use [t l] (trigger list), which works for passing anything
> through. +~ for audio.

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com

> In other words, if you have 10 signals in and 10 signals out to the

> patcher you describe, than Max will see 1000 signal patch cords. If

> they go through +~, then there are only 20.

I guess you mean 100 patch cords which would create also 100 addition

operations - for each destination sum ten inputs, versus sum one time 

ten inputs and then send the result to the destinations...

I doubt that the patch cord itself will eat CPU...

The patch thru is exactly like a direct connection. The unlikely

scenario you describe obviously is a good point for optimisation though...

mzed schrieb:
> In other words, if you have 10 signals in and 10 signals out to the
> patcher you describe, than Max will see 1000 signal patch cords.  If
> they go through +~, then there are only 20.

I guess you mean 100 patch cords which would create also 100 addition
operations - for each destination sum ten inputs, versus sum one time 
ten inputs and then send the result to the destinations...

The patch thru is exactly like a direct connection. The unlikely
scenario you describe obviously is a good point for optimisation though...

And it has a certain overhead on load, it even contains a uc_license 

object, though even in the U.S. I doubt this sort of patch is subject to 

any copyright (exept for the copyright text itself... ;-)

I have a version I use as type preserving trigger, called obviously 

"St". It will add a number of outlets, or in the version of St.hru it 

will also add inlets... Both add also overhead on load, as they have to 

execute some scripting for the ins and outs...

All of these are toys coming out of the natural play instinct of Maxers...

mzed schrieb:
> "nothing" is one of the gems of the CNMAT MMJ Depot:

And it has a certain overhead on load, it even contains a uc_license 
object, though even in the U.S. I doubt this sort of patch is subject to 
any copyright (exept for the copyright text itself... ;-)
I have a version I use as type preserving trigger, called obviously 
"St". It will add a number of outlets, or in the version of St.hru it 
will also add inlets... Both add also overhead on load, as they have to 
execute some scripting for the ins and outs...
All of these are toys coming out of the natural play instinct of Maxers...

On 14 avr. 08, at 09:26, Stefan Tiedje wrote:

> And it has a certain overhead on load, it even contains a uc_license 

> object, though even in the U.S. I doubt this sort of patch is 

> subject to any copyright (exept for the copyright text itself... ;-)

> I have a version I use as type preserving trigger, called obviously 

> "St". It will add a number of outlets, or in the version of St.hru 

> it will also add inlets... Both add also overhead on load, as they 

> have to execute some scripting for the ins and outs...

> All of these are toys coming out of the natural play instinct of 

It sounds like everyone like to make objects which does nothing;-) 

> And it has a certain overhead on load, it even contains a uc_license  
> object, though even in the U.S. I doubt this sort of patch is  
> subject to any copyright (exept for the copyright text itself... ;-)
> I have a version I use as type preserving trigger, called obviously  
> "St". It will add a number of outlets, or in the version of St.hru  
> it will also add inlets... Both add also overhead on load, as they  
> have to execute some scripting for the ins and outs...
> All of these are toys coming out of the natural play instinct of  
> Maxers...

It sounds like everyone like to make objects which does nothing;-)  
I've one too in js, called ej.nthru.

Is there a "dummy" object in Max?