continuous view - automatic scrolling

• Dec 10, 2013 - 04:56

When entering notes in continuous view, when you reach the end of the screen,

musescore autoscroll before.png

it automatically scrolls over to continue entering notes.

musescore autoscroll after.png

But it scrolls to a bad place. It scroll so the next position is all the way to the left, so you can't see the context of what you're doing. You can't see what you just entered.

It would be better if it didn't scroll so far, so the user can see a little bit of the previous music.

musescore autoscroll better.png


Similar issue on playback with continous view, just the other way round, it jumps to nect page only when reaching the last not of the current page, so no read-ahead possible.
I think in boch cases MuseScore should try to keep the Cursor within the middle third of the screen, or within the 2nd/3rd quarter.

Is this going to be addressed? Regardless of the continuous view width/position discussed in the linked thread above, this thread is about always leaving some context at the beginning of the line. This is especially frustrating when trying to add chords to the previous note that is no longer visible because of the automatic scroll.

In reply to by jmadren

It *has* been addressed to some extent and should in general be much better than it was then. but there are indeed certain cases where it doesn't happen. I take it you are running into one of those particular cases. Feel free to post the score you are havng trouble with and post rpecise steps to reproduce the problem - although it probably depends on details like your monitor resolution , zoom setting, etc.

In reply to by Marc Sabatella

I run 1600x1000 on a 24" screen - that's not unusually high.

I played around with the -x switch. It is not a dpi setting, it is a factor setting. And it makes other things bigger like toolbars and palette items. I don't have a problem with the size of anything else except the score at the default 100%. Here is an example of my screen at the default 100% view:


Also note that the size of the score is also affected by the number of staves you have. The default single staff new score looks a little bigger than the above example.

One more thing - this is on Mac OS X 10.9.5, if that matters.

Attachment Size
MuseScoreSize.png 64.65 KB

In reply to by jmadren

That definitely looks small, unless your score is itself small. But I can't view it on a 24" monitor because I don't have one. Do you have the scaling turned down in Layout / Page Settings or in Staff properties? As I said, it should be the same size (roughly) as printed. Are you finding otherwise?

In reply to by Marc Sabatella

I don't think the size of screen matters. The important point is that when you advance from the least entry of a page the next screen advances so that you no longer have a view of the last bar, so you don't have a visual picture of what you just did, instead you are presented with a "blank" page.

This certainly is a problem for me as I often wish to see just what I did. For example, I may want to tie to the next note, but be insecure as to whether or not I am tieing the proper note. This is just an example. I knoe I can go back and check, but it would be so helpful to have the image in front of me.

In reply to by Marc Sabatella

Yes, as I stated after you mentioned the zoom level, the "page shift/automatic scrolling" works correctly at 100% zoom. And yes, the size at 100% zoom closely resembles the printed page at my current resolution 1600x1000. But if I set my monitor to its native resolution of 1920x1200, then the score is really tiny. The Scaling was at the default(?) of 1.425mm. I bumped it up to around 2 and that helped some, but not enough. Plus then it throws off the printed size.

