live.slider, can I change range/enum on the fly?
Is it possible to remotely change range/enum’s values for the live.slider object?
i.e. by pressing a toggle button.
You can do it with the regular slider, but I don’t think you can do it with the live.slider.
----------begin_max5_patcher---------- 517.3ocyVFsaaCBEF9Z6mBDZW5UA1NNw6t8bLMUgiOykJGbDP5xVUe2m4PbS 6RSJ0o0o2fDGNA9++xgC993HZU2VvPIei7CRTz8wQQXHWfncyinqDaW1JLXZ TaWSSKPS7K0sw1BV6eVC98fJUVJ4m6Vcsvt7Fop4ZMrz5SHM6JVBozMjxFFe 7GHqwynq51uxynOtKZwJvB5qAknpEOI1t0TaVIU8J.0FeePut7QcAeHN1MjD nIUvu60vf.rvVq26jpiZ7Jgp4jNuH0Y2Ebzz4GX8e0orF4ewsi6R8Phvomx0 tMP0CJL+uqkhV5GMOLPKgcZhjPnATOjW3FyJFCUXuHUReiTIcDTYEXLhF3.r jx3WcTpDPMBmikGY3HewaBGkuKzf+NRC9nogu13bnw7KFM52gJPex1jIAzzv ifrbrtXFaD2OlM51nWhqNNuP9B+rpWlgvJubD0KYWr5ESqrde8xfJccRXmCK Vjs+kVd9wdp8C3kV7bnsR0++0EnVcweNLLcazKGb1v6+j8xsFLVoRXkcpmlD 6YIcirtFTOU00RiyHnWYu3eKAqG2QweM8vmN8vCfOkSKddM4LexjSY.pIaxT y7OUpIjBmYSlZB5Z9HUiuIjX856.sY2VhBou26scZ2zhDbpT4mhM1nZ3N4P9 9DD59Fr19tqaz91+aWTPicmyCw+CA9oAmB -----------end_max5_patcher-----------
Thanks, you are right!
In case you depend on live.slider i.e for automatation or MIDI control you can normalize the slider ie beteeen 0 and 1 and scale the output.
I totally agree.
But when you have i.e. an 8 steps parameter, you won’t have value quantisation for the envelopes, would you?
you’r right, you would lose quantization in the envelope. Are the amount of steps always the same, just the values different? in this case you could just route the live.slider output to different colls. If you need different amount of steps as well the only workaround I can think of is to use multiple live.sliders – for every case one and dynamically show/hide the active one in the UI.
The Live application requires that things like parameter ranges need to be set at instantiation and not messed with afterward. For that reason, NO live.* UI object lets you change slider or dial ranges – you’ll need to use standard Max UI objects for that. There may be some interesting attempts out there to circumvent this, so perhaps others may wish to contribute their interesting and idiosyncratic approaches to the problem that differ from going with vanilla Max objects. :-)
Hi Gregory, you are right. Gravetti’s point was that he was looking for the flexibilty of the vanilla objects in combination with the abilitiy of midi mapping in live. Hence the hacks. Sure this is not how live parameters are conceived, but hey isn’t max also about finding solutions ;)