Forum Jump
Originally Posted by: lunar_28664 
Actually Andi, the comment that the Cubase VSL Strings is not 100% compatible with Dorico seems rather flattering  .
I'm inclined to agree. Having worked out over the summer how to implement keyswitches in Finale, I had a bit of a head start working on the Dorico maps. First I looked at an import from the Cubase set, and found things like multiple instances of (say) legato referencing separate keyswitches. Rather than try to figure out why (also, there were combinations of terms that you can't* create or edit in Dorico) I set about making a set of my own.
Once you realize that, for Synchronized Special Edition, most sets are largely the same -- flute, oboe, clarinet, for instance -- it cuts down the time it takes.
*Shouldn't say 'can't'. Should say 'I haven't found a way to'.
|
|
|
|
|
|
Started to work with Dorico on day 1. Since Dorico 2 I switched nearly completely from Sibelius to Dorico. After working 15 years with Sibelius on a daily basis, I now start to forget how to work with Sibelius ...
At the moment I stopped using my VSL libraries, until it will be possible to use them in Dorico. I don't have the time, to create expression maps on my own. So this is a big +1.
|
|
|
|
|
|
I've tried developing my own expression maps for my universal VI presets, and for the VSO-XP library.
It is relatively easy to adapt Cubase xmaps, or create new ones, for Dorico. The basic commands already work, but multiple techniques on the same position are not always recognized. So, for example, accent and staccato may not always be recognized. Also, sending a command to select the Strings instrument and then the violas+pad down the tree doesn't always work.
The problem is that the system doesn't seem to be still complete in Dorico. And maybe there is some adaptment required to VSL and the other manufacturers in view of the use with Dorico. Once they work together, they will be a powerful creative tool, in my view without comparison with the others.
I hope
|
|
|
|
|
|
Hello,
I would like to know if we can expect the future Dorico Expression Maps for VSL to be compatible with VI Instruments and the Synchron-ized ones? And if it will be for Starter Editions and full ones?
Thanks for your answer!
Best regards,
Gil.
|
|
|
|
|
|
Hello Gil!
Every collection and most instruments of every collections would need its own Expresion Map. Furthermore it's currently not possible to make complex Expression Maps with combined articulations (like legato AND vibrato). So we can't yet say, for which collections Dorico Expression Maps will be made. We need to evaluate some things first and maybe wait for some further development at Dorico's side.
Best regards,
Andi Andreas Olszewski
Vienna Symphonic Library
|
|
|
|
|
|
I've bought Dorico in the meantime and actually found I can get reasonable results with the articulations just by starting with the Cubase strings map remapping the most important entries to the actual controllers/keyswitches used in the default "VSL Preset Level 2" with the Solo Strings. The most important articulations all seem to work except gliss which is (still) unsupported by Dorico, even in the new v3.1.
One thing which I still can't fully understand is dynamic control. VSL defaults to CC7 volume, CC11 Expression for strings, yes? One would think that the Volume dynamic in Dorico should be set to CC11 as appears to be the case in the Sibelius soundset. But it seems Dorico only transmits dynamics (as written in the score) to VSL through velocity and indeed the Cubase Expression Map is set to Note velocity. Frankly I couldn't care less (leaving aside for the moment questions of possible timbre differences) except of course that velocity naturally does not allow a dynamic change after the note in sounded and will require a doubling through a CC which can be done graphically in Dorico.
I've just seen from a different Dorico thread that Andi advises Velocity as primary dynamic controller together with VelX crossfade as a secondary. In actual fact my own tests led me to also to this but of course as VelX sends all the volume levels at once, you need to somehow compensate for the overall higher dynamic for instance. Any Dorico specific tips for the settings both in Vienna Instruments Pro and in Dorico -- for instance the optimal Dynamic Curve setting in playback settings?
many thanks, David
|
|
|
|
|
|
UPDATE
I realised I'd made a mistake in not changing the dynamics controller for all the articulations individually in the Dorico Expression Map as I'm used to just setting the control once in VI Pro itself for the instrument. So my previous post can be largely dismissed as nonsense and apologies for any confusion caused! In fact now, I get the same results setting Volume to CC7 as Note Velocity with the obvious exception that within-note dynamics work with the CC and not velocity. I'm using Vel.XF as secondary controller
This, though, begs the question why Andi advises in another Dorico post for notation software to use velocity as the primary dynamics controller in notation software (other obviously for percussive and other instruments with no post strike control). If I could understand this, then I might be another step on the way to really taming my VSL libraries!
|
|
|
|
|
|
Dorico makes it easy, in the Play mode, to deal with continual control of dynamics. So, maybe using modulation is better than velocity with long articulations in Dorico.
One of the things I love in the Expression Maps, is how you can use a text editor to batch-process several entries at once. Oh, how I would love if VSL presets were XML files!
Paolo
|
|
|
|
|
|
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.