New post
Avatar
0

Got a piece I've been working on for a few days.  Opened it this morning, and while everything is fine in page view, in scroll view I only see some of the staves, and they are empty.  And only the lower half of the score.

Big Band piece, only trumpet 3 and down is visible.  Scrolling does nothing.

Any ideas what might cause this, or how to fix it?  I've restared and rebooted already.

FinWin27.  Win11Pro64

4 comments

Date Votes
Avatar
0

View menu : did you create Staff Sets (visible in Scroll view) ?

Comment actions Permalink
Avatar
0

I'm using the same templates I've been using for years.

Comment actions Permalink
Avatar
0

Can we see the score? You can't post it here, but you can upload it to Dropbox, and post a link.

Comment actions Permalink
Avatar
0

That definitely sounds frustrating—especially when the page view looks fine but scroll view breaks like that.

A few things you might want to try:

  • Switch views back and forth: Toggle between Page View and Scroll View a couple of times. Sometimes the rendering just glitches and resets.
  • Check staff visibility: Go into your staff/system settings and make sure nothing is hidden or filtered (especially since only lower staves are showing).
  • Redraw the screen: Try forcing a redraw (often Ctrl+D or similar in notation software).
  • Zoom level: Change zoom in scroll view—sometimes certain zoom levels cause display bugs.
  • Graphics/driver issue: Since you're on Windows 11, try updating your graphics drivers or switching between hardware acceleration (if the app supports it).
  • Open a backup / copy file: Save a copy under a new name and reopen it, or try an earlier version if available.
  • Layout reset: Look for any “reset layout” or “optimize score” option—this can fix corrupted view data.

Since only part of the score is visible (Trumpet 3 and below), it could be a view/filter issue or a rendering bug rather than actual data loss—which is a good sign.

If none of that works, it might help to know exactly which notation software version you're using (Finale, Sibelius, etc.), because this kind of bug can sometimes be version-specific.

Comment actions Permalink

Please sign in to leave a comment.