I switched to Dorico several years ago and had to abandon using VSL - so I'm adding my voice to those who have requested VSL - Dorico integration. I know this cannot be turned around on a dime (that's an American expression) but I hope to see this soon. Thanks!
-
-
I have propose before but you refused
I have 3 weeks free where I can help, what do I gain ?
-
Hi Cyril,
You could start with Expression Maps for Special Editon Volume 1 and see how that works (you have the VI Special Edition Volume 1 registered
Your gain is the grattitude of your fellow Dorio users.A few words why this is not such a trivial task:
AFAIK, Dorico only covers around 50% of the articulations available with our bigger library products, so you will have to create new articulations in Dorico and assign them to the corresponding articulations in our libraries.Consistency and accuracy is key in such an undertaking.
The next challenge is that a dedicated Installer (like for Sibelius) has to be created, that places the correct files in the correct locations (manual installation is very tricky, unfortunately).
We don't have ANY resources to support this process right now, so my suggestion would be to start small and work your way up from Special Editon Volume 1 (which doesn't need many additional articulations added).
The alternative is to wait until Andreas has the time to provide you with the high standard flawless expression maps you are used to.
Best,
Paul
Paul Kopf Product Manager VSL -
Paul, while editing the Expression Maps you supplied for the High Strings, I can see that some articulations are duplicated. I don't see any difference in the two Legato entries just at the beginning of the list.
Is there a reason for these duplicated entries? Can we remove them, ignore them, or should we leave there for some particular reason?
Paolo
-
Hi Paul,
I'm not sure it is something that is not working. But I would like to understand why it is that way.
In Dorico, I import, for example, the "VSL Strings - Violins, Violas, Celli.expressionmap" file for Cubase.
In the list of techniques, I can see a first "Legato", linked to a C1 keyswitch, and another Legato, linked to the D#1 keyswitch.
The same happens with "Legato+Non Vibrato", "Con vibrato+Legato" and other articulations.
I can't understand the reason why there are multiple occurrencies of some articulations. If they have to be there, what's the particular use of each of them?
Paolo
-
Hello Paolo!
The Cubase Expression Map "VSL Strings - Violins, Violas, Celli" contains legato and "non legato" in various combinations with other articulations. Every combination is included one time only. The map isn't 100% compatible with Dorico though.
Best regards,
Andi
Vienna Symphonic Library -
Actually Andi, the comment that the Cubase VSL Strings is not 100% compatible with Dorico seems rather flattering 😊. I have found the compatibility to be nearer zero but I'm just trying out Dorico 3 and am maybe doing something wrong. If there is a way to get even 90% compatibility, then please let me know how best to set up a simple string quartet using the solo strings in Dorico using that Expression Map. If it's really not worth the effort (far too complicated to do manually) then any updates on progress towards a native Dorico version would be most welcomed.
Incidentally, the SE Expression map does seem to work quite well with the SE solo strings but of course having bought the full Solo Strings package, I want to use it!
David
-
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
