Tablature: Crash due to a tick in the "Open" column of Staff Properties > String Data

• Dec 29, 2021 - 16:46
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
  1. NEW score, guitar + tablature.
  2. EDIT string data for tablature staff: C2G2C3G3C4E4
  3. Copy the melody from the treble clef of the attached file, paste it into the top staff of the new guitar+tablature.
  4. Delete the first d in either the treble clef or the tab, enter in back in on either staff, crash results.
    4b. When I just tried it, no crash (after 3 sequential crashes, but it won't go on the correct string.
  5. Note that the d can not be put on the correct string, 2nd fret, 2nd string.
Attachment Size
Sleeping_Lulu_in_Open_C_Tuning.mscz 22.73 KB

Comments

Title Crash with guitar tablature in CGCGCE tuning. Crash with guitar tablature by ticking by confusion an Open string in string data.
Status active duplicate

"5. Note that the d can not be put on the correct string, 2nd fret, 2nd string."

Simply because you checked the second string as open D - see image below.
corde.jpg

This is another manifestation of the misunderstanding of this function in String Data. It's a duplicate so see the details in the report of this issue: #321767: Delete/rename/move/clarify the "Open" column of "String Data"

For your score, just uncheck this box of the second open string, and the problem goes away. See: 1Sleeping_Lulu_in_Open_C_Tuning.mscz

Title Crash with guitar tablature by ticking by confusion an Open string in string data. Tablature: Crash due to a tick in the "Open" column of Staff Properties > String Data
Status active needs info

I can reproduce (in MuseScore 3.6.2 on Wondows 10) if, and only if in the new score I also use that (bogus!) open string (matching the settings from the score attached to the initial post), that step is missing from the inital post.

Status needs info active

I can't reproduce in a 3.6.2 debug build either, so whatever the issue is, it probaby is not fixed, but sort of a Heisenbug (vanshishes when watching)