Vienna Symphonic Library Forum
Forum Statistics

200,906 users have contributed to 43,216 threads and 259,148 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro (legacy)
  4. build 7043: new versions of VI (PRO) and VE (PRO) software available
  • M
    M

     Yay! Been waiting for that - much appreciated!
  • J
    J

    Unfortunately, the CPU spikes and subsequent drop-outs are still there on the Mac. At the moment they are not as pronounced as they were with the previous version, but nonetheless still an issue.

    Anyone else confirm this?
  • B
    B

    Also in VI Pro, the problem with empty patches still exists, as well as missing licenses for certain instruments (Violin Ens). And a new problem introduced in this build -  the Cello Ens preset makes the program crash every time I attempt to load it.

    So sadly, VI Pro is still unusable to me.
  • K
    K

    If you have other VSL software installed, make sure to update them to the latest versions. Also make sure to kill the vsldaemon process (it won't be started by any of the current versions of all VSL software).
  • J
    J

    I get a 404 Server Error when trying to download the Changelogs for VI Pro.
  • J
    J

    Thanks, Karel.

    Vsldaemon is not running. Dropouts and CPU spikes still occur. Interestingly enough, those spikes and dropouts don't start in until after leaving the system running for a while without doing anything on it. They also often start in after loading another larger virtual instrument.

    No idea how all this is connected, but I thought to pass it on...

    Thanks,

    JB
  • PaulP
    VSL Team
    PaulP

    Hi Jack,

    this should actually be fixed by now. Can you confirm?

    Thanks, Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • J
    J

    Paul,

    I still get the 404 error.

    .
  • J
    J

    Did this latest version brake PLAY functionality again? I can't seem to instantiate a PLAY instance, prompting the old error "Could not create plugin play_VST_x64". 

    Am I missing something?
  • civilization 3C
    civilization 3C

    Yes, you're trying to instantiate a 32-bit plug-in as a 64-bit one.
  • J
    J

    Fixed by updating PLAY to the latest version.

    All working now. Well, with the exception of the CPU spikes and dropouts on the Mac...
  • S
    S

    Thanks Paul,

    I am so looking forward to being able to have VI Pro integrated with Vienna Ensemble.

    Thanks to all of the vsl team for this.

    best,

    Steve[:D]
  • J
    J

    Well, thought it was fixex, but it isn't. Here's what's happening:

    There seems to be a timeout issue with PLAY initializing in VE PRO. This happens with PLAY 2.0.25 on a Windows XP64 system, running VE PRO build 7043.

    When the workstation first boots, VE PRO starts and a metaframe is loaded that contains an instance of PLAY, VE PRO will return an error stating that "Could not create plugin play_VST_x64". However, shutting down VE PRO and manually starting up a standalone PLAY instance will remedy the issue, as PLAY will take a long time to start up, but eventually will show the standalone window. After that VE PRO will also instantiate PLAY instances.

    Above would be the workaround to get PLAY to work in the latest version of VE PRO. Would be nice though if we could have this addressed quickly. :)

    Thanks,

    JB
  • J
    J
    last edited
    last edited

    @Jack Weaver said:

    Paul,

    I still get the 404 error.

    I am seeing the 404 as well for the VI Pro changelog (english)
  • H
    H

     Sorry, this changelog was updated, it should work now.

    best

    Herb
  • K
    K
    last edited
    last edited

    @Jurgen Beck said:

    Well, thought it was fixex, but it isn't. Here's what's happening:

    There seems to be a timeout issue with PLAY initializing in VE PRO. This happens with PLAY 2.0.25 on a Windows XP64 system, running VE PRO build 7043.

    When the workstation first boots, VE PRO starts and a metaframe is loaded that contains an instance of PLAY, VE PRO will return an error stating that "Could not create plugin play_VST_x64". However, shutting down VE PRO and manually starting up a standalone PLAY instance will remedy the issue, as PLAY will take a long time to start up, but eventually will show the standalone window. After that VE PRO will also instantiate PLAY instances.

    Above would be the workaround to get PLAY to work in the latest version of VE PRO. Would be nice though if we could have this addressed quickly. 😊

    Thanks,

    JB

     

    There is no timeout in VE Pro with regards to creating plugins. This seems to be a problem with Play, so I recommend to report it to East West.
  • F
    F
    last edited
    last edited

    In ensamble pro 70 43 I It looks like it can load the instruments properlly, Doesn not start.

    @Jack Weaver said:

    Paul,

    I still get the 404 error.

    I am seeing the 404 as well for the VI Pro changelog (english)
  • A
    A
    Could not load VSTi Play x64.....Uh oh. How do I roll back to previous version? The only thing I changed was updating VI to 7043 and the regular Vienna Ensemble to 7043. I was already using VEPRO 7043.
  • S
    S
    Thanks. You refer to this as "build 7043," but on my computer (Mac), the version I have is reported as "Version 4.1.6844." So, aside from guessing, based upon installation dates, one can't tell if one has the latest build or not. Even your download page refers only to the "build," but not to the "version." It would be quite helpful if you'd refer to the versions (builds), using consistent nomenclature.
  • civilization 3C
    civilization 3C

    well, on my macs, they all (in applications, audio>plugins>components, VST, VST3) read: 4.1.7043. 'Build' = 'version'.

    '