Editing Fretboard diagram with linked tablature leads to crash
Reported version
3.5
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
duplicate
Regression
Yes
Workaround
Yes
Project
- Put a fretboard diagram (from the palette) in a measure on the piano linked staff (the staff above the guitar tablature staff). Adjust the fingering in the inspector for the chord fingering you want.
- Do Ctrl+K to put the chord notation above the chord tab because, most likely, the palette chord will not be the right chord. My palette only has about 20 ready-made chords.
- Do a Tools > Realize Chord Symbols on that chord. This will put notes on the linked guitar staff.
- Go into the guitar tablature (staves) and adjust some of the fingering. What I did was get rid of the fingering on one of the strings. But it also happens if you adjust the fret that the chord uses or attempt to add a string to the chord.
- Hit space bar in that measure to start the piece. Boom, it bombs.
Don't know if it matters, but the guitar is not the only instrument in my score. I also had flute.
I noticed once it bombs, every time I attempt to play that chord, it bombs even if I don't touch it. I have to delete that chord and start over.
Workaround (per Mike320):
Add a fretboard diagram, edit it as described above. Put it in a palette. Delete the one from the score, then reapply it to the score from the palette.
Comments
I wonder whether it is related to #309380: Crashes when pasting fret diagram without chord symbol in score with parts and fixed the same way, can you give the latest 3.x development build a try?
I'm going with Jojo's theory that this as fixed with #309380: Crashes when pasting fret diagram without chord symbol in score with parts, it doesn't crash for me with the latest nightly.
In reply to I'm going with Jojo's theory… by mike320
Great. Can't wait.
In reply to I'm going with Jojo's theory… by mike320
Not sure it is fixed. I just reported it in the Development forum. It is still doing it but it is more random - it is not always reproducible with the same steps. When it CTD, it doesn't give you an error reporting tool. Also,
once you get the CTD, score will refuse to run and continually CTD unless you delete chords. Works fine once chords are deleted.
No point in continuing on an issue that got closed as a duplicate of another