Vienna Symphonic Library Forum
Forum Statistics

174,397 users have contributed to 41,834 threads and 252,997 posts.

In the past 24 hours, we have 2 new thread(s), 18 new post(s) and 65 new user(s).

  • Workflow suggestions?

    I am new to VSL and use it with a G5 Mac (4GB RAM) and with Digital Performer 5.1.1. When programming a new piece into the sequencer, I'm finding it quite tricky to manage all the keyswitches and controllers in any sort of real time. I'd love to know how some of the more experienced composers and arrangers on this site work with the libraries.

    Thanks in advance for your help


  • For what it's worth I have 2 miditracks per VSI instance. These all go into one folder per section with the '2nd' set going into a second folder within the first. eg - 'Strings Folder' - Violin 1, Violin 2, Viola, Celli and Bass. Then a 'Strings Folder CCs' -Violin 1 CCs, Violin 2 CCs, Viola CCs, Celli CCs and Bass CCs within the 'Strings Folder'.

    These folders can be opened and closed as required either together or separately and avoids a cluttered track list.

    Any switches or controller info that I record on the first Violin 1 track gets transferred to the Violin 1 CCs track. I can then add additional switches and controller information as required.

    This helps me in several ways. When the Violin 1 track goes for copying for playing by a live orchestra you don't have any switch notes, articulation key switches, or controller information creeping into the written score-parts.

    Another way I find this method useful is I find it easier to then edit the controller information (such as volume or velocity X-fade on a slider) and/or key switch information without the risk of disturbing the actual 'part'.

    I don't say this will work for everyone - or anyone - but it is the best way I have found to date. [*-)]

    On another topic - I have seen other threads where folks are overwhelmed by the size of this library. I too sat and looked at it for a while [:D]
    I have found that saving your own 'basic' set up and then adding matrix and patches to this 'basic' set up lets you grow into this library while making your growing set up backward compatible.

    Good luck - and don't panic [:D]

    Chris C

  • Chris
    I really appreciate the very helpful comments. Great idea to separate the keyswitches and controller info from the actual part. Hadn't thought of that one! Many benefits as you point out.

    My first attempt at programming with the library was fun, but utterly wrong. I decided to render the Mozart Concerto for flute and harp thinking what could be more straightforward. Then after working with it and comparing to a recording I own, I realized how important mastering the nuances and complexities of articulations is. Also I've downloaded some of the demos and their tutorial presets. I am amazed to find that sometimes there is a change from one matrix to another several times in one four note grouping. That's what boggles my mind.

    Steep learning curve, but I can tell it is worth it and your suggestions will help me in this. Thanks again.


  • Glad you found it useful.

    I also found the video tutorials very helpful. And if you can get to one of the live demos - not only do you get to meet other users - and to nick their ideas and techniques - but also seeing VSI played and programmed live set a few light bulbs off in my head too.