Vienna Symphonic Library Forum
Forum Statistics

196,116 users have contributed to 43,014 threads and 258,391 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. New Updates available: Vienna Instruments PRO 1.0.6844 and Vienna Ensemble PRO 4.1.6844
  • R
    R
    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
  • C
    C

    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?
  • C
    C
    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,
  • C
    C
    [quote=Paul]

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

    THANK YOU!!!!
  • PaulP
    VSL Team
    PaulP
    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
  • D
    D
    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
  • I
    I
    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.
  • PaulP
    VSL Team
    PaulP

    Hi everybody,

    we´re looking into this as we speak.

    Thanks for your patience, gentlemen!

    Paul

    Paul Kopf Product Manager VSL
  • R
    R
    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
  • PaulP
    VSL Team
    PaulP

    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
  • R
    R
    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
  • A
    A
    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????
  • D
    D
    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?
  • A
    A
    Hi DG. Yes i did
  • A
    A
    On my Mac the server sees my PC, but when i connect with my PC, VI Pro on my PC crashes Update Elicenser on both machines and both machines has the same VI pro version 4.1.6844 Normally when i open a existing session in Protools, VI Pro opens automatically, but now it won't.
  • A
    A
    Hi Paul. On my Mac the server sees my PC, but when i connect with my PC, VI Pro on my PC crashes Update Elicenser on both machines and both machines has the same VI pro version 4.1.6844 Normally when i open a existing session in Protools, VI Pro opens automatically, but now it won't.
  • K
    K

    We're aware of the XP/XP64 issues and an update will follow shortly that fixes these. Sorry for the inconvenience. In the meantime you can install build 6776, which does not exhibit this problem.
  • R
    R

    Holding still on 6776 (three farm x64 machines) - working great.  The new updated features would be nice but there is value in 'working'[;)]