I'm beyond ready for the Auto Slur Melismas plug-in to work correctly. Applying it to a region, and then going over it to adjust the 60-70% of the time when it includes the next syllable in the slur, (especially when ties over barlines are involved) takes way longer than just manually adding slurs.
Win 11 / Fin 26.3 and 27
I'm pretty sure that every instance where things go wrong, it involves connecting the slur too far, ending with a note that is immediately followed by a rest. Most of the time, it starts on a syllable that starts a tie. I've added the brackets to indicate incorrect default behavior.
I arrange a lot of pop music, so this is a "nearly every single document" problem for me.
This is Finale 26.3 on Windows.
Is it the same in 26 and 27? What does Support have to say?
You're right, that's not how it's supposed to look but I don't agree that all of your examples are wrong.
Every one under a red bracket is wrong. I'll try it with 27 and report back.
To clarify: The shapes of the slurs are fine. I'm talking about the plugin that applies them based on where the lyrics are. The plugin draws slurs where none are needed, usually starting on a tied note and ending on a note that already has a syllable, just beyond the tie (or beyond what should be the last slurred note in a melisma)
27.4 has fixed some Elision slur issues per ScoringNotes. See if that helps.
Iniciar sesión para dejar un comentario.
6 comentarios
Fecha Votos