Re: [LMMS-devel] MIDI velocity handling

2014-03-06 Thread Vesa
On 03/07/2014 12:33 AM, 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), ke

Re: [LMMS-devel] MIDI velocity handling

2014-03-06 Thread Bill Y.
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 mid

Re: [LMMS-devel] MIDI velocity handling

2014-03-06 Thread Bill Y.
sorry, that should read 1-200% volume scale* On Thu, Mar 6, 2014 at 6:38 PM, Bill Y. wrote: > 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

Re: [LMMS-devel] MIDI velocity handling

2014-03-06 Thread Stian Jørgensrud
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 vel

Re: [LMMS-devel] MIDI velocity handling

2014-03-06 Thread Bill Y.
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: > Thinkin

Re: [LMMS-devel] MIDI velocity handling

2014-03-05 Thread Vesa
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 m

Re: [LMMS-devel] MIDI velocity handling

2014-03-03 Thread Vesa
On 03/01/2014 12:50 PM, Stian Jørgensrud wrote: > Will no instrument plugins be able to play above 100% volume or is it just > when you have activated MIDI or just Sf2 and VeSTige? > > I am strongly against removing support for >100%, at least for all plugins. > I would go for option 2, or even bet

Re: [LMMS-devel] MIDI velocity handling

2014-03-01 Thread Stian Jørgensrud
Will no instrument plugins be able to play above 100% volume or is it just when you have activated MIDI or just Sf2 and VeSTige? I am strongly against removing support for >100%, at least for all plugins. I would go for option 2, or even better, option 4. Option 4 - volume >100% uses a regular am

Re: [LMMS-devel] MIDI velocity handling

2014-02-26 Thread Nikko Rocksalot
Option 3 sounds best to me as a user, as it seems like it would be the most transparent to me. The idea of mapping everything as 0-127 a LA midi does sound like the best option in the long run, as not doing so from the start seems to be the cause of this issue. On Wed, Feb 26, 2014 at 5:07 PM, Vesa

Re: [LMMS-devel] MIDI velocity handling

2014-02-26 Thread Vesa
On 02/27/2014 12:58 AM, Vesa wrote: > I think I'd favour solution #1 - keep the 0-200 scale, map 200 to 127 > for MIDI instruments. Addendum: if we're concerned about backwards compatibility - let's just do it so that old tracks get translated into the new volume scale, so that for MIDI instrument

Re: [LMMS-devel] MIDI velocity handling

2014-02-26 Thread Vesa
On 02/27/2014 12:35 AM, Tobias Doerffel wrote: >> 2014-02-26 23:06 GMT+01:00 Vesa : >>> Would this mean, that the volumes in existing projects would be mapped >>> with a 0.5 factor, so that a volume of 200% in an old project would be >>> set to 100%? >> With solution 3, nothing would change except

Re: [LMMS-devel] MIDI velocity handling

2014-02-26 Thread Tobias Doerffel
2014-02-26 23:06 GMT+01:00 Vesa : > Would this mean, that the volumes in existing projects would be mapped > with a 0.5 factor, so that a volume of 200% in an old project would be > set to 100%? With solution 3, nothing would change except that you can't change the volume to values > 100% anymore.

Re: [LMMS-devel] MIDI velocity handling

2014-02-26 Thread Vesa
On 02/26/2014 11:36 PM, Tobias Doerffel wrote: > > - remove support for setting a volume > 100% for notes in piano roll > at all. Existing projects would load regularly so compatibility would > be kept. This would be the cleanest solution. > > Any opinions? > Would this mean, that the volumes in e

Re: [LMMS-devel] MIDI velocity handling

2014-02-26 Thread Tres Finocchiaro
For me, note volume is a very minor compatibility issue when migrating a project to the new version, if that helps. It's quick to fix volume via knob or fx channel, so if there were any negative impacts to backwards compatibility, I find volume to be relatively minor of one. The largest impact wo

[LMMS-devel] MIDI velocity handling

2014-02-26 Thread Tobias Doerffel
Hi, I'm about to deal with https://github.com/LMMS/lmms/issues/280 however we have a little problem here. Notes at volume 100% equal MIDI events with maximum velocity (127). For notes above 100% we can't map the volume properly to a MIDI velocity. This leads to problems in two areas: test notes in