Copy/Paste problems causing crash

• Jun 25, 2019 - 01:40

I have taken a copy of a score with the objective of adding a staff made up of sections from the various instruments to provide the melody. I then want to print the staff for the instrument I play with this 'melody' staff in 'cue note' format. I am having problems in creating this staff, however, causing crashing and have not found a solution to this problem.
When I copy and paste from one instrument to the melody staff I am careful to paste (usually mid-bar) to the position where the bar has the correct note duration content to match the time signature. However, MuseScore seems to add a rest making the note content exceed the limit and causing a crash. If I recover the file and delete the errant bar from the score with the aim of recreating it, the new bar suffers the same problem with possibly the value of 9 quavers in a 4/4 bar. The crash may not happen immediately but may happen after I have done 3 or 4 joins and the crash report identifies the 3 or 4 join bars as having too many notes. Screenshot attached.
I tried a different tack i.e. to leave the melody bars in their original staff and deleting the contents of all other bars. This, I thought, would give a less complex canvas to create the melody bar later. I didn't get that far, however, as the same problem reared its head again causing a crash. I gave up.


In reply to by ericfontainejazz

For the record, any devs...I'm on latest master and I had his scores open and wasn't doing anything but suddly I get a crash (assert failure) with the following stack trace:

1 raise 0x7fffee21d755
2 abort 0x7fffee208851
3 QMessageLogger::fatal(const char *, ...) const 0x7fffee62e8aa
4 qt_assert(const char *, const char *, int) 0x7fffee62dce2
5 Ms::Measure::write measure.cpp 1930 0x555556607dc5
6 Ms::writeMeasure scorefile.cpp 67 0x5555567ac005
7 Ms::Score::writeMovement scorefile.cpp 230 0x5555567ad519
8 Ms::Score::write scorefile.cpp 268 0x5555567adaef
9 Ms::Score::writeMovement scorefile.cpp 240 0x5555567ad658
10 Ms::Score::write scorefile.cpp 263 0x5555567adac6
11 Ms::Score::saveFile scorefile.cpp 724 0x5555567b09ad
12 Ms::Score::saveCompressedFile scorefile.cpp 575 0x5555567af6fd
13 Ms::MuseScore::autoSaveTimerTimeout musescore.cpp 5025 0x555555f0e6e3
14 Ms::MuseScore::qt_static_metacall moc_musescore.cpp 795 0x555555ceab8b
15 QMetaObject::activate(QObject *, int, int, void * *) 0x7fffee8592f9
16 QTimer::timeout(QTimer::QPrivateSignal) 0x7fffee8663f8
17 QObject::event(QEvent *) 0x7fffee859cd5
18 QApplicationPrivate::notify_helper(QObject *, QEvent *) 0x7ffff65ce485
19 QApplication::notify(QObject *, QEvent *) 0x7ffff65d79b1
20 QCoreApplication::notifyInternal2(QObject *, QEvent *) 0x7fffee82d782

In reply to by bobjp

This issue I presume: #290546: Copy-paste a part with mm rests on another part/mm rests leads to corruption/crash
Your second score (1st and Bass) annonces a corruption when loading, but the more serious problem is in part "Acc1" (with a lot of empty measures - visible by disabling mm rests)
And so, as already noticed, save this part, and you obtain a crash when restarting: Issue 1-Acc_1.mscz

The immediate solution is: delete parts and re-create them (of course fix too corruption measure 16 in main score) and the problem must disappear. See this repaired second score: Dam Busters 1st and Bass.mscz
And by waiting a global fix: avoid to copy-paste instrument part containing mm rests on another instrument part containing mm rests too. Disable first the mm rests in the "copied" part.

Do you still have an unanswered question? Please log in first to post your question.