Replicating several measures for volta or coda causes crash [2.0b1]

• Oct 11, 2014 - 21:57
Type
Functional
Severity
S2 - Critical
Status
closed
Project
MuseScore

In 2.0b1 I'm trying to set up a volta or coda fork. I replicated a couple of bars that will have the musical section variations. Before I can get further with my editing, MuseScore crashes. It crashes every time I reopen the session and click on a note in the area that is currently the first volta.

I suspect I know what's going on: the part I replicated is in the middle of a multi-bar note. I'm in 4/4 time and there is a dotted whole note, so it's six beats. But the pasted-in section of new measures interrupts that. (The end of the sustained note is in a bar that does not need to be forked for variation in the music.)

I am willing to attach the score, but I don't know if these reports and attachments are broadly public. If so, well, I'm not ready to share that score. Let me know and I'll gladly provide the score.

Comments

• Oct 11, 2014 - 22:18

Not sure what "broadly public" means. Anyone with an account on musescore.org who chooses to go around opening issue reports looking for attached scores will be able to see it. That's basically no one in thew world except us developers, so you should have nothing to worry about. And having the score would be necessary for us to be able to investigate.

Reply

• Oct 11, 2014 - 23:38

OK, thanks -- and sorry if I sound paranoid. :-) It's not like I think I'm Vivaldi or anything. But ... well, those are my emotions about it -- what can I say. I will be glad to do it if you still want it after I tell you that the current nightly build from 11 October is not crashing with it. I was able to edit the score further using that. I don't want to waste people's time, of course, but I thought it was an important thing to file a bug report on.

I did look for my issue in reports before posting, but I didn't see anything that similar. Yet, your code tweaks since 2.0b1 seem to have resolved it -- whether on purpose or because of a general fine-tuning of the code that was causing the crash.

/d

Reply