Finale 27 on a M1 2020 Mac mini (OS 12) with dual monitors SmartScore 64 Pro, JW Plug-ins www.cantilenapress.com "The better the composer, the better the notation."
I also got word from MakeMusic that they are "aware" of the problem. But, then, they have been aware of the problem for quite a while now according to previous reports.
Is this the way this is usually done? I am more familiar with double stemming, or using small notes to show differences of this kind. If you are innovating, be aware that there might be confusion...
Thanks, Mike. http://forum.makemusic.com/ is now responsive and searchable. Perhaps there was maintenance going on.
I agree completely that having to explain notation is generally a bad idea and often indicates a notational failure on the composer's part. And as you said, it may be necessary to explain it. Howe...
I agree that obscure notation is generally not a good idea. But the large fermata is actually fairly self-explanatory when you see it in context. It means the same as a single note fermata but appl...
Mike, large fermatas that cover more than one note are not common, but do occur in Mozart and Schubert and other composers. See: https://notat.io/viewtopic.php?p=100&hilit=fermata#p100
I tried that, Mike, but with no success.
I am having the same issue with Finale 27, that is the tuplet number can only be moved in a jerky imprecise way with the mouse. The arrow keys move the number normally. The same thing is being expe...
Thanks, Mike. Finale 25 is working fine, other than the problem described, so Rosetta II must be in effect. I also notice a similar problem happening with certain operations in the Speedy edit win...
Thanks for that information, George. That was what I have concluded; there is really no reason to move them out of 25.5. That assumes the 25.5 will always be viable on newer Mac operating systems, ...