![]() |
#1 |
Human being with feelings
Join Date: May 2020
Posts: 12
|
![]()
Loaded up kontakt today and played on my keyboard and noticed my notes kept being "pushed down" in kontakt eventhough i am not playing on the keyboard. Yesterday it worked fine. I have updated to lasted kontakt but kontakt works fine outside of reaper when playing my keyboard in it.
Anyone knows why Reaper holds my keysdown after i let go on the keyboard? I tried my nano kontrolk 2 and mapped "keys" on it. It works fine to play on it, reaper does not hold the notes i play on nanokontrol |
![]() |
![]() |
![]() |
#2 |
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,983
|
![]()
It seems Reaper doesn't send MIDI note on events with velocity 0 (also interpreted as note off) to VST3 plugins correctly. You should be fine if you use Kontakt VST2 instead of VST3.
But this might need to be fixed on Reaper side. Justin, schwa, any clue? There's some weird behavior with these events even when we generate them from MIDI Event List. Just add any note on (say MIDI note 60) at velocity > 0 at 0.1.000, then add note on with velocity = 0 at 0.3.000 and see what happens. ![]() This will create a hanging note with Kontakt 6.6 VST3, but VST2 will work. But then if you reopen the MIDI item in MIDI editor, the second event will vanish, and length of the first event will be incorrect (1 beat instead of 2 beats, because MIDI note on with velocity 0 was placed at 0.3.000). Since we can actually assign a length to the note on parameter, I think the solution here is to disallow entering 0 as velocity value for note on events in Event List, AND also detect note ons with value 0 when importing MIDI files and converting them properly. Also converting them to note off with value 64 if they are received through MIDI inputs? Last edited by EvilDragon; 08-17-2021 at 04:55 AM. |
![]() |
![]() |
![]() |
#3 |
Human being with feelings
Join Date: Jun 2009
Location: Croatia
Posts: 24,983
|
![]()
Bump on this one.
Is Kontakt's VST3 maybe doing something wrong here too? Would be good to know. But it seems that Reaper also shouldn't be able to create note on events with value 0, considering it already has a "length" parameter for such events? |
![]() |
![]() |
![]() |
Thread Tools | |
|
|