Vienna Symphonic Library Forum
Forum Statistics

191,403 users have contributed to 42,796 threads and 257,370 posts.

In the past 24 hours, we have 0 new thread(s), 14 new post(s) and 56 new user(s).

  • VEPro and audio units component are different versions.

    I have installed the latest version of VEPro but have noticed that the AU plug-in component did not update and is a different version number.  Is this an error on the part of the installer or has the plug-in simply been unchanged for a number of versions?


  • The version number will always update with a new version. Try using the included Vienna Ensemble Pro Uninstaller application first before installing a new version. While this should not be necessary, it should solve your particular problem.


  • I ran the uninstaller but it left the AU Component untouched.  Should I try again and manually remove the component and then install again?


  • It seems there is a problem with permissions on your system. You might want to consider repairing permissions with the Disk Utility. Removing the .component will indeed work as well.


  • Thanks for your help.  I have actually repaired permissions and uninstalled twice now.  The installer I downloaded does not seem to have an updated AU component, as it didn't replace v. 4.0.4881 and when I trashed that version it did not install any AU component. Meanwhile, the VST components are all the latest version.  Is this a problem anyone else has?  


  • The problem seems to be that the AU component doesn't install until after a restart but also might not install if the restart isn't right away.  I suppose this is probably the case for the uninstall as well, since, the old AU wasn't removed using the un-installer.  This is either a bug or VSL needs to inform AU users that a restart is necessary after the install.


  • The component is removed/installed immediately, without need for a restart. Something strange is happening on your system that prevents modifications to the components folder is my guess.


  • Or maybe there is a problem with the installer.  I haven't had this difficulty with any other update.