Identical measures as thick line do NOT transpose!
Already reported in "MuseScore on iOS" , now including the mscz file.
When using the MuseScore Songbook (iPad) identical measures found with the same chords (which are not repeated above the measures) will be replaced by a thick line with the mentioned chord from the first measure and the repetition number above the line. So far so good, but the chord does NOT transpose anymore.
Open it in the iPad Songbook and look for the thick line (3) with chord F. It will NOT transpose like the other chords. The app transforms the original 3 measures into a thick line apparently to minimize space. Additionally it should be noted that the repeated measure contains actually 2 chords F and F6 and NOT only a F so it seems to ignore the F6 as well (open the file in MuseScore.
Rob
| Attachment | Size |
|---|---|
| 9_20 Special (C) CH.mscz | 2.87 KB |
Comments
Not sure I understand the problem, but the last line is not stretched out to use the entite page width, so lots of chord symbols are on top of one another. Try the attached and see whether it works better in Songbook.
Also you may what to have a look at the slash notation plugin, so you'd actually have something to attached those chord symbols to, if there is more than one per measure
In reply to Not sure I understand the by Jojo-Schmitz
Quote Jojo-Schmitz:
"Not sure I understand the problem, but the last line is not stretched out to use the entite page width, so lots of chord symbols are on top of one another. "
Only a problem 1.3 not in 2.0, but that was not my problem. Your attached file does NOT open in MuseScore 1.3 and also NOT in the "iPad Songbook". Additionally I noticed that the file is 4 times larger (16k vs 4k). In 2.0 it opens and looks the same as my example.
My problem is that the chord for the "multimeasure rests" (I just learned from Marc Sabatella) do not transpose.
Rob
In reply to Quote Jojo-Schmitz: "Not sure by Robipad
That really can't be, I've modified and saved it with 1.3 and the files are 2.87k vs. 2.94k
Anyway, here it goes again, now with slash notation, to multimeasure rests should not happen.
And yes, it is slightly larger now, 3.3k
Be aware though that 1.3 slash notation looks strange when transposing, the positions of the slash heads moves and they may show accidentals. 2.0 should not have that issue, it having used its slash tool
In reply to That really can't be, I've by Jojo-Schmitz
OK, I now understand what happened. I opened the file with 2.0 which is the default for my PC.
Then saved it again with 2.0 in another directory (as the same mscz format again) in which case it grows till 16k and your new one with the slashes till 17k. So the files when saved again don't open anymore in 1.3 and not in the iPad app. Both your files original sended are OK and solved the problem with the crowded chords in 1.3.
Both files did open in the iPad as well. The last one with the slashes does not generate "multimeasure rests" so then there is not any transpose problem as well.
The crowding chords at the end of the file(s) seems only a 1.3 effect which is not present anyway if opened at the iPad or in 2.0. Nevertheless that chords above "multimeasure rests" do not transpose is a bug.
Now there is a new problem... files saved from MuseScore 2.0 don't open in the the SongBook! This is valid for any file. Additionally the files are till 7 times larger then the same ones from 1.3!
And the files don't open in 1.3. but backward compatibility is probably not to be expected.
I didn't discover this before because all my files are batch generated with 1.3.
I suppose that the SongBook app isn't ready for 2.0 files
Rob
In reply to OK, I now understand what by Robipad
Indeed, the songbook app is not yet read for 2.0 files.
In reply to OK, I now understand what by Robipad
The size difference may be due to the fact that in 2.0 builds, a thumbnail image of the score is stored in the MSCZ file for quick display when browsing files within 2.0. Since thumbnails are always roughly the same size regardless of the score size, this will be a more noticeable difference for very short/simple scores, where the thumbnail may indeed take more space than the score itself.
In reply to Not sure I understand the by Jojo-Schmitz
At first I didn't worry about the crowded last line since I planned to use 2.0 anyway where this problem has been solved. Since I now know that the Songbook cannot yet read 2.0 files a solution should be welcome. But remember that I use the MuseScore Batch plug-in which imports XML files. Adding slashes in the source didn't really help. Only adding notes did solve this problem. Another solution seem to be adding one extra empty stave. Just adding a new-system solved the problem. This is just a bug from 1.3 importing XML files. Although I can automatically add such a new-system, it is not a solution I prefer. Can you think of another solution?
My XML files are also automatically updated (by a find and replace batch file), so I can add any fixed new text during the batch process.
It seems there is no need to have chords attached to anything in the measures since they automatically are correctly positioned by the delivered info. Positions are defined by forward and backward durations in the XML file.
Rob
The "thick lines" you refer to are called multimeasure rests; they are the usual way to represent consecutive empty measures in standard music notation. I agree with Jojo that you probably should have used slash notation rather than rests here, but it is indeed a bug in the app that chord symbols attached to multimeasure rests do not transpose properly. It seems to work in the current builds of MuseScore 2.0 (upon which the app is based in part), so it seems possible the bug will be fixed at some point when it is updated to use the current 2.0 sources. But I believe transposing is handled differently in the app than in MuseScore itself, so maybe not.
Hey Rob, thanks for reporting this issue. We will have to ask some patience as all our attention goes to releasing MuseScore 2.0 first. As soon as the 2.0 Release Candidate comes out (i.e. the last test release before the final 2.0 release if no critical issues get discovered), support for 2.0 files in the app as well as on musescore.com will be enabled. Thanks again for your patience.