Skip to content
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

Open
4 tasks done
luto65 opened this issue Nov 9, 2024 · 4 comments
Open
4 tasks done

Newzik properly generated MusicXML file missing first 4 measures. #25472

luto65 opened this issue Nov 9, 2024 · 4 comments
Assignees
Labels
MusicXML needs review The issue needs review to set priority, fix version or change status etc. P3 Priority: Low

Comments

@luto65
Copy link

luto65 commented Nov 9, 2024

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

  1. interprete the first four measures.
  2. use the right instruments for playing
    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

  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Nov 9, 2024

Seems a regression vs. Mu3 (3.6.2, but also my 3.7 Evolution). That though shows an error on loading:

Fatal error: line 15516 column 15 There is one IDREF value with no corresponding ID: P2-I44.

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/

@mercuree
Copy link
Contributor

mercuree commented Nov 9, 2024

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

But that's what the specs say, isn't it?

The element specifies a notation style for repetitions. The actual music being repeated needs to be repeated within each measure of the MusicXML file. This element specifies the notation that indicates the repeat.
https://www.w3.org/2021/06/musicxml40/musicxml-reference/elements/measure-repeat/

@Jojo-Schmitz
Copy link
Contributor

Jojo-Schmitz commented Nov 9, 2024

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)

@Jojo-Schmitz
Copy link
Contributor

Seems #16216 is related

@bkunda bkunda added MusicXML needs review The issue needs review to set priority, fix version or change status etc. P3 Priority: Low labels Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MusicXML needs review The issue needs review to set priority, fix version or change status etc. P3 Priority: Low
Projects
Status: Some release after that
Development

No branches or pull requests

5 participants