Slur anchor note wrongly indicated when exporting to MusicXML
I am using MuseScore for the preparation of scores going into my android application.
Firstly, here is an image to help understand what I am talking about -
To create the tie, I select the E note on the left and press + : all is ok, I get a nice tie.
Now, to create the slur, I select the A on the left and shift click on the G on the right and press 's' : result is a slur.
Ok, every thing is good up to this point.
I now export the score as MusicXML.
The tie anchor points are correctly identified as being the two E notes.
However, the start of the slur is no-longer attached to the A on the left and the G on the right.
It is has been attached to the two E notes instead - which is evidently wrong.
This would not be too bad if the slur data included the positioning information provided for in the MusicXML spec.
Is this a known bug, or is it "by design" ?
Is there anybody working on improving the MusicXML export for version 2.0 ?
| Attachment | Size |
|---|---|
| TieSlurProblem.jpg | 5.22 KB |
Comments
There have been loads of improvements for XML Support in 2.0, please try a recent nightly build and see yourself
In reply to There have been loads of by Jojo-Schmitz
Thank you for taking the time to answer.
I will indeed try a nightly build again.
However, the last time I tried one, the page formatting was all out (note stems extending beyond the top of the document, for example). So was not too keen to try again.
Perhaps things have improved.
In reply to Last try catastrophic by Simon Giddings
bugs like that come and go on a daily basis, that is the nature these development builds
In reply to bugs like that come and go on by Jojo-Schmitz
Yes, I agree that this is indeed the nature of dev builds.
So, I just tried last nights build - no better.
After having looked into the file structure and in memory data structure, it is evident that slurs are not anchored to any other note that the first note in a chord.
This means that it is not possible to determine which was the original target note.
I wonder if this is a real problem in the real world. Will a slur over a chord have the same effect as having individual notes being tied together and having an over-arching slur ?
In reply to Agreed by Simon Giddings
In the real world, the figure you show would more commonly be notated using separate voices, not tying individual notes within a chord. If you tried notating it as two chords with a slur but no tie, people would repeat the repeated note - that is, the slur would not magically turn repeated notes into ties. But because this leaves an open question as to how you want it played - especially for wind or stringed instruments, which are the instruments for which slurs are most meaningful on the first place - you'd be best off not doing that at all. That is, slurs should not cover non-tied repeated notes, although this can be acceptable for piano and maybe other instruments where a slur doesn't really have much effect in the first place.
In reply to Agreed by Simon Giddings
lvinken is working on MusicXML import and export for 2.0 and he also worked on it in the previous version. Of course, as a developer, you are welcome to help.
Btw, (shameless plug) the MuseScore player on android, relying on the MuseScore format, probably doesn't have this issue and it's available for purchase!