MuseScore "bounces" when editing/adding to new score
Using: MuseScore 2.02; Windows 10 pc (just converted from Windows 7)
I started a new piece using the "Classical Orchestra" template; I was looking to make myself a "karaoke" accompaniment for the aria Il Balen from Il Trovatore.
Action: Make a change to the score, especially near the end (for instance, delete a cello or bass measure, add or delete a staccato marking, or edit lyrics).
Expected result: change is implemented, no change in what appears on computer display.
Actual result: change is implemented, but the displayed part of the score shifts. Sometimes, the section where the edit was made goes completely off the screen.
I recall seeing this occasionally with MuseScore 1.X, but not in quite some time.
For comparison, the other attachment (Au fond du temple saint from Bizet's The Pearl Fishers) does NOT have this problem. However, I didn't use the Classical Orchestra template on that piece, instead I started with a Voice/Piano template, and after completing the voice/piano version I gradually replaced the piano with the orchestra, adding the instruments manually and deleting the piano.
I've been doing a lot of other work, and Il Balen is the only piece displaying this problem. It's also the only piece where I started from scratch with the Classical Orchestra template, although I have no idea if that is related to the problem.
While I'm hear, a BIG THANKS to the MuseScore team, 2.02 is an incredible product. I used Timbres of Heaven & FluidR3 on the Au fond piece (T of H for the instruments, Fluid for the vocals) and after manually tweaking it throughout, it sounds incredibly life-like!
| Attachment | Size |
|---|---|
| Il_Balen.mscz | 22.47 KB |
| Au_fond_du_temple_saint orch.mscz | 59.42 KB |
Comments
Can you give precise step by step instructions to reproduce a problem? I tried a number of operations and didn't notice anything unusual.
In reply to Can you give precise step by by Marc Sabatella
step-by-step: (I re-confirmed the below just prior to sending this reply)
1) Open score "Au fond...", press End key (moves to end of score), select measure # 37, 38, or 39 for any instrument (doesn't matter if the measure has notes, or is just a rest), press Delete key.
Result: the viewed score shifts about 1 measure to the left, and the "canvas wallpaper" takes its place.
2) Press Ctrl+Z to undo the deletion.
Result: the viewed score shifts back to original position.
Same results happen if you delete or change a note, or a slur, or a staccato; basically any edit causes it.
The problem isn't obvious if you are closer to the beginning of the score, however if you make an edit at (for instance) measure #2, the screen doesn't shift but you can still see the affect in the Navigator.
*Doesn't* happen with any other scores.
Changing the "zoom" level has no affect.
I have a dual-monitor system; moving the score to monitor 2, or turning off the 2nd monitor in Windows, or dragging the score to display on both monitors has no affect.
Since the selected/active measure sometimes moves off-screen, this problem is detrimental to my work-flow. One work-around may be to add a large number of empty measures at the end of the score, since the problem is less noticeable near the beginning and middle of the score.
Thanks for your help! If only I could get this level of service from products that I pay for!
In reply to step-by-step: (I re-confirmed by marty strasinger
I see the same thing you're reporting in "Il_Balen" but not in "Au_fond...".
In reply to step-by-step: (I re-confirmed by marty strasinger
Hmm, I'm still not seeing it. Could be a case where that system is right on the edge of being able to fit one more measure - like the calculation says it can fit 2.99999 measures and depending the tiniest change might push that up to 3, and that is what is causing the jump. Or something like that.
As for workflow, you might consider Continuous view. I think it is probably just coincidence that it seems to happen more at the end than the beginning of a score or that it happened with some particular template. I suspect it is more just random round-off error, and I can't reproduce it because I'm on a different system with different floating point hardware.
In reply to Hmm, I'm still not seeing it. by Marc Sabatella
Typo in my 12:09 pm response above- read "Il balen" for the score that is having the problem, not "Au fond...".
bbburson, thanks for validating the problem. You're seeing the same thing with Il balen that I am; Au fond... doesn't have the problem, I only included it to show that, on my system, the problem is only with a single score.
Marc, continuous view works without a problem, thanks for the suggestion. However, I am concerned that slurs & ties that cross barlines may need to be edited once I shift back to page view. Do you have any experience with that?
Also, I bought your book "Mastering MuseScore". It is an enormous help, complimenting the Handbook nicely. Anything that I can't find in the one, I can always find in the other. Thanks!
In reply to Typo in my 12:09 pm response by marty strasinger
I tried following your steps with both scores, no problems with either. Which is why I suggested it might be a floating round off issue.
When I want to "force" layout to behave in a deterministic way, I:
Usually I wait till I'm finalizing my score to do this. I start off my score in continuous view, as Marc suggested, so I'm not distracted by physical page layout issues.