Thank you Karel. I am fairly new to VE Pro and am getting on well with it but my methods don't fit the template formula some have recommended. This is because of RAM. I have now 24 Gb but I feel wary of loading any more than about 5500Mb into VE Pro (should I be??). If I load a big template into say 3 instances that may seem convenient but I won't need most of the patches and it feels like an unnecessary load on resources. But perhaps I'm wrong.
My organisation of instruments in the instances has developed on a 'need it now' basis, ie I might have a flute in Ch 2, a violin section in Ch 3 and a Horn in Ch4, then a wind in Ch5 - you see the almost random structure building up. Each song needs a different set of instruments. So instead or preserving the instances (why? if they are usually different in each song) I resort to saving and loading Metaframes.
Hitting Save under File in VE Pro Server doesn't overwrite the file, but performs a Save As function, in that it asks me what I want to call it. Why? It does a Save (overwrite) if I Quit the app and it asks me do I want to save changes to the metaframe before quitting. Confusing to me...
Often if I quit the server, I get a crash report (the server app crashes on quitting).
Should this procedure work for me:
1. Fire up VE Pro.
2. Boot Logic and open a song with Instances
3 Load instruments into an instance if it's an empty one or let the saved one load itself.
4. Edit, add etc instruments in the instance.
5. Save the Logic song.
6. Save the Metaframe.
7. Close the song.
If I do this with every time, will the right data load into VE Pro every time I load a new Logic song or do I have to push the data to VE Pro using the arrow icon in the instance? I may have things confused, I know. By the way, I have read the manual, even if I may have missed something or not understood...