@MS:
For example:
1. I start the VEPro Server, then Cubase with a new project. I load a "Server Interface VST" in that Cubase project in an instrument track. (So I can put many instruments easy in one audio channel)
2. I open the "Server Interface VST" with the "e" button in Cubase and click the connect button.
3. I choose 127.0.0.1 (new) from the list (master instance) or my slave computer (new).
4. I press the "ve" butto on that "Server Interface VST" to open the actual connected VEPro instance.
5. I delete the preexisting VSL Instrument track and right click select "Add VSTi" to add for example Kore2VST to the VEPro instance.
6. I set up the midi in Kore2 and load up some nice samples to get an fat sounding instrument.
7. Back in cubase I compose some nice melody then I save my cubase project and close everything because it is late nigt and I want to get some sleep.
8. Next morning I start the VEPro Server then cubase and load my project from last night. (in cubase only, I leave the VEPro server window white because cubase does the job and puts in the connected VEPro instances automatically!!)
9. Trying to play my melody, but no sound!! So I go to the cubase intruments track "e" button to pull up my connected "Server Interface VST" window. I click on the "ve" button to open my VEPro instance.
10. In that instance there is no plugin (Kore2VST) loaded. I first have to click on the big arrow and select "Load plugin data" to load everything back.
11. After that everything works again and I can continue composing.
Same goes for instances on slave computers but I have to go the the computer that is standing a little bit away and press there "Load plugin data"! Would be nice to control that VEPro slave instances from the main daw. At the moment I have to travel across the room to make some changes on the slave.
I hope you can follow my procedure.