Vienna Symphonic Library Forum
Forum Statistics

174,051 users have contributed to 41,812 threads and 252,916 posts.

In the past 24 hours, we have 5 new thread(s), 22 new post(s) and 76 new user(s).

  • A Consistent strategy for custom matrices?

    Hi everyone,

    I bought into VSL a few months back, now using App Strings 1 and various download wind instruments. Currently working on would-be John Willams Hollywood-style orchestration for a production library project. (Yeah, I know). The VSL sounds are great but I spend a disproportionate amount of time tweaking VSL matrices, and then even longer tweaking the Cubase expression maps to choose the right cell for each note. A few basic questions emerge:

     - Is there any difference, processing-wise, between having several matrices key switched within one preset as against one very large matrix? I get the feeling Cubase stumbles when making fast switches between matrices (requiring 2-3 keyswitch commands in sequence, one to choose the matrix and one or two to specify the cell), but not when switching between cells. This is a problem where eg a legato phrase has frequent staccato or detache notes in it.

    - Has anyone come up with a consistent method of producing custom presets so that, as far as possible, the same keyswitches and controllers call up the same musical effect regardless of instrument? Obviously some articulations are specific to intrument families but things like staccato, portato, sfz, fp etc are universal for sustained instruments, as is the need for a single controller that mimics blowing/scraping harder as you advance it

    - Or should one just accept the need to make a new set of custom matrices for every arrangement?

    - Is there a utility which derives Cubase expressionmap data from VSL matrix files automatically? Having done it by hand a few times I can assure you it is an entirely brain-dead algorithmic process, the sort of thing a computer should do rather easily.

    Any thoughts?

  • A slightly more specific question:

    Cubase expression maps are in XML so easily generated with any text-handling language like PHP or C. VSL preset and matrix files however are not readable in a text editor - but is the format in which the data is encoded and stored something that Vienna makes publically available? If so it would be quite easy to write a program that would scan a VSL file, find the keyswitches/controller zones and cell names, and generate a Cubase expression map instantly.

    Such a program wouldn't be able to invent "musical" articulation names, but in practice I just want to see the matrix cell name ('sta', 'rPo' etc)  in the Cubase articulation strip so I can assign the right patch to the right note.

    Just a suggestion ...

  • Hello Vyv!

    Your questions are hard to answer. There are so many different ways to use our sample collections. It depends very much on personal preferences. If you prefer working with Expression Maps or without is entirely up to you as well.

    There should be no or very little difference processing-wise, if you change articulations within a matrix or between two different matrices.

    The presets for the Strings Expression Maps are consistent, as well as the presets for the woowinds & brass Expression Maps. But I admit that the strings presets for Expression Maps are very different from the woodwinds & brass presets.

    I'm sorry to say that there's no tool to translate VI presets to xml code or something similar. Nor do we plan to make something like that.

    Best regards,

    Vienna Symphonic Library
  • Yes, check this out:

  • last edited
    last edited
    Hi Andi and Vyv!

    @Another User said:

    but I spend a disproportionate amount of time tweaking VSL matrices

    So true! Just to enable velocity for Konzerthaus Organ presets in Vienna Instruments Pro ended in a click-orgy. Much like Vyv! I too am looking for a unified way to operate my instruments that suits me. In my case its both for live strumming/blaring, preferably over the whole keyboard range and for some form of automation in a DAW. With the addition of the super package standard libraries the variety has become overwhelming. I am very reluctant to yield a single of my 88 Keys or the modulation wheel to such mundane tasks as patch switching. Preferably I'd use other controllers and live controllers like velocity, polyphonic aftertouch, playing style for doing this. More so now that buttons on controllers become ever cheaper, more colorful and numerous. And last but not least I utterly fail at remembering where AB switches, matrix X switches, matrix control switches, matrix key switches and my precious playable keys begin and end. So I want the whole matrix switching thing to go to a different MIDI channel or preferably (to keep all associated MIDI data in a single channel) different controller types which I could map to buttons on a physical controller. One Button per matrix element, except maybe A/B. A file format which can be parsed by a program or script would be of great help for all of this. Still - sound's great. And the Applications are improved constantly. Cheers badibeat

  • Hello badibeat!

    Did you check out the VI Pro Remote App?

    By the way. The Konzerthaus Organ has only one velocity layer. So Velocity X-Fade doesn't make that much sense. Controlling the Expression or Master Volume fader would have done. [;)]


    Vienna Symphonic Library
  • last edited
    last edited

    @EdouardB said:

    Yes, check this out:

    Video is gone. Can you find and repost?