VE Pro - quick "preserve" question

[TobiasWagner]

Hi all,

VE Pro works just great. No complaints. However, I have been trying to get a clear idea of how I can save all my settings to each logic session I use my orchestral template with. There are always little things I adjust within the VE Pro interface, such as loading additional articulations or setting pannings differently.

The idea is obviously not having to load the large template over and over again, yet recall each project with all individual adjustments. Say I make a few tweaks to fader settings in a VE Pro instance. Will I have had to have set VE Pro instances to "unpreserved" to save the data into my sequencer session? Will these tweaks be saved into my sequencer session regardless of the preserve-state?

Moreover it seems that I should generally stick to one option (preserved / unpreserved), as I will get a double instance count when loading a song with an unpreserved session while having the same preserved template still open.

The manual rushes a bit throuh the preserve section and leaves some aspects unclear.

Some clarification would be appreciated.

Thanks,

Tobias

[john_1332]

I had a similar confusion, and this is my understanding of it.  If it is incorrect I hope someone will jump in and correct me.

If you have two sequences built upon the same large template (1m1 and 1m2), you can make little tweaks and changes in the two projects.  When you close 1m1 and open 1m2 then the VE Pro window may disappear but the samples remain loaded in RAM. When you open 1m2 it will be very fast.

If you create a new session (1m3) that has never existed before, then you would preserve 1m2, create 1m3, link it to the VE Pros from 1m2 and then tweak 1m3.  The next time you open 1m3 it will open with your tweaks.

Seems to me if you make a template in Logic or ProTools that covers 90% of your sessions, then you'll never have to deal with the preserve feature at all, since a new session (1m3) would be made either from a "Save as..." from 1M2 or from the Template.

Does that sound right?

[Paul]

HI John,

that sounds quite right [:)], thanks for jumping in!

In short words: If you preserve an instance, it behaves like a stand-alone application (it doesn´t know anything about other programs). So if you are loading another song that had a similar template, but with a few differences (e.g., some more plug-ins), you need to reload the instance (with the "load data" button). The sequencer pushes the saved information to VE PRO and you can decide to load or discard the data. So your arrangement is always safe.

Now if you, as John says, keep an instance with your favourite instruments loaded in the background, loading will be much faster, as the samples are already in your RAM.

Best,

Paul

[TobiasWagner]

Thank you guys for the insight.

Paul, can I assume that a preserved instance is handled exactly like an unpreserved one when it comes to saving all the settings of a connected VE Pro instance into my sequencer? The only difference would be the handling of switching sessions / sequencers in that preserved instances stay alive and can be reconnected? Everything else behaves the same way, am I correct?

I am asking because normally Logic loads whatever was connected in that session into VE Pro without any problems (I have to click "load plugin data" in each instance). However [takes a breath], as of this early morning only one of my 3 instances loads correctly. The others opened connected and preserved, but with an empty document. This happens even though in my initial setup I had loaded instruments into all 3 instances. Not sure why Logic decided I wasn't going to write for brass or woodwinds. [*-)]

Lastly, when exactly does the "load Plugin Data" option disappear when I just opened a session? Does it simply time out? One time I somehow missed clicking on it, and I had to reload the session. Not a big deal, but I would just like to know whether this function is available only within a certain window of time.

Other than that I am very happy with VE Pro. Logic seems much more stable and I seem to get more processing power out of it loading my setup into one 64 bit host. Might be an illusion, but if so, it works! ;-) At the very least, it's an incredible time saver to work off one big template that stays up.

Thanks again,

Tobias

[Paul]

HI Tobias,

@Another User said:

Lastly, when exactly does the "load Plugin Data" option disappear when I just opened a session? Does it simply time out? One time I somehow missed clicking on it, and I had to reload the session. Not a big deal, but I would just like to know whether this function is available only within a certain window of time.

15 seconds, I believe.

Glad you like VE PRO. Stay tuned for the update, we hope to release it today.

Best,

Paul

[TobiasWagner]

@TobiasWagner said:

Lastly, when exactly does the "load Plugin Data" option disappear when I just opened a session? Does it simply time out? One time I somehow missed clicking on it, and I had to reload the session. Not a big deal, but I would just like to know whether this function is available only within a certain window of time.

15 seconds, I believe.

Hi Paul,

Thank you for the clarification.

You know, it would be great to be able to load session data retrospectively at a later point. Meaning, if I somehow miss the 15s window to click "load plugin data" I would still be able to load the data into the VE Pro server. The following scenario is very likely: You get up in the morning and fire up VE Pro and then your session. You go get coffee and the line at Starbucks, or whereever you get your beans, is longer than expected. You come back and you have to reload the session because of the session-specific tweaks in your setup.

Also, in Logic, instances of VIs are loaded in the order of channel strips (low to high). If I have all my instances of VE Pro at the top, it's a short wait, but if they are splattered across the mixer, I will have to sit there and basically watch it load. This is where I'd wish I could sync up the VE Pro server with my Logic session at a later point. Does that make sense?

Looking forward to today's update.

Best,

Tobias

[MS]

@Another User said:

Also, in Logic, instances of VIs are loaded in the order of channel strips (low to high). If I have all my instances of VE Pro at the top, it's a short wait, but if they are splattered across the mixer, I will have to sit there and basically watch it load. This is where I'd wish I could sync up the VE Pro server with my Logic session at a later point. Does that make sense?

The update will offer a "decouple" mode for the plugin, which might be interesting for your workflow. More information about this will come in the updated manual.

[TobiasWagner]

@Another User said:

The update will offer a "decouple" mode for the plugin, which might be interesting for your workflow. More information about this will come in the updated manual.

Aweseome. Can't wait to try it out. 😉

Tobias

[Sampling]

Hi, I'm confused about saving and loading instances too. I must be missing something. I'm using Logic pro 9 on a mac pro core 8 and snow leopard. When I open a new project or simply replace an instrument in kontakt 3.5, my ram is used up as thought the instrument or instance I have replaced is still open.So I have to restart my computer everytime i change projects. What am I doing wrong? Many thanks,, M.