Musescore crashes when I press 'x' on the beam of a tuplet
In a 6/8 bar I have put a tuplet of 26 semiquavers in the left hand which fills the duration of the bar. All the notes are beamed, but when I pressed 'x' to invert the beam and stems to be downwards rather than upwards, Musescore crashed and says it quit unexpectedly. I have attached an image of that tuplet.
Can this be fixed?
Many thanks,
From James
| Attachment | Size |
|---|---|
| Screen Shot 2020-08-17 at 19.08.55.png | 29.03 KB |
Comments
Which version of MuseScore, sample score?
In reply to Which version of MuseScore,… by Jojo-Schmitz
I'm using the latest version I think - 3.5. Not sure what 'sample score' means though.
In reply to I'm using the latest version… by jamesmayhew
a score that demonstrates the problem
In reply to a score that demonstrates… by Jojo-Schmitz
Should I attach my whole score then? (is that what you mean?)
In reply to Should I attach my whole… by jamesmayhew
yes. Or a shortened version that still shows the behavoir. Single measure should be enough I guess
In reply to yes. Or a shortened version… by Jojo-Schmitz
OK - I attached the measure which had the problem in my original description of the problem, but here is the file of the whole piece, and the problem is in bar 53.
In reply to OK - I attached the measure… by jamesmayhew
OK, with that I can indeed confirm the crash...
3.4.1 crashes on it too (so not a recent regression), 3.2.3 and 3.3.4 just ignore the flip it seems?
Doesn't seem to happen on any beamed tuplet though, doing it on a triplet on a quarter note works.
In reply to OK, with that I can indeed… by Jojo-Schmitz
Sorry I don't understand that last sentence... But can this be fixed at some point? It's not much of a big thing to worry about, but would be nice if it was fixed anyways.
In reply to Sorry I don't understand… by jamesmayhew
I'm just trying to analyze the problem. Check where it started to happen and what is needed to make it happen.
Next step is to fire up MuseScore in a debugger...
OK, stack trace:
1 Ms::Beam::gripsPositions beam.cpp 2206 0x8ba3ec
2 Ms::Element::updateGrips element.cpp 2096 0x9307ff
3 Ms::ScoreView::updateGrips editelement.cpp 59 0x6b7649
4 Ms::ScoreView::updateEditElement scoreview.cpp 5338 0x607c7e
5 Ms::ScoreView::cmd scoreview.cpp 2057 0x5f33f6
6 Ms::MuseScore::cmd musescore.cpp 6618 0x432aba
7 Ms::MuseScore::cmd musescore.cpp 6040 0x42f37f
8 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 518 0x5a0ef2
9 QMetaObject::activate(QObject *, int, int, void * *) 0x68a947c8
10 Ms::ScoreTab::actionTriggered moc_scoretab.cpp 225 0x5bf62e
11 Ms::ScoreTab::qt_static_metacall moc_scoretab.cpp 110 0x5bf0b6
12 QMetaObject::activate(QObject *, int, int, void * *) 0x68a947c8
13 QActionGroup::hovered(QAction *) 0x2ab44db2
14 QActionGroup::qt_static_metacall(QObject *, QMetaObject::Call, int, void * *) 0x2ab4573c
15 QMetaObject::activate(QObject *, int, int, void * *) 0x68a947c8
16 QAction::activate(QAction::ActionEvent) 0x2ab43e0e
17 QAction::event(QEvent *) 0x2ab448cb
18 QApplicationPrivate::notify_helper(QObject *, QEvent *) 0x2ab47bdc
19 QApplication::notify(QObject *, QEvent *) 0x2ab4ec23
20 QCoreApplication::sendEvent(QObject *, QEvent *) 0x68a692e8
...
In reply to Sorry I don't understand… by jamesmayhew
Hmm, preventing the crash is pretty easy, a 2-liner, but that would still ignore the flip.
Better than a crash and no worse than in older versions where it got ignored too...
In reply to Hmm, preventing the crash is… by Jojo-Schmitz
The problem is that, for some reason, this figure is beamed with the previous notes in previous system.
![pb.jpg]( "pb.jpg")
Simply select the first note at measure 53, apply a "Beam Start" (first symbol, Beam properties palette) to it, and the problem (crash and flip) is solved.
See fixed score: 1 Variations_on_an_original_theme.mscz
In reply to The problem is that, for… by cadiz1
Thanks so much! It works now (I can press 'x' without a crash), and when I tried using the 'Beam start' in other scores I selected a group of notes that I wanted to beam separately (which didn't work), but now I have just realised I need to only select the first note. This is going to help a lot with other scores.
In reply to The problem is that, for… by cadiz1
Ah, excellent!
See also https://github.com/musescore/MuseScore/pull/6466, which fixes the crash (by ignoring the flip)