During playback, display jumps to top of page if last staff of system is showing

• Oct 30, 2010 - 16:41
S4 - Minor

I have symphonic partiture. In violin section I create some notes. I make zoom to have string staves good visible, but when i start playing, I see no strings because view showe top of the partiture, where are empty staves of woodwinds.

This makes my work very difficult.


There is no enough information to say for sure, but I would be this is a duplicate of the issue where playback always resets the view to the top of the page if the bottom staff of the score is in view. I tried to find an issue - open or otherwise - but couldn't. I know it's been reported, though. It's still an issue in the latest nightly.

- Load a score with a single system per page but too many staves to fit on screen
- Position the view to show the bottom staff and staves above it - the top of the page will not be in view
- hit Play

result - view jumps to top of page while playing, rather than leaving the view at the bottom of the page

Title While playing partiture I can't see staff I need During playback, display jumps to top of page if last staff of system is showing
Status (old) needs info active

Here is a thread with further discussion of the problem:


Since there is no reason to believe the person who submitted this issue was talking about something different, and there does not seem to be an existing formal issue, I am marking this one "active" and updating the title to be more clear.

I've also attached a sample score. View it at 100% in a window where all staves do not fit on screen. Position the view so you can see only the last three staves (with just the canvas showing below). Select the first bar and hit Play. Result: view jumps to top of page, meaning you can't see the staves you were trying to view.

Attachment Size
service notice.mscz 83.12 KB

Confirmed Windows XP Pro SP 3/MUseScore 2.0 Ra419129

This is an extremely annoying "feature" of MuseScore if you are habitually working with scores taller than the screen. It would be good if we could get this fixed for the stable release of 2.0

This is actually a different issue - this one is about playback, not clicking - but they might turn out to have the same underlying cause, and the same fix might address both.

Status (old) active needs info

They do have the same underlying cause, but they don't have the same fix.
I fixed the click problems in my local repository:
1) jump to top of system when clicking note lower in system
2) jump to beginning of measure when clicking note later in measure

But for the playback issue, I need a bit more info. How would you like the canvas to be adjusted? I think the best way would be to be able to move up and down during playback and when jumping to the next system the same staff previously displayed should also be the one displayed in the new system, but I don't know if I can achive that (I'm trying now), so I would like to know what do you consider the next best thing? For example it could follow the staff that has the selection when the playback starts.

Ideal for me would be to the code to check which staves are visible when playback starts, and keep following that same set of staves where possible (might not be if systems are not uniform in height, which can happen for a number of good reasons). Following selected staff would be better than current but not as good as keeping the entire view as similar as possible. Hmm, another possible solution: if the last staff is visible when playback starts, always position things to keep it at the bottom.

Hello, I was very busy. Now it is better with me. So, I think that would help that playback would show at least the stave, where note or measure has been selected to start playback from. So if I select violas, I will not see celos and I probly will not see flute, but I will see violas, violins, and maybe also harps.

Status (old) active patch (code needs review)

See https://github.com/musescore/MuseScore/pull/1415/files

This PR currently fixes the problem at hand in the case of a single large system on the page - it keeps the view fixed at the bottom of the page. If there is more than one system on the page, but even one system does not fit on the page, it reverts to the current behavior, but hopefully this is not common - a system too big to fit on screen, but yet more than one of them fit on the page.

"Mostly" fixed anyhow. It works if there is only one system on the page, which is hoepfully the majority of cases where this ends up being a problem. If you have two or more systems on the page and yet one system will not fit on screen, there may still be a jump.