Show Time Signature on part causes crash

• Jul 25, 2013 - 01:20
Type
Functional
Severity
S4 - Minor
Status
active
Project

1. Open attached file.
2. Click on part.
3. 'Staff Types…'.
4. 'Tablature (Built-In)'.
5. 'Show Time Signature'.
6. 'OK'.

Result: Crash.

Note: See attached log. The file was taken from a complete score and edited in TuxGuitar 1.2.

Using MuseScore 2.0 Nightly Build (5be9488) - Mac 10.7.5.


Comments

I'm not sure if this is related, but I've got a consistently reproducable crash in a piece I've been working on. (I can try to come up with a reproducible test case, but need to remove copyrighted material.) This is the text of the report I just submitted to Apple (but I've been seeing this in 1.3 for a few weeks now with this one file.)

crash deleting measure marked 4/4 in a 3/4 piece with invisible time signatures when trying to replace with a measure using differing nominal and actual time signatures instead of hidden time signatures. This is the second measure in this piece I tried to do this with, The first seemed to work fine, but even after several saves, exits and crashes, the same operation causes this crash.

I confirmed that I cannot reproduce this crash on the 2.0/nightly builds. It certainly isn't picking up all the correct score formatting from the *.mscz file that it should be, but I understand that this is a very early incarnation of the 2.0 tree.

That said:

  • How close is 2.0 to release?
  • Has all 1.3.x maintenence been suspended?
  • Should 2.0 read all 1.3.x formatting correctly?
  • Is this not yet a high priority?
    • (Should I document the 2.0 formatting issues I'm seeing as bugs to be fixed?)

Thanks,

-Loren

P.S. ABL: The score in question was created entirely in MuseScore 1.3... it wasn't imported from anywhere.

No official word on when 2.0 might be releasd. Certainly not "any day now", but it's close enough that if you have 1.3 scores that don't load properly, you should indeed file issues, as they *should* work. And it does appear the 1.X series is over - no more maintenance releases as far as I know.

Still the case that there is no crash on import, but the "orphaned" staff in the part won't show a time signature either. We probably shouldn't create such staves on import.