Editing Tempo crashes Musescore
Version 4.3.1.241490900, Revision 06c26b
Latest 6/6/2024
If you have an existing tempo, and edit the value, the software crashes instantly.
Do you still have an unanswered question? Please log in first to post your question.
Comments
Note: in the prior version, this worked fine with no crash.
Maybe I'd love to look your score.
In reply to Maybe I'd love to look your… by rrrrrrrrrrrrr1
Is the tempo marking, by any chance, located in the same place as a multimeasure rest? See image below. For my part, in this scenario, I can reproduce the crash, and so it's most likely a variant of: https://github.com/musescore/MuseScore/issues/23050
Could you please confirm.
If not, please attach your .mscz score.
In reply to Is the tempo indication, by… by cadiz1
Yes, it is. I attached the starting portion of the score.
In reply to Yes, it is. I attached the… by garysimpson
OK. Thanks. Variant added to the bug report.
Try the artifacts from https://github.com/musescore/MuseScore/pull/23146
AS a possibly unimportant aside. Yes, the OP score crashes for me.
I notice that if I open the score and hit "M" twice, I can then edit the tempo. I don't think I would make the kind of major edit that changes the entire score, from within a part. I know we are supposed to be able to. But still.
In reply to AS a possibly unimportant… by bobjp
With that artifact?
In reply to AS a possibly unimportant… by bobjp
"hit "M" twice, I can then edit the tempo."
Yes, a workaround already mentioned in the bug report.
Or simply disable the MM rest while you edit the tempo, or whatever.
"I know we are supposed to be able to"
As you say...
In reply to "hit "M" twice, I can then… by cadiz1
I only mention it for those who don't read or understand bug reports. Like myself.
In reply to I only mention it for those… by bobjp
Writing or understanding a bug report is just as easy as writing or understanding a thread on this forum... You just have to do/try it.
In reply to Writing or understanding a… by cadiz1
Easy for someone like yourself. I don't think general users are interested in them that much. Your bug report is relatively short compared to others I've looked at that wonder all over the topic. And to create one requires an extra sign-in and proper format. All doable, of course, and needed. But I think most users just want an answer.
In reply to Easy for someone like… by bobjp
"I don't think general users are interested in them that much."
How would you know? You speak for yourself.
"But I think most users just want an answer."
The answer was clearly given in the bug report.
![press M.jpg]( "press M.jpg")
That's why I didn't put it back in the thread. But I could have. That's what I usually do.
In reply to "I don't think general users… by cadiz1
Sorry. You seem to not understand my point. You have been around here for a while. You take an active interest in how the forum and MuseScore work. The forum is full of people who are new to notation software and MuseScore in particular. They just want an answer. I have certainly been guilty of not going to the manual first. Although the MU4 manual leaves much to be desired, as of yet. But a bug report?
I did got to that report. But I had already discovered that method on my own.