Accidentals not displaying in Finale 25
Moderators: Peter Thomsen, miker
Hello everybody!
I have this problem: occasionally, accidentals will NOT display on Score and Parts unless I force them to show (using the * key in speedy entry or otherwise). Finale will play it back correctly but they NOT display. Already for two different scores I had problems because when the parts were played the errors came out! Anyone know how to avoid this problem? Thanks!! Corrado
I have this problem: occasionally, accidentals will NOT display on Score and Parts unless I force them to show (using the * key in speedy entry or otherwise). Finale will play it back correctly but they NOT display. Already for two different scores I had problems because when the parts were played the errors came out! Anyone know how to avoid this problem? Thanks!! Corrado
Hello Zuill, I attached a fragment where you can see the problem.
At bar 2: lower staff piano b and d accidentals not display!
Thanks!
Corrado
At bar 2: lower staff piano b and d accidentals not display!
Thanks!
Corrado
- Attachments
-
- fragment.musx
- (92.41 KiB) Downloaded 96 times
- michelp
- Posts: 2045
- Joined: Fri Jul 25, 2003 3:35 pm
- Finale Version: 27.4.1,26.3.1, Mont.
- Operating System: Mac
This happens sometimes when you delete a note of the same pitch (with an accidental) before the one in question.
Check the attached file. There are 2 Bb. Delete the first one, the second doesn't display the needed accidental.
This "dangerous" behavior (the audio will sound correct !) is not new and has never been fixed.
Check the attached file. There are 2 Bb. Delete the first one, the second doesn't display the needed accidental.
This "dangerous" behavior (the audio will sound correct !) is not new and has never been fixed.
Michel
MacOsX 12.7.4, Finale 27.4.1 & 26.3.1, Mac Mini Intel Dual Core i7 3Ghz, 16 Go Ram. Azerty kb. MOTU Midi Express XT USB, Roland Sound Canvas SC-88vl, MOTU Audio Express. 2 monitors (27"' pivot, 24'"), JW Lua, RGP Lua
MacOsX 12.7.4, Finale 27.4.1 & 26.3.1, Mac Mini Intel Dual Core i7 3Ghz, 16 Go Ram. Azerty kb. MOTU Midi Express XT USB, Roland Sound Canvas SC-88vl, MOTU Audio Express. 2 monitors (27"' pivot, 24'"), JW Lua, RGP Lua
- zuill
- Posts: 4418
- Joined: Sat Dec 10, 2016 9:35 pm
- Finale Version: Finale 2011-v26.3.1
- Operating System: Windows
The reason the second note does not display the accidental after the first note is either changed to a natural or removed is that the second note is already frozen regarding accidentals. Finale does not do this automatically. Somehow this state was activated by something you had done. How you entered it is possibly involved. How were these notes entered?michelp wrote: ↑Thu Mar 11, 2021 12:54 pmThis happens sometimes when you delete a note of the same pitch (with an accidental) before the one in question.
Check the attached file. There are 2 Bb. Delete the first one, the second doesn't display the needed accidental.
This "dangerous" behavior (the audio will sound correct !) is not new and has never been fixed.
accidentals.musx
Zuill
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."
"When all is said and done, more is said than done."
- zuill
- Posts: 4418
- Joined: Sat Dec 10, 2016 9:35 pm
- Finale Version: Finale 2011-v26.3.1
- Operating System: Windows
Possibly something happened as the notes were being entered that caused the problem. Finale won't do that automatically. The state of these accidentals is frozen, as indicated by the * when on that note in Speedy Entry. I take the time to visually inspect my scores for these kind of errors as even when we're careful, something we have done causes strange behavior. It's rarely the program, unless we enter things in ways that might trigger behaviors. Sometimes imported MIDI files or XML files can have these errors.
Two plugins can be helpful, but are not always perfect either. Jari's JW Accidentals plugin, and the Canonic Utilities plugin. The second one seems odd, by its name, to have anything to do with accidentals. However, it has a little known feature that unfreezes frozen accidentals, which is the issue in your file.
Zuill
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."
"When all is said and done, more is said than done."
- zuill
- Posts: 4418
- Joined: Sat Dec 10, 2016 9:35 pm
- Finale Version: Finale 2011-v26.3.1
- Operating System: Windows
Something else. Finale used to have a "Check Accidentals" feature that was removed when they redesigned the whole accidental paradigm. I don't recall which version made that change. I already mentioned 2 plugins which can be of help. Another place where you can actually see what's "behind the curtain" is the Speedy Edit Frame, accessed by ctrl-clicking the measure in Speedy Entry. There is a box by "Freeze Accidental" that is checked when an accidental is frozen. In the attached file (fragment), I unchecked each of the frozen accidentals and they now appear. Again, Finale won't automatically freeze these accidentals. Something we do causes this. Thinking about how we are entering notation and making the necessary adjustments usually prevents this kind of result, which is definitely undesirable. If, somehow there was something Finale did to cause this (I can't imagine), we have ways to fix it.
I hadn't thought of this before, since I don't use the Cautionary Accidentals plugin, but that plugin might also have triggered freezing of accidentals. Did you use that plugin?
Zuill
I hadn't thought of this before, since I don't use the Cautionary Accidentals plugin, but that plugin might also have triggered freezing of accidentals. Did you use that plugin?
Zuill
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."
"When all is said and done, more is said than done."
- michelp
- Posts: 2045
- Joined: Fri Jul 25, 2003 3:35 pm
- Finale Version: 27.4.1,26.3.1, Mont.
- Operating System: Mac
I have entered these notes with the mouse, rests first, converted to half notes. The strange thing is that I cannot reproduce the problem anymore (I encountered it several times this morning !). It is a familiar one... Why this accidental gets frozen on the second note is a mistery.zuill wrote: ↑Thu Mar 11, 2021 2:06 pmThe reason the second note does not display the accidental after the first note is either changed to a natural or removed is that the second note is already frozen regarding accidentals. Finale does not do this automatically. Somehow this state was activated by something you had done. How you entered it is possibly involved. How were these notes entered?michelp wrote: ↑Thu Mar 11, 2021 12:54 pmThis happens sometimes when you delete a note of the same pitch (with an accidental) before the one in question.
Check the attached file. There are 2 Bb. Delete the first one, the second doesn't display the needed accidental.
This "dangerous" behavior (the audio will sound correct !) is not new and has never been fixed.
accidentals.musx
Zuill
Michel
MacOsX 12.7.4, Finale 27.4.1 & 26.3.1, Mac Mini Intel Dual Core i7 3Ghz, 16 Go Ram. Azerty kb. MOTU Midi Express XT USB, Roland Sound Canvas SC-88vl, MOTU Audio Express. 2 monitors (27"' pivot, 24'"), JW Lua, RGP Lua
MacOsX 12.7.4, Finale 27.4.1 & 26.3.1, Mac Mini Intel Dual Core i7 3Ghz, 16 Go Ram. Azerty kb. MOTU Midi Express XT USB, Roland Sound Canvas SC-88vl, MOTU Audio Express. 2 monitors (27"' pivot, 24'"), JW Lua, RGP Lua
- zuill
- Posts: 4418
- Joined: Sat Dec 10, 2016 9:35 pm
- Finale Version: Finale 2011-v26.3.1
- Operating System: Windows
You entered the rests in Simple Entry, I imagine. Did you then change them to notes in Simple Entry?
Zuill
Zuill
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."
"When all is said and done, more is said than done."
- michelp
- Posts: 2045
- Joined: Fri Jul 25, 2003 3:35 pm
- Finale Version: 27.4.1,26.3.1, Mont.
- Operating System: Mac
It must have been completely done with Speedy (2 half note rests with the numeric keypad (6), then the mouse to convert them into notes, and the + and - keys for the flat). I almost never use Simple.
Redoing these steps now functions normally, go figure...
Redoing these steps now functions normally, go figure...
Michel
MacOsX 12.7.4, Finale 27.4.1 & 26.3.1, Mac Mini Intel Dual Core i7 3Ghz, 16 Go Ram. Azerty kb. MOTU Midi Express XT USB, Roland Sound Canvas SC-88vl, MOTU Audio Express. 2 monitors (27"' pivot, 24'"), JW Lua, RGP Lua
MacOsX 12.7.4, Finale 27.4.1 & 26.3.1, Mac Mini Intel Dual Core i7 3Ghz, 16 Go Ram. Azerty kb. MOTU Midi Express XT USB, Roland Sound Canvas SC-88vl, MOTU Audio Express. 2 monitors (27"' pivot, 24'"), JW Lua, RGP Lua
- zuill
- Posts: 4418
- Joined: Sat Dec 10, 2016 9:35 pm
- Finale Version: Finale 2011-v26.3.1
- Operating System: Windows
For reference, in Simple, entering an accidental twice automatically hides the second accidental in the same measure. Speedy doesn't. So, on the second Bb, a natural would appear. Normally, pressing the - key changes it to a flat, but then the accidental is hidden per the convention of not showing the second accidental in the same measure.
Possibly, when pressing the - on the second note, the * got pressed too? They are next to each other on the numeric keypad. I'm just thinking about things that have happened to me in the past.
Zuill
Possibly, when pressing the - on the second note, the * got pressed too? They are next to each other on the numeric keypad. I'm just thinking about things that have happened to me in the past.
Zuill
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."
"When all is said and done, more is said than done."
- motet
- Posts: 8231
- Joined: Tue Dec 06, 2016 8:33 pm
- Finale Version: 2014.5,2011,2005,27
- Operating System: Windows
I don't know if this caused it, but I suggest getting out of the habit of using * in Speedy to create a cautionary, since it will remove a legitimate accidental if you hit it by mistake (and freeze it). Use the A key instead, which will toggle a cautionary but never remove a real accidental.
- zuill
- Posts: 4418
- Joined: Sat Dec 10, 2016 9:35 pm
- Finale Version: Finale 2011-v26.3.1
- Operating System: Windows
Pressing the * key freezes an accidental. Pressing it again does not unfreeze it. Pressing the A key freezes and accidental. Pressing it again unfreezes it. That is a big difference.
Zuill
Zuill
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."
"When all is said and done, more is said than done."
- zuill
- Posts: 4418
- Joined: Sat Dec 10, 2016 9:35 pm
- Finale Version: Finale 2011-v26.3.1
- Operating System: Windows
In Simple, ctrl+shift with the - key does the same as the * key in Speedy. Pressing that combination again does not unfreeze the accidental. Simple doesn't have a comparable method to the A key in Speedy, as far as I know.
Zuill
Zuill
Windows 10, Finale 2011-v26.3.1
"When all is said and done, more is said than done."
"When all is said and done, more is said than done."
Hello everybody, thanks for all your replies.
I contacted Finale support and there were no clarifying answers. I have had this accidentals not dispaying problem, up to now,
in two files: the first was a file started with Finale 2008 and ended with Finale 25.
In the opinion of Finale support, files coming from previous versions may have informations that produce errors.
So I was advised to export and import files in xml format.
But the second file, where I had the problem, is a file started and finished with Finale 25:
the error originated after a copy-paste from the version of Tuba and Piano to that of Tuba and Chamber Ensemble.
In the Piano part the accidental (natural) was present, in the version for Chamber Ensemble in the three parts, where I copied that particular phrase, the accidental not displaying.
I saw the error when I corrected the drafts of the publisher where the accidental (natural) appeared.
Finale support doesn't have an answer.
Thanks! Corrado
I contacted Finale support and there were no clarifying answers. I have had this accidentals not dispaying problem, up to now,
in two files: the first was a file started with Finale 2008 and ended with Finale 25.
In the opinion of Finale support, files coming from previous versions may have informations that produce errors.
So I was advised to export and import files in xml format.
But the second file, where I had the problem, is a file started and finished with Finale 25:
the error originated after a copy-paste from the version of Tuba and Piano to that of Tuba and Chamber Ensemble.
In the Piano part the accidental (natural) was present, in the version for Chamber Ensemble in the three parts, where I copied that particular phrase, the accidental not displaying.
I saw the error when I corrected the drafts of the publisher where the accidental (natural) appeared.
Finale support doesn't have an answer.
Thanks! Corrado
- motet
- Posts: 8231
- Joined: Tue Dec 06, 2016 8:33 pm
- Finale Version: 2014.5,2011,2005,27
- Operating System: Windows
I'm a little skeptical of the "older version" theory.
However it happened, this seems easily fixable by clearing frozen accidentals. The Canonic Utilities plug-in can do that much less destructively than exporting and importing XML. Select All first.
However it happened, this seems easily fixable by clearing frozen accidentals. The Canonic Utilities plug-in can do that much less destructively than exporting and importing XML. Select All first.
- Attachments
-
- 0826.png (3.69 KiB) Viewed 3286 times