Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
Vienna Ensemble tips
Last post Fri, Oct 26 2007 by Rob Elliott, 4 replies.
Options
Go to last post
Posted on Fri, Oct 26 2007 04:59
by fcw
Joined on Wed, May 11 2005, UK, Posts 153

Here's one to get started:

On Windows, shift-clicking on the name of an instrument or bus in the main VE window brings up a colour selector, which lets you waste at least fifteen minutes futzing with the colour of each strip.  (For some reason, I've always coloured wind instruments green, brass yellow, strings lilac and percussion grey in my sequencer, so it's nice to carry that over into the VE windows.)

Posted on Fri, Oct 26 2007 19:47
by Rob Elliott
Joined on Sun, Feb 02 2003, Salt Lake City, UT, Posts 1649

 Great tip.  Having 4 slaves on KVM - nice to 'see' right away which part of the library is siwtch on the KVM (I too have always had specific colors for insturments).   Although my colors are way better than yours Stick out tongue

Thanks again fcw

Rob 

(fcw - have another thread on this but how are you importing .fxp files from previous Vstack incarnations (given you used that).  And how are you saving the VE project - I can't seem to 'recall' the viframe files I save???) 

what would you attempt to do if you knew you could not fail?
Posted on Fri, Oct 26 2007 21:44
by fcw
Joined on Wed, May 11 2005, UK, Posts 153

I don't use Vstack, so I can't help you there.

As for saving the project, as a matter of course I save each non-trivial configuration of any plug-in in a templates directory associated with each project. I do this in case I decide I want to revert to a previous config, or I want to transport a set-up to another project quickly, for example.

So, I presently have vframe files for each of the four VE VSTs I've set up, plus an .nki file for the Kontakt 2 VST, in addition to the Cubase project file.

As it happens, I expect SX3 to save the VST configs as a part of the project, and it does seem to do that fine, but perhaps because I've explicitly saved them anyway, that's having an effect on the project save/restore mechanism.

Also, I've noticed that there is a timing issue of sorts: Cubase doesn't become interactive after loading a project until all the VSTs have loaded. Previously, this meant loading all the VI instances, so they were all ready to use once you got control of Cubase back, having just finished drinking your coffee.  However, now Cubase comes back before the instruments are ready, because the heavy loading is now in the external VE processes, which you still need to wait for.  Could this be what you're seeing?

Rob Elliott wrote:
Although my colors are way better than yours 

Yikes, tone it down, I can hear them from here. 

Posted on Fri, Oct 26 2007 22:05
by Rob Elliott
Joined on Sun, Feb 02 2003, Salt Lake City, UT, Posts 1649

Thanks - really just talking about my slave machines (running VE as stand alone).   I can save the 'project' fine but I have having the dickens duplicating a VI within VE (say I want two perf of a woodwind).  Or if I have 'performance criteria set up on a VI and I want to use that same one for a dozen diff instruments, etc.

Rob 

what would you attempt to do if you knew you could not fail?
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.