Key Signature disappearing (linked Tab Staff), wrong fret numbers on TAB

• Oct 10, 2011 - 09:04

Bug 1: I was trying to convert a linked staff to a TAB staff with a key signature for C Minor Scale, but after converting the linked staff to a TAB, the key signature(for C Minor Scale) disappears and shows a regular staff. (Screenshots attached)

Bug 2: The wrong fret numbers are getting inserted on Guitar TAB Staff.
e.g. The lower C note is inserted as 1st Fret on 2nd string(B) on the TAB, instead it should have been inserted as 3rd Fret on the 5th string(A). It is inserting a note an octave higher on the TAB. (Screenshot attached)

Note:
Bug 1 Screenshots - "Staff Before Linking.JPG" & "Staff After Linking Guitar TAB.JPG"
Bug 2 Screenshot - "Wrong Fret Numbers on TAB.JPG"

Attachment	Size
Staff Before Linking.JPG	28.98 KB
Staff After Linking Guitar TAB.JPG	44.16 KB
Wrong Fret Numbers on TAB.JPG	42.1 KB

Comments

eapenzach

• Oct 10, 2011 - 09:07

These bugs appeared on the build "mscoreNightly-r4851"

Miwarre

• Oct 13, 2011 - 18:35

Hi and thanks for your report.

(Incidentally: for all users of the stable MuseScore version, these issues refers to ver. 2.0 still under development, aka "trunk").

I spent a while looking into the matter and, while I can confirm both issues, these are my findings so far.

1) Staff linking has problems of its own, even without TAB's involved. I am still looking into this and I'll post a proper issue report in the issue tracker as soon as I can reach solid evidences.

2) This has actually not to do with TAB's, rather a basic bug affects initial clefs: they are displayed as intended (so you see a treble 8aBassa clef in your guitar score), but actually behave as treble clef (see this issue report I filed after your post: #13105: [trunk] Instruments show their clef, but actually use treble clef).

This becomes apparent if you save and reload your score: all notes will become one octave higher. So, the TAB itself is showing the 'correct' frets, as all notes are actually one octave higher than shown.

As I only deal with TAB's and I leave to other more experienced developers to deal with deeper matters, I'll try to analyze your report into individual issues and report them in the issue tracker; point 2) is already there, point 1) will follow.

Thanks,