I believe the important point is that printing and composing are two very different things (and page layout is not composing either - it's part of printing). Currently the "Continuous View" size is the same as the "Page View" size. I can't compose at the "Page View" size. The "Continuous View" display size should not be bound by the "Page View" size. One is for composing and the other for layout/printing. So the continuous view size should default to a larger size than the page view, and per the topic of this thread, automatic scrolling should work correctly at that (or any) size.

In reply to by jmadren

I run into this issue on extreme zoom levels (I didn't find a way to tell the numeric percentage of zoom, it isn't displayed anywhere in status line). If the score is rhythmically more complicated, it happens I can't see just the previous selected note during note entry - "great" for entering chords. Attached files might be useful. Wish continuous view ensured selected (blue) object is always visible, even just after auto scrolling.


In reply to by mike320

Thanks for reminding me, as you can see, my eyes are anything but good and when scanning UI, I may miss some parts. So yeah, 600+% zoom is quite extreme, but I need it for comfortable music entering - and if the selected object becomes hidden due to auto scrolling, it might be quite a problem.

In reply to by TomVal

The current notes being played should not scroll off the screen in during playback. The exception is if the current measure is so long it cannot be displayed in the current zoom, since MuseScore make the beginning of the current measure the left end of the screen. If what you are seeing is not part of the current measure, this would be a bug that needs fixed. If the measure is too long to fit your screen, you'll have to adjust the zoom, at least temporarily, for playback.

I don't zoom THAT much to enter music (I do zoom more than many people), so I always have all of the current measure displayed. I'm not sure what happens when the width of the measure exceeds the screen width and you try to enter notes at the end of the measure.

In reply to by mike320

Well, I think included image makes it clear I'm not seeing a note at the end of previous measure. Yes, I'm using such a zoom level that with 16th notes, only two beats fit on screen, since my eyes are anything but good and such a zoom level permits me to be 15 cm away from screen instead of usual 5 cm. And if there's a chord on the end of a measure, which gets hidden due to measure wrapping rule of MuseScore, it's qauite hard to enter a chord with accidentals using a piano keyboard, since you can only guess which accidental is used for a specific tone. So I think the selected (i.e. blue) note/rest should be always visible when entering music in Continuous view, otherwise it's a mess, at least for me.

In reply to by TomVal

I actually agree with you about the note currently being entered along with the last note entered should always stay on the screen. I don't see anywhere in your picture that shows notes scrolling off the screen. I was simply explaining how it currently works. If I were a C++ programmer this issue would have been fix long ago, but I'm not, so we are at the mercy of those who program and do not see this as an issue.

I would also have the current note being played during playback ALWAYS on the screen, even if that means the beginning of a measure scrolls off to the left. Some may say that long measures would zip across the screen too fast. That becomes my problem to solve, either by adjusting the zoom or the playback rate, which is easily done in the playback window.

In reply to by mike320

It's not that no one sees this as an issue. it's that we keep getting random reports of things not working as expected, but very cases where we understand *precisely* what the user is doing to trigger the unexpected behavior. And even in some of those cases, it is clear other users would expect a different behavior given those same circumstances. In the cases where we can both reproduce the problem and there is widespread consensus that there is a better behavior, we have actually implemented fixes. Quite a lot, in fact - I can remember at least a dozen such cases being addressed over the past few years.

So in other words, it's not one issue being reported over and over that isn't getting fixed. it's lot of *different* issues being reported that just happen to involve some of the same buzzwords making them *seem* like they are all the same. Some of these are fixed, but others are not well understood, others are well understood but unfortunately there are conflicting viewpoints on the expected behavior.

No doubt there are still a handful of such reproducible cases that do have consensus and are still waiting to be fixed. Feel free to post a link to the specific issues for them and I will see about getting them fixed for the 2.2 branch

In reply to by TomVal

In order to really understand, we'd need to follow your exact steps. Positioning of the score view is a complex matter, depends on lots of factors, so to understand the specific situation where you are seeing a problem, we'd need to understand the state of things just before the problem happens and what you do that triggers the problem.

In reply to by Marc Sabatella

How to reproduce my result:

1. Set your display resolution to 1920x1080, scaling 100%
2. Start a new pice based on "Treble Clef" template.
3. Palettes at left and inspector at right are placed there by default, try to put them there as shown on image above.
4. Set zoom to 672.75%
5. Activate continuous view.
6. Using PC keyboard, re-enter music contained in "Problem_demonstration.mscz" included above with my first comment at this topic.
7. After entering quarter note C in fourth measure, you should be in the state illustrated at image "Musescore problem demonstartion.png" included above.
8. Without exitting note-entry mode, try to add notes Eb and Ab, creating a triad instead of single note at the end of measure 4.

Most natural thing I'd do would be to move the score by clicking at empty area and dragging, but that doesn't work in note-entry mode, insted I have to either a) get to relatively narrow scroll bar at bottom and scroll, or b) exit note-entry mode, move score, re-enter note-entry mode and continue working, since there are occasions I really need to see the note I just entered.

Hope that helps.

In reply to by Nicolas

Yep, exactly, I'd like to see last entered note and insertion point always in continuous view. Objects aren't always inserted at insertion point, but sometimes to the selected object before insertion point. And soumetimes you need to see if thing added is exactly what you meant to add. Sorry for non-exact explaining of my problem, my English isn't as good as I'd like it to be.

Do you still have an unanswered question? Please log in first to post your question.