Forums > MaxMSP

Bug? bpatcher update when saved -> infinite loop

February 12, 2007 | 11:21 am

Hi all,

Description:
When I have a bpatcher in a bpatcher in a bpatcher, and I save the innermost patch (sub2 in example), the outermost patch and the one inside it keep updating their interface infinitely and max hangs.

Steps to reproduce:
- save the patches below
- open all patches
- save sub2

Expected behaviour:
main and sub1 update once

Please let me know if you can confirm,
- Mattijs

save as ‘sub2′:

#P comment 73 23 28 196617 sub2;
#P bpatcher 4 23 64 32 0 0 1;

save as ‘sub1′:

#P bpatcher 4 147 188 121 0 0 sub2 1;
#P bpatcher 4 23 188 121 0 0 sub2 1;
#P comment 196 24 29 196617 sub 1;

save as anything:

#P bpatcher 3 22 332 380 0 0 sub1 1;

btw, I noticed that this doesn’t occur when a) there is no bpatcher in sub2 b) there is only one bpatcher in sub1.


February 12, 2007 | 2:00 pm

confirmed. weird.

On Feb 12, 2007, at 6:21 AM, Mattijs Kneppers wrote:

>
> Hi all,
>
> Description:
> When I have a bpatcher in a bpatcher in a bpatcher, and I save the
> innermost patch (sub2 in example), the outermost patch and the one
> inside it keep updating their interface infinitely and max hangs.
>
> Steps to reproduce:
> – save the patches below
> – open all patches
> – save sub2
>
> Expected behaviour:
> main and sub1 update once
>
> Please let me know if you can confirm,
> – Mattijs
>
>
> save as ‘sub2′:
>
> #P comment 73 23 28 196617 sub2;
> #P bpatcher 4 23 64 32 0 0 1;
>
> save as ‘sub1′:
>
> #P bpatcher 4 147 188 121 0 0 sub2 1;
> #P bpatcher 4 23 188 121 0 0 sub2 1;
> #P comment 196 24 29 196617 sub 1;
>
> save as anything:
>
> #P bpatcher 3 22 332 380 0 0 sub1 1;
>
>
> btw, I noticed that this doesn’t occur when a) there is no bpatcher
> in sub2 b) there is only one bpatcher in sub1.
> –
> SmadSteck – http://www.smadsteck.nl
> Interactive audiovisual sampling soft- and hardware
>
>


February 12, 2007 | 4:39 pm

I can confirm this behaviour – I was never able to reproduce it, but
I have been bitten many times. Nice work finding it!

On Feb 12, 2007, at 6:21 AM, Mattijs Kneppers wrote:

>
> Hi all,
>
> Description:
> When I have a bpatcher in a bpatcher in a bpatcher, and I save the
> innermost patch (sub2 in example), the outermost patch and the one
> inside it keep updating their interface infinitely and max hangs.
>
> Steps to reproduce:
> – save the patches below
> – open all patches
> – save sub2
>
> Expected behaviour:
> main and sub1 update once
>
> Please let me know if you can confirm,
> – Mattijs
>
>
> save as ‘sub2′:
>
> #P comment 73 23 28 196617 sub2;
> #P bpatcher 4 23 64 32 0 0 1;
>
> save as ‘sub1′:
>
> #P bpatcher 4 147 188 121 0 0 sub2 1;
> #P bpatcher 4 23 188 121 0 0 sub2 1;
> #P comment 196 24 29 196617 sub 1;
>
> save as anything:
>
> #P bpatcher 3 22 332 380 0 0 sub1 1;
>
>
> btw, I noticed that this doesn’t occur when a) there is no bpatcher
> in sub2 b) there is only one bpatcher in sub1.
> –
> SmadSteck – http://www.smadsteck.nl
> Interactive audiovisual sampling soft- and hardware
>

v a d e //

http://www.vade.info
abstrakt.vade.info


February 12, 2007 | 5:12 pm

Quote: vade wrote on Mon, 12 February 2007 17:39
—————————————————-
> I can confirm this behaviour – I was never able to reproduce it, but
> I have been bitten many times. Nice work finding it!

vade and joshua, thanks for confirming. I hope that cycling can find the cause of this behaviour..

Cheers,
Mattijs


February 12, 2007 | 6:59 pm

Yeah Ive had this happen several times. Very annoying bug.


February 12, 2007 | 11:40 pm

Thanks for the report, Mattijs, and for the clear steps and example
patches. I was able to reproduce here as well. We’ve logged this bug
in our tracking system and will try to get around to fixing it as time
permits.

Cheers,
Andrew B.


February 13, 2007 | 2:15 pm

Quote: andrewb@cycling74.com wrote on Tue, 13 February 2007 00:40
—————————————————-
> Thanks for the report, Mattijs, and for the clear steps and example
> patches. I was able to reproduce here as well. We’ve logged this bug
> in our tracking system and will try to get around to fixing it as time
> permits.
>
> Cheers,
> Andrew B.
>
—————————————————-

No problem, happy to contribute. Actually the credits for this one go to Bas van der Graaff, member of the SmadSteck team (we tracked down the problem together).

Best,
Mattijs


Viewing 7 posts - 1 through 7 (of 7 total)