Guitar tablature import from XML goes wrong

• Apr 22, 2019 - 13:31

Hello! I have a MusicXML file that includes a guitar tab. When opening it in MuseScore 3.0.5, all the tablature numbers are displayed on the top string. However, the playback sounds okay. Resetting the instrument and tablature style does not help. Looking into the XML file with a text editor tells me that the correct string data is there. How to make MuseScore display it?


Comments

In reply to by Kristo

Wrt file TEST.xml, the string data may be present but it is encoded incorrectly: e.g. at line 123 it uses tuning-step C#/Db, instead of tuning-step C and tuning-alter 1.

Note that fixing this is not sufficient to make the file import correctly. The string data is not read correctly (it is missing from the instrument definition in the MuseScore file produced), nor does MuseScore allow editing of the string data. This smells like an incorrectly imported staff type.

Unfortunately, the story is not over yet. Here's some additional information to who might have similar issues:

  • Dolet + MuseScore 2.3 (Windows 7) works fine. All tab numbers go where they should.
  • Dolet + MuseScore 3.x + Windows 7 = the tab digits are displayed as question marks and placed on the top string. Nothing helps, and after opening such XML, all new guitar tab files that I create from scratch will have the same problem (tab digits will be red question marks. Both linked staff and separate tab staff).
  • Dolet + MuseScore 3.x + Linux = the tab numbers are initially red question marks, but when adding a new linked tab staff, the digits will appear. Naturally, they have lost their correct string information.
  • Sibelius's XML export - no luck at all.

Our current workaround is Dolet + MuseScore 2.3 > MuseScore 3.

In reply to by Kristo

Seems perfectly fine in MuseScore 3.0.5 on Windows 10

EDIT: Could it be that you have a text font file locally installed that could interfere? After all, the tab numbers are drawn using a font; and missing glyphs are often shown as question marks…

In reply to by Kristo

Kristo could test out the font issue theory by right clicking the tablature staff, choosing Staff/Part properties, click Advanced staff Properties then change the font to see if that helps.

Dear Friends

This is an important issue to fix.
Without fixing it will be impossible to import tabs form other software like guitar pro, finale or sibielius.

In reply to by herrlein

Which "this" are you referring to?
All bugs mentioned and detected in this thread have already been fixed in the current version (3.4.2).

If you have a score that doesn't work, then please attach it so it can be investigated. Note that MuseScore can directly import some Guitar Pro file versions as well.

In reply to by herrlein

https://musescore.org/sites/musescore.org/files/2020-05/GTR_MIDI_CHART…

GUITAR AS A MATRIX

Here is a MIDI Chart I did some years ago,
It can help to figure out the problem involved in this Tab-String-Filter by channell.

For example, MIDI note #76 appears in all strings (in a 24-fret guitar, for example).
There is a color code:
1) BLUE NOTES: Appear just in one location in the TAB.
2) BLACK NOTES: Appear in two locations in the TAB.
3) GREEN NOTES: Appear in 3 locations in the TAB.
4) 2) BLACK NOTES (BIG FONT): Appear in 4 locations in the TAB.
5) 2) PINK NOTES: Appear in 5 locations in the TAB.
6) RED NOTE: Appear in 6 locations (in the case of 24-fret guitars) or 5 times (in the case of 20, 21 or 22-fret guitars).

Hope it helps to find a solution.

Best !
Julio Herrlein

In reply to by herrlein

First off, let's try to keep topics on topic and not cross post your other ideas from other topics in here as well as it is unrelated.

I can confirm that there is something not working as expected. I noticed the string data after import being off by one octave. After correcting that in the staff properties, I could move those notes back to their strings.
I also think this is the reason why your positions aren't honored, with that wrong stringdata (bug!) those positions simply don't match with the notes themselves. At least MuseScore honors the actual note, and thus adjusts position information to match its new string data.

The cause of your bug is different though, as your file doesn't include multiple <staff-details> elements.
So please post that score + PDF as a new issue into the issue tracker: https://musescore.org/en/project/issues/musescore

In reply to by jeetee

Yes, Musescore honors the right notes. No problem. The question is preserve the the right string. Maybe a possibility would be a channel to string filter, for inputting the notes with a MIDI guitar. I don´t know if you play guitar, but the chart help the understanding of the matrix nature of the guitar. Thank you.

In reply to by herrlein

I'm sorry if my response seemed aggressive to you, that was not my intention.
Although I indeed was slightly irritated at the moment of posting that after having investigated and confirmed your import issue and pointed out to please not include the discussion about MIDI input into this thread, as it already had its place to be discussed your answer seemed to somehow imply that your proposal for MIDI input somehow magically would fix the musicxml import as well.

That assumption of mine was likely wrong, so for that I apologize; but it could be just as well that you as a user has no background or insight into the technicalities that come into play between MusicXML import and/or MIDI note input. Therefor I stressed the separation of those two items in my answer.

So I again apologize for the perceived tone of my answer. I very much appreciate you taking the time to share your example of this bug and hope that once it is entered into the issue tracker a developer will pick it up swiftly.

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