OKay Martin, thanks for clearing that up.  My VST3 version was separated from the other in my VST list and I didn't see it.

@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.

@Another User said:

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 would suggest to use a remote desktop solution.

@BloodyJoe said:

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.

If the server is empty, without any instances in it - it will load up as it was saved. Unless the instance was saved preserved - there will be no arrow visible.

No it won't be loaded as it was saved. In my example the Kore2VST is missing after reloading the cubase project. I first have to go in the VEPro instance and click on that arrow to select "Load plugin data". And no it was not preserved, not by me.

The behavior you are describing is no the intended one. Could you please send a report to support@vsl.co.at, include your system specs & software versions. I will have a look at it asap.

@BloodyJoe said:

No it won't be loaded as it was saved. In my example the Kore2VST is missing after reloading the cubase project. I first have to go in the VEPro instance and click on that arrow to select "Load plugin data". And no it was not preserved, not by me.

 I can't duplicate your repro properly, because i don't have Kore and I don't have any slaves. [:(]

However, using Local host and Kontakt everything works as expected and is connected on opening the project, so I think it must either be something about your system, or something about Kore that causes this problem for you.

DG

Ahah. That's a VST3 plugin. The way you're working you probably don't need to use the VST 3 version, as you won't miss any of the extra features.

DG

it happens here as well, been using the Vst3 version too.

Whenever i load up a cubase project, nothing is loaded in VEPRO (well the default template is loaded) and i get a arrow going on for about a minute, but furthermore...the arrow dissapears after a little while, so if im not paying attention or step away from the computer while its loading, nothing gets loaded up with the cubase project, so now i cant even launch a project and go do something else, i have to sit there and press these arrows? If i dont, then i have to reload the cubase project and hit the arrows.

I dont get it...keeping the contents loaded\preserved only really makes sense if you never ever adjust anything inside vepro?

Id like to keep the same template open when possible, but...theres a big chance i will adjust some paramter in one or more of the VSTI`s...and how will i know later..if i did or not, i have to take notes i guess (!)..of which project uses the default template settings or not?

Or always reload the plugin data, so im sure everything plays back correctly? ( by pushing the arrow button every time?)

OR make a habit of never ever adjusting anything in any vst instrument, lol...which doesnt seem very practical..

Hm, maybe im missing somethin ( i usually am) but that seems rather...unpractical.?

But anyway i love VEPRO tho...i really do, i guess there are some adjustements that has to be made from my side for it to work the way it was intended :D

@Another User said:

I dont get it...keeping the contents loaded\preserved only really makes sense if you never ever adjust anything inside vepro?

Id like to keep the same template open when possible, but...theres a big chance i will adjust some paramter in one or more of the VSTI`s...and how will i know later..if i did or not, i have to take notes i guess (!)..of which project uses the default template settings or not?

Or always reload the plugin data, so im sure everything plays back correctly? ( by pushing the arrow button every time?)

OR make a habit of never ever adjusting anything in any vst instrument, lol...which doesnt seem very practical..

Hm, maybe im missing somethin ( i usually am) but that seems rather...unpractical.?

The Preserve feature is one that has been requested for years by VSL users. Already I am loving it. I do exactly as you say; never adjust anything in the template. I don't need to. It works just the way I want it to. If I want to load extra stuff, I'll do that on a project by project basis, but the generally the orchestra is the orchestra, in my template. [:D]

DG

Well, i dont...i adjust release times for individual articulations, crossfades, cellcrossfades, etc etc, and not to mention kontakt and stuff like Omnisphere and more sound design based VSTI`s. NO chance the template wont be touched, so i guess its best to divide up the VEPRO instances in a way that makes it as easy as possible, so atleast not all of them needs to be reloaded.

BUT still, unless you make a habit of actualy writing down any deviation from the master template, how will you know later...if you made any changes or not ? You wont remember the details for every cue\song forever, ...so there potential for alot of weirdness and messy playback issues here. 

BUT i agree its a great feature, reminds me of the days of hardware samplers, and the conveniance of having stuff loaded up all day.

And in any event, its a feature, but one doesnt have to use it offcourse.

In the case of VEPRO not loading when opening up a cubase project, it might be worth mentioning that im still on Cubase 4.5 , on a vista 64 machine. I have to try the VST2 version as well..but i was under the impression VST2 cannot support multiple midiports, so that doesnt really work anyway.

Please post back when it is sorted out, and let us know what the solution was.

DG

Regarding this "load data" disappearing, I have changed the behavior now, so it simply stops blinking after 15 seconds. Will come with the next update.

@BloodyJoe said:

I already mailed the issue to the vsl support and got a ticket from Martin. Let's see if he/they can track down if that is a bug or if my system is just messed up. I'm also using C4.52 and that error seems only to occure with the VST3 plugin. It is neccesary because I will change up m workflow back to the cubase VSTRack and multitimb. And I like VST3!

I cannot reproduce this issue with either VST2 or VST3 plugins, using Cubase 5.1. Since both you (BloodyJoe) and Pzy-Clone seem to be on Cubase 4.5.X, looks like it is related to this system. Are you planning to upgrade?

@Another User said:

3. I'm using VEPro with cubase4. When I reload a project with some VST plugin VEPro server interfaces, the VEPro instances are not set up properly. I additionally need to click at that down arrow and then click on "Load plugin data" on every instance. Is that meant to be so? Is it possible to set that to automatic connect? I don't want to click every VEPro instance everytime I reload a big project.