[import xml] articulations don't play back
There is an issue of importing xml files into musescore. The articulations don't play back correctly. Dynamics play back correctly, but not articulations, staccato,etc. It even happens when importing from a saved musescore file that is xml. There is a work around. One has to copy and paste the piece into a new document. Then the articulations and all play correctly.
Attached are a couple of files.
| Attachment | Size |
|---|---|
| anway test from muse.xml | 20.88 KB |
| Away manger dolet.xml | 31.65 KB |
| Away manger sibelius export.xml | 21.92 KB |
Comments
Note:
The behavior occurs also, when you import XML files, that MuseScore previously exported itself.
It doesn't matter if the XML comes from other software.
Those affected: Duration-base articulations: (Staccato, Tenuto, Portato, Accent (sforzato), Marcato, Staccassiomo... )
a test file is attached.
another behaviors is after export / import xml:
(If they are not affected by the same bug,) perhaps, each item in the list can be a separate issue; I don't know.
Without further investigation, I would assume that when creating an instrument on MusicXML import, we don't attach "articulations" to the instrument.
Indeed, amateur and professional range as well as all articulations definitions are missing after the xml import.
Workaround: There is no need to copy/paste into a new score to fix this, just "change" instrument (to the same one, here Bb Clarinet)
There are some more differences though, some extra text styles and clefs and some more, run a diff on the attached files
The work around to change instrument with staff properties works. Thanks.
Best to all,
Hadley :)
In reply to Without further… by [DELETED] 5
Currently min and max pitch, instrument id and articulations are not set on MusicXML import. The information is not present in the MusicXML file and would have to be obtained somewhere else.
Isn't what the MusicXML id is for?
In reply to Isn't what the MusicXML id… by Jojo-Schmitz
You're probably right (as always the spec is somewhat unclear on the exact purpose of instrument-sound), in which case if a MusicXML file contains an instrument-id, it could be used to lookup articulations (and probably range too) in MuseScore's instrument list.
My recollection is that is exactly the reason why it got introduction into instruments.xml
Will see what I can do.
Indeed, the issue can be solved by creating instruments from the templates in instruments.xml if the instrument-sound element in the MusicXML file matches the MusicXMLid. This works because in that case the instrument-specific articulations are set based on the instruments.xml information.
Note that (at least in my sample set), most MusicXML files do NOT contain instrument-sound elements, so in most cases this is not a solution.
Suggested (full) solution: if present, try to use instrument-sound to create the instrument based on instruments.xml. If instrument-sound is not present or cannot be found, use the global articulations as defaults.
Yes, sounds like an excellent plan to me. Most instruments don't have their own set of articulations settings anyway and as such use the global settings. And those are much better than ignoring articulations altogether.
Furthermore, if the program doing the export does not include that instrument-sound information, it is that program's fault.
Fixed in pull request #3345. Would appreciate code review and testing, as this turned out to be a little bit more complicated than expected and I may have missed corner cases. The normal MusicXML iotest still passes, of course.
Fixed in branch master, commit a9f02622dd
255066 musicxml articulations dont play back (#3345)
fix #255066 - MusicMXL import articulations don't play back
I merged it in master. It's not straightforward to merge in 2.2 but it's possible to solve the conflict.
Tests are welcome before I do that !
I did test with a piano score. It works well.
Fixed in branch 2.2, commit a02dbcb6e2
255066 musicxml articulations dont play back (#3345)
fix #255066 - MusicMXL import articulations don't play back
Also merged in 2.2. Tests welcome.
Thanks for also merging in 2.2. I could not quickly test the result, but did review the changes and believe it is all OK.
In reply to Also merged in 2.2. Tests… by [DELETED] 5
I want to test, but No windows 2.2 nightlies here.
Edit: OK, I used the current nightly version for testing. (2.2 nightly = 4caf6e7.)
Good:
Articulations are working.
Bad:
Title (vertical) frame size is changed: 10sp to 8.17sp.
Tempo text's size is changed: 12pt to 10pt
Ugly: (No change) :D
Line-prall is changed to Down prall.
Text positions are shifted, text colors disappear.
I used the following attachment for the test.
Automatically closed -- issue fixed for 2 weeks with no activity.