View Issue Details

IDProjectCategoryView StatusLast Update
0001403OpenMPTGeneralpublic2020-12-26 21:57
ReporterExhale Assigned To 
PrioritylowSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Platformx64OSWindowsOS Version8
Product VersionOpenMPT 1.30.00.* (current testing) 
Summary0001403: Velocity filter for MIDI note to keyboard shortcut assignments
Description

Hello and merry xmas guys...
I finally managed to test the midi to keyboard capability and it is glorious and I am convinced I will find ways to use it, but right now I am running into problems...
for example I have a mute button which I assigned to mute channel on transition but when I press the button it puts the squair brackets on only while I am pressing the button, I am unsure how to solve this, this mute button is assigned to f10 of the midi keyboard which is great because that is out of the range of the actual keyboard keys, but this leads me to my next example :
I have a play/pause button on the launch pad which is assigned to g6, and I set it to play from cursor. It is within the range of keys on the keyboard (it has an octave up and down button which will get my keys up and down even though I dont have the rest of the keyboard), so I press octave up once on my keyboard which turns my g5 into g6 and I press the g6 at any velocity and it plays the track... can I suggest if we are using midi keys to trigger keyboard controls it only registers if the key is pressed at full velocity? I know my launch buttons do that, and I think the same is true for other launch systems, that way we can turn the sensitivity of the keyboard up and get full volume without full force on the keyboard using the "record midi note velocity, amplified by [???]" in the midi tab of the setup and without triggering the keyboard commands we assign to the note.

I imagine working on things like this from a distance it extremely difficult Saga, so thank you very much for adding this feature in the 'snapshot' release and I am having great fun playing with it, but hoping we can iron stuff like this out before a full release :)

TagsNo tags attached.
Has the bug occurred in previous versions?
Tested code revision (in case you know it)

Activities

Saga Musix

Saga Musix

2020-12-26 20:08

administrator   ~0004570

Please please please don't write walls of texts in bug reports or feature requests. Write a concise description of what you want to do or what doesn't work. The back story is absolutely unnecessary in almost all cases and only makes it much harder to parse what you actually want. I tried to read through everything you wrote twice and I still have no idea what is actually the bug you are experiencing.

Exhale

Exhale

2020-12-26 20:30

reporter   ~0004571

Ok... I will try my best to be concise and precise here...
Assigning MIDI notes to keyboard commands works for all velocities, so if I hit G-6 at velocity 5 it is the same as hitting G-6 at velocity 126 (I think that is the highest midi keyboard velocity)
I suggest when keyboard commands are assigned to a midi note input they only work for the highest velocity.
I assigned my mute button (F-10) to 'mute channel on transition' keyboard command, and the brackets that show the channel will change mute status only stay on while I hold the mute button down.

I will post some more information of how these midi keyboard button presses look on MIDI-OX and MIDIKey2Key in a few minutes to give you more information that I think will help in a few minutes.

Saga Musix

Saga Musix

2020-12-26 20:35

administrator   ~0004572

Okay, so from my understanding there isn't a bug but the MIDI to keyboard shortcut functionality just doesn't work exactly the way you imagine it to work... The problem with generally restricting MIDI key pressed to full velocity is that this will not work with all MIDI devices. While it may be easy with your Launchpad to reach full velocity for a note, it is outright impossible on some devices (e.g. the Yamaha DX7 only has a MIDI velocity range of 0 to 100, if I remember correctly). So outright rejecting such MIDI messages cannot work as a general solution in OpenMPT.

Exhale

Exhale

2020-12-26 20:42

reporter   ~0004573

PLAY/PAUSE button
Midi OX (timestamp ignored)
IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
1 2 90 5B 7F 1 G 6 Note On
1 2 90 5B 00 1 G 6 Note Off
MIDIKey2Key
DATA | STS | CMD | CH | DATA1 | DATA2 | DESCRIPTION
805B7F| 80 | 80 | 01 | 5B | 7F | NoteOf G7 Velo=127
905B7F| 90 | 90 | 01 | 5B | 7F | NoteOn G7 Velo=127

MUTE button
Midi OX (timestamp ignored)
IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
1 2 90 55 7F 1 C#6 Note On
1 2 90 55 00 1 C#6 Note Off
MIDIKey2Key
DATA | STS | CMD | CH | DATA1 | DATA2 | DESCRIPTION
80557F| 80 | 80 | 01 | 55 | 7F | NoteOf C#7 Velo=127
90557F| 90 | 90 | 01 | 55 | 7F | NoteOn C#7 Velo=127

I am including this (and it took a while to type out by hand) because I think this is information you can use... I am not sure what most of it means most of the time

Exhale

Exhale

2020-12-26 20:43

reporter   ~0004574

"The problem with generally restricting MIDI key pressed to full velocity is that this will not work with all MIDI devices"
ok I see... so maybe another solution would be to set the velocity range?

Saga Musix

Saga Musix

2020-12-26 20:44

administrator   ~0004575

Maybe. But it would add a lot of complexity and it's unlikely to happen very soon.

Exhale

Exhale

2020-12-26 20:49

reporter   ~0004576

OK thank you :) I am sure I will find ways to make what I have work anyways... I was thinking of assigning some other keys to set modplug's octaves instead of using my octave buttons then I might get the result I am looking for, thank you for including this feature dude... I will just have to think a bit different to get it to work to my advantage. and merry xmas :)

Exhale

Exhale

2020-12-26 21:05

reporter   ~0004577

ok now my play/pause seems to be g7... this is so very confusing... also I tried changing modplug's octaves and the g7 on the keyboard still triggered play/pause... and I assigned the play/pause button on the keyboard to play/pause in ompt... it plays as long as I hold the play/pause or g7 button down then it pauses... unlike the traditional F5 keyboard shortcut which plays until you press F5 again... it is just very strange... midi keyboards man..love them and hate them XD
sorry I am trying to make this make sense but it doesnt make sense to me...

Exhale

Exhale

2020-12-26 21:57

reporter   ~0004578

anyways... I definately think this feature is a good step in the right direction for customising our midi keyboards' functionality in modplug, congratulations guys... :) unfortunately it doesnt seem to be a way for me to solve my problems without reaching into other software. the 'bugs' I mention above is the deal breaker for me... if I cant keep the keyboard functioning as usual and if I cant keep it playing the f5 way or mute/unmute a channel properly by hitting the button then this is unfortunately not what I am looking for... thank you very much for trying Saga and I hope you and everyone else have a good xmas.

Issue History

Date Modified Username Field Change
2020-12-26 20:05 Exhale New Issue
2020-12-26 20:08 Saga Musix Note Added: 0004570
2020-12-26 20:30 Exhale Note Added: 0004571
2020-12-26 20:35 Saga Musix Note Added: 0004572
2020-12-26 20:42 Exhale Note Added: 0004573
2020-12-26 20:43 Exhale Note Added: 0004574
2020-12-26 20:44 Saga Musix Note Added: 0004575
2020-12-26 20:49 Exhale Note Added: 0004576
2020-12-26 20:49 Saga Musix Summary Midi to keyboard input is buggy and I have some suggestions to get it to work better for lunch pads => Velocity filter for MIDI note to keyboard shortcut assignments
2020-12-26 21:05 Exhale Note Added: 0004577
2020-12-26 21:57 Exhale Note Added: 0004578