Vienna Symphonic Library Forum
Forum Statistics

182,313 users have contributed to 42,218 threads and 254,754 posts.

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

  • Creating new presets for DAW and Notation

    Hi,

    I'm always trying to find a way to use a single set of selection commands, and a single set of presets, to choose articulations on both a DAW (Logic) and a Notation program (Dorico). This would allow easy transfer of sequence data between instruments and programs.

    I've had great hopes on the universal VIPRO and the Expression Maps presets supplied by VSL. However, none of them can be used, in my way of working, for all situations.

    - VIPRO presets are quite uniform and coherent. I've used a series of modified presets of this type up to now. Unfortunately, since the Basic matrix contains all the articulations on multiple rows, there is no way to let the Speed parameters alternate between slow and fast articulations (like legato slow and fast, or staccato and spiccato). You have to program it manually in the DAW, or in some way I've not yet discovered in the Notation program.

    - Expression Map presets are not universal. Strings have a map, Winds a different one, Dimension Strings another one, and so on. Higher-pitched and lower-pitched instruments use different maps. The good part is that each type of performing style (sustain, legato, staccato, tremolo…) is in a different matrix, so you can alternate two rows in a matrix to let the Speed parameter automatically choose the right articulation.

    Is this automatic selection of articulation useful, when programming in a DAW or a Notation program? Up to now, I've manually assigned the right articulation, but maybe it is better to let VIPRO decide which is the best choice. Or, will I always need manual control on these details?

    In any case, I fear I will have to make my presets again. This time I will probably not start from the VIPRO universal preset, but from the Expression Map preset supplied for the Strings.

    - Matrices (performing style) will be selected by the notes in the lowest octave in the MIDI map (C-1 to B-1).
    - The X-Axis (timbral variations) will be controlled by notes in the adjacent octave (C0 to B0).
    - Rows in the matrix (speed) will be automatically selected by the Speed parameter.
    - Slots in the cells (for crescendo/diminuendo or progr./dim. vibrato intensity) will be selected by CC#20.

    Both Logic and Dorico seem to allow this type of control mapping. I've not yet tested them for bugs or other issues, but on paper they should work.

    Everything will be controlled by a single Articulation Set or Expression Map. I will, however, have to create a separate preset for each instrument (and I plan to have some hundreds of them).

    How would you do, to build the presets? I plan to start from a modified Strings Expression Maps preset, with the controllers reassigned as described above. Starting from a template, I will drag all the needed patches from the different instruments repertory to the corresponding cell, then save the preset in the VSL Custom Data folder.

    I fear this will be a very long process. If someone has a better idea, I'll be very happy to consider it.

    Paolo


  • I use Sibelius and REAPER. I just export MIDI from Sibelius, drag-and-drop into REAPER, and it matches up.

  • Hi Paolo,

    actually I think your approach and workflow is the right one. I also spent quite a bit of time to look for better integration between different sofware and available sound maps and matrixes etc.

    The outcome of my research is discouraging similar to yours, too much discrepancies, and the only way to make it work properly and without redundancies, conflicts or mismatches is creating your own maps, full stop: it's a hell of a lot of work, I know, but the advantage is you really tailor it to your vey personal set of sound libraries, software and workflow (beside music style of course).

    I may add a comment: check the opportunity of using an additional dimension with KeySwitch velocity. Last versions of Logic offer already multi dimentional patches (more events triggering one articulation) in the articulation database, but still open the velocity of the keyswitch as additional dimension of a single event (e.g. when you trigger a KS note, if it's lower than 64 it will pick a cell, if it's higher it will pick another and so on). 

    The same is in VIPro, that allows you to control one of the X or Y dmension of the matrix with the velocity of the corresponding Keyswitch.

    Finally Dorico Expression Maps also offer 2 parameters for the KS event, the note and the velocity, enabling you to control different articulations with the same note, changing velocity.


  • Fatis, yes, the Keyswitch+Keyswitch Velocity is one of the most precious tricks in Logic. In VIPRO. It can however only be used for a limited set of situations with VSL presets (linking the X- and Y-axis).

    Making your own presets really seems the only way to deal with VSL's full instruments. I've been tempted to surrender, and adapt to the supplied presets, but then there are several things that make it impossible for me:

    - VIPRO presets do not cover all the articulations, but only the basic one (for example, I can't find separate vib/n.v. versions for legato); the same seems to apply to the Expression Map presets.

    - VIPRO presets can't rely on playing speed to automatically select articulations; the same happens with other presets.

    - In case you want to add something in the b-slots, you end out of the maximum of three messages allowed by Logic (and switching programming from CC1 to Keyswitch Velocity is a long work).

    So, unless you are happy with the basic set, and you are ready to create and use several different Articulation Maps, you need custom presets. It would have been great to see them made by VSL themselves.

    Paolo