Vienna Symphonic Library Forum
Forum Statistics

180,809 users have contributed to 42,142 threads and 254,365 posts.

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

  • New Updates available: Vienna Instruments PRO 1.0.6844 and Vienna Ensemble PRO 4.1.6844

    last edited
    last edited

    Hello everybody,

    Thanks to our super-quick development team, the first updates with quite a few minor bug-fixes and cool additional features are already available in your User Area.

    Changes for Vienna Instruments PRO include a new brightness control application for Vienna Instruments PRO [:)], the "loop bug" is also fixed. Of course, an updated manual is also available.


    Changes for Vienna Ensemble PRO include "Convert to Vienna Instruments PRO" feature and the crash when deleting VI PRO instances is also fixed.

    More details are available in the respective changelogs in the User Area.

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • The "Convert to Vienna Instruments PRO" feature works very well. I was just wondering how on earth would I change all my VIs to VI PROs and the I read this announcement. [:)]

    Would it be possible to get a "Convert single instance to VI PRO" feature to the VE PRO to be used before the VI PRO gets ready to completely replace the basic VI? I have a problem with the VI PRO using too much CPU resources. I have a VE PRO instance with 61 VIs loaded at the moment. I converted the instance to VI PROs and it became unusable because of the considerably higher CPU usage. Everything went back to normal when I reloaded the old VIs. The slave has an Intel Core 2 Quad processor.

    Are the high CPU requirements for VI PRO a known issue? I know it has a lot of features but at the moment it takes several times more CPU than the basic VI.


  • Hi info,

    to convert one instance from Vienna Instruments to Vienna Instruments PRO, simply save the preset in Vienna Instruments, then load the same preset in the new VI PRO instance [:)]

    VI PRO needs some more CPU, but I can´t see "multiple times" the CPU usage of Vienna Instruments on any of our computers, to be honest.

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • Hi Paul,

    I tried installing VE Pro 4.0.6844 (you called it 1.0.6844, which, I think, is a mistake) but it wouldn't install and the message was I have to update my elicenser.   I did uninstall 4.0.6150 first, perhaps I should just install the new version over the old one?

    Best,

    Jerry


  • last edited
    last edited

    Hi Jerry,

    no mistake, the version number of VE PRO is 4.1.6844, the version number of VI PRO is 1.0.6844. These are two different programs.

    As always and with every update or new product, please update your eLCC.

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • last edited
    last edited

    @Another User said:

    VI PRO needs some more CPU, but I can´t see "multiple times" the CPU usage of Vienna Instruments on any of our computers, to be honest
    The CPU core running the VE PRO instance went from 25% to 100% and the VE PRO CPU meter from 10-20% to 80-90% when I switched to the VI PROs. I couldn't play a single flute without hickups. The system is Vista 64, Q6600, Asus MB and 8 gigs of RAM. Doesn't get much more average than that.

    Also the new VE PRO 4.1.6844 crashes on my only 32-bit XP slave. When I try to add an instance from the DAW or from the VE PRO on the slave it crashes. It worked fine with the previous version but that doesn't work with the latest version on other systems. I tried removing the VE PRO and reinstalling but that didn't help.


  • Yeah, I just updated on 2 machines... it works fine on Win 7 x64, but crashes on startup of VEP every time on WinXP x64 .. can't get it to run at all. I updated VEP and got the demo of VIP both today. -Russell

  • Hi Paul,

    I have to disagree with you.  I'm looking at the new release as I write.  Vienna Ensemble Pro on the Mac is saying V4.1.6844 in the 64-bit server window.  The Stand-Alone Vienna Instrument Pro is saying 1.0.6844 on the top.  When Vienna Instrument Pro is loaded into VE-PRO, the version at the top right is saying 1.0.6843 next to the word version.

    Also I think the new release just broke Pro Tools.  A couple of hour ago I finished a completely new VE-PRO / VI-PRO orchestral template that was working fine.  Now the instrument play but when I go to start a sequence, it just hangs.....

    Any suggestions?


  • last edited
    last edited

    @Chuck Green said:

    Also I think the new release just broke Pro Tools.  A couple of hour ago I finished a completely new VE-PRO / VI-PRO orchestral template that was working fine.  Now the instrument play but when I go to start a sequence, it just hangs.....

    I think we're ok for now.  For some reason I had to change the Number of Host Processors from 8 to 7.  It worked fine with the previous release at 8 but now when I hit play to start the sequence, the first beat heats (Have STYLUS RMX loaded in VE-PRO) then pauses for a few seconds and then starts up.  Changing the Host Processors from 8 to 7 seems to have solved the issue.  The sequence starts right away.  CPU (RTAS) is still at 32% as it was when I was using the previous version.  Nothing else is jumping out at me.......

    We'll keep working and let you know if I run into something else.  

    Take care,


  • [quote=Paul]

    Thank's Paul for that one.  Even after adjusting the monitors, this brightness utility really makes the difference.  

    THANK YOU!!!!


  • last edited
    last edited

    Hi rpossum,

    @rpossum said:

    Yeah, I just updated on 2 machines... it works fine on Win 7 x64, but crashes on startup of VEP every time on WinXP x64 .. can't get it to run at all. I updated VEP and got the demo of VIP both today. -Russell

    Win XP64 is not supported, sorry to say.

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • last edited
    last edited

    @rpossum said:

    Yeah, I just updated on 2 machines... it works fine on Win 7 x64, but crashes on startup of VEP every time on WinXP x64 .. can't get it to run at all. I updated VEP and got the demo of VIP both today. -Russell

    Win XP64 is not supported, sorry to say.

    Best,

    Paul

     

     And the latest versions of both VI Pro and VE Pro don't work at all, whereas all previous versions did. [:(]

    DG


  • last edited
    last edited

    @Paul said:

    Win XP64 is not supported, sorry to say.
    But Win XP32 is, right? Maybe it's the same thing that broke both XP32 and XP64.


  • Hi everybody,

    we´re looking into this as we speak.

    Thanks for your patience, gentlemen!

    Paul


    Paul Kopf Product Manager VSL
  • Checking into the WinXP64 thing... or the other things? Thanks.. just trying to determine if I need to buy Win7 for that machine Cheers R

  • Hi,

    we´re looking into all bugs that are reported, always. Whatever can be fixed, will be fixed. But you´re better off with Win7 in any case, as there is no development for XP64 anymore, if I´m not mistaken.

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • Thanks Paul, I just went through on my Win7 machine and converted a cue that had LOTS of EastWest instruments to just using the Epic Orchestra instruments that came with VEP... using the VI Pro demo... amazing! Because of the flexibility of VI Pro, I am able to use far fewer instruments to achieve a richer and more detailed sound. Nice work guys... I'll definitely be buying the full version of VI Pro. Cheers Russell

  • Hi there. I installed the update VI Pro on my Mac and my slave PC (win XP 32 bit) when i start up Protools my slave VI Pro crashes. Cant load VI Pro. Reinstalled the older version of VI Pro and then there is no communication with the slave. Not visible in the server window. What can be wrong????

  • last edited
    last edited

    @Arthur said:

    Hi there. I installed the update VI Pro on my Mac and my slave PC (win XP 32 bit) when i start up Protools my slave VI Pro crashes. Cant load VI Pro. Reinstalled the older version of VI Pro and then there is no communication with the slave. Not visible in the server window. What can be wrong????
     

    Did you update the eLicencer?


  • Hi DG. Yes i did