Mathieu Chamagne

I would like to add that especially when using osc with jitter, I took the habit to always deferlow all upd messages arriving in Max, so I never had this...

Thanks very much Rob for your feedback. I did noticed that this issue only concerns setting color of jit.gl.videoplane (and in some cases, jit.gl.layer) ; other parameters of other jit.gl...

doesn't break patches and makes Vincent happy, so I'm happy too :-)

Pas de panique, on dirait bien que ce problème est du en fait à un autre package qui empêche Max de finir de se charger complètement... (et qui fait que...

position.openGL is broken in latest build. in a remote : conversion from cart3D is wrong and crash when setting a parameter @unit openGL ----------begin_max5_patcher---------- 811.3oc2W00aaBCE84To9evhmSQXvPf8zdXRSZZ+CllhbINIzA1HaSWRq1+8 YeMzR9njOZZ6zjZED6q84dNbtWLOd8Ui7tUrho7PeB8CznQOZFYDLlcjQcCL xqhtJujpf.8xEUULt1ab6jZ1JMLghUxx0HQMi+0uiJ3H8xBExDaiY1bIUs7o 0TVvY4hFNrvvtQ4MUhFcISC.EzMbwLX6E2d2MYOsC0Tc9xB9hoRClNBPHD+f wnvf.6EbLbIxLF5m8Pnf2A.FF7OWek8p4x3WuD7f2wykICwkv.fK3zI.kRbD 68jJqOApjLDUvjfOXpr5DnR7PTYR5GLSTKEMkyPFNT2nQqPOfNkGSQC53HQV...

sorry for late reply... position.openGL seems to work as expected in latest build : cart3D x y z --> openGL x z -y

thanks for considering my FR :-) I don't think that the default value of this attribute should change depending if the patch is in Max or in Live. It would...

I really think the Overdrive issue is THE big problem... If you say "Ossia-Max is not compatible with overdrive" .. half of Max users will just run away !

here is the simplest example I could find to reproduce the overdrive crash : no remote, just a parameter connected to a jit.matrix + jit.gen ----------begin_max5_patcher---------- 1710.3oc0Z08aiaCC+4z+JB7qKWfj72CX.a6kALf8zdZ3vPfRhRh5jkLrU50 aGt+2m9v1QJw10IWZWuCnt9HkLI+QJRZ59kGlErV7LoNX9ON+iymM6KOLalg jlvrl++rfB7yaX3ZyxB1HJJHbYvBKOI4Yog9OMeSEt9PKc9wBJmQjlMAaHVh kaNP46WUQ1HsBMObIXwbXbh9WYQ5qHvRv7+9zyQbT19f.sOnJRsRIvRpfeEO...

If it prevents from creating node with address message, I would say NO. To use patcher name, it's always possible to do it using argument (inherit #1 from parent patcher...