Notes from a gp5/tuxguitar import detach from stem when being moved up/down using the cursor keys
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
- Import the attached gp5 file (created with TuxGuitar)) in MuseScore 3.0.2 (or 2.3.2, so not a regression)
- select any of the notes
- move up using the cursor keys, multiple times
- move up using the cursor keys, multiple times
At steps 3 and 4 you sometimes see the stem detaching from the note, or overshooting it
Came up in https://musescore.org/en/node/284533
| Attachment | Size |
|---|---|
| Saturation Point.gp5 | 18.58 KB |
Comments
As said in the related forum thread, it's a known consequence of this kind of issue: #62416: Changes to staff transposition (and other properties) not reflected in linked parts
From GP, Musescore displays in parts Standard staff + Parts. And so, this is what happens.
Remove the parts (and recreate if wished, so only in Standard staff), and no more issue.
And minor/normal issue, since the layout fixes itself during the following action.
I don't see how detached noteheads could relate to staff transposition in linked parts?
And the detached stems are not mentioned there, as far as I can tell?
Transposed, "and other properties". It's the "generic" issue.
![2019-02-21_15-06-48.png]( "2019-02-21_15-06-48.png")
Other one, marked as duplicate: #275667: String data/tuning not synced between score and parts
Basically, the display (images in the comment of this "duplicate") have the same origin.
See eg the third attachment in forum thread:
And so, can you reproduce this glitch after removing parts ? (and recreate new ones eventually)
With the parts removed the issue is gone. But #275667: String data/tuning not synced between score and parts is not marked as a duplicate
It could/should be since, "basically no staff properties are linked"
So, this current one is a duplicate.
"With the parts removed the issue is gone"
Q.E.D
Still these detatched stems have got nothing to do with staff properties, or any properties being linked between score and parts or not. It is which the score itself, it is not about being moved in score and then detached in parts.
It is related to having a linked staff apparently though.
Any it may turn out to have the same underlying root cause, but that remains to be seen.
But yes, #275667: String data/tuning not synced between score and parts and #62416: Changes to staff transposition (and other properties) not reflected in linked parts do look like duplicates of one another
Again, I can reproduce these glitches when changing quicky the pitches (fix themselves) on all GP files. Eg: Aerosmith - Dream On (guitar pro).gp5
(it's due to the linked staves Standard + TAB in parts) when imported with MuseScore. Remove these parts, and it's gone.
and again, yes, it seems to be related to parts with linked staves, but I don't see it as being related to properties not being properly linked between score and parts