Vienna Symphonic Library Forum
Forum Statistics

182,231 users have contributed to 42,213 threads and 254,717 posts.

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

  • recurring "newer version" problem

    I've been having this odd problem on and off for a long time, over many versions of VEP, and am wondering if this is a known issue at all. It's not deadly, but very irritating. I work in Digital Performer 7.24 and a Mac Pro. The bulk of my VSL library is on a slave PC, Windows 7 Professional, with all the sample libraries on SSDs. Both computers have heaps of power. Normally, everything works perfectly. But then...

    So I'm currently working on a feature film and have about 30 different "chunks" in DP representing different cues of the film. There's a lot of live audio tracks and the occasional virtual instrument in the main sequence, but most of my virtual instruments are in a V-rack as most of the film uses the same basic template. I have an 32-bit instance of VEP in there hosting GVI on the slave machine, a 64-bit instance hosting 16 VSL instruments using MIR on the slave machine, and Vienna Imperial on the host computer.

    I've been working on this project happily for several weeks, then today left everything running when I went for some lunch. I can back, and the 64-bit VEP was disconnected. When I tried to reconnect, I got the error message on the PC, "The project you are trying to load was created with a newer version of Vienna Ensemble Pro. Please download and install the latest version at..." I have the latest versions of everything on both machines. Other projects open fine, but this one doesn't. I tried restarting both machines, but the same error comes up when the project tries to open.

    I went to a backup of the project file. That opened fine. I saved the 64-bit instance as a viframe, closed the backup project. Reopened the main project. Got the error. Dismissed it and loaded the viframe, and everything works fine.

    So like I said, it's not deadly. As long as I keep project backups and/or save viframes of every project as I go, I can recover from the error. But if there's any way to avoid it, that would be much preferred! I suspect it has something to do with DP as the project file gets larger over the course of a big project, but I don't know. Any ideas would be appreciated.


  • I'm having the same problem running with Pro tools even on small projects. I have reinstalled the latest VEP to no avail. Like you I have had to open a saved project in order to run it.

  • last edited
    last edited

    @didger said:

    I suspect it has something to do with DP as the project file gets larger over the course of a big project, but I don't know. Any ideas would be appreciated.
    So, I guess you're leaving the VEP coupled with DP? That is a bizarre error, I have never seen that and I have projects that were in fact created with a newer version and reverted to the previous version... but I would advise decoupling, for a couple of reasons aside from what I see here.


  • It's true I've never even bothered to learn how to use decoupling and will look into it, but in the 9 months or so since I posted that, the problem has gone away. I don't know if it's VSL's upgrades or DP's, but it hasn't happened to me in a long time.

    So sorry, JBova, for the moment it seems you're on your own!


  • The same problem just occurred on my system after I added a soprano sax.

  • Hello umarekawaru,

    Which versions of VE PRO /VI / VI PRO are you using, on which OS, in combination with which sequencer?

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • VE/VI 5.3.13408 VI PRO Standalone 2.4.13135 ( will update today) Mac OS X 10.8.5 Logic 9.1.8