Transposing causes massive layout problems (attached score)

• Aug 8, 2012 - 17:02

I created the attached file in MuseScore 1.2 and opened it in the latest nightly build (MuseScoreNightly-2012-08-07-ce351a2.7z). It loaded ok, looked just fine.

Then I tried to transpose it to the key of E, and the layout was completely hosed. See attached file for results.

I transposed by following these steps:
1) load the file
2) go to the menu Notes/Transpose, then "transpose entire score"
3) Leave Transpose by Key selected, and mark the Up radio button.
4) Change the key (in the drop-down) from G major to E major.
5) Select "single sharps and flats only" (in the drop-down)
6) Click OK.

Resulting score has multiple problems, including:
* Measure 10 goes off the left-hand margin
* multiple barlines in a row right after Rehearsal A, and notes overlapping the key signature and extra barlines
* Rehearsal A is not the first measure on the line, but still has a key signature and clef symbol
* gliss markings are stretched inappropriately
* Stems of grace notes in measure 65 overlap the beams of the "regular' notes they are next to

When I followed the same steps in MuseScore 1.2, the only problem was the inappropriate stretching of the gliss symbols. None of the other layout problems appeared. On the other hand, when I open the file produced by 1.2 with the nightly build exe, I see the layout problems listed above.

Also, when I do the transpose in version 2.0, and save the file, and then reload it, the problems around Rehearsal A are slightly different.

I'm using Windows 7, by the way.

Attachment Size
yakety_sax.mscz 7.99 KB
yakety_sax_2.0_bug.mscz 9.36 KB
yakety_sax_1.2_bug.mscz 8.1 KB

Comments

In reply to by chen lung

It might be related. I did some digging using the debugger and I see that the tick counts are off right around the time the layout gets screwed up. I wonder if Transpose does some recalculations that are buggy.

I noticed that when I click on different notes, the "Bar x Beat y" display in the status bar (?) is incorrect. In version 1.2, this display is correct.

I realized that the problem with the gliss marks is that MuseScore doesn't let you gliss from one line to the next. It gets confused since the gliss mark is actually attached to the next note (e.g., the first note in measure 10). This doesn't make sense to me, because the note you're ending up on is not the note that being glissed. The symbol ought to be attached to the note you're actually glissing from (e.g., the last note in measure 9).

If I delete the note following the gliss, then the misplaced (and stretched) gliss mark disappears, and I can put that note back, but then I have to way to indicate that the previous note ought to be glissed. I used a generic line and some staff text to work around the problem.

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