Crash when trying to add a ligature
I'm trying to continue fixing the sheet converted from the importer tool and now if I try to add a ligature mscore crashes, tryed to run in debug mode, the last select event mode was the last before clicking on the ligature icon:
select element type 0(state 1) staff 0
MuseScore::cmd
ScoreView::cmd
===startCmd()
UndoStack::beginMacro 0x7f90cdde04c0, UndoStack 0x7f90cae0d300
[1] 41427 segmentation fault ./mscore -d
Here is the sheet, the ligature that causes the crash is the last note in section 11 in the right hand. I cann add ligatures on other notes
OSX: Yosemite
MS: 2.0.2
Comments
Ligature? Do you mean a a tie?
Assumign you do mean tie, I can confirm the crash in 2.0.2:
1) click last "B" in measure 11
2) press "+"
Result: crash
However, it works fine in a current development build.
The problem seems to stem from the fact that the note you are trying to tie to is actually in the bottom staff but moved to the top staff via cross-staff notation. Thus, I believe you are seeing #77366: Crash on tie between notes on different staves with cross staff notation, which was indeed fixed after 2.0.2.
FWIW, this wasn't really a situation that called for cross staff notation, Simply using multiple voices in the top staff would have made much more sense.
In reply to Assumign you do mean tie, I by Marc Sabatella
Sorry for not being clear in my posts, I'm just translating from spanish and perhaps I don't choose the word that it fits correctly. I googled and I confirm (Música) ligature; tie
Regarding the cross staff notation, I don't understand. I had moved some notes that were not in place with shift+arrows, do you mean that ? What should I've done ?
In reply to Sorry for not being clear in by Raúl Macián
I guess you used Ctrl+Shift+arrows? See https://musescore.org/en/handbook/cross-staff-beaming-0
In reply to Sorry for not being clear in by Raúl Macián
In measure 12, on the top staff, you should have entered the dotted half note B in voice 2, then entered the rest of the notes in that measure as voice 2, also on the top staff. The notes in the bottom staff should have been entered into voice 1.
That's assuming you entered the music yourself. Maybe you got this score from somewhere else and it was already entered incorrectly so you moved notes to try to fix it?
In reply to In measure 12, on the top by Marc Sabatella
It was extracted from a PDF file from www.musescore.com/import
For some reason in some places added a C Major key in the voice 2 (left hand) and JoJo helped me to remove it but leaving the notes on its place. Hence moving the notes with shift+arrows. I think that the precise note was added manually or moved.
For me , musescore sometimes do extrange things, I tryed to add a note on right hand (voice 1?) where some notes were missing and the notes were added in the left hand (voice 2?) when this happened I copy and paste a full section from another section. May be this related?
I don't know if the problem was me or the extracted file.
In reply to It was extracted from a PDF by Raúl Macián
I think it is most liekly a problem with the imported file. Attemption to import music from PDF does not usually produce very good results, and it often takes longer to correct the problems than to simply enter the music yourself. You definitely get better results doing it yoursle f- notes will be in the correct staff and voice etc.