Score jumps out of focus in 2.0 beta1
I'm working in a score for chamber orchestra. When I zoom in, say 200%, so that only part of the score is visible, and then I click on a note in one of the bottom staves, the view suddenly jumps to the upper staves. Apparently, this only happens if I have just dragged the score to that page. If after the jump I go back and select the same note, the view stays focused on it.
I made a recording of the screen and placed it inside my Dropbox. You can find it here: //dl.dropboxusercontent.com/u/4857747/Musescore%20bug.mp4
You can see this strange behaviour occurring between 00:11 and 00:12
I'm running MuseScore 2.0 beta1 on a Macbook Pro OS 10.9.4
P.D.: also, at 00:10, you may also see that the 6th bar appears fuzzy; some kind of problem with the anti-aliasing, I guess. I'll report that in a separate post.
Comments
This may be connected to this issue as well.
#7724: During playback, display jumps to top of page if last staff of system is showing
See this perhaps.
Yep, that's it! Good to know it's not only happening to me and glad that is has been already reported. Sorry for the duplicate post.
Not at all, thanks for filing (I had been meaning to). :)
My impression is that Andrei has a fix for this but was waiting to also figure out #7724: During playback, display jumps to top of page if last staff of system is showing
See also #37676: Selecting note or rest in one window repositions other window as well if viewing same score - I think the cause is basically the same. That is, it is the moving of the playback cursor that is problem here; it triggers an eventual adjustCanvasPosition call with the measure as the parameter.
https://github.com/musescore/MuseScore/pull/1415
The fix for the measure-too-wide-to-fit portion of the issue seems quite straightforward. The fix for the system-to-tall-to-fit portion is a little trickier and could have other side effects, but it does work for this case.
Fixed in d02b701bc8
Automatically closed -- issue fixed for 2 weeks with no activity.
When people say "Fixed in d02b701bc8", is it safe to just download that version and use it? I mean, I've been using the Beta version from this page: http://musescore.org/en/node/30866
I guess the ling on that page goes to a one and only Beta 1 release. Not to each new nightly release. But can I assume that whatever I've writen with Beta 1 will be compatible files with any later nightly, and vice versa?
I downloaded the latest nightly and the score jumps exactly as in Beta 1. I have a big band score and view it in 200% while I edit. I use Page View. Every now and then the score jumps forward one or two bars to far from the point where I'm writing.
There has been a small change in file format, so scores created in a later nightly build may not open correctly in Beta 1 any more.
Any nightly build compiled after that commit was merged will include the fix.
In general, scores made with a recent nightly build will still be good in the next. I wouldn't have said that pre-Beta, but we tried to make all incompatible changes we could *before* beta. No guarantees, but it's pretty safe, and you always have the option of MusicXML export for safety.
To get a recent nightly, see the main Downlaods link in menu at right of this page and scroll down.
Well, I downloaded the latest nightly, which is MuseScoreNightly-2014-11-30-0907-c547bb7.7z and the score jumps there, too. I can return with a video or something, after a while.
There are some "jumps" that are perfectly normal. Other jumps may represent different bugs unrelated to this one. So be sure to describe as precisely as possible what is going on.
duplicate post
Ok, now I know what happens here. My annoying jumps have to do with entering full note chords. After entering one full note, the cursor jumps to the next bar. Sometimes this means the view jumps to the next line or the next page. Or in "continuous view", it sometimes does a page-full jump forward. But I want to stay at the same bar to be able to enter the remaining notes of the chord. In continuous view it's kind of unexpected when it happens. I guess it happens, when there would be a line break, but since you are in continuous view, you don't see the line breaks.
These kind of jumps are obviously intended. One would normally expect the cursor to jump to the next position, after entering a note. But does one actually need a cursor there? I click in my notes. And I can click anywhere, despite where the cursor is. Isn't the cursor solely for some keyboard input? This jumping behaviour could perhaps only be activated in keyboard input.
The problem isn't the jump as such, but the jump out of sight, right? And I think I've seen than not only on whole notes, but also on other notes, if they were the last in their measure. Well possible that it only happens at line breaks, I didn't notice that at the time, esp. As line breaks shouldn't have any meaning in continues view.
It would be best to start a discussion in the Technology Preview forum on this. As noted, the cursor advance on note tnry is indeed intended normal and intended. But it certainly could make sense to have different behavior depending on whether one is entering notes by mouse or keyboard. Not just this, but perhaps other differences as well. Worth discussing on the forum for sure, even though I suspect actually implementing it might be easier said than done,