Couldn't we offer something like a normalize toggle that when checked scales midi input to fit the 200% range, but when uncheck scales only to 100%? That way people can choose how they want to deal with the problem on a per instrument basis.

On Thu, Mar 6, 2014 at 2:06 AM, Vesa <> wrote:
Thinking about this again, I'm starting to think it'd be best to just
keep native instrument volume as it is (0-200), keep the MIDI velocity
mapping at 100=127, and cap the velocity at 127.

This would mean that for MIDI instruments, volumes between 100-200 would
be exactly the same, but that's a minor issue. MIDI instruments already
don't support many things that native instruments do support (per-note
pitch bends...), and this way, >100 volumes would just be another thing
that aren't supported by MIDI-instruments.

This would to me seem to be the easiest solution for now - MIDI
instruments keep the default 127 velocity (no soundfonts sounding less
bright by default), native instruments retain the ability to amplify
notes beyond 100, it's a win-win.

Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
LMMS-devel mailing list