MuseScore 3 Issues - Time Sigs, Key Sigs, Cursor
I upgraded to v3.0.1.5087 yesterday and have been experiencing some weird behaviors.
Even in a newly-created score (i.e., not one from v2.3), I notice if I insert a new measure in the middle of the score, it inserts the measure but automatically duplicates the key signature in the new measure. It doesn't let me delete it, but sometimes if I ignore it move measures around so that the new measure crosses a page boundary, then it often disappears on its own.
Also, when changing time signatures mid-stream, it sometimes doubles them up (see attachment). If I try to delete one, they both disappear.
Lastly, I'm finding the new cursor difficult to work with. The "Do not" sign is a pain in the neck... every time I need to drop something on a note, I have to spend a second or two "fishing around" for the note. Couldn't this just be an arrow that turns red when it's not over a suitable target? That would be much easier to work with than the circular icon.
Thanks for considering these comments.
| Attachment | Size |
|---|---|
| Double Time Sigs.png | 6.41 KB |
Comments
It does that in continuous mode, right? If see, see #279925: Permanent courtesy time sig and key sig before system/page break when toggling in Continuous View and/or Parts
In reply to It does that in continues… by Jojo-Schmitz
I only ever use MuseScore in Page View, but I checked Continuous view and, yes, it's doing it there too. The doubled time signatures act as if they "think" they are at the edge of a system and need to show at the end of one and the beginning of another system, but they're doubling up right in the middle of systems (another attachment where you can see the system edge).
I've been noticing other bugs, too. For instance, I will type in a line of lyrics, and for no good reason, random "syllables" of what I had just typed are in a different, heavier (san serif) font. If I click on them, the Inspector says that everything I typed is in "FreeSerif" but that is visibly untrue, and if I highlight the aberrant syllables and click "Remove Custom Formatting," the font switches back to what it should have been. So I have a workaround but this has happened several times.
FYI, this is on the Windows version running Windows 10. I installed MS3 on a second Windows 10 PC and exhibits the same behaviors.
In reply to I only ever use MuseScore in… by FiveLines
Oh, and I forgot to mention this -- when I change time signatures in version 3 with double-barlines to indicate the change, it doesn't consistently apply the barline (see attached). I never saw any of these issues with MuseScore 2.1~2.3.
In order to investigate, we would need you to attach your actual score, not a picture, and give us precise step by step instructions to reproduce the problem.
In reply to In order to investigate, we… by Marc Sabatella
"I've been noticing other bugs, too. For instance, I will type in a line of lyrics, and for no good reason, random "syllables" of what I had just typed are in a different, heavier (san serif) font. If I click on them, the Inspector says that everything I typed is in "FreeSerif" but that is visibly untrue, and if I highlight the aberrant syllables and click "Remove Custom Formatting," the font switches back to what it should have been. So I have a workaround but this has happened several times."
I had observed the same thing these last days.
After investigation, see: #282202: Discrepancy between lyrics font style displayed in Inspector and text toolbar leads to crash
In reply to See: #282202: Discrepancy… by cadiz1
See also #281831: text cursor before first character of a text element or before a special character of text aren't initialized to text element's default.
In reply to In order to investigate, we… by Marc Sabatella
Okay, as requested, here is a dummy score created in MuseScore 3 exhibiting the bugs I described, bugs I never saw in MS2. I have also uploaded a screen gran explaining what to look for.
In reply to Okay, as requested, here is… by FiveLines
In reply to Okay, as requested, here is… by FiveLines
Thanks for the score!
The font issue is probably #281831: text cursor before first character of a text element or before a special character of text aren't initialized to text element's default, seems to be sensitive to exactly where you double click when editing text and something this glitch can happen. You can reset with the "Remove custom formatting" button in the Inspector.
The time signature issue appears to have already been baked into this score - meaning whatever went wrong in the past to produce these elements, it's there now and MuseScore is doing its job correctly displaying them. The question is, can you come up steps to reproduce the problem - that is, to get the time signatures to appear in the first place? So far we know of #279925: Permanent courtesy time sig and key sig before system/page break when toggling in Continuous View and/or Parts - if you read through the descriptions of how those scores got into the state they are in, do they seem like they might apply?
Similar story for the barline in that the more interesting question is about how ti got that way. I'm guessing you had a double bar then added a staff, and thus you are seeing #123436: Double barline doesn't appear on the staff of the added instrument.
In reply to Thanks for the score! The… by Marc Sabatella
I will work on trying to determine exactly how some of these things happened.
With the lyrics/font, I have gotten this effect without double-clicking to edit -- I just Ctrl-L the first note and type syllables with spaces between them, and when I look back, sometimes random syllables are in the wrong font. I did discover that I could use 'Remove custom formatting' to fix it, but it seems odd to me that the inspector is otherwise showing the correct font name even when that's not what's being displayed.
As for the doubled-up time signatures... I change time signatures a lot. When I drag in a time sig from the Master Palette, I don't immediately notice the doubling. It's when I come back to it later that it has doubled up. It's possible that, during editing, that measure is pushed out of one system and into another, and that's when the courtesy time sig appears and never goes away. I never use Continuous mode, only page view. Still seems like a bug, though, no? I never saw this in previous versions. Same with the fonts changing.
For the single/double barline, I think you are correct -- I think that instrument was added AFTER adding the double barline was put in place, and the new staves didn't pick it.
I will keep an eye on these behaviors and report if I can find simple steps to reproduce them. In general I haven't often immediately noticed them until later, so it's difficult to say exactly when they happened.
Thank you!
In reply to I will work on trying to… by FiveLines
The glitch with double-click of text in just the right (wrong) spot resulting in bad formatting is hopefully now understood and a fix ready to be included in the next update. For now, try to avoid clicking too far to the left, that's the way I know to trigger it. As for why the Inspector shows the right font, that's because the element as a whole is still set correctly, it's certain individual characters within the text that have the wrong formatting applied to them, in the same way as if you had selected a single letter and made it bold using the text toolbar.
The time signature thing is definitely a bug, and knowing you never use continuous view is important information. I encourage you to go over to the issue I linked and attach your score there and anything other insight you can share about how this happened, so we can hopefully get to the bottom of it.