When using Ableton Move as a controller, it cannot correctly read the knob values.
When connecting Ableton Move to Max/MSP as a controller, I can only read 0 or 1 values using notein to retrieve knob data.
I think I understand why this happens — on Ableton Move, this design makes it convenient to see the related information. However, when using it as a controller, how can I get 0-127 values for the knobs?
Thanks for your help!
Wouldn’t you need to use ctlin for that? Are the knobs sending a note value or a cc?
Thank you for your reply. I can only read the values 1 and 127 when using notein / ctlin.
you should check settings of that device, mode, options etc
and post precisely what you captured.
pad ? dial ?
also a patch showing how you parse incoming midi messages.
I use Ableton Move and this is my patch.
this here won't work
if it is named so you must use symbol
try this - record short sequemnce using your pads and dials,
write file as text and upload it here.
Thank you for your help! This is something I added temporarily to clarify the issue, but I can actually detect the device without any problem.
As described in the question, I can get the button values and detect the knobs, but the knob values are only returning 1 and 127. I believe this is related to the Ableton Move device, because when using it, touching the knob shows its mapped parameter on the screen, and rotating it adjusts the value.
In this case, I would like to know if it's possible to read the knob values from Ableton Move in Max/MSP, getting a range of 1 to 127, instead of just 1 and 127.
Have you tried viewing the raw midi to see what’s coming in with a midi monitor? That way you could tell if it’s a max problem or a move problem.
You have to read manual of that device.
As "Live control" specialised controller it might lack
option to work as simple midi controller.
I had a short look into manual, and to me it seems
that it is locked to either Live control mode
or standalone mode.
None of that modes seems to work for what you expect.
but if you record input from it as I suggested,
maybe one could do something about it.
Thank you all for your help. Although the issue hasn't been resolved yet, I will continue to find a solution.
Found here in the Move manual:
As stated, MIDI CC isn't supported, which isn't entirely true as you can apparently still receive data from the knobs. The data you get (1 or 127 but nothing in between) looks like some relative-mode MIDI controls. If it sends 1 when turning the knob in one direction and 127 in the other, so it is indeed the case and you can use that to create a precise controller, but it won't be synced with the actual value you see on the controller side. Maybe try to send some MIDI CC values to the same CC number you receive data and see what it does. I wouldn't be surprised that it actually works even if stated as "Not supported", but at your own risk.
In that manual (if I read it correctly)
midi described applies to USB A port, which expects external composite midi device,
but not computer connected. Move acts as USB Host.
On the other hand, it migt be that in Live control mode (USB C connected)
one can capture and use data sent from Move, but one needs to
analyse input, and I suggested that twice without any reply,
so I am out here...
P.S.
in case that it is not possible to activate control output without live,
one could plug cheap arduino into USB A port that acts as usb midi to din midi output or midi BLE device etc and use at least what there is .