Vienna Symphonic Library Forum
Forum Statistics

194,968 users have contributed to 42,945 threads and 258,052 posts.

In the past 24 hours, we have 7 new thread(s), 23 new post(s) and 97 new user(s).

  • Vienna Instruments information thread

    Vienna Instruments Information Thread

    In this thread you will find important information regarding

    - Software and content updates
    - WIN XP stress test reports
    - OS X stress test reports
    - Common useful information

  • Software Updates

    October, 2007

    Version 1.12 XP & OS X (PPC, Intel)

    - Pedal usage in Legato mode fixed

    - Maintenance core updates

    Additional Improvements OS X

    - RTAS compatible


    March, 2007

    Version 1.11 XP, OSX PPC, OSX Intel

    Improvements XP & OS X (PPC, Intel)

    - New Syncrosoft licenses added
    - Improved Bösendorfer Imperial support
    - A new loaded Matrix stays selected
    - Support for startup.fxp to load preset on startup
    - Speed Control slider shows percents
    - Note On Velocity can be assigned to any controller
    - Various core changes

    Additional Improvements OS X

    - Read-Only folder problem solved
    - Upfront window bug fixed
    - Cubase 4 display fixes

    October, 2006

    Version 1.1 XP, OSX PPC, OSX Intel

    - A completely rewritten User Interface code allows for a quicker start-up time and a more responsive GUI behavior. More than 10 interfaces can now be opened at the same time.

    - The plug-in remembers the last open page.

    - Matrices can be switched by program change commands (101 – 112).

    - The Matrix has been completely overhauled. It can be re-sized by dragging the borders using the mouse.

    - Cells of a Matrix can be dragged around by holding the Alt key, or copied by holding Alt+Ctrl.

    - Octave and semitone transposition shifts can be adjusted in the Cell Editor.

    - The dynamic range (velocity response) can be adjusted in the Cell Editor.

    - The information pane has been overhauled.

    - The Matrix save/delete function has been moved to the Matrix pane.

    - The Preset save/delete function has been added directly to the plug-in.

    - The behavior of sliders has been improved: Right-click to learn, right-click again to clear, alt-click to edit the controller parameters. Sliders move slower when holding the shift key while dragging.

    - Key select controls have been improved: The key name can be dragged up/down in order to select the key, and the up/down arrows can be used as well.

    - New shortcuts for defining key switches: Hold shift to select white/black keys only, hold ctrl to set a chromatic scale, hold alt to set just one key switch only.

    - Tabs on the Perform Page have been re-arranged.

    - The behavior of the pitch wheel for switching horizontally/vertically has been improved.

    - Many subtle graphic improvements make working more consistent, such as the Matrix 1-2 selector, parallel cell relocation, color and font adjustments, etc.

    - The Directory Manager now supports presets.

    May, 2006

    Version 1.06 XP & OSX

    - Core optimizations, faster startups when adding multiple instances, slightly smaller memory footprint per instance
    - Graphic usage optimizations - now more GUIs can be popped up at the same time
    - Directory Manager now has option to select multiple items for deletion
    - OSX VST version included

    April 26, 2006

    Version 1.05 XP & OSX
    introduces shared memory
    different VST plugins share the same pre cache mem
    -> if you load same patch - no additional RAM for wave data will be allocated


    March 17, 2006

    Version 1.05 OSX Intel
    public beta
    introduces shared memory
    different VST plugins share the same pre cache mem
    -> if you load same patch - no additional RAM for wave data will be allocated


    March 5, 2006

    Version 1.04
    Both platforms:
    - Patch loading optimization
    - Volume and pitch knobs reveal their numeric value in "magic eye"
    - Drag and drop folders onto Directory Manager - does recursion as well
    - Package now also includes Library Installer [provision for future MacTel version]

    February 27, 2006

    Version 1.03
    PC:
    - Maintenance
    - Speed fix
    OS X:
    - Load time improvement: first time 1 min (still), subsequent starts approx. 6-10 sec.
    - .fxp and .aupreset support for preset loading


  • Library updates

    August 2006

    updates available for

    Orchestral Strings I
    Orchestral Strings II
    Woodwinds I
    Woodwinds II
    Brass I

  • First Vienna Instruments Stress Test results on PC

    We have tested the Vienna Instruments on various computers and doublechecked on similar machines. All computers are fully equipped DAW´s that are used in everyday studio work, no additional tuning.

    More tests are in the works, with different processors and hosts. Our tests with Sonar, FX Teleport, Chainer, Plogue Bidule, Forte showed the same results, the Vienna Instruments behave the same way as in Steinberg Cubase SX or Vstack.

    The test results for Audio Units on Apple will follow as soon as possible.

    Please bear in mind, that the RAM available is also used by the hosts (around 300 MB) and Windows (another 300 MB), which is why the limit of RAM usage is 1.3-1.5 GB for the Vienna Instruments in a computer equipped with 2 GB RAM.

    The testing routine: Play a (really stressy!) stress test song with different loading options (more instruments, less RAM, and the other way around). All instruments are playing all the time, using all kinds of matrices and patches, and of course including additional MIDI data like ModWheel and different assigned sliders.

    You always see the maximum Vienna Instruments possible in the given setup without any sonic trouble.

    TEST COMPUTER 1

    Processor: Pentium 4, 3.2 GHz,
    Ram: 2 GB
    Data storage: internal SATA
    Host application: Cubase SX3
    Soundcard: RME HDSP Multiface


    Latency at 512 Samples (12ms) / 1.2 GB Ram usage
    Maximum Vienna Instrument instances: 24 (CPU 75%)
    Maximum polyphony: 200 stereo voices / (CPU 75%)

    Latency at 256 Samples (6 ms) / 1.3 GB Ram usage
    Maximum Vienna Instrument instances: 20 (CPU 70%)
    Maximum polyphony: 200 stereo voices / (CPU 75%)

    TEST COMPUTER 2

    Processor: Pentium 4, 3 GHz,
    Ram: 2 GB
    Data storage: Firewire 400
    Host application: Cubase SX2
    Soundcard: RME DIGI 9652


    Latency at 1024 Samples (24 ms) / 1.3 GB Ram usage
    Maximum Vienna Instrument instances: 24 (CPU 50%)
    Maximum polyphony: 200 stereo voices / (CPU 60%)

    Latency at 512 Samples (12 ms) / 1 GB Ram usage
    Maximum Vienna Instrument instances: 18 (CPU 50%)
    Maximum polyphony: 200 stereo voices / (CPU 60%)

    Latency at 256 Samples (6 ms) / 1.2 GB Ram usage
    Maximum Vienna Instrument instances: 14 (CPU 60%)
    Maximum polyphony: 180 stereo voices / (CPU 65%)

    TEST COMPUTER 3

    Processor: AMD 2.6 GHz,
    Ram: 2 GB
    Data storage: Firewire 400
    Host application: Cubase SX3
    Soundcard: Creamware Pulsar & Luna


    Latency at 13ms / 1.3 GB Ram usage
    Maximum Vienna Instrument instances: 20 (CPU 70%)
    Maximum polyphony: 200 stereo voices / (CPU 70%)

    Latency at 7 ms / 1.2 GB Ram usage
    Maximum Vienna Instrument instances: 16 (CPU 65%)
    Maximum polyphony: 174 stereo voices / (CPU 60%)

    TEST COMPUTER 4

    Processor: Pentium 4, 2.8 GHz,
    Ram: 2 GB
    Data storage: internal SATA
    Host application: VSTack
    Soundcard: RME DIGI9632


    Latency at 512 Samples (12ms) / 1.4 GB Ram usage
    Maximum Vienna Instrument instances: 16 (CPU 70%)
    Maximum polyphony: 180 stereo voices / (CPU 70%)

    Latency at 256 Samples (6 ms) / 1.4 GB Ram usage
    Maximum Vienna Instrument instances: 8 (CPU 55%)
    Maximum polyphony: 160 stereo voices / (CPU 70%)

    TEST COMPUTER 5

    Processor: Pentium 4, 2.4 GHz,
    Ram: 1.5 GB
    Data storage: Firewire 400
    Host application: VSTack
    Soundcard: Steinberg VSL 2020


    Latency at 512 Samples (12ms) / 1 GB Ram usage
    Maximum Vienna Instrument instances: 16 (CPU 60%)
    Maximum polyphony: 200 stereo voices / (CPU 80%)

    Latency at 256 Samples (6 ms) / 1 GB Ram usage
    Maximum Vienna Instrument instances: 14 (CPU 60%)
    Maximum polyphony: 200 stereo voices / (CPU 80%)

    TEST COMPUTER 6

    Processor: Laptop Pentium M, 2 GHz,
    Ram: 2 GB
    Data storage: Firewire 400
    Host application: Cubase SX3
    Soundcard: RME HDSP Multiface


    Latency at 512 Samples (12ms) / 1.2 GB Ram usage
    Maximum Vienna Instrument instances: 14 (CPU 65%)
    Maximum polyphony: 160 stereo voices / (CPU 65%)

    Latency at 256 Samples (6 ms) / 1.1 GB Ram usage
    Maximum Vienna Instrument instances: 10 (CPU 55%)
    Maximum polyphony: 150 stereo voices / (CPU 65%)

    TEST COMPUTER 7

    Processor: Pentium 3, 1 GHz,
    Ram: 2 GB
    Data storage: Firewire 400
    Host application: VStack
    Soundcard: RME DIGI 9632


    Latency at 512 Samples (12ms) / 0.6 GB Ram usage
    Maximum Vienna Instrument instances: 5 (CPU 70%)
    Maximum polyphony: 90 stereo voices / (CPU 65%)

  • First Vienna Instruments Stress Test results on Mac OS X

    So here they are, the first official test results with the new Vienna Instruments as Audio Units on Mac.
    As on the PC platform, we have tested the Vienna Instruments on various computers and doublechecked on similar machines. All computers are fully equipped DAW´s that are used in everyday studio work, no additional tuning.

    More tests are in the works, with different processors and hosts. Test results for the Quad will be released as well, we expect more Vienna Instruments to be loaded with maximum amount of RAM.

    The limit of RAM usage is about 2.8 GB for the Vienna Instruments in a computer equipped with 4 GB RAM, that translates to 47000 samples.

    The testing routine: Play a (really stressy!) stress test song with different loading options (more instruments, less RAM, and the other way around). All instruments are playing all the time, using all kinds of matrices and patches, and of course including additional MIDI data like ModWheel and different assigned sliders.

    You always see the maximum Vienna Instruments possible in the given setup without any sonic trouble.

    TEST COMPUTER 1

    Processor: G5, 2 x 2.5 GHz,
    Ram: 4 GB
    OS 10.4.2
    Data storage: Firewire 800
    Host application: Logic 7.1.1
    Soundcard: RME HDSP MADI with 648 MADI Interface


    Latency at 512 Samples (12ms) / 2.5 GB Ram usage
    Maximum Vienna Instrument instances: 24 (CPU 90%)
    Maximum Samples loaded: 45000
    Maximum polyphony: 300 stereo voices / (CPU 70%)

    Latency at 256 Samples (6 ms) / 1.74 GB Ram usage
    Maximum Vienna Instrument instances: 23 (CPU 70%)
    Maximum polyphony: 200 stereo voices / (CPU 75%)

    TEST COMPUTER 2

    Processor: iMac G5 single, 1.8 GHz,
    Ram: 2 GB
    OS 10.4.5
    Data storage: Firewire 400
    Host application: Logic 7.1
    Soundcard: Built in Audio


    Latency at 512 Samples (12ms) / 1.08 GB Ram usage
    Maximum Vienna Instrument instances: 11 (CPU 85%)
    Maximum Samples loaded: 17400
    Maximum polyphony: 250 stereo voices / (CPU 80%)

    Latency at 256 Samples (6 ms) / 1 GB Ram usage
    Maximum Vienna Instrument instances: 9 (CPU 85%)
    Maximum polyphony: 160 stereo voices / (CPU 80%)

  • [PC] Memory configuration and VI...
    by Matthias Henningson


    I was asked by the VSL people to check on some memory related things as they have already had several questions from VI users about this. I still have a couple of things to go through but here are at least some guidelines as a start that covers the most basic setups.

    If you encounter problems with low load limits with VI or if you are migrating your GigaStudio machine into a VI machine this text is for you.

    Machine previously used for GigaStudio

    If you have been using the “memory tweaks” on the machine to be able to load more samples in GigaStudio the tweaks need to be removed. This can be done in a number of ways, but these are simple and fail-safe and therefore recommended:

    Using the GigaStudio Memory configuration utility
    1. Start the GigaStudio memory configuration utility.
    2. Apply memory preset #1 (Windows XP default).
    3. Reboot the machine.

    Using the Memory Load Optimizer for GigaStudio
    1. Download and run the small utility from http://www.musikbanken.se/gigastudio/memopt.htm
    2. If you like you can check your current settings by pressing the “Get current settings” button.
    3. Run the utility and press the button “Revert to default settings”.
    4. Reboot the machine.

    New machine or machine previously used for other purposes

    Normally you shouldn’t need to change anything to the memory configuration on a machine that hasn’t been tweaked specifically for GigaStudio. As always there are exceptions to this rule so if you experience problems with unreasonably low load limits in VI it can be well worth performing this check:

    1. Download the Memory Load Optimizer for GigaStudio utility from http://www.musikbanken.se/gigastudio/memopt.htm
    2. Run the utility and press the button “Get current settings”.
    3. If the values you're seeing in the four boxes are anything but zeros you may be affected by this. If you like to be on the safe side of things write down the 4 numbers.
    4. Press “Revert to default settings”.
    5. Reboot the machine.

    I will be updating this post with more details later.

    /Mattias

  • last edited
    last edited
    FAQ link

    find the new FAQshere

  • Software update version 1.12 available.
    You find more details in the 2nd post.