Major changes in Nightingale 5.6 (from v5.5):

On MIDI playback, if multiple notes are simultaneously playing the same note number on the same channel but end at different times, hold the note till the last one ends. (A compile-time option can make Ngale stop playing when the first one ends, as it's always done.)

Nightingale no longer complains about unisons (whether perfect or augmented) in a chord, (1) when an attempt to create one is made and (2) in Debug command output. (A compile time option can make it complain as it always has.)

Fix bug: Double Selection often fails to update context in following objects correctly.

When a (non-hairpin) dynamic is double-clicked, hilight its attachment point, as with text graphics and tempo marks.

Fix bug: On PostScript output, piano pedal up and down symbols are unintelligible because they're not drawn in a music font.

In addition to "duration problems", the Score Info dialog now reports how many empty measures the score contains and the measure no. of the first, and how many out-of-range notes the score contains and the measure no. of the first.

Fix bug: In a C score ("Transpose MIDI" unchecked), some notes are incorrectly considered out of range because Nightingale assumes the notation is transposed.

Get with 21st-century conventions by taking filename extensions seriously: put the part name in default filenames of extracted parts before the dot instead of at the very end.

When parts are extracted, they now inherit page headers and footers from the score.

When extracting parts, if in a series of TEMPO objects there's more than one relevant to a part, Nightingale extracts only the first one, on the assumption they're identical (e.g., for an orchestra score where the tempo mark appears above the top staff and somewhere in the middle).

Add to tempo/metronome mark dialog an option to have no M.M., so you can have a tempo mark that doesn't affect playback timing.