Hello V.I.Cs, I developed a brand new VEP system (Beta in 2017) which is called "VEPro MULTI Instance". For example, you can load up to 16 Kontakt Instances (1024 MIDI channels with A.B.C.D Kontakt Ports) per VEP Instance and address/switch the articulations using any DAW regardless using VSTi 3 or AU 3 (it works with VSTi 2/AU 2 and VSTi 3/AU 3). By now I developed three MIDI switching types: • A Velocity KS# switching (works 100%), recommended for Cubase & Logic Maps. • A CC# switching (works 100%) with any DAW. • Program Change. It works with VEP loaded as a VSTi 2 100%. The VST 3 is in question here????? I have reported several times to VSL that the Program Change events cannot pass to the VEP 6 if you use VSTi 3. Now VSL announced that the Program Change response is fixed in VEP 7. I have tested that in VEP 7 using Cubase 10 Pro and it works. However it does not work in Reaper or may be in some other DAWs - I need to know which ones? Could you test VEP 7 as a VSTi 3 connected to your DAW and report if the "Program Change" are received in VEP 7. The Test Monitoring Example 1. Load a Kontakt in VEP 7 server and click the "KSP" icon in the Kontakt header to open the Multi Script MIDI FX processor user interface. 2. Go to (left pane), Preset => Utilities=> and load the MIDI Monitor utility. 3. Send a Program Change from your DAW and see if it is shown in the VEP 7 Kontakt MIDI Monitor utility. Please report negative or positive tests here and which DAW you use. Thanks in advance! BTW. Your replies here will be reported to the VSL team and I hope all will be fixed soon.