Vienna Symphonic Library Forum
Forum Statistics

194,425 users have contributed to 42,920 threads and 257,967 posts.

In the past 24 hours, we have 4 new thread(s), 11 new post(s) and 69 new user(s).

  • Backwards compatibility

    Hi,

    Ok. I have a project that uses VE 2. I am running 2 Mac Pros, one as a server and one as Nuendo machine with VE running beside it. A third machine also serves up another VE2, and this is a PPC Quad.

    The manual to VE Pro states that you can get VE Pro to load up your old projects. I can't seem to get this to happen. Is the idea that you leave the VE2 plugins in the sequencer, and connect it to VE Pro on the servers? This would be the only way to preserve the mix in Nuendo, and I am doubtful this is what is intended.

    Or does the manual mean: load VE Pro plugin in sequencer and connect THIS to VE 2 on slave?

    In Nuendo, if you remove a plug, you'll lose all your mixer settings in Nuendo.

    If anyone has managed to do this, it would be great if they would say how they did it.

    Many thanks

    Ben


  •  You can use VE Pro to load your old VE3 projects. You can't do the same trick with VE2.

    However, you can run VE2 and VE Pro at the same time, so at least you are no worse off than before VE Pro existed. [:D]

    DG


  • You can save the .viframe files in VE2 and open these files in VE Pro. There is no way to "replace" the VE2 plugins in your existing arrangement.


  • Thanks guys.

    I actually framed my question wrong - I am not using VE2 at all. Just VE 3 and VEPro. I was rather hoping I wouldn't have to:

    Load old project in Nuendo.

    Instantiate VE Pro plugin in Nuendo

    Save VFrame from VE3 to VEPro on Slave.

    Check it - outputs etc

    Copy tracks on Sequencer that currently address VE3.

    Paste to new tracks, all checked for MIDI/Ports etc to now address VEPro

    Carefully select all automation in Nuendo that was on VE3 tracks, and paste to new VEPro tracks.

    Done.

    Anyways - it seems this is the only way, and is really a limitation of VST. It's asking too much for VE3 to transmogrify into VEPRo!

    Thanks.