Vienna Symphonic Library Forum
Forum Statistics

180,779 users have contributed to 42,141 threads and 254,364 posts.

In the past 24 hours, we have 1 new thread(s), 12 new post(s) and 64 new user(s).

  • VE Pro 7 (newest version for iLok)--Can't open older files

    last edited
    last edited

    Hi,

    I am running VE Pro 7, latest iLok version.

    Numerous older ensemble projects won't open. I get a message saying the file is invalid or inaccessible. I DO have the e-license software and USB key in the computer, so that's not the issue.

    What is odd is that these filetypes (Vienna Ensemble Project 64) are the same type as other files that open fine. Some will open and some will not. Also, some of the Vienna Ensemble Pro Frame 64 files open and some do not.

    I downloaded the VI Pro compatibility version but that didn't resolve it.

    I'd like to have access to these older ensemble files. Is it possible?

    Thanks,
    Jerry


  • Same question here.

    Is it not possible to have a co-install of iLok and eLicenser versions of VE Pro?

    I've tried reinstalling version 7.0.1120 but the installer is blocked saying a newer version (presumably iLok) is installed.


  • last edited
    last edited

    Hi,

    You always have to decide between eLicenser and iLok for each VSL software, they cannot run side by side.

    Working on the fix for this, should be there later today.

    Meanwhile, please uninstall 7.1.1249 with the UNINSTALL option in the Vienna Assistant, then roll back to 7.1.1245 manually for now:

    Mac VE Pro 7.1.1245
    Win VE Pro 7.1.1245

    Sorry for the inconvenience, new territory 😊

    Best,
    Paul


    Paul Kopf Product Manager VSL
  • Same problem as above.

    I was running 7.0.1120 (eLicenser) on my slave PC, but installed 7.1.1390 (iLok) ready for MIR Pro 3D.

    However, my existing projects refuse to load under 7.1.1390 (error message "The project you are trying to load is invalid"). I would have tried 7.1.1245, but the download link above no longer works, so I have been forced to revert to 7.0.1120

    The ability to load existing projects is more important for me than the new MIR features, but obviously I'd like to be able to access both (having just paid for the MIR upgrade).

    Is there a fundamental compatibility problem with the switch to iLok versions of VE Pro7?


  • Hi rogerdp, 

    This should all work juts fine by now. 

    Can you tell us a bit more about your system? Which OS, which sequencer, which plug-ins and versions are included? Did you make the full switch to iLok yet, in your Vienna Assistant => The "NOT INSTALLED" tab should be empty!

    Also, are you online with your music computer?
    => If you are offline, you will need your eLicenser key with the licenses connected for the conversion of your projects. 

    You can also send your project to us to check: support@vsl.co.at

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Hi Paul,

    Many thanks for your prompt reply.

    I'm using Logic on an iMac with 2 slave PCs (1 Win 7, 1 Win 10) running quite a complex orchestral template, but the problem relates to the Win 7 slave, where my VEP7 projects include a mixture of VI (eLicenser), Synchron (iLok) and 3rd party instruments, plus MIR Pro 24 (in inline mode).

    I've deliberately avoided migrating my VI libraries to iLok to minimise potential problems when loading legacy projects (and to avoid substantial migration work and drive space issues). So far, this combination of eLicenser & iLok authorised libraries has worked fine in 7.0.1120 but it sounds as though I would need to do a full migration to avoid problems in the new iLok versions of VEP7? I would need assurance that old VI projects would still load OK before going that far.

    My iLok and eLicenser keys are permanently connected to the PC and all my licenses are on one or the other so, although the PC is online, I don't think licence access is an issue here.

    I will certainly send a typical VEP7 project to your support team for further investigation.

    Thanks again for your help,

    Roger


  • Update:

    The errors only occur while trying to load older projects into the latest version of VEP7 under Windows 7. Win 7 is no longer supported and the same projects load OK on my Win 10 slave, so I plan to use Win 10 on both my PCs.