Forum Jump
Hello!
I am struggeling to get VI Special Edition to play portamento in Dorico.
I cannot find the portamento in dorico anywhere. I try as described in the dorico manual to insert a glissando and write portamento in the popup but this does not trigger the portamento sound in syncron player.
How do i get dorico to tell the syncronplayer to trigg a portamento in syncronplayer.
It only plays a glissando (with a cromatic run) i just want the player to do a short slide up to the next note.
What are i'm missing here?
Thanks
Lasse
|
|
|
|
Hi,
I was just about to prepare to ask the same question!
I looked at the expression map for Special Edition. The right key switches are ordered for the right cells in Synchron Player. The problem: this brings us to legato (with a chromatic run) and not the portamento articulation (the cell just below). The result is the same whether we use the line or zig-zag line symbol (Glissando / Portamento) in the Dorico's score. Everything seems to indicate a bug in the expression maps.
Has anyone encountered the same problem? A solution?
Thank you very much,
Claude B.
C.B.
|
|
|
|
Hello Lasse and Claude!
Thanks for your message.
Currently portamento patches cannot be used with Dorico comfortably. It's not possible to assign playing techniques to ornaments such as glissando or portamento. Custom "portamento" articulations don't bring satisfying results either, because the switches from the Expression Maps always get sent before the note. In this case this leads to a portamento performance that's one note early.
We have already reported that to the Dorico team. It's in their hands.
Best regards, Andi
Andreas Olszewski Vienna Symphonic Library
|
|
|
|
Thanks Andy.
Hope a fix will come soon from Dorico team.
Claude B.
C.B.
|
|
|
|
Hello
thanks for reply.
i Get answer from John at Steinberg dorico. I will copy and paste. And my quesstion Are, can it be done this way ?
is it possible to Edit the template that vsl create for syncronized spesial edition without mess it up?
 document.write(
'<'+'a'+' '+'h'+'r'+'e'+'f'+'='+'"'+'&'+'#'+'1'+'0'+'9'+';'+'&'+'#'+'9'+'7'+';'+'&'+'#'+'1'+'0'+'5'+';'+'&'+'#'+'1'+'0'+'8'+';'+
'&'+'#'+'1'+'1'+'6'+';'+'&'+'#'+'1'+'1'+'1'+';'+'&'+'#'+'5'+'8'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'5'+';'+'&'+'#'+'5'+'1'+';'+
'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'5'+';'+'&'+'#'+'5'+'2'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'5'+'3'+';'+'&'+'#'+
'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'5'+'7'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'6'+'9'+';'+'&'+'#'+'3'+'7'+
';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'5'+'0'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'5'+'3'+';'+'&'+'#'+'3'+'7'+';'+'&'+
'#'+'5'+'5'+';'+'&'+'#'+'5'+'0'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'5'+'5'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+
'2'+';'+'&'+'#'+'4'+'8'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'5'+'2'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+
'&'+'#'+'5'+'7'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'5'+';'+'&'+'#'+'5'+'1'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+
'5'+'1'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'7'+'0'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'5'+';'+'&'+'#'+'5'+'3'+
';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'5'+';'+'&'+'#'+'5'+'0'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'5'+';'+'&'+'#'+'5'+'1'+';'+'&'+
'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'5'+'3'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'6'+'8'+';'+'&'+'#'+'3'+
'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'4'+'9'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'5'+'7'+';'+'&'+'#'+'3'+'7'+';'+
'&'+'#'+'5'+'4'+';'+'&'+'#'+'6'+'7'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'0'+';'+'&'+'#'+'6'+'9'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+
'5'+'4'+';'+'&'+'#'+'5'+'1'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+';'+'&'+'#'+'7'+'0'+';'+'&'+'#'+'3'+'7'+';'+'&'+'#'+'5'+'4'+
';'+'&'+'#'+'6'+'8'+';'+'"'+'>'+'&'+'#'+'1'+'1'+'5'+';'+'&'+'#'+'1'+'1'+'6'+';'+'&'+'#'+'1'+'0'+'1'+';'+'&'+'#'+'1'+'0'+'5'+';'+
'&'+'#'+'1'+'1'+'0'+';'+'&'+'#'+'9'+'8'+';'+'&'+'#'+'1'+'0'+'1'+';'+'&'+'#'+'1'+'1'+'4'+';'+'&'+'#'+'1'+'0'+'3'+';'+'&'+'#'+'6'+
'4'+';'+'&'+'#'+'1'+'0'+'0'+';'+'&'+'#'+'1'+'0'+'5'+';'+'&'+'#'+'1'+'1'+'5'+';'+'&'+'#'+'9'+'9'+';'+'&'+'#'+'1'+'1'+'1'+';'+'&'+
'#'+'1'+'1'+'7'+';'+'&'+'#'+'1'+'1'+'4'+';'+'&'+'#'+'1'+'1'+'5'+';'+'&'+'#'+'1'+'0'+'1'+';'+'&'+'#'+'1'+'0'+'9'+';'+'&'+'#'+'9'+
'7'+';'+'&'+'#'+'1'+'0'+'5'+';'+'&'+'#'+'1'+'0'+'8'+';'+'&'+'#'+'4'+'6'+';'+'&'+'#'+'9'+'9'+';'+'&'+'#'+'1'+'1'+'1'+';'+'&'+'#'+
'1'+'0'+'9'+';'+'<'+'/'+'a'+'>');
" data-name="John at Steinberg via Steinberg Forums">
John_at_Steinberg December 14
Dorico unfortunately didn’t have portamento mapped internally yet. If you’re using a vsl instrument that has a key switch for portamento you can create a playing technique and map that to the playback technique of ‘Portamento up’, which is already defined in the expression map.
Then use that new playing technique in the score where you need it (and optionally hide it using the properties panel)
Thanks
Lasse
|
|
|
|
Hello Lasse!
That custom playing technique that John mentions doesn't work properly either, because it will always be one note early. The portamento transition will go from the preceeding note to the note where the portamento custom articulation mark is added. I have reported that to the Dorico team a while ago.
Best regards, Andi
Andreas Olszewski Vienna Symphonic Library
|
|
|
|
portamento in general works perfectly OK with Dorico. I find the best way seems to be to create a new custom playing technique called "portamento" (which makes it easier to distinguish from those built in to the software) and add it to the Expression Map. You then also put a port slide in the score but you must disable the playback, otherwise it will override the VSL switch. In the score then hide one or the other as preferred.
It may be that John's suggestion also works but one other often critical step is to assign a "playback start offset" in the order of -10 to the note in question. This ensures that the port starts on the correct note. Several people on the Dorico forum have confirmed my suggestion works when they had otherwise had some problems.
A final point is that if you use the VSL SE template, you not only can but probably should be editing it to match your own musical preferences Simply adding a line assigning a keyswitch to portamento won't break anything -- if you make a mistake, just modify or even delete the line in question and nothing will get broken. Of course it's always best to export the original EM as a back-up just to be sure.
David
|
|
|
|
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.