[MusicXML] first-fret tag not supported for fretboard diagrams

• Apr 3, 2018 - 05:38
Type
Functional
Frequency
Few
Severity
S4 - Minor
Status
closed
Regression
No
Workaround
No
Project
MuseScore
Tags
musicxml

Screenshot - 03.04.2018 , 06_06_02.png
^- as you see in the picture on higher fret's the fret dot's are running of the fret matrix.

That's how it should look like:
Screenshot - 03.04.2018 , 06_13_59.png
'Note Flight Viewer': https://haldms.halleonard.com/nf/preview/146/19726 creator of the XML was 'Dolet 6.2 for Sibelius'

The dot-data and fret information is read correctly from the music XML.
However problem seem about correctly instantiating/initiating the fretboard diagram.
Or maybe there's a problem about rendering the fretboard diagrams

Here is the MusicXML to test:
2HL_DDS_0000000000125653.xml.gz_.xml

I tested this issue with MuseScore 2 and MuseScoreNightly-2018-03-30-2124-master-b92a6e0.7z

Well beside fixing this bug - may also consider to change general layout.
Show the fret number at the right side of the fretboard matrix and formating it smaller and append 'fr' at it's end.

Comments

• Jun 18, 2020 - 20:12
Title Guitar Fretboard Diagrams imported from Music XML are created incorrectly ⇒ Guitar Fretboard Diagrams imported from MusicXML are created incorrectly

Reply

• Jan 4, 2021 - 20:36

I've also encountered this issue and found it is not working in the 3.6beta. I could certainly believe that this is not the highest priority thing to fix, but I'm adding this comment just to register my vote to have it addressed. What's the best way me to track this issue?

Reply

• Jan 5, 2021 - 16:54
Title Guitar Fretboard Diagrams imported from MusicXML are created incorrectly ⇒ MusicXML imnport: fretboard diagrams ignore first-fret tag

As far as I can tell, the diagrams are correct except that they are ignoring the "first-fret" tag in the MusicXML. In principle it could be a simple matter to workaround by changing the corresponding property in the Inspector, but that doesn't actually shift the dots to compensate. I suppose there are other cases where that is desirable, but not here unfortunately.

Reply

• Apr 16, 2021 - 07:15

Storing the MusicXML first-fret element in the FretDiagram's FRET_OFFSET property (perhaps combined with subtraction that value from every string's fret number) may do the trick. It seems the inspector displays the text as fret number instead of fret offset. Will look into this.

Reply

• Apr 18, 2021 - 20:47
Title MusicXML import: fretboard diagrams ignore first-fret tag ⇒ [MusicXML] first-fret tag not supported for fretboard diagrams

Fix implemented. No pull request yet, there are more fretboard MusicXML fixes to be implemented.

Reply

Fix version
4.0.0