The pitch bend messages for MIDI 1.0 and MPE are identical (14 bit / 0-16383 resolution), just the usage of MIDI channels varies from one per instrument to one per note.
Thereâs nothing wrong with the pitch bend range. Typically MPE instruments have the much wider range (+/- 48 seminotes) as the former MIDI 1.0 instruments (+/- 2 seminotes). I donât understand what you mean with reversed scale. Just make sure that your VST and MG3 are set to the same bend range.
Because on your guitar you are very limited in bending. With 48 you end up in the 8500 region, whereas 1 or 2 gives you the 16383. All is fine, you canât bend 48 semi notes on the guitar. I donât understand your problem.
Now I see that the UI field for bend range is not for output scale (as it was in output section) but it is input bend range that guitar is able to produce. So fix that and place that field on input section.
You should learn logic, UI and language, dear. You sound consufsing.
This topic visitors talks too much about my guitar, my pitch band abilities and my tone.
I have not asked for that.
I am happy to be ignored with such volunteers, masters, whatever.
I am here to point up weak spots. Suggest a solution. And hope to get it implemented.
Calling it as abuse - just shows the way your mind is constructed. If you are not happy with that - I can give you an advice, but not for free and not on this forum.
The pitch bend settings work correctly and as intended in MG3.
To put it simply, and reiterate an earlier post, the bend range settings should be matched in MG3 and your target synth â end of story unless you have a synth locked at +/-2 semitones and you over bend the range, in which case you would need to physically bend within that range.
So, the âbend rangeâ of the Floyd Rose is basically irrelevant unless you over bend the set range.
New members are always welcome to the community. Please remember to communicate respectfully and in good faith.
Just for your story. As intended. But you donât get the point.
And story went further. Once again:
Troubles are next:
Mismatch UI logic for pitch bend range.
Developers need to move bend range settings from output section of UI to input section. Cuz depending on a view point it can be understood in both, but reversed way.
Right now it looks like when you set out range to +48 - you will output wide range. But actually not. Moving it to input will indicate that app will capture +48. And that is true.
MPE for monochroming mode instead of midi BND (channel) message.
Ha-lion 6 (which I use for vst 2 midi PC messages support in Ableton) responds to BND for all presets. It responds to MPE just for a certain presets. Thatâs how I have discovered an issue.
I used not to use MPE, as I use simple midi controllers. But MPE is obvious for guitar-midi polyphonic.
But since user want to use monochromic (for a bass) there is no need in MPE, and app is not sending BND messages at all.
To solve it developers need to add an option to output BND midi messages for monochromic mode.
Thatâs it.
And remember: respect is everything.
If you donât understand certain things - just ask. If you receive advices as disrespect - you donât respect yourself, right?
Halion 6 doesnât even support MPE in a proper way (no multi-channel pitch,no CC74,no per-note aftertouch, etc.). You inability to set up Halion has nothing to do with MG3.
You gave me the advice to learn the language, youâre probably right since I donât understand what you are writing.
The developers donât need to add anything; the users simply need to understand MIDI. Again: there is no MPE, monophonic, or polyphonic pitch bend information. Itâs all the same; please accept this fact.
@Hellem could you kindly point me towards a pitch-to-MIDI conversion system for guitar where there is any control of input bend range?
Of course, you cannot. Because it does not exist.
It would appear that you â despite your incredible abilities across the board â do not understand the generalities of the technology. Please refer to earlier responses to help you understand.
So you had about 1k visitors that you count as idiots. And all of them count you so too.
Statistically only 23 are real ones. I would say 26.
It explains everything. Write that statistic on your home page, please. So people will not waste their time trying to help. Also you will save some time from tagging unknown people as lamers (as you look really upset with that kind of activity) for self education in midi, logic, and in RESPECT
I knew why Akai, Ableton, Steinberg, Paint Audio, Remotify suxx.
This forum exists for MG2/3 users to discuss the software in a way that is testable, verifiable, and useful to others. Your participation in this thread has not met that standard.
You began with the claim âMG3 recognisez (sic) pitch but it sends it wrong,â presented as fact. It is not supported by evidence, and multiple experienced users have already explained why your interpretation is incorrect. Instead of engaging with those explanations, you dismissed them with comments such as âyou do not get the point,â told others to âlearn logic, UI and language, dear,â and posted a list of software that âsuxx" (sic).
This is not a misunderstanding but rather a pattern of behaviour:
⢠making unverified claims
⢠ignoring or rejecting technical correction
⢠responding with condescension and insults
That stops here.
If you believe there is an actual issue, present it in a way that can be evaluated:
⢠capture and inspect MG3âs MIDI output with a monitor
⢠state the exact MIDI mode and configuration
⢠provide full host/plugin details
⢠identify the precise, reproducible point of failure
If you cannot do that, then do not continue to repeat the same claim.
Further posts in this thread that are dismissive, insulting, or unsupported by clear technical evidence will be removed. Continued behaviour in this vein will result in loss of posting privileges.
This is your opportunity to reset and contribute constructively. I hope you will use it wisely.