Duplicates from endless encoders
is there a way to get the same value twice from an endless encoder to register in max
I used the displayMIDI patch i found here to see what was coming off my faderfox LV2
turning it steady one click at a time gives me 44 127 , 44 127, 44 127. which is what i want
i can see them there in the displayMIDI patch
when i try to use ctlin or midiin with a midiparse it doesn't register the new clicks if they are by the same amount, only when i turn it faster and get a 44 126 or the other way and get a 44 1, 44 2 etc...
how can i get the duplicate values to send as messages every time?
thanks
Take a look at the accum object. Not sure what your device outputs, but you could have clockwise values add 1 to accum, and counterclockwise values subtract 1...
\M
Endless rotary encoders don't send absolute midi values, but up or down
or better say clockwise - counterclockwise movement bundled with speed info.
So it is totaly device specific what midi data gets sent.
Read specs, midi implementation or whatever infos came with Your device.
Then You can bundle that with step up down counter or similar
Hey
yeah i have it working with a little simple patch in terms of it giving me 126 clockwise or 1 counter clockwise, that part is fine, however the problem is, if i send it a 1 clockwise, followed by another one (i.e. me steadily turning it clockwise) all my max input objects seem to only give the the first tick
so i get
44 127... and then nothing
whereas if i look at what is actually coming out of my controller using displayMIDI patch i get this
44 127, 44 127, 44, 127 (which is what i want, every click can then be used to turn a dial)
i.e. a 44 127 every time it clicks counter clockwise
i think somehow the cntl in or something is filtering out repeat CC values
Max midiin object does not filter incoming repeated cc values.
You have to go step by step, looking where that happens...
Maybe a mistake in Your patch ? Using change object somewhere ?
Hey Source
weird?
ive attached here
can you see anything that might be causing it?
at the moment im not getting any new messages in the print until the increment amount changes
so i could turn it 10 clicks but as long as they are the same amount, it will only register the first one
thanks
Do you send them from Max to Max? through physical midi? midiin/ctlin certainly has no problem to receive lots of the same messages. For ctlout this does not make too much sense but is working with a simple test:
set all midi ports to an IAC bus (I am on a Mac, don't know how to do this on a PC)
What is your concrete setup?
copy compressed your patch and paste it into the text here...
Here is simplest patch to test, based on Your info on 44 127 for up, and 44 1 for down movement.
thanks for these, however it isn't registering on any of them
i've just figured something out
it's running inside M4L and this definitely has something to do it it would seem. when i bring in the mididisplay patch (which registers repeat clicks in standalone) and copy it into M4L it doesn't register the extra clicks
this must be why right? is it maybe just picking up the CC value at any time? and not as messages?
can i get past this if it needs to be in m4l? (the whole thing is to control a dial that is also moved by other things, that is inside a m4l patch [i even bought the controller especially])
set up is this
endless encoder on Faderfox LV2 > MIDI > RME UCX > M4L device
You would spare our time if You say from the beginning what You are dealing with.
Max and Max for Live are not the same thing.
Max is not filtering midi messages if they are repeating.
Live probably does.
Apologies, didn't even click that that might be the problem
yes this actually appears to be a live issue
have found some externals that look promising now that i know what to look for
thanks for all your help