Vienna Symphonic Library Forum
Forum Statistics

181,730 users have contributed to 42,180 threads and 254,562 posts.

In the past 24 hours, we have 1 new thread(s), 12 new post(s) and 59 new user(s).

  • [announcement] Vienna Ensemble Pro v4.0.4780 (Public Beta)

    last edited
    last edited
    Hi people.

    A new public beta is now available in the user area. Some of the most notable additions are Pro Tools (RTAS) support for the Server Interface plugin on Windows, ability to use EW Play and the VE Pro AU plugin in the same host on Mac, and saving/loading of individual channels and sets of channels.

    Keep in mind that this is a beta release, so it could still contain some bugs.

    Here is a more detailed changelog for this beta release (also available in user area):

    • MAC: Added time synchronization to AU hosting
    • AU: Fixed crashes when loading East West Play in the same host as the connector plugin
    • MAC: Fixed redraw problems with Ueberschall products
    • WIN: Fixed bug which disallowed VST editors to create new windows (as seen in Synthogy Ivory)
    • WIN: Added RTAS version of VE PRO Server Interface
    • Fixed crash when a Vienna Instruments startup.fxp is available
    • Added ability to save/load channel presets and sets
    • Added update checking functionality
    • Possibly fixed slave instances not showing in the VE PRO Server Interface with a lot of instances present

  • Thank you so much for the channel presets, it's amazing!!


  • createsharedbufferandretrieveitshandle

    "This buffer already exists - please report this"

    Error while loading jbridge/Samplelord project on win7 64.

    While I can create large templates from scratch without priblems - I can't load them afterwards.

    It seems to me that one issue is the fact that Vepro is "switched off" when projects loaded. Some plugins may not work properly in this mode e.g. don't load preferences neccessary to load their programs correctly.

  • Hi mmueller,

    please include some information about your setup, and some real numbers will also help [:)]

    Thanks, 

    Paul


    Paul Kopf Product Manager VSL
  • Some progress on the metaframe file opening problems from the desktop in OS X.  I no longer get invalid file errors and the correct server app is opening for the metaframe files.  Thank you for that.

    However, the following problem still occurs: if you open a metaframe file of one type (e.g., 32-bit) and then try to open one of a different type (64-bit), by double clicking the metaframe file, then it won't open.  Also fails to open if you try to open a different metaframe file of the same type.  

    Note: You can launch the app and open it from the file menu.  Or you can select both files and double click one of them and they will both open.  So it's not consistent with how it should work yet, but better than before.  Open from the file menu always seems to work as expected.  Double clicking a metaframe file from should behave the same way as File>Open in every case.


  • last edited
    last edited

    @Paul said:

    Hi mmueller,

    please include some information about your setup, and some real numbers will also help

    Thanks, 

    Paul

    Hello Paul;

    What do you mean with real numbers? I currently have a test system with Intel Mobo and an intel single core cpu. OS is WIN 7 Pro x64.

    I think I solved the issue with the help of the Samplelord developer.

    It seems that (only) the bridged Samplelord does not load its own global parameters , e.g. disk streaming. I can insert an "empty" plugin, set the parameters to disk streaming and can load and play tons of samples. I can also save everything as project. But when I try to load the project again then SL "forgot" its global parameters and tries to load all samples into RAM - and crashes when RAM is full. Its only a problem when using the 32bit version bridged with jbridge in the 64bit vepro server. It works flawless within Vepro 32bit server.

  • Hi mmueller,

    glad it works now!

    I missed the the tricky part with jbridge somehow....

    "Real numbers" would be for example the amount of RAM in your computer, and the size of "big templates" - makes it easier for us.

    Best,

    Paul


    Paul Kopf Product Manager VSL
  • can it now load EW play AU in the Ensemble server?

    eldad


  • last edited
    last edited

    @Paul said:

    Hi mmueller,

    glad it works now!

    I missed the the tricky part with jbridge somehow....

    "Real numbers" would be for example the amount of RAM in your computer, and the size of "big templates" - makes it easier for us.

    Best,

    Paul

    Oh, I forgot. The machine has 4 gig and I indend to use them all 😊 Vepro is really tempting to spend a lifetime in building perfect templates... 😉

    I contacted Wlodzimierz Grabowski - the developer of samplelord - this afternoon and he released a fix for the problem within hours (on saturday!). I tested it and it works. With the fix (and jbridge) it is possible to play back gigasampler files (and many other formats) without 32bit memory limits in VePros 64bit server. The "christmas price" of the gem is 39 euro what is a bargain for keeping old sample libaries in the game without having to deal with the conversion hassle. Anyway, I am thrilled that this works 😊

    One more thing... Just my compliments for delivering such a great product with VePro. I have to use Protools nowadays and while midi is improved in the latest version Rtas plugin performance in Protools (Le) simply sucks. Two standard plugins on two tracks and you can be sure to get a "cpu overload" message even when you set latency to highest values. Thanks to VePro I am done with that: I host anything outside protools in VePro and everything runs smooth. Thank you for that!

  • last edited
    last edited

    @eldad.guetta_10897 said:

    can it now load EW play AU in the Ensemble server?

    eldad

    It will not crash anymore when running EW Play AU and VE Pro Service Interface AU in the same host (Logic, DP, ...). For Play to work in an actual VE Pro instance, some work from EW's side is required.

  • Hey, this appears to fix the legato bug I was getting in Kontakt 3. Whoo hoo!

    But now the sale is over. :( 


  • Hello,

    I get double note (phasing) with LOGIC 9 and VEPRO... any idea why?

    Also, last night session, I don't get a double note but when I play other EXS track, the sound from VEPRO will also play along... This beta is strange... I think I need to reverse to the old version!

    Thanks for any help!

    Sonny


  • last edited
    last edited

    @dsstudio said:

    Hello,

    I get double note (phasing) with LOGIC 9 and VEPRO... any idea why?

    Also, last night session, I don't get a double note but when I play other EXS track, the sound from VEPRO will also play along... This beta is strange... I think I need to reverse to the old version!

    Thanks for any help!

    Sonny

     

    Sounds like a routing error. Make sure that the MIDI input in Vienna Ensemble is set to Plugin MIDI, rather than Omni, assuming that you're not intending to use any external MIDI inputs.

    DG


  • last edited
    last edited

    @dsstudio said:

    Hello,

    I get double note (phasing) with LOGIC 9 and VEPRO... any idea why?

    Also, last night session, I don't get a double note but when I play other EXS track, the sound from VEPRO will also play along... This beta is strange... I think I need to reverse to the old version!

    Thanks for any help!

    Sonny

    No MIDI handling was changed in this version. It sounds like a MIDI routing error indeed.

  • Before I take the plunge: (especially since I'm in the middle of a project!): does the new Beta fix the issues many of us have been having with audio dropouts and/or dropouts that occur when bouncing? (for example, when using Logic 9.02?)...Anyone notice a difference? :-) - robjohn99 MacPro (early 2009), 12 gigs RAM, Logic 9.02, Snow Leopard 10.6.2

  • Hi robjohn33, i am using the same hardware/software and get no problems at all.

    -A


  • Thanks for the update. However, I'm experiencing problems. Every time I try to open up Kontakt 2 within VE pro, it crashes. I can open up Kontakt 2 fine in Logic, and K2 use to work fine in older versions of VEpro (dont remember which version, but it was either the 2nd or 3rd build) but since updating to this build it no longer works. Was K2 support dropped? Whats interesting is if I open projects created with the older VE pro they open fine, but once I try to open the kontakt instance in VE pro (i.e. to add more instruments), it crashes VE pro. 

    I'm on a Dual 2.5 G5 w/ 7GB Ram OS 10.5.8. Logic 8.0.2

    Thanks! 


  • I am sorry but i am using Kontakt3.5 and 4.03 and no problems at all.

    No eperiencing about Kontakt 2 in VePro, but due of the K3-4 improvements the version 2 have not reason to exist actually.

    I suggest to you to update.

    And as you can imagine VePro has a different architecture, so what you open in Logic not necessary work in VePro.

    -A


  • last edited
    last edited

    @anton said:

    No experiencing about Kontakt 2 in VePro, but due of the K3-4 improvements the version 2 have not reason to exist actually.

    I suggest to you to update.

    This maybe true in some cases, but is not true in all. For example, Tonehammer recommends you use their libraries in KontaKt 2, and state that some of their patches do not work correctly in Kontakt 3 or 3.5! Even so, at the very least I should be able to open my old projects in VE pro, correct? Imagine trying to look at past work and it can no longer open!! I know this will happen eventually, but it should NOT happen from a maintenance update, especially when I haven't made any other changes to my OS, sequencer or DAW. 

    I know programming for all these variables is extremely difficult, but suggesting one should upgrade is not the answer, especially when in previous versions of VE pro K2 worked fine. You might say "stupid me" for updating when everything was working fine, but I HAD to update as the version of VE pro I was on had a MAJOR problem with the mac platform that caused the entire system to act slow!! (See thread here) http://www.kvraudio.com/forum/viewtopic.php?t=266341&postdays=0&postorder=asc&start=90


  • last edited
    last edited

    @anton said:

    No experiencing about Kontakt 2 in VePro, but due of the K3-4 improvements the version 2 have not reason to exist actually.

    I suggest to you to update.

    This maybe true in some cases, but is not true in all. For example, Tonehammer recommends you use their libraries in KontaKt 2, and state that some of their patches do not work correctly in Kontakt 3 or 3.5! Even so, at the very least I should be able to open my old projects in VE pro, correct? Imagine trying to look at past work and it can no longer open!! I know this will happen eventually, but it should NOT happen from a maintenance update, especially when I haven't made any other changes to my OS, sequencer or DAW. 

    I know programming for all these variables is extremely difficult, but suggesting one should upgrade is not the answer, especially when in previous versions of VE pro K2 worked fine. You might say "stupid me" for updating when everything was working fine, but I HAD to update as the version of VE pro I was on had a MAJOR problem with the mac platform that caused the entire system to act slow!! (See thread here) http://www.kvraudio.com/forum/viewtopic.php?t=266341&postdays=0&postorder=asc&start=90

    Could you supply us with a report of that Kontakt 2 crash? Thanks.