![]() It's bad enough that my Dorico 3.5 ignores them, too. I'm glad MM is aware of the fermata issue and is working to fix it. This way you can copy everything except the articulations into the new document, so you'll only need to enter the articulations again. Before copy/pasting, make sure to choose Edit > Edit Filter and deselect Articulations. You can refer to Creating Legacy Font Based Documents in Finale v27. If you've already written a piece and it wouldn't be feasible to start over, you can copy/paste into the new legacy font-based document. In the meantime, the workaround I'd suggest is to create documents with a legacy font rather than SMuFL, in which case Human Playback will work as expected. You can read more details in Certain Expressions and Articulations Not Playing Back in Finale v27.0. While I don't have a specific timeline for these Human Playback improvements, I can tell you that they are in progress. We were aware of this issue when Finale v27 was being developed, and our developers are working to improve Human Playback in a maintenance update to version 27. Unfortunately, Human Playback does not recognize some SMuFL characters yet, and that includes the fermata articulation from Finale Maestro. ![]() Finale's Human Playback engine relies on the the characters used in articulations and expressions to play them correctly. The default documents in Finale v27 were updated to use SMuFL fonts, although documents based on the legacy fonts are still available as well. ![]() One of the new features in Finale v27 is support for SMuFL fonts. You're right that there is a difference in behavior depending on the font you are using, such as Finale Maestro vs. We are aware of a problem with playback of some articulations and expressions in Finale v27, and I can provide some information and a workaround. ![]()
0 Comments
Leave a Reply. |