prko

To which object should I connect in my patch.

I am very sorry for my too often stupid question.

To which object should I connect in my patch.
I receive only error.

problem-with-begin

As you'll notice from the help file, the best way to mute parts of your patch is to save them as abstractions and load them into the [poly~] object.

With [adc˜] as in my patch, there is problem, but I have solved it.

Poly~ produces many windows. These windows very troublesome.

Unfortunately, I had no success to connect each instance produced by poly~ to an instance of bpatcher.

So I need another method to mute a subpatch.

I did so already. 
It functions well.
With [adc˜] as in my patch, there is problem, but I have solved it.

The problem is the following:
I have decided not to any poly~.
Poly~ produces many windows. These windows very troublesome.
I want rather to use bpatchers.
Unfortunately, I had no success to connect each instance produced by poly~ to an instance of bpatcher.
So I need another method to mute a subpatch.

Could this be because you saved the patch that you load in poly~ with open windows? Anyhow, there is also the mute object, and pcontrol can do something similar.

Quote:Poly~ produces many windows. These windows very troublesome.

Could this be because you saved the patch that you load in poly~ with open windows? Anyhow, there is also the mute object, and pcontrol can do something similar.


If I recall correctly, in the very first versions of max it was not allowed to have multiple dac objects. Anyhow I got accustomed to the style of having only one place in my patch where audio flows in and out, and distributing the signal being part of the programming process. Muting a bpatcher with an adc~ inside sounds rather dirty.

Quote:Still the issue is how to nute the adc~!

i havent looked at his patch, but one can just have dac~s in a poly~ in order to 

i havent looked at his patch, but one can just have dac~s in a poly~ in order to 
cut off stuff from the "main out".


I think poly~ is useful, if one does not need a GUI.

In order to use GUI, bpatcher with arguments is much better, isn't it?

thanks a lot!
I have solved with mute~ and pass~.
mute~is placed the patch.
pass~ is placed as an abstract.
I think poly~ is useful, if one does not need a GUI.
In order to use GUI, bpatcher with arguments is much better, isn't it?

problem with begin~