Cycling 74 » Topic: Basic Max 5 patchs not workin 6

Basic Max 5 patchs not workin 6

Kyred — Tue, 08 Nov 2011 21:29:04 +0000

Hi,

I’ve just purchased Max6 and this simplified patch which works in Max 5 does not in Max 6.
Same for many others …

What important changes should I know apart max6 new features?

Thanks

– Pasted Max Patch, click to expand. –

Re: Basic Max 5 patchs not workin 6

Kyred — Tue, 08 Nov 2011 21:33:19 +0000

An other example with [jit.gl.multiple]

– Pasted Max Patch, click to expand. –

Re: Basic Max 5 patchs not workin 6

Wesley Smith — Tue, 08 Nov 2011 22:03:40 +0000

hi Kyred.
Looks like there’s an initialization problem with the targetname attribute that crept in. This one threw me for a loop for a bit. If you hook up attrui to jit.gl.multiple and choose the targetname attribute, you’ll see the value the object has stored. Sending a loadmess targetname elmt, it’ll work. I’ve logged this as a bug and will fix it ASAP. Sorry for the inconvenience:

– Pasted Max Patch, click to expand. –

Re: Basic Max 5 patchs not workin 6

Wesley Smith — Tue, 08 Nov 2011 22:11:46 +0000

Here’s a better solution. This seems to have been a long standing bug in jit.gl.multiple. As long as you give both the destination name and the number of inlets to jit.gl.multiple (i.e. [jit.gl.multiple tester 1]), things will work as they should:

– Pasted Max Patch, click to expand. –

Re: Basic Max 5 patchs not workin 6

Kyred — Wed, 09 Nov 2011 17:07:21 +0000

Thank you for the suggestion,
Max crashes if you set the @targetname after the @glparams (forgot to tell it).
An other issue is the target object has a @scale set to 0.1, that [jit.gl.multiple] in Max6 does not take into account.

Re: Basic Max 5 patchs not workin 6

Wesley Smith — Wed, 09 Nov 2011 17:16:20 +0000

Can you give me the exact steps to trigger the crash? I wasn’t able to make it happen. I think I might have already fixed this issue for the next release.

Re: Basic Max 5 patchs not workin 6

Wesley Smith — Fri, 11 Nov 2011 23:44:40 +0000

I see that it’s not taking into account the target objet’s scale, position or rotate. We’ve logged this and it should be fixed for the next release.