i thought I'd take a moment to share the successes I've been having with a workflow that I've had in place now for a few weeks... and this workflow has been most stable, and does NOT tempt fate by saving massive data back to protools.
here's the rig:
HOST: Mac G5 2.7 PPC, OS 10.5.8, 8gb ram, ProTools HD 8.0.1cs2
SLAVE #1: macbook Pro C2D 2.33 17", 3gb ram, OS 10.6.4, VE Pro 6853 32-bit server
SLAVE #2: AMD Athlon 64X2 4400X+ - 3gb ram - WinXP 32-bit VE Pro server v.6853
Gigabit (Cat 5e) hardwired to switch, static IPs all around
THE WORKFLOW:
1. Open a protools session.
2. Make 2 stereo auxes in pt - name the aux tracks "VEPro_1"; "VEPro_2"
3. instantiate VEPro plugins on the aux tracks - but DO NOT connect just yet.
4. Verify the VEPro servers are running on both slave machines;
5. make a NEW VE Pro instance, per slave -- NAME IT something appropriate.
6. IMMEDIATELY select the 2 default tracks and delete them (1 VI and 1 bus - this should not be there and VSL is encouraged to stop this practice - but that's the subject of a different thread)
6. Back in protools, now CONNECT to each NAMED instance from the 2 plugs
7. Immediately after connecting, select DECOUPLE in each protools plug
8. back at the servers, unselect the PRESERVE function
9. Save your project as... on each slave.
10. SAVE your protools session.
AT THIS POINT you are in good shape to continue working, without any saving issues from Kontakt or other plugs that save their data back to the host. Let's keep going...
If you were to CLOSE your protools session, then re-open it, it will RE-CONNECT to empty, default VE Pro instances. At this point, you must Open or load the saved VE Pro projects (viframe) per slave. ---> dialog box: "do you want to save changes to the project?" -- NO (Don't Save) and then choose the project for this session to load.
Done. Perfect every time. Don't forget to RELIGIOUSLY save your projects as you edit them in VE Pro, since there is ZERO data stored back in protools.
<rant> In a more perfect world, this workflow could improve with the following:
a) VE Pro would default to an EMPTY document on new instances, like every other app ever made
b) we wouldn't have to "don't save changes" on loading a document when there's never been a document opened
c) VE Pro would allow protools to link to a VE Pro viframe, and store the linked file location, but not the contents or the sample data (simplifying this process)
</rant>
I KNOW this sounds complicated, but it's the sure thing. I'm just about done with a 12-song mix that I produced and this workflow has been reliable as can be, and zero crashes related to Kontakl4 or other data rich plugs that all tried to embed their data in the protools session. If you have had any crashes related to saving a protools session and you have more than a tiny bit of VE Pro content, this workflow will be superior.
Hope this helps someone.
Best,
J