-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Newzik properly generated MusicXML file missing first 4 measures. #25472
Comments
Seems a regression vs. Mu3 (3.6.2, but also my 3.7 Evolution). That though shows an error on loading:
4.0.2 has the same issue as 4.4.3 plus showing the above error. (AFAIK as of 4.4 the MusicXML schema validations isn't done anymore) I believe though that Newzik is the culprit (and IIRC not for the first time), the MusicXML seems to be non-sensical, it has a measure repeat in the first 4 measures for all staves, but for all but the first 3 staves/instruments also notes in them: <part id="P4">
<measure number="1">
<attributes>
<divisions>1</divisions>
<key>
<fifths>-3</fifths>
</key>
<time>
<beats>4</beats>
<beat-type>4</beat-type>
</time>
<clef>
<sign>F</sign>
<line>4</line>
</clef>
<transpose>
<chromatic>0</chromatic>
<octave-change>-1</octave-change>
</transpose>
<measure-style>
<measure-repeat type="start">1</measure-repeat>
</measure-style>
</attributes>
<note>
<pitch>
<step>G</step>
<octave>3</octave>
</pitch>
<duration>4</duration>
<instrument id="P4-I44"/>
<voice>1</voice>
<type>whole</type>
<staff>1</staff>
<notations>
<technical>
<fingering>8</fingering>
</technical>
</notations>
</note>
<note>
<chord/>
<pitch>
<step>B</step>
<alter>-1</alter>
<octave>3</octave>
</pitch>
<duration>4</duration>
<instrument id="P4-I44"/>
<voice>1</voice>
<type>whole</type>
<staff>1</staff>
</note>
</measure> Seems Mu3 ignores those measure repeats and interprets the measures as empty if no notes, while Mu4 does not but then ignores the notes. To me that looks like a case of garbage in -> garbage out, and Mu3 only does the right thing because it doesn't import the measure repeats at all The MusicXML exporting software identifies itself as "Maestria_v2.7.2". I guess https://newzik.com/en/maestria/ |
But that's what the specs say, isn't it?
|
Hmm, not sure. Mu3 just doesn't know anything about (multi-)measure repeats IIRC, while Mu4 does, but messes up here in the MusicXML import. Not sure how MusicXML implements that, but I'd think you'd have measures with notes first, then a measure repeat that repeats the last measure(s) |
Seems #16216 is related |
Issue type
Import/export issue
Description with steps to reproduce
I purchased a PDF of a partiture, however need to change some instrumentation due to the different availability of musicians in my orchestra. I then imported that partiture in Newzik and it generated a musicxml .
I verified the MusicXML by importing it into
However when I imported that musicxml file in MuseScore4 then it fails to
although in the musicxml file the instruments id are the same as in the instruments.xml of MuseScore, all the instruments are played as pianoforte.
Supporting files, videos and screenshots
score5-8.zip
What is the latest version of MuseScore Studio where this issue is present?
MuseScore Studio version (64-bit): 4.4.3-242971445, revision: github-musescore-musescore-eb6b367
Regression
I was unable to check
Operating system
OS: macOS 11.7, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.3-242971445, revision: github-musescore-musescore-eb6b367
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: