Vienna Symphonic Library Forum
Forum Statistics

181,857 users have contributed to 42,189 threads and 254,611 posts.

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

  • New VE 3 versions

    Just noticed, downloaded & installed the new VE3 updates (3388), both XP64 and Mac OS X versions. Am running now.

    This doesn't appear to be the long-awaited VE3 update that won't require reloading of samples each time we switch projects.

    Dear VSL, any news when that feature will be available?

    Hoping soon.

    Thanks for all you do!

    Best,

    -- Stu Goldberg

    --Mac Pro Intel 8 Core (2007), 16GB Ram, Sys 10.4.11, PC 4 core, 8 GB ram, XP64, Digital Performer 6.01,  ProTools 003 Factory, DV Toolkit 2, PCI-E 424, 2408 Mk II, 2408 Mk III, optical in and out to Apogee AD-8000, Apogee DA16, 3 MTP AV USBs, MTP II, MidiExpress 128, 12 SampleCell cards on Nubus Mac, 2 GigaStudio PCs, Aardsync II word clock house sync, Mach V, Mach V 2, MSI, Vienna Ensemble (4 instances), VSL Special Edition Extended, SE Plus, Concert Guitar, Upright Bass, Bass Flute, CB Clarinet, Stylus RMX, Atmosphere, Trilogy, Analog Factory, AVOX AT5, SoundSoap, SoundSoap Pro, Altiverb, Elektrik Piano, Canopus ADVC110...


     


  • the so-called *static* option (working title) will be implemented in a 3.1 version and i don't think our developers will find the time to even touch it before the NAMM show ...

    christian


    and remember: only a CRAY can run an endless loop in just three seconds.
  •  What is new in this version?   Right in the middle of a project - need it ROCK solid (maybe I should wait) - unless there are some performance improvements.

     Rob


  • Thanks for the info Christian. Good to know.

    Looking forward to when it's ready!

    --Stu


  • last edited
    last edited

    Hello Rob,

    the latest version has been release as a public beta version. Please find the changelog here.

    Paul


    Paul Kopf Product Manager VSL
  • Thanks Paul.   I see the MAC version as beat but the PC (which I am interested in shows now beta reference)??

    Rob


  •  In the changelog it says "Lowered GUI resource usage". Does it mean we can now load more than 60 (or 100 if using the tweak) instances of VI into VE, as that restriction was apparently due to the high number of graphic handles?

    Dom


  • Usage of GDI objects is very much reduced with this update. There will still be a dialog that pops up when going above 70 instruments however. With enough positive reports from this version, we will remove this dialog for the next update.

  • last edited
    last edited

    @MS said:

    Usage of GDI objects is very much reduced with this update. There will still be a dialog that pops up when going above 70 instruments however. With enough positive reports from this version, we will remove this dialog for the next update.

    Martin, is there a new VE2 version with this improvement as well?

    Thanks.


    DG

  • Yes, the latest VE2 version (r3388) has the same improvements as found in VE3 r3388.

  • last edited
    last edited

    @MS said:

    Yes, the latest VE2 version (r3388) has the same improvements as found in VE3 r3388.

    Excellent, I'll give it a whirl today.

    DG


  • last edited
    last edited

    @DG said:

    Excellent, I'll give it a whirl today
     

    Great. Let us know how it went.

    Dom


  •  Hi,

    A quick test :

    One Vienna Ensemble, with  100 Instruments :

    GDI Handle : 3600

    User Handle : 117

    Before this beta, each instrument used 168 user handle.

    Good job [Y]

    Now I cross my fingers and hope a future release will use less memory for each Instrument's instance : 100 empty instruments use about 1.6Go.


  • last edited
    last edited

    @DG said:

    Excellent, I'll give it a whirl today
     

    Great. Let us know how it went.

    Dom

    It seems stable so far. Still limited to 7 VE instances, but I did load 120 Instruments before I got bored, so that's an improvement. I've only used the plug so far, so I can't say whether or not it is any more efficient.

    DG

  • The reason for the high per-instance memory usage is due to our buffering strategy for disk streaming. Each VI instance in VE is dedicated to 64 voices. There is however an undocumented feature to lower the polyphony per instance, and therefore the memory consumption:

    Select the desired VI instance and press Ctrl-Alt-P. You will then get a dialog for setting the polyphony for the instrument. Please note that the new polyphony setting will not be effective until you stop/start the engine again.

    If your VE template uses many instances, you could save alot of memory by lowering the polyphony this way.


  • last edited
    last edited

    @MS said:

    The reason for the high per-instance memory usage is due to our buffering strategy for disk streaming. Each VI instance in VE is dedicated to 64 voices. There is however an undocumented feature to lower the polyphony per instance, and therefore the memory consumption:

    Select the desired VI instance and press Ctrl-Alt-P. You will then get a dialog for setting the polyphony for the instrument. Please note that the new polyphony setting will not be effective until you stop/start the engine again.

    If your VE template uses many instances, you could save alot of memory by lowering the polyphony this way.

    Martin, I find that playing with the polyphony setting causes VE to become unstable. Well I say VE, but it could be that it causes Nuendo to become unstable. I don't know which app is the culprit, but either way gives the same result. Crash. However, I haven't tried it with this new version yet. Should I?


  •  UNDOCUMENTED!!!!   I would be yelling this one from the rooftops.   Very nice option.

    In a practical sense what do you recommend for say WW's - I can't imagine more than 8-16 or so would be needed (of course dependent on cue/piece)!

    Rob