Vienna Symphonic Library Forum
Forum Statistics

180,742 users have contributed to 42,140 threads and 254,362 posts.

In the past 24 hours, we have 3 new thread(s), 18 new post(s) and 49 new user(s).

  • NEW UPDATES: VI PRO 2.2.10738 and VE PRO 5.0.10738

    last edited
    last edited

    Hello everybody,

    Find these new builds, along with updated manuals and changelogs, in your USER AREA!

    All additions in 2012 have been highlighted in green in the manuals for your quick reference.

    VI PRO 2.2 main improvements:

    Reduced memory usage per instance, optimized voice sharing between all instances, enhanced GUI performance, and new control options are just some of the improvements that have been implemented by our developer team. => more info in your changelog and manual

    VE PRO 5 / MIR PRO main improvements:

    Added second microphone position, convenient grouping options, many bug-fixes, MANY new venue presets. More about the news for MIR PRO in DietzĀ“s announcement thread.

    Enjoy!


    Paul Kopf Product Manager VSL
  • Thank you Paul and the VSL team for the great support you all provide.  Looking forward to checking out the new features and performance enhancements.  Keep up the good work.


  • last edited
    last edited

    @Paul said:

    Reduced memory usage per instance,

    Whoa thats awsome and so timely. I'm currently running on 12 GBs of ram whilst I'm awaiting my other 12 to be replaced (corsair taking forever). I'm running a project with 72 VIs (only 28 so far loaded with samples - mostly optimized) which just before I Installed the new updates was running at 84% RAM and immediately after updates is running at 70%. Great result. Thanks VSL team.[:D]


  • First, thanks to the whole VSL for the latest updates!

    Just checking:

    The version number of the VI Pro update is 2.2.10674 but the changelog says .10684

    I assume this is a typing error....


  • Hi, 

    Yes, a typo. Sorry. Will be corrected with the next changelog. 

    Best, 

    Paul


    Paul Kopf Product Manager VSL
  • Paul or Dietz,

    Is there anyway to save a Room EQ Custom Preset in MIR PRO?


  • Not yet, sorry to say so. It's high up on my own wish list, too, but VSL software engineers had other priorities for this release.


    /Dietz - Vienna Symphonic Library
  • Thank's Dietz..... Will be a good feature when it comes.....  Have a great weekend....


  • Thanks guys!  Do you still recommend running all VI's in ONE big instance of VEpro server if possible?


  • Just to let you know, I am no longer able to do any Ableton automation mapping with this new VEP5 update. In the previous vesrion, I could do mapping but my problem was that whenever I tried to play back my recorded automation, "Back to Arrangement" would light up red, rendering the recorded automation useless in playback. But the new version has taken away the ability to even map any automation through Ableton, let alone record any.. Normally I would choose "Parameter x(eg. 1,2,3), and then choose a destination, such as Master Volume, and with the Ableton plugin "Configure" button lit it would populate those parameters in the Vienna Ensemble Pro plugin in Ableton's track view. Can somebody explain what I can do now to get this to work? Thanks, Ben

  • last edited
    last edited

    Hi svdutton, 

    @svdutton_8399 said:

    Thanks guys!  Do you still recommend running all VI's in ONE big instance of VEpro server if possible?

    Yes. 

    @ soundchemist: IĀ“m sure that Karel Bassez will look into this, please also contact us through  with more details (at least your OS, but also the used LIVE version and possible illustrating screenshots or short projects), so that he can reproduce this situation.

    Best, 

    Paul


    Paul Kopf Product Manager VSL
  • I can't get to specific but the latest update has crashed once per day since I downloaded it......well that's only twice but it's twice more than the previous version which actually NEVER crashed.

    I've noticed some "funkiness" when moving knobs and sliders on plugs. It's as if the mouse pointer has to be slightly to the side of the knob to make it react.

    First crash was moving a slider in a Waves plug, second crash was moving a slider in BFD2.

    Sorry I can't be more specific.

    It's just that VEP5 never crashed, and now it does.

    I will send crash reports.


  • Hi, I'm using Windows 7 and Ableton 8.3, aS well as 8.3b5.

  • Works just fine here. Which plugins inside VE Pro are you trying to automate? I tried with a couple of plugins without issues just now.


  • Hi Karel, I've tried automating The basic Volume and Pan controls found in the VEP5 channel strips into Ableton 8.3, after pressing the "Configure" button on the "Vienna Ensemble Pro" plugin, displayed in the Ableton track view. Also consider that in version VEP5.0.10370 I was able to see "Parameter 1-512" show up in the "Vienna Ensemble Pro" plugin window in the ableton track view. It just doesn't work in the newer version. I will send you an email with a screen capture.

  • I'm having a major problem in that I cannot load up a project saved with a previous version. I've updated on all my computers, done the eLicenser check and, whether in standalone mode or loading the project from the original song in Pro Tools, I get "the file you are trying to load was created with a newer version of Vienna Ensemble Pro". Clearly it wasn't so I'm pretty stuck at the moment. I can't load the viframe64 file separately as it just gives me the same message.

  • Could you send the viframe file to  so I can have a look at it? Thanks.


  • The WIndows version on my PC has crashed twice this morning with this version, which has not ever happend before. I am getting a message "Vienna Ensemble Pro has stopped working". As I am still unfamiliar wwith Windows, I do not know how to find the equivalent of CrashReporter.

    i am redoing an older Logic cue so perhaaps the Logic file is corrupted and causing this?


  • When did the crash occur exactly? Is it reproducable?


  • Turns out  it is a bad note in a specific patch in Hollywood Brass that caused it and EastWest is aware of it.