score from 53d4ad2 plays correctly but displays bizarre in newest nightly

• Jan 15, 2017 - 12:03

I entered a score yesterday in the nightly build 53d4ad2, and today in the newest build
it displays really wierd. But it seems to play correctly.
MuseScoreNightly-2017-01-15-0831-master-eb4455c.dmg

Is there a way to fix this, or is my work just lost?

Screen Shot 2017-01-15 at 12.56.45.png

I notice it displays much better in 2.0.x but I see all articulations and ornaments
are displayed as a fermata sign.

Screen Shot 2017-01-15 at 13.00.51.png


Comments

The recent nightlies from master are pretty unusable in the Moment (those for 2.1 should be rather stable though). See for example the lack of time sigs (and see #159366: Invisible time- and key signature.

And for real work you shouln't be using those nightlies anyway, they are for testing only.
They are intended for testers and advanced users who want to experiment with new features, or need access to the latest bug fixes and are willing to risk the instability of an unfinished product. A file saved from a nightly build may not open in a future nightly or any released version. Use at your own risk.

Your work is probably not enrtirely lost, just foxe those femata vs. articulations and ornaments glitches

In reply to by jim.newton.562

As long as by "want to use..." you realize this means, "and fully expect the scores I created today to be work I can never again open in future builds at some point" - there is no guarantee of future compatibility for scores created in nightly builds, and in fact one can bet pretty safely *against* it at this point.

I tried to download yesterday's and Jan 5's nightly to see if they can read the score,
they both seg fault on startup, with or without the -F flag.
Is that normal?

Jims-MacBook-Air:MuseScoreScores jimka$ find /applications -name mscore -ls
48088476    39856 -rwxr-xr-x    1 jimka            admin            20402736 Apr  1  2016 /applications/MuseScore 2.app/Contents/MacOS/mscore
56842132    40632 -rwxr-xr-x    1 jimka            admin            20801604 Jan 14 19:16 /applications/MuseScoreNightly 2.app/Contents/MacOS/mscore
56837258    40632 -rwxr-xr-x    1 jimka            admin            20801604 Jan 15 09:52 /applications/MuseScoreNightly.app/Contents/MacOS/mscore
^C
Jims-MacBook-Air:MuseScoreScores jimka$ /applications/MuseScoreNightly 2.app/Contents/MacOS/mscore -F
-bash: /applications/MuseScoreNightly: No such file or directory
Jims-MacBook-Air:MuseScoreScores jimka$ "/applications/MuseScoreNightly 2.app/Contents/MacOS/mscore" -F
Segmentation fault: 11
Jims-MacBook-Air:MuseScoreScores jimka$ find /applications -name mscore -ls
48088476    39856 -rwxr-xr-x    1 jimka            admin            20402736 Apr  1  2016 /applications/MuseScore 2.app/Contents/MacOS/mscore
56842132    40632 -rwxr-xr-x    1 jimka            admin            20801604 Jan 14 19:16 /applications/MuseScoreNightly 2.app/Contents/MacOS/mscore
56844915    40624 -rwxr-xr-x    1 jimka            admin            20797508 Jan  5 15:41 /applications/MuseScoreNightly 3.app/Contents/MacOS/mscore
56837258    40632 -rwxr-xr-x    1 jimka            admin            20801604 Jan 15 09:52 /applications/MuseScoreNightly.app/Contents/MacOS/mscore
^C
Jims-MacBook-Air:MuseScoreScores jimka$ /Applications/MuseScore\ 3.app/Contents/MacOS/mscore -F
-bash: /Applications/MuseScore 3.app/Contents/MacOS/mscore: No such file or directory
Jims-MacBook-Air:MuseScoreScores jimka$ "/applications/MuseScoreNightly 3.app/Contents/MacOS/mscore" -F
Segmentation fault: 11
Jims-MacBook-Air:MuseScoreScores jimka$ "/applications/MuseScoreNightly 3.app/Contents/MacOS/mscore"
Segmentation fault: 11
Jims-MacBook-Air:MuseScoreScores jimka$ 

Looks like the xml tags have changed.

Articulation: unknown <ornamentTrill>
Articulation: unknown <articStaccatoAbove>
Articulation: unknown <articStaccatissimoAbove>
Articulation: unknown <articStaccatoBelow>

I see these errors when reading into an earlier nightly

In reply to by jim.newton.562

There have been some additions lately.
2.0 scores should load just fine in 3.0 (if not that'd be a major Regression and we definitly want to know about it), but not vice versa (and by design), same for scores created in newer 3.0 build, when opening on older builds. Or even newer builds, while 3.0 is in development there's no garantee of any sort that any score created in one version will open in any other version, not even in the same at times

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