Any updates on this as of July 2024?
Nope.
I expect, when there is an update, either the Development Team or interested users will make sure folks know.
Just chiming in here - please let users “insert end tie” or create some other way to do this very basic thing asap - thank you!
Hello Susan, and welcome to the forum!
There is already another way to do this thing: by using l.v. ties and adjusting them in Edit Mode.
At some point in the future there will be probably a built in clever “Dorico” solution to handle these situations.
ps.: as I am not an English mother tongue speaker, what does asap mean?
“As Soon As Possible”
Thanks Derrek, that makes sense.
asap, please vs. asap, thanks seems to have quite a different meaning, I feel. Both seem polite, one of it is polite.
At first it reminded me of Aesop, a Greek storyteller. An Australian company uses it as brand name for skin care products.
I think many people have a list of things they are really hoping for in Dorico 6 - I certainly do - but my expectations are tempered by the knowledge that everybody’s list is different!
Hi @Susan_Capestro and from me also: welcome to the Forum.
In case you don’t know, the mentioned (by @k_b ) l.v. tie, is to find on the manual, that you can reach with the link below
:
Please don’t get addicted to asap. Its use is most often passive-aggressive.
(Sorry for that, I edited my post.)
Sorry about the asap! No offense intended, I was just chiming in, having used Dorico for quite a few releases, always creating l.v. ties and adjusting them, just hoping for a quicker way. Thanks!
I did it in Finale by using slur and editing after. Can it work im Dorico, too?
The laissez vibrer tie is the thing to use. Dorico won’t slur to nothing, or to a rest.
I would surely appreciate Dorico handling ties to 2nd endings. I shudder to think of the complexity of the program in dealing with all these fine points but I seem
to need it more often than I expected.
Regards,
Marc
Hi @mjhemphill, and welcome to the Forum.
In the meanwhile, you can record a macro that produces a “second ending tie” automatically (you may need to make minor adjustments, depending on the context of your piece). And sorry for my terrible French pronunciation!:
“…hope it helps”
you are an angel, Christian. Thank you so much for your incredible help to everyone.
I’d like to offer an alternative method (which of course I saw somewhere on the forum, I believe it was johnkprice who suggested it but I can’t find the post anymore) which I started using when I needed to add a backward tie to a note that was also tied to the next note in the bar- you can’t use an l.v. tie in those cases. It involves adding a whole note grace note (because it’s stemless) before the first note in the 2nd ending with playback suppressed, setting the scale to 100%, tying it to the main note and hiding the notehead.

Other than being able to use this method if the first note in the second ending is tied to the next one, I also like that it creates some extra space at the beginning of the bar which avoids collision of the tie with the repeat barline (of course, the latter can also be a disadvantage when you already have ample horizontal space). I haven’t tried to record a macro for this yet, but I’m sure that’s also possible using @Christian_R 's instructions. ![]()
New to forum. And sorry. But, Dorico people, this is simply not acceptable. How come simple features used in everyday life for many composers and editors are not yet present in the PRO version?
Heckuva self-introduction….
Welcome to the forum, @stripiperdit. I trust you’ll find this a valuable place filled with many fellow users of good will.
I kind of agree. But let’s put this in perspective: Dorico is eight years old. That featured appeared in Sibelius last year, I think (or was it 2023?). Kind of over 30 years after the app appeared.
Let’s be clear, I think it’s the most wanted feature now, and the Team probably knows, and they won’t implement it until it’s perfect (or close to it).
There are workarounds (and since we now have real note hiding tools, those are way easier than they were one year ago — described by @Zalde up there), and they do work.
