Vienna Symphonic Library Forum
Forum Statistics

194,476 users have contributed to 42,922 threads and 257,973 posts.

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

  1. Home
  2. Software
  3. Vienna MIR & Vienna Suite
  4. New updates of VE PRO, Vienna Suite and Vienna Imperial available!

  • New updates of VE PRO, Vienna Suite and Vienna Imperial available!

    PaulP
    VSL Team
    PaulP
    last edited
    last edited

    Hi everybody,

    please find all software updates in your User Area!

    Vienna Suite and Vienna Imperial now also work as 64-bit plug-ins with OS X, the highlights of the Vienna Ensemble PRO update are:

    • various fixes with plug-ins including Kontakt
    • the new Decouple feature
    • external MIDI ports now accessible from server instances
    • Sonar compatibility
    • faster saving times
    • and much more....

    As always, our changelogs will inform you in detail about all improvements.The Vienna Ensemble PRO Manual has also been updated, of course.

    Enjoy!

    Best,

    Paul


Paul Kopf Product Manager VSL
  • P
    P

    Great! Amazing news! That's like christmas [:)]

    @Paul, Martin and all other members of the Vienna-Team:

    many thanks for your brilliant work!
  • K
    K

    wow, I'm really amazed !

    You guys rock hard :)

    Thanks so much
  • A
    A

    VE-PRO + Cubase5 (Mac SL)

    - preserve instance in VE-PRO

    - close Cubase

    - reopen Cubase with the same project

    - it doesn't reconnect to the preserved session, opens a new one instead :(

    which means that unless "decouple" has already been turned on in the project, it will load the whole template once more. Not a good thing when switching between multiple sessions (film scoring). It should reconnect to the preserved session.
  • M
    M

    @Abel: Did you name your preserved VEP Instances and save the project with those? Because I think that did the trick for me but maybe there's some other way that I haven't noticed yet. It's working like a charm here now and it's great. :)

    @VSL: Thanks for the new updates and improvements. Wish other companies were as fast as you with bug-fixing and feature-adding. :)
  • A
    A

    I think I found the source a problem:

    A. when a VEPRO session is in "Preserve" mode, the plugin interface displays: 127.0.0.1 [name of your preserved session]

    if you save your Cubase project, close it and reopen, it will reconnect to the preserved session

    B. when "Preserve" mode is off, the plugin interface displays only: 127.0.0.1

    if you save your Cubase project, then turn on "Preserve" and then close the project and reopen, it will not reconnect to the preserved session, it will load a new session instead.

    So, the problem is that an unpreserved VEPRO session reports a blank name to Cubase project.

    The workaround: you have to remember to make your last save (before quitting the project) in "Preserve" mode, otherwise your project will not reconnect.

    BTW, I run both Cubase and VEPRO on the same computer.
  • M
    M

    Thanks for this new update, guys!


    However, VE Pro crashed when I do the following:

    1. VE Pro and Cubase are running and connected to each other, in VE Pro a VI is loaded.

    2. I save and close Cubase (decouple mode off), close VE Pro completely.

    3. Restart VE Pro Server (32-bit), restart Cubase and load that saved project file.

    4. Now, Cubase tries to connect to VE Pro and VE Pro crashes.

    Important: This does not occur when the last instance of VE Pro is still running! And I don't know if it is a new problem, which came with the update because I have not tried that before...

    May be this is related to Abel's problem?
  • B
    B

    Yes I'm having problems too.

    I eagerly downloaded because I'm a LASS user, but now upon loading my existing project the 32-bit server crashes.  Also, all instances of VEP receive midi at the same time.  In other words, even if I'm playing on a non-VEP track (say B4 or Trilogy), the VEP instance(s) play regardless of the channel setting.  It of course doesn't work the other way - playing a VEP instance doesn't trigger a non-VEP track.

    The midi 'all receive' problem, and the 32-bit server crashing occurs not just on my existing project, but any new project created since the update.

    With regret I'm going to have to go back to the previous build. 

    Brett

    {edit} I'm on XP64 running Cubase4
  • A
    A

    @Brett the new VEP has this new "external midi port" feature.

    Make sure it is turned OFF when you work with sequencer, otherwise when you play your keyboard, VEP will receive midi regardless of which track you selected.
  • B
    B

    Thanks Abel.  Missed this new feature - this of course fixed the midi issue.

    However, VEP still crashes when loading a saved project.  I've done some more testing though and only the 32-bit server crashes, not the 64-bit version and this occurs whether I'm connected using the VST2 or VST3 version of the plugin.  Nothing has to be loaded into the VEP plugin - it can be empty.  Also, the crashes to the 32-bit server only occur when 'connected' to the Cubase.  If I've disconnected (preserved) prior to saving the project then it will load without crashing. 

    Brett
  • S
    S

    Thanx sooo much for taking care of MIDI for us Mac  users!!

    SvK
  • K
    K
    last edited
    last edited

    @brett said:

    Thanks Abel.  Missed this new feature - this of course fixed the midi issue.

    However, VEP still crashes when loading a saved project.  I've done some more testing though and only the 32-bit server crashes, not the 64-bit version and this occurs whether I'm connected using the VST2 or VST3 version of the plugin.  Nothing has to be loaded into the VEP plugin - it can be empty.  Also, the crashes to the 32-bit server only occur when 'connected' to the Cubase.  If I've disconnected (preserved) prior to saving the project then it will load without crashing. 

    Brett

    I can not seem to reproduce this here. Could you perhaps give a more exact list of actions leading up to the crash? Thanks.
  • B
    B

    Thanks Karel for your reply.  I'm using xp64 and cubase4 on a PC, with VEP only on my local computer.  No slaves.

    Load VEP server 32-bit.

    Load Cubase4

    Open a new Cubase project

    Instantiate a single VEP from the VST instruments rack

    'Connect' to localhost [32] (new)  - I'm not naming the preserved session which means the VEP instance is connected to the host and not preserved

    Save the project

    Close the project

    Re-open the project = crash! (exception in vienna ensemble pro.exe)

    In contrast...

    Load VEP server 32-bit.

    Load Cubase4

    Open a new Cubase project

    Instantiate a single VEP from the VST instruments rack

    'Connect' to localhost [32] (new) and either name the instance (automatically preserving it) or don't name but then preserve.

    Save the project

    Close the project

    Re-open the project = No worries.

    [edit - however, if you shutdown the VEP 32-bit server, or delete that preserved instance of VEP, after closing the cubase project, and then re-open the project, this will force VEP to load with the project and cause a crash similar to the first example above]

    (Also, the problems with cc-instensive patches like the legato LASS patches is not fixed here - I've detailed this in the LASS thread)

    Thanks Karel - Brett
  • P
    P

    Hi Vienna-Team,

    is it possible that there's a memory leak in the update? After updating to 4.0.4536 VE Pro crashes every time when editing a bidule instance (v. 0.9693). Then the memory of VE PRo rises rapidly until the whole application crashes.

    Reinstalling VE Pro 4.0.4416 I don't have this problem any more, then bidule works fine in VE Pro.

    Best regards,

    Peter
  • S
    S

    Hi, I had some crashes too after the update. When open the Cubase project I had created using the other version, it crashes immediately after open it.

     I'm using WinXp 32 and Cubase 4.
  • M
    M

    VEPro 32/64 4536 cannot start the audio engine in the standalone mode (including the built-in audio).

    PPC G5 2.3 Dual, OS 10.5.8 and MacBook, OS 10.6.1

    VE3 works fine standalone on both platforms.
  • D
    D

    VE Pro server crashes as soon as I try to do anything over IAC. Are you interested in crash logs?
  • K
    K
    last edited
    last edited

    @michkhol said:

    VEPro 32/64 4536 cannot start the audio engine in the standalone mode (including the built-in audio).

    PPC G5 2.3 Dual, OS 10.5.8 and MacBook, OS 10.6.1

    VE3 works fine standalone on both platforms.

    Try setting a specific samplerate and blocksize in the audio preferences instead of using the defaults.
  • M
    M
    last edited
    last edited

    @Karel said:

     Try setting a specific samplerate and blocksize in the audio preferences instead of using the defaults.

    That worked, thanks!
  • B
    B
    last edited
    last edited

    @brett said:

    Thanks Karel for your reply.  I'm using xp64 and cubase4 on a PC, with VEP only on my local computer.  No slaves.

    Load VEP server 32-bit.

    Load Cubase4

    Open a new Cubase project

    Instantiate a single VEP from the VST instruments rack

    'Connect' to localhost [32] (new)  - I'm not naming the preserved session which means the VEP instance is connected to the host and not preserved

    Save the project

    Close the project

    Re-open the project = crash! (exception in vienna ensemble pro.exe)

    In contrast...

    Load VEP server 32-bit.

    Load Cubase4

    Open a new Cubase project

    Instantiate a single VEP from the VST instruments rack

    'Connect' to localhost [32] (new) and either name the instance (automatically preserving it) or don't name but then preserve.

    Save the project

    Close the project

    Re-open the project = No worries.

    [edit - however, if you shutdown the VEP 32-bit server, or delete that preserved instance of VEP after closing the cubase project, and then re-open the project, this will force VEP to load with the project and cause a crash similar to the first example above]

    (Also, the problems with cc-instensive patches like the legato LASS patches is not fixed here - I've detailed this in the LASS thread)

    Thanks Karel - Brett

    Karel - Did you manage to test the above repro?  It happens everytime here.  If I ever load up my current project which had been saved in a disconnected (non preserved) mode, the 32-bit version of the server crashes on load while the 64-bit is fine.  However if I had previously saved the project with all instances preserved, then loading the project (after loading the metaframe files) there is no crash.  This is a 'once a day' problem - I just have to remember disconnect, and to save the meta files for both 64 and 32-bit server versions at the end of the day otherwise my first load the mext morning results in a crash

    XP64 with Cubase 4 here - Thanks

    Brett