MuseScore is not displaying the ties of my Cakewalk XLM files

• Apr 2, 2022 - 14:59

I am using a recent version of Cakewalk by Bandlab as my DAW, from which I am exporting MusicXLM files. When I open an XLM file in MuseScore the ties neither show, nor do they play back as one single note, but as 2 short notes - sounding as written without a tie.

I am new to MuseScore (only had it for 2 days), and new to any kind of notation software. Is this a problem only with Cakewalk? Am I doing something wrong in the settings of MuseScore?

I tried exporting from Cakewalk as a MIDI file, and the ties showed up and played back well in MuseScore, but all sorts of data is lost or misinterpreted by Musescore when it reads my DAW’s MIDI files. Musescore seems to read all the basics of the XLM file ok, but not the ties.

Comments

bobjp

• Apr 2, 2022 - 16:51

Welcome to MuesScore. I don't have a DAW, so I can't check this. I do have a different notation program. I exported an .xml from it and imported into MuseScore. Ties were present. Transferring files is always a gamble. Hopefully someone with Cakewalk can help.
I only responded to you to let you know that Musescore can import ties.

jeetee

• Apr 2, 2022 - 21:22

Please attach a small example MusicXML file.

Dilaco

• Apr 3, 2022 - 05:49

Thank you Bobjb and Jeetee for taking an interest in this Musescore-Cakewalk issue.

As requested, Jeetee, I have attached a MusicXLM file. All instances where the same note is repeated consecutively should be tied, as they are in Cakewalk’s notation.

Attachment	Size
one track ties demo XLM File.xml	4.65 KB

Jojo-Schmitz

• Apr 3, 2022 - 08:58

Comparing that with a MuseScore MusicXML export shows that the latter additionaly has

        <notations>
          <tied type="start"/>
          </notations>
...
         <notations>
          <tied type="stop"/>
          </notations>

Not sure these are strictly needed or whether a plain

        <tie type="start"/>
...
        <tie type="stop"/>

like Cakewalks has (and MuseScore too), should be enough?

Jojo-Schmitz

• Apr 3, 2022 - 09:48

Ah: see https://www.w3.org/2021/06/musicxml40/musicxml-reference/elements/tied :

The <tied> element represents the notated tie. The <tie> element represents the tie sound.

As a DAW is about sound, Cakewalk uses only the the latter. But that is an invalid notation when it comes to the notation.
Still MuseScore could use the latter as a hint to do the former, "be generous in what you accept, but strict in what you generate"?

Dilaco

• Apr 4, 2022 - 12:35

Thank you Jojo-Schmitz.

I admire your cleverness in being able to analyse the file in such a way. I am clueless about such things.
So it is a lack on Cakewalk’s part. I guess it means that I will have to manually insert the ties.

There is still the option of using Cakewalk’s MIDI files instead of its XML files, because then the ties show up. But other issues occur, one of which is hard for me to explain: I exported a Cakewalk MIDI file that had 5 different parts/MIDI tracks. MuseScore displayed the 5 parts as 3 Pianos, with the first two having a double stave—two treble clef staves joined together. I have attached a screenshot. The Musescore import page shows 5 separate instruments, but interprets them as 3.

Attachment	Size
MIDI import Screenshot.JPG	92.93 KB

Jojo-Schmitz

• Apr 4, 2022 - 12:42

Better stick with MusicXML and add the ties
Also report that bug to Cakewalk

Leon Vinken

• Apr 6, 2022 - 07:21

Agree with Jojo, submitted issue #331007: [MusicXML import] support tie element.

Jojo-Schmitz

• Apr 6, 2022 - 17:47

Thanks

Dilaco

• Apr 8, 2022 - 04:17

Thanks Leon

Dilaco

• Apr 8, 2022 - 04:27

Jojo

Yes, I think I will stick to the MusicXML files. Thanks for your advice.

I've just noticed that I have been misspelling the acronym for the files, sometimes calling them XLM files instead of XML files. Sorry for that oversight and for any confusion it may have caused.