@Paul said:
Hi Daniele,
Thanks, that's good information. Why doesn't VST3 work in Reaper??
The Event Input plug-in is really only a workaround for hosts that didn't offer VST (which are very few), I doubt that the VST version is used by many users (which is why this bug has gone unnoticed, I assume.
Please send me such a Reaper song to check: support@vsl.co.at
Best,
Paul
I have many VST3 plugin and they are all working in Reaper.
The main plugin (VST3 version, the VST one works instantly) is very slow on loading, it freezes Reaper for some seconds every time I load it in a track. Moreover every time I open the FX window Reaper freezes for sometime and then I could work on the plugin interface. This happens every time and this behavior was confirmed by another Reaper user on VI Control forum, so it is not only on my PC.
To replicate this it is enough to open a new project in Reaper, load a new instrument on a new track, select VEP7 main plugin VST3 and look what happens.
I'm not at home right now so I can't send you another template file but I already sent one at support@vsl.co.at
I don't know if it is a matter of track number or what it is exactly because it behaves very random, sometimes I hear the notes and sometimes not.
Yesterday I tried to put offline all the tracks except for one with main plugin and one with an event input connected to it and the first note worked, if I put online the other tracks (other VEP main plugins connected to other instances) and try to play more tracks at the same time some of them works and some other not.
About the Event Plugin I'm building my template like this (look at what I already sent you via support ):
Inside VEP:
Instance1
- Track: kontakt instance (1 for instrument), Port - 1 Midi - All Output 1/2
- Track: kontakt instance (1 for instrument), Port - 2 Midi - All Output 3/4
- And so on....
Instance2
- Track: kontakt instance (1 for instrument), Port - 1 Midi - All Output 1/2
- Track: kontakt instance (1 for instrument), Port - 2 Midi - All Output 3/4
- And so on....
Inside REAPER:
Track with main plugin VST connected to instance1
- Track: Event Input VST3 on port 1, assigned to instance1 receive input 1/2 from main and send to master (or a semi master or a bus)
- Track: Event Input VST3 on port 2, assigned to instance1 receive input 3/4 from main and send to master (or a semi master or a bus)
- And so on....
Track with main plugin VST connected to instance2
- Track: Event Input VST3 on port 1, assigned to instance2 receive input 1/2 from main and send to master (or a semi master or a bus)
- Track: Event Input VST3 on port 2, assigned to instance2 receive input 3/4 from main and send to master (or a semi master or a bus)
- And so on....
By doing like this I could use 32 ports on VEP and 64 audio channels (due to 64 audio channels limit in Reaper) and I see the parameter list on every track (for automations) with their names (last update add this 7.0.834).
If I route MIDI channels to main plugin I should stay always on port 1 and I could use only 16 tracks per instance (due to the 16 channels MIDI limit). Moreover I can't see automation parameters to automate them in Reaper.
There some connection conflict or some latency problem with the Event Input plugin that can't communicate correctly with VEP in some circumstances or configurations.
Maybe I'm doing something wrong but I don't see other ways to do this, let me know if I am clear or you need more.
I'll send you the updated template this evening after work (it is the same of the old one I sent you but I replaced more instruments with event plugin and added some main plugin tracks, I'm replacing the old one). In the meantime try to work on what I sent you and what I said you. I think you could find the problem more easily now.
Thank you.