Here is the thing. Midi is a two way street.. If some one uses LMMS as their sequencer, and makes volume changes in LMMS then sends that sequence data back out over midi, the music volume will clip. This would be highly undesirable. Instead it would be better to have the option to normalize the midi volumes so the external instrument can reproduce the actual track. The physical volume of the external device can then be adjusted to compensate. From a recording standpoint  if your track is mixed with a 1-20% volume scale, and then try and record a new midi tack, if it comes in at 100% it could be adjusted after, but it would be nice if you could play relative to the existing data, because it could impact how a person plays. Thus having a toggle for normalizing/over-driving the midi volume in my opinion is the best option that way the user can choose how they want to deal with the issue.

On Thu, Mar 6, 2014 at 5:33 PM, Stian Jørgensrud <> wrote:
Agreed. Thit is the best option apart from option 4: Simulating 200% by
boosting above 100 with an amp.

diiz 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.

View this message in context:
Sent from the lmms-devel mailing list archive at

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