I'm testing VEP 6 in Bitwig 2 on Windows 10. The way I set up tracks, I have the main VEP Pro plugin on one track, with all outputs muted. I then make a Bitwig 2 track for each VST instrument on VEP. Each of these Bitwig 2 tracks has and VEP event input plug, followed by a Bitwig 2 Audio Receiver that extracts its audio from the main VEP Pro plug. This way, I have individual BW 2 tracks that behave very closely to what I would have if the VSTi were inserted directly in the host as usual: this track can be individually routed and it carries its MIDI clip around as expected. Note that in this setup the main VEP Pro plug doesn't receive any MIDI input at all.
All the routing works, except that if I let the DAW sit idle for a while, VEP becomes unresponsive. Nothing comes out of it unless I send some MIDI to the main VEP Pro plug. It then wakes up and everything is fine. So I made a quick BW2 widget that sends a CC message to the VEP Pro plug every measure to make sure it stays awake. It works. I'm just curious if this is expected behavior for VEP 6. Does it happen with other hosts, or should I report it as a bug to the Bitwig devs?