Vienna Symphonic Library Forum
Forum Statistics

181,978 users have contributed to 42,198 threads and 254,643 posts.

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

  • VE PRO 5.1.11947 available

    last edited
    last edited

    Hello everybody,

    a new version of VE PRO 5 is available in your User Area.

    Changes include improved connection times between master and slave machines, more details in the changelog.

    Enjoy,

    Paul


    Paul Kopf Product Manager VSL
  • Hi Paul.

    Thanks for the update! I hoped this would have solved the slow connection speeds on my end, but unfortunately not.

    I am trying to figure out what makes connecting slow and what doesn't.... I am on a Mac Pro with Logic, and I have once slave connected using DHCP with a fixed IP. It seems that connecting/disconnecting to instances of VEP that have many plugins, as well as whether it is a slave or a local connection.

    Local:

    E.g. I have an instance that has just one Kontakt 4 instance inside. Connecting is instant and disconnecting takes about 1,5 seconds.

    Then I have an instance that has 1 instance of Kontakt 4 and 11 instances of Kontaktplayer 5 - connecting is instant, but disconnecting takes 13 seconds!

    An instance with one instance of PLAY connects instantly but takes only 1 second to disconnect.

    Slave:

    Then I tried the same to the slave instances which all just have 1 Kontakt 4 or PLAY. Connecting takes about 8 seconds for PLAY, 5 seconds for Kontakt, disconnecting takes about 3. So I can see how connecting my 12 slave instances and about 15 local can take quite a while. Unfortunately this used to be much faster with VEP4 - something seems to have changed in the network department that makes VEP5 much slower in this regard.

    I even tried creating a closed network with only the Mac Pro and the one slave connected and I got the exact same figures, so that is not where the problem is.

    Anyone who has much faster connections than I do?


  • yea a bit on topic but not much i have a mac pro 12core running pro tools 10 native and i want to stream 48 audio tracks into pro tools on that mac machine from a slave pc also running pro tools 10. what i would like to do is put a nebula plugin on each of that channels running a console emulation and a tape emulation and i would like to do that on the pc in vep5 because NEBULA is VST (no RTAS, AAX) only and also very(!) processing intensive, so i would like that taken of before it hits the pro tools. then i would like to use VEP5 on the mac to send the audio coming from the pc into pro tools. the realness of nebula blew me away and all plugins sound like toys compared to it. complicated angedachtes setup, i know, but this would be my perfect setup ever. i dont care how much cost machine wise is involved its way cheaper than the real consoles and tape machines :)

  • Thanks! I'm noticing the improvement in connection time.

    @Simon I had some sluggishness going on with the last few versions and after I rescanned all plugins on my slave, things went back to normal.  I hope you'll solve it. 


  • Lennert, thanks for the tip. However I can't see how rescanning plugins could affect connection times, since everything I do is decoupled connections. I tried rescanning though just to be sure, but it didn't make a difference. Still a slow 5-8 seconds per instance on the slave.


  • Using Cubase 7.0.1 64bit, Win7/64, with VE Pro 5 and Play 3.0.40 on a slave machine - after an unknown amount of time, playback will begin stuttering heavily on the slave machine. VE Pro has not crashed completely, but task manager reveals that CPU usage is at 99% for VE Pro, thus crippling the computer (takes 30+ seconds to click the mouse and have it register).

    This has happened several times, and again, it seems to happen at random times during playback.


  • Does the latest 5.1.11947 update include Any improvement on tempo sync in tempo based plug ins receiving sync/tempo info INSIDE VE PRo and slaved to DAWS like DP? etc. For example, ALL tempo synced VI’s go OUT of sync when VE is set to anything above “none”. So, if I have a midi loop to audition in, NI Studio Drummer, Superior drummer, etc, or, I have a looped pattern inside Stylus RMX to sync, I have to have VE set to “none” for those loops to be in sync with DP. 1x, 2x, 3x, 4x all result in the internal loop based VI getting more and more out of sync. I reported this long ago and have heard little more about it. So, please answer specifically if you can: 1) is this issue addressed in the recent update? 2) Have you guys verified this as a problem? 3) Is it a VE issue or is it specific to Digital Performer? 4) Is any sort of “fix” in the works? This is VERY important to me. Thank you for your attention, David PS. It appears your changelog has the wrong year for the latest update. It says 2012, should read 2013.

  • I assume you're working with DP7, which doesn't have any latency compensation for instrument plugins (such as the VE Pro plugin). Update to DP8 and things should be in proper sync.


  • I am running DP 8.01. Please verify this problem if possible. It really sucks to lose all the 4x buffer advantage when trying out drum loops and using tempo synced VIs. Best, David (DP 8.01, OS 10.6.8)

  • Hello! This is my first time posting to the forum! I've read them many times, but never had to post until now. I recently updated to VEPRO 5.1.11947 and up until I installed the update, Ensemble Pro 5 was the sturdiest piece of software out of everything I own. But for the first time, I am experiencing some really wacky stuff... All of a sudden, my slave is taking twice as long to load my 64 bit template, I will go to access a channel in my DAW, (CUBASE 7) and it just won't be there and when i click on the (EAST WEST PLAY) plug in within my Vienna EP5 window and it will reload the samples.... Like all of a sudden, I'll lose Cello, so I'll go to my slave and click on my HollyWood Strings Plug in for Cello and instead of opening the plug in, it will re load the Cello. Also, half the time my DAW will not even connect with my VEP5 instances, but instead, there will be a new instance below for every one I've created that just says VE Pro 5.1.. So I'll see... Woodwinds (64-bit) Brass (64-Bit) Perc (64) Vienna Ensemble Pro 5.1.11947 (connected to localhost) Vienna Ensemble Pro 5.1.11947 (connected to localhost) Vienna Ensemble Pro 5.1.11947 (connected to localhost) Or something really close to that.... None of these problems happened before I updated my Ensemble Pro 5 software. Could I have maybe not done it correctly? Is there something I need to do maintenance wise that I might have missed since I updated? Is there an uninstaller? Should I reinstall? Will my templates still work after? Anyway, just having a really hard time working since I updates the software and was looking for anything I might have done wrong, since a strong VEpro 5 is vital to my workflow.... Thanks, Chris

  • Similar problem here (though I'm not using the server connection - using ASIO with a Lynx AES16e).  After loading template, whenever I try to open Kontakt 5 or Play plugins, the samples start reloading.  Reverted back to 5.1.11548 and all is back to normal.


  • Thank you but now I'm wondering why something different is happening on both my external PC DAWs. After completely loading a metaframe I created on an older version of VE PRO, when I double-click on a channel that has plug-ins loaded, i.e. East West PLAY with Stormdrum 2, it will completely re-load all the sounds in that particular plug-in/channel. It will do the same for all plug-ins I have instantiated.  I've rebooted, loaded different metaframes, various plug-ins from different manufacturers and have the same issue on all of them.  Is this functioning as normal for this new version of VE PRO?


  • Hi, I also have problems after the update. Within Sibelius 7 my playback configuration doesn't work anymore and rebuilding it doesn't work either. When I try to connect instances to my (virtual) 64bit server it says that the version is invalid. What's going on here?


  • Hello Heike!

    I guess you have copied or moved the file "Vienna Ensemble Pro x64.dll" from your previous installation and now are trying to connect the old plugin to the new Server version. This cannot work. It is not recommended to move or copy plugin files, but rather to setup effect folders in your host software.

    To get things back to work again, I recommend the following procedure:
    - Uninstall Vienna Ensemble Pro.
    - Search your hard disk for remaining files "Vienna Ensemble Pro.dll" and "Vienna Ensemble Pro x64.dll". Delete these files.
    - Reinstall the latest version of VE Pro.
    - Remember where you install the 64-bit versions of the Vienna Ensemble Pro plugins.
    - In the Sibelius 7 Audio Engine Options/Virtual Instruments and Effects folders menu add the folder where you have installed the VE Pro 64-bit plugins.

    Best regards,
    Andi


    Vienna Symphonic Library
  • Thanks for your swift response Andi! I now saw the problem: when updating, the VSL software always automatically displays my personal VST folder, and I'm used to not really looking when accepting the choice. But this time it displayed another (standard) location and so I acepted wrongly. It's solved now, I'll have to be more alert next time!

    Best regards, Heike


  • Samre problem here....did we get a response???   I think I have to go back to an older version.  Is there an update to address this coming soon?


  • I'm also experiencing this "re-loading" issue.  Specifically with Kontakt 5.  Any time I click on a Kontant instance, VEP begins to re-load all the samples.

    I'd rather not revert to previous version if possible.  I've made a number of changes to my template in the past week, so "going back" would be a pain.

    One additional note, there are times when this "re-loading" will simply crash-midway through and purge the entire Kontakt instance.  (I'm running a pretty huge template, roughly 48 gb, so I'm sure that's contributing to said crash.  But the crash wouldn't happen if VEP was constantly having re-load the samples back into the memory every time I clicked on a plugin.)


  • We are aware of the "double-load" issue, and have already fixed the problem. We will release a new VEP version asap.


  • Hi Martin - can't seem to find how to enable my PC with VEP 5 installed, licensed and setup, to be seen on my Mac host running Logic...

    The Mac localhost VEP is detected, but the PC, connected to the Mac via gigabit ethernet, isn't seen when running the Server apps. Can only load the localhost VEP in Logic.

    Sorry for the newbie question - I'm new to VEP and have read lots of tutorials but can't seem to get the Mac VEP to see the PC VEP.

    Thanks for any help with this !

    Best,

    John.


  • This may be elementary, but did you launch VE Pro Server on the slave? Before, when it hasn't shown up on my slave, I've forgotten to actually launch the VE Pro Server app.

    Just a thought.

    Mahlon