Alex Danson

I had a subpatcher in a poly~ object, which window I left open when I saved the main patcher that was supposed to go in the poly~ object.

When I opened the master patch (that the poly~ was in), Max 5 opened that subpatch in no less than 128 windows on top of each other (I counted them...)

I realized (4 hours later) that I have to open the original poly~ patcher, close tha subpatcher window then save it, so everything was back to normal.

Another victory of the humans over the machine...:-)

I had a subpatcher in a poly~ object, which window I left open when I saved  the main patcher that was supposed to go in the poly~ object. 

I realized (4 hours later) that I have to open the original poly~ patcher, close tha subpatcher window then save it, so everything was back to normal. 

bug-report-a-subpatcher-in-a-poly

On Jul 11, 2008, at 10:33 PM, Alex Danson wrote:

> When I opened the master patch (that the poly~ was in), Max 5 opened 

> that subpatch in no less than 128 windows on top of each other (I 

If you save the poly~ patch with a subpatcher window open, Max will 

open a window for each voice instance. I think this is long-standing 

behavior, and makes sense, even though it's not what you want.

On Jul 11, 2008, at 10:33 PM, Alex Danson wrote:
> When I opened the master patch (that the poly~ was in), Max 5 opened  
> that subpatch in no less than 128 windows on top of each other (I  
> counted them...)

If you save the poly~ patch with a subpatcher window open, Max will  
open a window for each voice instance. I think this is long-standing  
behavior, and makes sense, even though it's not what you want.

Chris Muir
cbm@well.com	
http://www.xfade.com

I never asked for 128 instances... only 16

On 12 juil. 08, at 10:12, Alex Danson wrote:

> I never asked for 128 instances... only 16

I can't reproduce that. Could you provide a patch?

> Chris,
>
> I never asked for 128 instances... only 16

Chris is right... I did ask for 16 voices in that poly patcher object, but I was also using it several times throughout the main patch, which indeed added up to 128.

so... my bad, no bugs here, but the phenomena is still confusing when it happens to you for the first time :-)

attached are a couple of patches that reflect this behavior

On 12 juil. 08, at 17:13, Alex Danson wrote:

> Chris is right... I did ask for 16 voices in that poly patcher 

> object, but I was also using it several times throughout the main 

> so... my bad, no bugs here, but the phenomena is still confusing 

> when it happens to you for the first time :-)

> attached are a couple of patches that reflect this behavior

just for the record, it's the expected behavior, when you save a patch 

with opened subpatchers, they'll be automatically opened on loadbang 

> Chris is right... I did ask for 16 voices in that poly patcher  
> object, but I was also using it several times throughout the main  
> patch, which indeed added up to 128.
>
> so... my bad, no bugs here, but the phenomena is still confusing  
> when it happens to you for the first time :-)
>
> attached are a couple of patches that reflect this behavior

just for the record, it's the expected behavior, when you save a patch  
with opened subpatchers, they'll be automatically opened on loadbang  
next time you open the main patch.

> just for the record, it's the expected behavior, when you save a patch 

> with opened subpatchers, they'll be automatically opened on loadbang 

I'll add for the record, that my proposed savebang object would make it 

possible to avoid those accidents. It would bang and close/delete/init 

whatever you want before the patch is saved when you hit cmd-s...

Don't know if its easy to implement though, as it has to prevent the 

normal saving till all these tasks are finished...

And if we would have an undo object, send it an "all", it would put the 

patch in its original state, literally making it impossible to save 

(Maybe there is a command to Max to undo...?)

Emmanuel Jourdan schrieb:
> just for the record, it's the expected behavior, when you save a patch 
> with opened subpatchers, they'll be automatically opened on loadbang 
> next time you open the main patch.

I'll add for the record, that my proposed savebang object would make it 
possible to avoid those accidents. It would bang and close/delete/init 
whatever you want before the patch is saved when you hit cmd-s...

Don't know if its easy to implement though, as it has to prevent the 
normal saving till all these tasks are finished...

And if we would have an undo object, send it an "all", it would put the 
patch in its original state, literally making it impossible to save 
changes to the same place... ;-)

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


bug report - a subpatcher in a poly~