[matrixctrl] and Preset's interpolation problems
Hi there,
we just found something we didn't know about preset interpolation.
In my example below, if [matrixctrl] is 8x8 .. no problem.
If it is bigger (we didn't dig the exact limits), interpolation doesn't work.
Maybe it also happens with other objects.
Actually, we tested with a (BIG) multislider with 1000 ... it works fine.
is it a bug ?
Do we have any information of what could be the cause of this ?
Is there a limit to the number of values that can be interpolated ?
Actually, multislider object can be interpolated with nodes even if there are 1024 sliders...
Si maybe that's a bug with matrixctrl
Don't know if it can help but here is what I recently posted on the FB group :
I had problems to interpolate matrictrl in the past too. The solution was to replace the 0 value of a connection with a small float, like 0.0001. If I remember well, triplets with a 0 value are not saved in the pattstorage, but using a non-zero value forces Max to save the whole matrix in the pattrstrorage.
Interesting, but not a viable solution !
Reaching support.
Did any of you find the solution?
Or did you get a response from Cycling Support?
Hi ! testing your patch i 've had that ine console :
matrixctrl: the preset data in this matrixctrl cannot be interpolated; store the preset again to enable interpolation
restoring schift-press the 2 presets and the interpolation seems to work ( M1, Max 9.07 )
hth
michel
Hi there, yes, this is something that have been fixed a couple of minor release ago, as far as I remember.
Tested yesterday again.
And even with the @MIZU solution, the bug is still there.
@Damiensko, the bug has normally been fixed in Max 9.0.6. Make sure you have at least this version.
When building the patch from scratch, things work as expected for me. When using the patch from OP, I need to resave the presets as Mizu stated, and then it works.
Same here, no problem, as I mentioned above.