hi folks, i have a 14 bit touchosc layout im trying to get working to achieve higher resolution on the fader, its just a single fader for now and it seems to be working and sending the correct format of data however when i map it in the mapping editor its very jumpy, much worse than a 7 bit normal fader i am going to post a video below so you can see what i mean, if anyone could point me in the right direction i would be very grateful
As you can see above the configuration is correct, its receiving the correct data, but i cant get it to work smoothly
7 bit is from 0 to 127. All midi controllers use 0-127.
Using high resolution will achieve 0-127 in a very short travel.
Not sure if this is the answer that you need.
Although a single MIDI Control Change value is 7 bits, two MIDI CC messages can be used in tandem to achieve a 14 bit wide value by employing them as a LSB/MSB pair.
2 Likes
I normally don’t use the mapping assistant but I did some quick tests with a controller sending Control Change MSB/LSB pairs and it appeared to work as intended.
How is your TouchOSC configured?
1 Like
while it seems to be sending the correct data im not so sure, its new to me ill post some screenshots so you can see, the script is not my work but the guy who did it asures me its correct
Looking at the data captured by MIDIOX, the jumps between values are quite large. This makes me think that your setup is probably correct but the input range is not great enough. For example, if your TouchOSC fader is 400 pixels in height, each input step (being 1px) will be converted to about 41 on the MIDI side. Could this be what is happening?
1 Like
When you send a 14 bit data, the data range will be 0-16384.
Unless there is some sort of scaling in between, a value of 127 will be reached with a very tiny fader movement. I am not sure if the OP is experiencing this.
Regards.
Im dont think the size of the fader in TouchOSC has any relation to that, as far as i know it is proportional , i could be wrong but i think not, it would make no sense, TouchOSC is designed to be used on all sizes of devices
if you look at the original post in the video you can see the min and max values are set to 0-16384. so i dont get what you are saying, my post is all about what you are asking if i am aware of, that is what i am trying to achieve, a higher resolution on the fader
It does. The smallest step you can move the fader on your touch screen is 1 pixel. Go the MIDI Monitor you had open in your first video. Move the fader on your TouchOSC device as slowly as possible and note the size of the each jump in the monitor.
1 Like
so you are saying if i make the fader bigger on my tablet it will move more smoothly?
Yes. The size of the fader travel range will dictate the smallest step/change once converted to MIDI.
MIDI_Range / Pixel_Range = Smallest_Step
Example with a 500px range fader using 14bit MIDI:
16384 / 500 ≈ 32 (step size)
2 Likes
Ah ok thats news to me, im going to look into this, thanks, just as a matter of interest where did you find this info?
I think you might be on to something there, however if thats the case 14bit is pointless in touchosc, i dont see any advantage or way to implement it in a usable way
Wasn’t found, it was concluded.
I don’t have any experience with TouchOSC I’m afraid. But even if you don’t get the full resolution of the 14 bits, it’s likely more than a 7 bit value, no?
1 Like
i guess so, 0-127 will have to do, maybe in a hardware controller it is better suited
if i can do you mind if i pick your brain on something else?