any thoughts on how this voice confusion could be fixed?

• Dec 4, 2013 - 21:36

hi all,
i imported a .xml file and swapped voices so the top was in voice 1 and so on.
Aparently something went wrong along the way as (in the intro) the noteheads in voice 1 have stems and beams in voice 3 and the 16th flags are facing the wrong way...
In the deun(tune) the noteheads from voice4 have stems and beams from voice 2 although the value for the bass in voice 2 is okay...

how can i tie a note from voice 4 to a note in voice 1 in the next bar? eg. the a's in bar 9-10


I'm not quite sure what you mean about "noteheads in voice 1 have stems and beams in voice 3" - can you point to a specific note in a specific measure and say what's wrong?

But I do see a number of beam issues with sixteenths, such as in bar two, top staff, the D that is the first entrance of voice 3 - it's partial beam extends left instead of right. Presumably the complexity of the beaming confused MuseScore somehow. I found I could workaround those errors by selecting the notes in question and explicitly setting the beam mode to "Start beam" using the Beam palette.

In the nightly builds for 2.0, the file doesn't want to load at all - MuseScore reports the file is not valid. Is this direct output from Sibelius? When I look at the file, it seems normal enough. If I try to load the file despite the errors, there are no beams at all.

In reply to by Marc Sabatella

Hi and thanks,
i exported directly from sibelius > scarborough_fayre-anoniem.xml
imported into musescore > scarborough_fayre-sibelius.mscz
and then copied the guitar part into a "template" > scarborough_fayre-anoniem.mscz

I am talking about scarborough_fayre-anoniem.mscz
"I'm not quite sure what you mean about "noteheads in voice 1 have stems and beams in voice 3"
in bar 1-5 the notes with the blue heads have yellow stems and flags and the pink notes have green stems and flags.

I guess you are referring to scarborough_fayre-sibelius.mscz, right?
"D that is the first entrance of voice 3" i am not sure of which D you are talking, what i do see now is 6-line staffs :?

Are we seeing the same thing? i attached my screenshot...

Attachment Size
scarborough1.png 228.69 KB

In reply to by aeLiXihr

I didn't actually look at the MSCZ files at all - I simply imported the XML file for myself. In that file, there was no issue with voices that I could see - just the beam issue. And sorry, the "D" I referred to was actually in bar 3. The corresponding note in bar 2 is an F. Those are the ones with the backward beams. Looking at your screenshot - which looks very different from what I see when I import the XML - I guess maybe the reaosn those beams are backwards is that they were supposed to be part of an across the bar beaming figure, but that didn't work because the last note of the bar 1 in that voice was a quarter note and hence didn't have a beam. So you probably did something funny in Sibelius to trick it into creating a beam across the bar line anyhow, and that's what MuseScore is finding confusing. I'm guessing whatever you did in Sibelius either did not export correctly, or else it is just something too strange for MuseScore to understand.

Now, if I look at the MSCZ file (the one without Sibelius in the name), I do see what appear to be beams that highlight in the wrong color when you select them. I assume that's related to the more general beaming issue here. I think the whole beam structure of your original XML file is either invalid, or at least, just something MuseScore doesn't recognize. So your attempt to move voices around just made things worse.

...'how can i tie a note from voice 4 to a note in voice 1 in the next bar? eg. the a's in bar 9-10.'
The answer can be seen at the a's in bar 14-15. That is: keep, or place, the notes in the same voice.

More problematic:
The strange pairing of beams with voices they don't belong to can be fixed by exchanging voices - being aware that rests in voice 1 can not be deleted (only set invisible).
Basically, since 'scarborough_fayre-anoniem.mscz' looks like a guitar part, you can finesse the score to a point where you can delete all the extraneous rests in the voices (other than voice 1) for readability. As you can see in your present score, many rests collide. The same is true with some overlapping notes - you can delete the unnecessary ones.

P.S. Use Marc's 'Start Beam' workaround for the16th flags facing the wrong way.

I imported the XML file and there is definitely something amiss with the note rendering and/or beaming. Either Sibelius is exporting wrongly, XML is inexact (i.e. stuff is getting lost in the translation), MuseScore is importing wrongly or MuseScore is displaying the resultant notes wrongly

In the second measure if you remove the beam from the D (eighth-note that gets tied to the quarter-note) then the 16th note F looks like it has become a quarter-note. If you look closer however, you will see that the note now mysteriously consists of a note-head, a stem and a couple of short, vertical dashes. Further playing about shows that the dashes are the double-tail of a 16th note that have become distorted. Overall, I'd say it looks like a MuseScore problem in that the notes are not being laid out correctly.

There are (at least) two issues here:

1) MuseScore (trunk) incorrectly reports a validation error. I am investigating, but have not found the cause yet.

2) The beam information in the xml file is completely incorrect: beam continue without beam start, not a single beam end. Currently MuseScore handles this by removing all beams it does not understand (for this file: all beams)

In reply to by Leon Vinken

The file is from Dolet 1.8. It's quite an old version.
The changelog says "Version 1.8 is now distributed free of charge. If you are using Sibelius 5.1 or later, you will get better results using the Dolet 6 for Sibelius plug-in, also distributed free of charge." So you might want to install Dolet 6 and try again.

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