606: Fixes and improvements in Sibelius 6.0.1

  • Sibelius’s memory usage no longer grows unbounded when scrolling through the pages of a large score without editing (e.g. during playback)
  • Sibelius no longer crashes when pasting material at the start of a score where the first item in the top staff of the selection would need to be pasted before the start of the first bar.
  • Creating a key signature in a dynamic part no longer causes Sibelius to crash.
  • The initial volume used by Sibelius when clicking on a note in the score, or inputting a note via the Keyboard or Fretboard windows, before the score has been played back is now correct.
  • The Allow first syllable to overhang barline option in House Style > Note Spacing Rule now works as expected once more.
  • Lyric hyphens are now correctly centered between syllables, as they were in Sibelius 5 and earlier versions.
  • It was possible for Mixer redraws to cause a crash under some obscure circumstances. This bug has now been fixed.
  • A minor problem with the Essentials Choral Combo sound set (for users of Sibelius Sounds Choral for Sibelius 6) has been corrected.
  • Plug-ins > Simplify Notation > Combine Tied Notes and Rests now runs without an error.
  • Non-magnetic lines no longer perform the look-ahead associated with the new slur direction rule for magnetic slurs, resulting in a small performance increase in scores with many lines.
  • Various small problems related to the appearance and positioning of lines that cross system or page breaks when exporting scores to Sibelius 5 format or earlier have been fixed.
  • A number of small improvements to the order in which scores are compared when exporting Rich Text Format log exported via the Export Log dialog, which now also includes line breaks.

Sibelius 6.0.1 has been superseded by Sibelius 6.2, which you can download here.

Details

Product
Sibelius
Versions
affected
6.0 - 6.1
Changed
27 Apr 2010

Did this solve your problem?

 

Yes
No - I didn't understand the answer
No - I tried it but it didn't work
No - this answer wasn't relevant to my problem