Thanks Fatis, that's very informative.
Dorico, Notion, Sibelius, StudioOne, Cubase, Staffpad VE Pro, Synchon, VI, Kontakt Win11 x64, 64GB RAM, Focusrite Scarlett 18i20, August Forster 190
193,960 users have contributed to 42,904 threads and 257,885 posts.
In the past 24 hours, we have 4 new thread(s), 16 new post(s) and 82 new user(s).
Hello Andi
can you reply to my previous mail :
Hello Andi,
Can we have that list of requirements
Dorico Expression Maps is compatible with Cubase Expression Maps, VSL is compatible with Cubase Expression Maps, it is strange that VSL is not compatible with Dorico's Expression Maps
Thanks
I think Dorico is still a moving target in this respect, and they're waiting for something solid before putting energy into it.
Why do you answer for Andi ?
Are you a member of VSL team ?
Hello Cyril!
Please understand that I don't want to fully post this internal information on a public forum. I can give you an example though. So far it's not possible to make sfz or fp trigger the according articulations in our instruments. These notation marks can only modify the dynamics.
I also want to remind you that we try to have a friendly tone here. Two of your posts in this thread are close to an insult.
Best regards,
Andi
Hello Cyril!
Please understand that I don't want to fully post this internal information on a public forum. I can give you an example though. So far it's not possible to make sfz or fp trigger the according articulations in our instruments. These notation marks can only modify the dynamics.
I also want to remind you that we try to have a friendly tone here. Two of your posts in this thread are close to an insult.
Best regards,
Andi
Hello Andi
I did not mean to insult you
What post are close to an insult ?
Maybe it's a problem of a barier language !
Both VSL and Steinberg company and booth VSL and Dirico's users have interest to have the full support of all articulations
There are no secret to know what does and not does work
Doric's user may buy VSL and VSL users may buy Dorico
I have attached all the articulation supported by Dorico 1.
In Dorico 2 you can add your own articulation.
I fear, the fact, that there seem to be currently no velocity-Editor in the Dorico Player-Section, is something what can make it currently a bit difficult to work with VSL as we want to.
Yes there is ; look a bit better in the Play section
If my memory is good you can also use pppp to ffff
I fear, the fact, that there seem to be currently no velocity-Editor in the Dorico Player-Section, is something what can make it currently a bit difficult to work with VSL as we want to.
Yes there is ; look a bit better in the Play section
If my memory is good you can also use pppp to ffff
Well the picture you show is actually about note lenght, and not velocity! Whre should it be the velocity editor? I didn't find it, so if you did, please let us know! 😊
I fear, the fact, that there seem to be currently no velocity-Editor in the Dorico Player-Section, is something what can make it currently a bit difficult to work with VSL as we want to.
Yes there is ; look a bit better in the Play section
If my memory is good you can also use pppp to ffff
Sorry I thought I understood Daniel Spreadbuury right, in the Thread "Look of the velocity for single notes"
Where he answered for Dorico 1.12 "This is not currently possible in Dorico, but it is planned for the future."
However like the pretty limited Tempocurveeditor the solution for Velocityediting which is available now does not seem to me yet a really satisfying solution at least as far as the score gets a bit more complex.
So I understand why still for Dorico 2 the user ask nevertheless for "Note velocity lane, please"
I expect that User demands will bring Dorico closer to what we have in Cubase for Midiediting but imho we have not reached that point yet.
I fear, the fact, that there seem to be currently no velocity-Editor in the Dorico Player-Section, is something what can make it currently a bit difficult to work with VSL as we want to.
Yes there is ; look a bit better in the Play section
If my memory is good you can also use pppp to ffff
Well the picture you show is actually about note lenght, and not velocity! Whre should it be the velocity editor? I didn't find it, so if you did, please let us know! 😊
There are two parts on the note, the velocity is blue surrounded by orange
You say:
"There are two parts on the note, the velocity is blue surrounded by orange..."
Then I'm sorry, but you are wrong. Read the manual and/or experiment yourself: it's the note duration "as played" over the note duration "as written".
(Why do you defend so strongly a misunderstanding without verifying it before confirming wrong assumptions by the way?)
Can you explain why there is this pref in Dorico
This is the authomatic management of dynamics: you may decide the dynamic curve across expression marks.
It will affect velocities or CC according your choice or the Expression Maps choice (velocity or CC): that's probably why an independent velocity editor is not implemented yet: it would conflict with authomatic rule, and so a more complex code has to be written to manage mismatch and assign priorities.
Anyway it's not rocket science and several other programs have fixed it already for years, that's why I complained that Dorico is still too primitive and limited for the actual ambitious target they have.
They are focusing on note-writing first... and in this field the program is already very advanced. I just hope they will fill the gap in MIDI editing ASAP.
But up to now, no way. I understand why VSL is waiting for better feedback and fixes by Steinberg before they spend excessive time.
Sorry I thought I understood Daniel Spreadbuury right, in the Thread "Look of the velocity for single notes"
Where he answered for Dorico 1.12 "This is not currently possible in Dorico, but it is planned for the future."
However like the pretty limited Tempocurveeditor the solution for Velocityediting which is available now does not seem to me yet a really satisfying solution at least as far as the score gets a bit more complex.
So I understand why still for Dorico 2 the user ask nevertheless for "Note velocity lane, please"
I expect that User demands will bring Dorico closer to what we have in Cubase for Midiediting but imho we have not reached that point yet.
You don't have to apologize, you understand correctly, no velocity editing yet.
The actual possible workflow is:
- let expression map manage correct keyswitches
- let dynamic curve manage velocity (then all the expression map articulations must be checked with "Velocity" only)
- adjust manually all the CC in the CC lane.
This will go very close to your intentions, but only until the velocity and expression are going in the same direction. If you want to use velocities for attack and CC for expression independently, you will face some issues (because all pp will have very low velocity and all ff will have very high velocity etc. etc.)