Vienna Symphonic Library Forum
Forum Statistics

178,804 users have contributed to 42,061 threads and 253,918 posts.

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

  • VEP 7.1.1245 MacOS project not loading bug still there

    Hi. This problem was introduced in version 1120 or something I believe, so my hopes were high that the iLok version had fixed this, but it isn't: If you load a .vesp64 file (double click it for instance) in MacOS, it will not load that project. It will just start up Vienna Ensemble Pro and then you have to manually select the project again to load it. Would be great if this could be looked into, thanks!

  • Yep, same here. It started happening to me with the VEP7 update back in October or November of 2021 (I can't remember the release version). 


  • +1.  Same problem.  Worked fine in MacOS PRIOR to 7.0.1120


  • Hi, 

    Working update just released. 

    Please click REFRESH in the upper right corner of your Vienna Assistant and install all available updates. 

    Really sorry about the inconvenience!

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • Awesome, Paul! Thanks for the quick update!

  • Unfortunately this is still not solved with version 1263.


  • Hi Simon, 

    Please send the details and ideally also the project to support@vsl.co.at

    Seems to work for everybody else so far, but there can always be exceptions. 


    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • last edited
    last edited

    @Paul said:

    Hi Simon, Please send the details and ideally also the project to support@vsl.co.at Seems to work for everybody else so far, but there can always be exceptions. Best,Paul
    VEP is surely now working! But it doesnt load the project when you double click/load up the .vesp file as it used to. If you double click a project, it just starts VEP (server). Nothing else happens. It is not project dependent. Happens with all project files.

  • Is this never going to be fixed? I would think it isnt too hard to re-implement.

  • the same problem on my system.


  • Bumping this up since VSL doesnt seem to notice/acknowledge the problem.

  • Same problem here. MacOs 11.6.5


  • Same here Mac OS 12.3.1 latest VEP. Version.I usually open recent projects so I did not notice. I think it has something to do with this VSL helper which seems run each time you open a .vesp file or also a VSL library in a plugin in a daw but which does not open when you click in the finder on the vesp file.


  • last edited
    last edited

    @Mavros said:

    Same here Mac OS 12.3.1 latest VEP. Version.I usually open recent projects so I did not notice. I think it has something to do with this VSL helper which seems run each time you open a .vesp file or also a VSL library in a plugin in a daw but which does not open when you click in the finder on the vesp file.

    Same here! latest version on iLok! Started for me when switching to iLok! Have to rebuild all my templates since it doesn't seem like VSL wants acknowledging this. Very disappointing from a long time user here!


  • last edited
    last edited

    @Mavros said:

    Same here Mac OS 12.3.1 latest VEP. Version.I usually open recent projects so I did not notice. I think it has something to do with this VSL helper which seems run each time you open a .vesp file or also a VSL library in a plugin in a daw but which does not open when you click in the finder on the vesp file.

    Same here! latest version on iLok! Started for me when switching to iLok! Have to rebuild all my templates since it doesn't seem like VSL wants acknowledging this. Very disappointing from a long time user here!

    It started before iLok. Also it has nothing to do with the need to rebuild projects, so not sure you are talking about  the same thing here....


  • Hi Simon, as I mentioned I first checked this when I saw your post and  I already had iLok installed at that time. So I cannot confirm that it was also an issue with the eLicenser, on my Mac. I am sure it was as you indicate. 

    I did find another a maybe related detail. When VEP is open with or without a file loaded and you click on a vesp file in Finder it does open up correctly in VEP.