Max Dial behaving differently?!?!?!
I had a project from about 2 years ago, and one of the thing that it used was these high definition dials. I used the dial object and set the number of steps to 1024. Then I scaled everything down. Basically, I needed all that definition to create an analog tuning dial that could fine tune a range of 2 octaves.
Anyway, I’m revamping the project. I opened the patchers, and the dials are behaving funny. The high definition ones seem to turn like a midi dial with only 127 slots. When I used this tuning dial, it made big skips in the range like it was not hitting every step in the 1024 range, and instead interpolating a lower resolution.
I also had one dial that acted as a switch (like the moog register switch on the oscillators). It now turns like a dial, but only outputs the 6 slots. It doesn’t snap to each slot.
Anyway, is this something with an update? I think I did this project before updating to the latest Max 5 release. I have since updated to latest Max 5 with the MFL objects.
If so, does anyone know a way to configure the dials to give a nice high resolution output? Gotta add that I love the compactness of midi, but I hate that it has bound music into 128 slots.
Here is an example of high resolution live.dial with range 0-1024 (1025 steps).
----------begin_max5_patcher---------- 336.3ociQEsiBCBD7Y5WAgm8LUiW7N+UtXZnxVk6nPCrsQiw+8qPopWBXtWn kYF1c1YuVPX0lyfiQ2Q+hRHWKHj.jGfDuSXs7yGTbWPFSIGfkBIWwVLwNvsZ dKjlT22Z5QEfgGuNhNAgW5foNyXKnrFkgiL59nlNNd3jTerxBGvIYetZY4B5 Ga7malN2tr79KjhfGL0e+1J18pXG8FB1JPyqUg9s5g2j5YqMC53CfnhinUV2 ivi+bwLIFJ94V0CllY3Y7m6Y6XxEJd4ZucSIPp8BJSxNGPo3jZINlyOMVoT4 NYrX1syeshQL610aSZGkQe7+WqWMXJo9Gekb47su.FwKF9FSvEoZd+Xx3xxZ rBvlqtBnIOoqC.gR1FhnjikCgNWbe+dRaOHcxWrtfycFMnw7sfq0FjiRit59 pHaHfWhsZh+VQwiOgyaEz8E2J9kbRxPQ -----------end_max5_patcher-----------
Thanks for the patcher. So I’m assuming the original dial is going deprecated?
If you choose circular instead of linear in the inspector and take your mouse far from the dial after clicking, you’ll get a much greater resolution. But this seems to be a case where the live.dial is more efficient…