Pedro Lopez-Cabanillas

copyright years updated

Fix for GH ticket #27: Enable F10 key in Windows when using native filters

There is a specific message for F10 that causes this issue: https://learn.microsoft.com/en-us/windows/win32/inputdev/wm-syskeydown All other keys are reported as WM_KEYDOWN: https://learn.microsoft.com/en-us/windows/win32/inputdev/wm-keydown This will be fixed by this GH ticket: https://github.com/pedrolcl/VMPK/issues/27

Is VMPK indeed treating F10 differently from the other keys? Or is it a problem specific to my setup? VMPK does not process F10 in any way. The only function key with a predefined use is F1 (for help) that you can redefine in the shortcut editor. I don't think it is a problem with your setup. It affects Windows, but not other OS. I am not sure yet if it is another MS annoyance, or a bug in Qt.

fixed artifact name

allow manual workflows trigger

fix for ticket #24

This question is off-topic for VMPK. If you ask it here may be because: 1. You do not understand how MIDI works. 2. You do not understand what is VMPK, or what is Windows MM. Anyway, I can easily verify that WinMM works perfectly well with the Portamento messages. I assume that you know the MIDI controllers related to the Portamento effect: * Portamento switch, CC 65. * Portamento time, CC 5 (MSB), CC 37 (LSB). * Portamento control, CC 84. Here is a screenshot of several Windows programs, including:...