Hi all,
I have a weird problem with Kontakt 7 Portable.
If I play it stand alone with a midi keyboard it works perfectly.
If I load the VSTi into a host (Patchwork, P&M Chainer) the notes remain pressed on the Kontakt keyboard, as if they were also pressed on the midi keyboard.
I looked at all parameters and options but couldn't find anything.
Is it a strangeness of my PC only (Win8), or does it happen to others too?
And what can I do to fix the problem?

Thank you in advance for the advice

 

i also have this kind of behaviour in the old 6 portable versions .but using in standalone.
sometimes it happens sometimes it don`t. seems like the portables do not working 100 % as intended.

 

I remember having this issue with legit version, lol. If I pressed the same key again it went away (on K).. Idk if it's the same thing

 

I have seen this in past versions of Kontakt in SA and VSTi but not for a long time.

Does this happen when playing on 1 track?
Are you arming more than one track in Thru mode?
I wonder what ver. of Kontakt Portable are you using and what is your controller?
Are you using the latest ver. of Patchwork?
Does this also happen in a DAW like Cubase or Reaper or Bandlab or Studio One or Logic etc.?
Does using the ! MIDI Panic button at the top right clear the note downs?

I use Savihost with the x64 VSTi dll of K7P 7.1.5 just for practicing.
If a track is muted no incoming events are shown on Kontakt's on screen kybd.
It may be that your MIDI thru is switching from track to track and not sending key up midi events.

The GUI kybd shows events from the currently selected Kontakt Instrument.
If I have more than 1 instrument loaded and play the first one and hold a key down as I select the next instrument no keys are sticking.

Even if you have no problem with the Standalone there could be different behavior in the VSTi. For example some kybds like some Yamaha send Running Status which can cause problems. It may be filtered out in the SA but not in the VSTi. I am just speculating.

Maybe you could toggle or disable the GUI keyboard option in Options > Engine > Send MIDI to the outside world > Gui keyboard

Another possibility is a problem in your signal path. Make sure no loops are happening via MIDI Outs and Ins or through other MIDI devices. Patchwork may have some active MIDI Out options. I am not familiar with P&M Chainer.

 

You should debug MIDI messages with MIDI-OX or similar.

Easier to do than explain, but it should do something like
Keyboard-->MIDI-OX port-->Kontakt s.a. or host-->back to MIDI-OX
Check that note off bytes are sent/received.

You need virtual multiple MIDI devices like LoopBe or MIDI Yoke or similar.

Yes, for example mine sent active sense each 300ms making blink MIDI interface led, but it was no problem to Kontakt.
However there could be the option to disable it from the keyboard panel, or if not use MIDI-OX to filter it out.

 

Thanks for the reply.
I don't use DAW, but HD recorder (Korg D3200). PC and the VSTi are therefore only a sound generator,
The problem is with both KTP 7.1.5 and the latest 7.1.8. Does not occur with Kontakt full option non portable, and all the others VSTi.
If I click the Kontakt GUI keyboard the keys are released, but if I use the keyboard they stay pressed.
The keyboard is an M-Audio Keystation Pro 88, but I don't think it's the problem, because it works perfectly with all other Vsti in any host.
I think it's a specific bug to all Portable versions of Kontakt...

 

I have used all of the portables right up to the present one. Obviously as it is not installed certain software like Komplete Kontrol will not find files in the expected places. Other than that I think your problem is your host apps as I have never had that trouble with any portable version on my system. As the files live in the root of your C drive you might be able to work around by sticking things there. Symlink or something? OS Win 7 then Win10

 

i have that sometimes with legit kontakt too. mostly in spitfire libraries but happened in piano libraries as well.

also on a side note u-he synths do that a lot too. see if your daw or host has a 'panic button' that sends off-messages on all midi channels or whatever is the right way to call it. i press it frequently because something often gets stuck in one way or another

 

KONTAKT 7 SYSTEM REQUIREMENTS:
Windows 10 or 11 (latest Service Pack)

 

Not really for Portable version... from the included notes:
System requirements: OS: Windows 8+, CPU: SSE4, GPU: Open GL 2.1+, Direct 3D 11.1+

 

hum...
https://www.native-instruments.com/en/products/komplete/samplers/kontakt-7/specifications/
but you can believe anonymous reverser

 

There is no problem when you use Portable in standalone. So Kontakt is doing a great job of handling Midi input.
The problem only arises when you use Portable as a vst.
This means that the host is the problem, since in that case Kontakt no longer handles Midi In. The host does that.

You need to look at the way your host handles Midi In.
Are you using input via your USB? Or do you also have a Midi cable?

I use Kontakt Portable 7.1.6 on a WIn 7 system, both standalone and in DAW, and it works pefectly.
Windows version is NOT the issue.
I also have an M-Audio keyboard w USB connection, but I use a Midi cable, not the USB driver.
I only have the USB connected for power. The M-Audio USB drivers are tricky.

 

Last edited: Feb 16, 2023

The keyboard is connected to PC via USB cable. However it gives no problems on Kontakt 6, and no other VST or host. The problem only affects K7.
Playing K7 with the mouse on the VSTi loaded in the host, works fine; only using the keyboard does the problem occur.
Surely something is missing in the keyboard-host-K7 passage... I'll keep looking...

 

You're right, but I can assure that at least portable works also on one of my old win7 x64 system, however I had to change GUI to OpenGL, if not it crashes.
I didn't test it thoroughly, I'm not much into Kontakt, but I will test for the sake of curiosity.

 

minimum system requirements ensure full compatibility and stable operation of the application without any errors that can completely destroy what was intended.

my adx trax pro 3 sp also runs on catalina (it only officially works on versions 10.11-10.13), but if I decide not to transfer the file from the folder to the application window, but import it through the menu, the application immediately closes and all unsaved work disappears .

now is not 2003, when 2-3 updated dlls were enough to run the first versions of the vegas video editor on windows xp, which could only run on windows 2000.