"Play transposition" is not reflected in Parts
I'm not very used to use the "Play Transposition" in Staff Properties. I think there is a bug, but it is possible that my way of doing things is not the best for my purpose. And so, two pairs of eyes, or more..., are better than one to check!
So: Open this file (Voice + Guitar Standard / linked Tab staff) in F# m : 1TEST.mscz
- After a while, my goal is to play the guitar with a Capo1: 2TEST Capo1.mscz
- I add a new local Key Sig with Ctrl (ie Gm, a higher semitone to correspond with the Capo1-fret) in the guitar staff: 3TEST Capo1 new keysig.mscz
- Right-click on the same staff -> Staff Properties -> Play transposition -> Choose "Minor Second"/UP -> Ok
4TEST Capo1 new keysig after Play transposition.mscz
First unexpected result: no change in the linked Tab staff (numbers expected: 3-1-1-1 instead 4-2-2-2)
- Now, view Guitar "Part": second unexpected result: the keysig is Gm. "Play transposition" has been ignored in Parts.
- To obtain the wished result, you must repeat the same operation in this part: Staff properties -> Play transposition -> "Minor Second"/UP -> Ok
You have now in main score and parts a good result with display and playback: 5Final result.mscz
Comments
Changes made in staff properties *after* the parts are generated do not reflect in the parts. I consider this a bug - see #62416: Changes to staff transposition (and other properties) not reflected in linked parts. it was a bug I really wanted to fix for 2.0.2, but I don't understand what the expectations were with respect to guitar and capo specifically, so I was afraid to change anythiung before getting feedback.
I can say that you should not need to change the key signature manually - changing the transposition should do that automatically if appropriate. At least, for the "normal" uses of this field - to handle transposing instruments - this works as expected. But I still don't understand the relationship of transposition and capo for guitar, which is why I was not able to look at this issue further.
In reply to Changes made in staff by Marc Sabatella
Ah, thanks, I forgot your mentioned bug report: #62416: Changes to staff transposition (and other properties) not reflected in linked parts
Well, it's tricky for me to obtain the desired result.
I guess that guitarists expect the behavior of GP with the capo: ie like first picture of this bug report: #70101: [GP] A file containing a part with a Capo indication is not played properly.
That is to say: with a Capo indication, the notes/numbers in tab staff remains at the same location, but the playback takes into account the position of the Capo, like when you play guitar.
The current result with MuseScore is not this one, and I suspect that it is the same cause of the bug reported about import files of GP ?
In reply to Ah, thanks, I forgot your by cadiz1
What I still don't understand is whether / how this is *supposed* to work in MuseScore. I don't want to do anything about #62416: Changes to staff transposition (and other properties) not reflected in linked parts until I understand if it is supposed to be possible to get capo behavior, and if so how, so I can be sure not to break it.
In reply to What I still don't understand by Marc Sabatella
I don't know if that helps but with GP, the feature looks at this:
There is a dropdown list (left to the image) to select the Capo fret. It is reflected automatically on the score (and above all in the playback, while the notes - G in second staff - don't change of location on the score.)
Said in an other way, in the playback you heard the Am arpeggio in staff 1, and the two G in the second staff but "transposed" to A in reason of the capo 2-fret mark.
So, I think simply that it is not possible with MuseScore to have this capo behavior (not implemented), right?
And that is the reason (I guess?) for why the import of a GP file containing a staff or more with this notation fails with the playback.
I don't know if Sibelius, or others, supports this feature.
F# minor = E minor + Capo 2:
Incidentally, it might be useful if MuseScore offered the user the option to show the open string tunings at the beginning of the first TAB line.
In reply to F# minor = E minor + Capo 2: by geetar
Yes, but as you see, the key sig is not the same in your score (see the result with GP),
![key sig.jpg]( "key sig.jpg")
and above all, this does not solve the problem of importing files GP with Capo markings.
In reply to Yes, but as you see, the key by cadiz1
The proof: listen this file (the same test file as writing in my previous reply) exported in GP5 format and then imported with MuseScore: Nylon Guitar MS.mscz
Re: the illustration. The TAB line in Guitar pro is fine but, for some reason, perhaps a limitation of the program, it has notated the guitar part in F# minor rather than E minor! The right notes, but in the wrong key!
In reply to Re: the illustration. The TAB by geetar
No, it's not the same behaviour: it is notated in Em, indeed, but the playback is in F#m in reason of the Capo II mark.
If you have a Capo II, it "sounds" in F#m (like the score), but your left hand fingering is the same as when you play in Em. So, it corresponds at the practice for guitar, right?
Have you listened the gp5 imported?