prko

can we display the instance produced by poly~in a single bpatcher window?

It is very complicated to open and close many windows.

Thus, I want to encapsulate all sub-windows linked to one poly into one bpatcher.

can we display the instance produced by poly~in a single bpatcher window?
It is very complicated to open and close many windows.
Thus, I want to encapsulate all sub-windows linked to one poly into one bpatcher.

how-to-display-the-instances-produced-by-poly-in-a-single-bpatcher

A typical solution would be to create bpatchers with the controls that hook up to the individual voices within poly~. That would require dynamic assignment of sends (forward) and receives.

However, I have not got the technical details from your answer.

Which objects should I use for the controls that hook up to the individual voices within poly~. 

What does mean dynamic assignment of sends (forward) and receives?

Thank yoy for the answer.
However, I have not got the technical details from your answer.
Which objects should I use for the controls that hook up to the individual voices within poly~. 
What does mean dynamic assignment of sends (forward) and receives?
Is there any instruction for it?

This isn't functional. it's just a visual diagram of how to achieve what your looking for

What I meant was displaying a small part of all instances which are produced by poly~.

I want to have five displays produced by bpatcher linked to xxx.

The method which you suggest means that I must produce a displaying patch for each prototype for a poly~.

I want to have five displays produced by bpatcher linked to xxx.displaying.

I must create one more file just for the display.

Is is possible to reach my goal without an extra file for the display?

e.g.:
[poly~ xxx 5]
I want to have five displays produced by bpatcher linked to xxx.

e.g.:
[poly~ xxx.processing 5]
I want to have five displays produced by bpatcher linked to xxx.displaying.
I must create one more file just for the display.

Did I understand the method correctly?
Is is possible to reach my goal without an extra file for the display?

no, a bpatcher represents one of two things: An abstraction, a subpatcher.

I don't know how to use the symbol "#1" with bpatcher.

The following is the patch which should be produced five times by [poly~].

Thus, there is the following object with the following argument:

I have tried in the inspector of bpatcher.

I don't know how to use the symbol "#1" with bpatcher.
The following is the patch which should be produced five times by [poly~].

I don't know how to use the symbol "#1" with bpatcher.
I have tried in the inspector of bpatcher.
However, it does not work.

edit-> actually i'm not sure that is what you wanted

thanks, but your answer is not the answer what I have asked.

My question is, how to load a patch A into a [bpatcher] and this instance of patch A in [bpatcher] must be one instance of [poly~ adc~s_poly 5]!

it's not possible, but a bpatcher-like external could probably be written with the new sdk that does this.

oli larkin wrote on Tue, 22 September 2009 17:52

no problem, he needs that, too, because he had it wrong before.

i think you have to rethink yur patch, not wait ffor a bpatcher 

i bet you have interface elements in your poly patcher, and this

is what you should change. everything "control" and "gui" has to 

run from the outside world. then it is no problem to have different

voices visible and controllable at the same time without opening 32

try to use poly~ more or less for signal only.

oli larkin wrote on Tue, 22 September 2009 17:52[poly~ adc~s_poly args 5]

i think you have to rethink yur patch, not wait ffor a bpatcher 
update in maxmsp v 6.

i bet you have interface elements in your poly patcher, and this
is what you should change. everything "control" and "gui" has to 
run from the outside world. then it is no problem to have different
voices visible and controllable at the same time without opening 32
windows.

Matthew Aidekman has right!
I have solved the problem!
Thanks!
My problem was another problem!


I reached my goal by the method of Matthew Aidekman.

The sound ist twice louder because two instance 1 in [poly~] and [bpatcher] work simultaneously!

Roman Thilenius has also right!
I reached my goal by the method of Matthew Aidekman.
The sound ist twice louder because two instance 1 in [poly~] and [bpatcher] work simultaneously!
I will follow your method!
Thanks very much!


Hmmm. If poly~ could host a bpatcher, that would be a really elegant way of creating mixers, where you have a bunch of identical guis that differ only in subtle details (channel name, x-coordinate, etc.) Require very little cabling between interface and audio.

But it sounds like this is not currently possible? No big deal, as this can be done with javascript.... but it would be cool to be able to patch it that way, and much cleaner.

Hmmm.  If poly~ could host a bpatcher, that would be a really elegant way of creating mixers, where you have a bunch of identical guis that differ only in subtle details (channel name, x-coordinate, etc.)  Require very little cabling between interface and audio.

But it sounds like this is not currently possible?  No big deal, as this can be done with javascript.... but it would be cool to be able to patch it that way, and much cleaner.


how to display the instances produced by poly~ in a single bpatcher