musescore3 xml bug

Tirt

• May 11, 2019 - 19:52

Hi,

There is an error displaying xml with musescore3.
please look at the attachment.

The top g note should be one long note, but in the notation it get
separated with each lower note.
Why is that?

I have tried opening this same xml with musescore2 and there is no error,
only with musescore3.
Please fix this error in the future.
Thanks.

Attachment	Size
(05) Let It Be x .xml	12.38 KB
Snap3.gif	72.82 KB

Comments

Ziya Mete Demircan

• May 11, 2019 - 21:43

Musescore2, Sibelius and Musescore3: They all show the same way.
Actually the Musescore versions show better :)

Maybe you opened the wrong score (xml)?

jeetee

• May 11, 2019 - 21:50

Your XML file explicitly shows this note as a lot of small tied notes. So MuseScore 3 is showing exactly what is in that file.

For the record, so is 2.3.2. It shows the exact same result. Not sure why you think it doesn't ?

Pentatonus

• May 11, 2019 - 22:05

Am i blind? In MS 3.x there are only two g's tied!?

Ziya Mete Demircan

• May 11, 2019 - 22:20

        <tie type="start"/> //starting
        <tie type="stop"/> //and it stops immediately.
        <voice>1</voice>
        <type>64th</type>
        <staff>1</staff>
        <notations>
          <tied type="start"/> // continue
          <tied type="stop"/> // and it stops immediately.

But it should be: (first: tied type="stop" and then tied type="start" )

        <tie type="stop"/> // stopping
        <tie type="start"/> // starting
        <voice>1</voice>
        <type>64th</type>
        <stem>up</stem>
        <staff>1</staff>
        <notations>
          <tied type="stop"/>  // and stopping
          <tied type="start"/> //continue
     //...

According to this code, I think Musescore3 is correct.

jeetee

• May 11, 2019 - 22:25

Nope, I'm the blind one.. I thought the original report assumed multiple voices should've been used in the "correct" result because of the wording.

This one might've to end up on the radar of Leon Vinken for confirmation