Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Velocity response bug #280

diizy opened this Issue Feb 7, 2014 · 6 comments


None yet
4 participants

diizy commented Feb 7, 2014

Seems to affect all velocity-sensitive instruments.

Seems like velocity goes normally from 0 to half-velocity (normal), if you go over half, the instrument doesn't louder, instead the velocity curve "starts over" from 0 and goes again to half volume near the top.

So the velocity response curve is "doubled", so that instead of going from 0 to 0.5 and then 0.5 to 1, it goes 0 to 1 and then 0 to 1 again.

I'm not sure if I'm explaining this well. To reproduce, open up eg. triple osc, edit a pattern in piano roll, add a note, adjust the velocity of the note and listen.

I'm not sure if this is exactly how, but I can confirm that velocity has been acting weird.


Sti2nd commented Feb 8, 2014

Confirmed. While editing in the Piano Roll 101% sounds the same as 1%. While playing it sounds normal.


diizy commented Feb 19, 2014

This is still an issue: right now, the volume caps at 100%, in editing, and doesn't go all the way to 200% as it should. In playing it sounds normal.


tobydox commented Feb 24, 2014

FYI: working on a fix.


Sti2nd commented Mar 1, 2014

Option 4

  • volume >100% uses a regular amplifier, and 0-100% corresponds to MIDI velocity 0-127. So the user would have the exact same options as before, but above 100% you aren't changing MIDI velocity, you are changing volume gain.

@diizy diizy added this to the 1.0.0 milestone Mar 4, 2014


diizy commented Mar 4, 2014

Option 4 isn't possible.

Marking this for 1.0.0. since this is already being worked on.

@diizy diizy added the bug label Mar 6, 2014

@tobydox tobydox closed this in 0ca3901 Mar 8, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment