Dirk Diggler wrote: Thu Feb 10, 2022 2:16 pm
The difference between 24 and 48 is twice the smoothness.
What kind of smoothness are you talking about and how it affects the pitchbends?
I tried to measure midi CC pitch values range with the Linnstrument's different bend ranges while sliding 1 same semitone and ended with this table:
2 range of 1 semitone slide 8192 - 11912 = 3720
12 range of 1 semitone slide 8192 - 8828 = 636
24 range of 1 semitone slide 8192 - 8588 = 396
36 range of 1 semitone slide 8192 - 8428 = 236
48 range of 1 semitone slide 8192 - 8350 = 158
So, having higher range decreases midi CC values range but didn't affect CC messages amounts, is this might cause less precision? Also would that cause higher jumps in tone between 2 neighbor CC?
Or it just scales within the numbers which actually you can't hear the difference thus there is no any smoothness (until it goes some really high bend range like while 1 step between midi CC could be more than 1-5% of pitch change)?
Imagine having 96 bend range and something like 10 CC values range so each message could send value like +-10% of semitone pitch change - that would just result as very segmented/truncated data, is that smoothness you mention?
That just seems to me the process like adding Moving Awerage to the CC data source making it less precise but removing the wide fluctuations, but I'm not sure that it works exact that way and actually removes the wider fluctuations, at least with the Linnstrument (yikes there is algorithms in the Linnstrument which tries to solve this with quantize/quantize hold but you lost control over the bend speed/precision with using of them).
And I just checked it, so I tried to slide from left to right for 1 semitone (~1 second bend length) and here is messages with 48 range which was received (I cutted some top and bottom values to shorten the list):
Pitch Wheel, Channel: 1, Value: 8275
Pitch Wheel, Channel: 1, Value: 8281
Pitch Wheel, Channel: 1, Value: 8288
Pitch Wheel, Channel: 1, Value: 8294
Pitch Wheel, Channel: 1, Value: 8299
Pitch Wheel, Channel: 1, Value: 8303
Pitch Wheel, Channel: 1, Value: 8311
Pitch Wheel, Channel: 1, Value: 8312
Pitch Wheel, Channel: 1, Value: 8320
Pitch Wheel, Channel: 1, Value: 8284
Pitch Wheel, Channel: 1, Value: 8289
Pitch Wheel, Channel: 1, Value: 8296
Pitch Wheel, Channel: 1, Value: 8298
Pitch Wheel, Channel: 1, Value: 8299
Pitch Wheel, Channel: 1, Value: 8303
Pitch Wheel, Channel: 1, Value: 8304
As you can see there is jump 8320 -> 8284 in the middle while I was crossing the pads notches.
Which is actually sudden back jump ~23% of semitone.
Also recovery after jump to 8320 was took like 15% of bend time and it's easily noticeable by the ears.
I don't have such jumps in the Velocity KB and with MIDI Guitar 2 while bending.
Dirk Diggler wrote: Thu Feb 10, 2022 2:16 pm
iPad surface does not allow any velocity for touch.
There is screenshot of the notes velocity recorded with iPad's Velocity KB midi controller, as you can see they are not constant. Also there is some settings in Velocity KB related to the velocity detection/sending range so it could be adjusted (I think it's using the finger's touch dot diameter/size to apply the volume or something like that).
Dirk Diggler wrote: Thu Feb 10, 2022 2:16 pm
Midi Guitar is great for what it is, I've been using it since it was beta.
I still don't love it's handling of bends.
Agreed, it's not perfect and needs some additional approach (like adding string dampener which I don't have), but it's best solution that I ever tried on the guitar related to bends audio2midi converter.