"speedlim" and "timer" in m4l,please FIX
its been said before,i ll repeat it—
"speedlim" and "timer" in m4l have been BROKEN ever since max6 came out."clocker" is working,after all.
thats um oh about a year now!!
I agree, RBRT.
Cycling74 could make this angry-user bug-reporting thing a little easier on us all I think by making the bug bug tracker public using, say, https://www.uservoice.com/ or whatever – which might possibly assuage user angst. And might also speed up bug reports since we would know if anyone had reported the bug and thus report faster. I know I took a while to report that particular bug because it was so bloody obvious that I assumed the problem must be me. then I assumed that it was so enormous that they must surely have noticed to fix it… then a year passed.
Sorry for the inconvenience.
These problems with clocker and speedlim are fixed for the next update, which will be Max 6.1.3
At this stage I do not know the date for the release of that.
As well as the JS workaround, there may be simpler ways to replicate the functionality of speedlim
----------begin_max5_patcher---------- 445.3oc2TFraiBCDF9L7TX4yYqrABhzSsG6yPU0JGX1DWA1TaSR1spu6KdLr KsMUhlTkC8hs7v3Y9mOlwOGGQWqO.VJ4Zx8jnnmiihPSdCQCminMhCk0BK5F UA60qejtH7IGbvglaMRkazppqQ24pAGdE1f0VgqbqTs4mFnzERIOmcEaAIks B2x7qI8lHOLbmeoUNq7Of2cdxUigRVgIsWH+fynS7UIZPeo2Zjh5I5QpFkC2 a6k3X+xhyqna.mQSJXLxMhRmbGP3GGA7OFAoYXsmw8q7D9bQPH5te2Bg3PWK Tan+6VSHzpOIfRNA.0.VqXC7NBcGYurtlnzNR4VXOYSWCQpHgK9YQ0P2RRxP eRAhrhSfUGkSEeW3zPK0pTjOKW90ho7K.l9f4smBCbb1YMwwWh3gmkiaoK+5 G4xNCFgwiVKUu8cYrT71eM3r5NS4nhFRN4+0REXcRkvI0pI9T7Je1Jqp.0z2 pqjVw5Z.qH1Q+ANW0TLC03eC+BImUyPN4WL0jOyeU7SPMg9HQa6NvXGBIJj9 QsG0F+w7E3QoJbDmYnFXmbz+TzhvzOB45me5LgF4C4YzXeddI9u.E1L61. -----------end_max5_patcher-----------