Vienna Symphonic Library Forum
Forum Statistics

200,608 users have contributed to 43,204 threads and 259,106 posts.

In the past 24 hours, we have 4 new thread(s), 9 new post(s) and 72 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries (legacy)
  4. Expression Maps for Cubase need to be *REDONE* except the ones for Dimension Strings.
  • N
    N
    last edited
    last edited

    @DaddyO said:

    I still don't get the notion that harsh language is warranted, either for Steinberg or for VSL. In the first place, it usually doesn't move people to respond positively to your suggestions; more often, people will react by diggin in their heels. In the second place, it may say more about your own attitude issues and unrealistic expectations than it does about the people you are unloading on. Direct and unvarnished objective criticism is helpful. Ridicule and harsh language? Usually not so much. You might find it helpful to consider how you would respond if someone turned your own words on yourself. There's enough problems to overcome in life without needlessly creating more for yourself.

    Thanks, I will try to tone it down on my next frustrating moment.  🤐 My apologies...

    Btw, Steve Jobs was known to be harsh with his employees, and managed to create amazing products in the end. Bottom line, if something needed a redesign, it needed a redesign, and he'd send it back to the drawing board...

    Well written expression maps for Cubase are critical for utilizing VSL to it's full potential (if you are a Cubase user). There needs to be a way to have 100% coverage of the articulations. I can possibly do it myself, but would rather have a solution from VSL as they are far more experienced in this than someone like me.
  • J
    J
    last edited
    last edited

    @nektarios said:

    Btw, Steve Jobs was known to be harsh with his employees, and managed to create amazing products in the end. Bottom line, if something needed a redesign, it needed a redesign, and he'd send it back to the drawing board...

    My personal little peeve is when someone brings up "Steve Jobs" in any kind of discussion. From there on, I just stop listening. "But dude, Steve Jobs used to boil his eggs soft!.." Well?.. It's also generally brought up as an attempt to drive a non-existant point home, by the head and shoulders.

    Meaning: don't you think you're really exaggerating now? A "redesign"? We're talking about expression maps. We're not even talking about VSL products!

    Considering the time and energy already invested in this thread: you could have punched in those few spiccati and portati you're missing into the expression maps by now.
  • N
    N
    last edited
    last edited

    You prove my case: if it is so simple, why didn't they add them? I can certainly add them myself, but that is not the point. What is needed, I think, is each library should have their own individual Expression Map that matches the library presets (without the need to load a separate expression map preset). That's because some libraries just have more articulations than others (i.e. Orchestral/Solo Strings).

    It needs a redesign because right now it's more of a setup than a way of specifying articulations (a setup I don't favor). For instance, articulations change based on speed (staccato/spiccato). Anyway, they have already done it perfectly with Dimension Strings, and that should be their gold standard. I could probably devote a whole weekend and do it myself, but right now, I just don't have the time...

    I am done with this subject now. I'm glad we've beaten this to death... 😈
  • W
    W

    Hmmm... the strength of the VI Pro is that you can configurate it for your very own unique needs.

    IMO very soon one will come to the point when one will have to create ones own Xmaps designed for ones specific needs.

    It is nice to have some Xmaps for a start but actually it is the cook who has to keep the knives sharp.
  • N
    N

    Each person can have their own unique setup, which is great. For example, the Y Axis being cotnrolled by speed, or having a sequence map etc. etc. But I am not looking for a setup. I am looking for a way to specify any articulation from the given set of articulations. For example, if I want a detache articulation, to specify it, and indicate in a different selection if it's the long or short version. In other words, being able to see all articulations being specified on the midi editor. They do this already with many of them.

    At the end, I think I'll devote a weekend and do it myself and share it with everyone.
  • J
    J

    Dimensions Strings has fewer articulations than many other VSL libraries, so it is possible to work with one neat expression map. If all of the articulations of say Solo Strings were put in a single expression map, it would be a mess in Cubase, which isn't really set up to deal with an instrument having 150 articulations.
  • N
    N
    last edited
    last edited

    @johnstaf said:

    Dimensions Strings has fewer articulations than many other VSL libraries, so it is possible to work with one neat expression map. If all of the articulations of say Solo Strings were put in a single expression map, it would be a mess in Cubase, which isn't really set up to deal with an instrument having 150 articulations.

    Since articulations can have different variations, it can easily be condensed. For example, staccato and rep_stacatto. So if I select a staccato, I can specify which type I want (repetition, or regular). They do this already, but don't cover a vast number of them.
  • DaddyOD
    DaddyOD
    last edited
    last edited

    @nektarios said:

    Each person can have their own unique setup, which is great. For example, the Y Axis being cotnrolled by speed, or having a sequence map etc. etc. But I am not looking for a setup. I am looking for a way to specify any articulation from the given set of articulations. For example, if I want a detache articulation, to specify it, and indicate in a different selection if it's the long or short version. In other words, being able to see all articulations being specified on the midi editor. They do this already with many of them.

    At the end, I think I'll devote a weekend and do it myself and share it with everyone.

    Yeah, I get what you're looking for. That's how I'm starting out with expression maps, just mapping individual articulations so I can select them. I changed my initial approach to where I'm now saving the X-axis cells (after the first column) for variations on the each articulation, whether it be multiple articulations, or cross-fades, or time-stretched versions, etc. That way my map can grow easily as I advance in my ability to us VI Pro.

    W 10 i5-9600K 64 GB Synch - Woods, Brass, Perc I, Str Pro, Elt Str, Dua Str & Sordino, Prime Studio - Woods, Perc, Solo Str, Ch Str, Orch Str, App Str, Harps, Choir St Dim - Brass, Strings VE Pro, MIR Pro 3D, Vienna Suite Pro Cubase 14, St One 6, Dorico 5
  • W
    W
    last edited
    last edited

    Hi guys,

    I run into another problem. Due to the lack of Cubase to allow scrolling the expression map region very soon there is no space on the screen when it comes to large expression maps with loads of articulations.

    So I created a universal expressionmap for low and high instruments. This is for the midi-editor only. The notation feature has no affect on the expressions.

    Basically it only names the cells, rows and the matrices but no articulations at all to keep everything as flexible as possible.

    It is designed as the following:


    Matrix one has 3 rows

    Matrix two has 1 row

    Matrix three has 3 rows

    Matrix four has 1 row

    and finally Matrix five has 3 rows.

    Acutally one is controlling the cells rather than the articulation. So no matter what is loaded into a cell one can trigger these articulation by calling the cell.

    I also have set the cc1 for changing rows to pay attention on the SE. Changing rows with "speed" will work properly anyway as long as cc1 is not set as a controller for something.

    I am using an excel sheet to keep up with the loaded cells per instrument but also have opened the VI pro on a fifth screen anyway.

    One will get a routine and I am quit happy because I have a clear and almost empty screen.

    It can be expanded at any time following the logical stucture.

    BUT AGAIN: This is not meant to be used with the Notation feature of Cubase. Yes, you can use it but then you will have to type all the weird text-strings.

    VSL Universal ExMaps.zip-1696282562440-b0m8l.zip
  • T
    T

     

     Hi,concerning expression maps, i did a lot trial and error to build a map which fits my needs best.I added two screenshots.I use Special Edition Full (old Version) and Appasionata1 full.

    I fact the amount of articulations coming with the Special Edition are quiet limited, it wasn't a big deal to make expression maps containing all articulations available. I made one for string, one for wood and one for the brass instruments. More compllicated was to make the maps for the Appasionata Strings, from which the screenshots are made.

    I wanted to load all atriculations available and use only one map to play them all.

    The changes I did in VIPro:

    -expression is controlled by CC1 (=modwheel) (one thing i'll never understand when looking at the presets provided by VSL is, why should i play "not-percussive" instruments with velocity ???)

    -when CC1 is lowered near 0, expression control is being given back to velocity (useful when playing pizz. or staccato, short notes). This is done by changing the VeolcityXF ON/OFF controller to CC1, too. Applying a curve.

    Now to the expression map itself, which might look a little bit complicated.

    It has 5 large rows.

    The first row, with the smaller rows 1 to 9 ist the main selection. The other rows are a kind of "fine selection".

    To get the articulation you want, you have to select the same number.

    It's not easy to understand, but easy to use (i think), I'm not a good explainer and egnlish isn't my mother language,so here are some

    examples:

    You want to play a Sustain Note with strong Vibrato:

    You select "1 Sustain"(1st row)  and "1+2 Vib+  3 Slur | 4 - " (11th row from the top)

    1 is Sustain, Vib+ means strong vibrato.

    Legato with strong Vibrato:

    You select "2 Legato vel: portam" from top and again "1+2 Vib+  3 Slur | 4 - "

    vel: portamento means: if you hit hard, you'll get a portamento

    Performance repetition harsh:

    You select "4 perf. rep." (4th row) and "1+2 tune | 3+4 harsh" (13th row)

    Diminuendo - 4 seconds:

    You select "5cresc. vel:dim." (5th row) and "5 4sec.|6 6sec." (18th row) and hit hard.

    The first selection selects crescendo/diminuendo, the second the time (4 seconds).

     

    You have just to select the main articulation in row 1-9 and then look for the number you

    selected in the other row, to do the fine tuning.

     

    If you have any questions don't hesitate asking them.

    Best regards

    Image

    Image
  • T
    T

    Thank you TFIS for sharing. I've running around the issue of VSL Expression Maps in Cubase for years now, and unfortunately there is no best method to be found. Everyone just has to custom create a map which suits his or her way of working. Until Steinberg gets their act together and develops this excellent feature further, possibly trashing the useless and space-consuming "staircase" pattern of the articulation lane in favor of a drop-down menu and one or two simple lines. There is absolutely no point in having all possible articulations visible at all times when most of them never occur simultaneously.

    Just my 2c.
  • G
    G

    While trying to make expr. maps for chamber strings and for solo woodwinds and brass', I have of course also been looking for "universal principles" to facilitate making maps without too much effort. I would be interested to find out/hear about any "principles" VSL had in making the expr. maps with the presets that were made available for us.

    regards Gerard
  • andiA
    VSL Team
    andiA

    Hello Gerard!

    For the Special Editions and our later Instrument collections we made Expression Maps for the VI presets and matrices that come with the library content. This seems to be the better way to go than making dedicated VI presets with matrices of grouped articulations which we did for earlier Instrument collections.

    Best regards,
    Andi

    Vienna Symphonic Library
  • G
    G

    Andi, thanks, I can well agree with that approach. Lacking "in depth" experience in instrumentation, I add to the matrices one or two with the articulations that appeal to me, but those are without "any" structure,

    regards,
    Gerard