Re: [Lmuse-user] How do I get MIDI velocity to work?

[Robert J. <rj...@sp...>]

Hello again,

First, i reread your mail about how you edited the velocity values using the 
Velo On field. 
I just wanted to mention that there is an alternative way, which often is much 
easier. 
In the drum editor, click on [ctrl] so the events are viewed.
Select the drum you want to edit, all events for the drum should be visible in 
the Ctrl-view. Now try using the pencil tool (press D) to set velocity in the 
ctrl-view.

> > That worked.  However I found that even when I hit the pads very
> > lightly, the smallest velocity I could coax out of it was 103:
> > time:5361444 port:2 chan:1 NoteOn e1(0x28) 127
<...>
> > time:5361479 port:2 chan:1 NoteOn g#1(0x2c) 104
> > time:5361289 port:2 chan:1 NoteOn g#1(0x2c) 0
> >
> > This contrasts strongly with the way it behaves when I connect the
> > port to QSynth using Qjackctl.  Then I can easily get velocities as
> > low as 26, and I have to hit it hard to produce a velocity of 127.
>
> Odd. Definitely odd. I will do some more checking.

As I currently have no equipment apart from a computer I had to try and 
recreate this virtually using vkeybd for sending events to MusE and qsynth 
connected to ..nothing.

Using this method I cannot reproduce this. Whatever velocity I set in vkeybd 
it will travel through the drum track in MusE, and end up in the trace info 
for MidiOut.

The tests you have done. Did you start with an empty song or is it a song you 
are working on? 
Is it possible that you have changed the Velocity (or possibly Compr.) setting 
in the [Track Info] for the track ? If that is the case there's an 
explanation.
Velocity sets the minimum output velocity. If this is e.g. set to 100 all 
velocity values will be +100. Mostly 127 all the time.

Regards,
Robert