Guitar TAB and physical capo setting

Issue type

Other type of issue

Bug description

Musescore imports .gp files with a capo - setting correctly but changes fingering (the TAB information) when generating the . mscz - file.

Steps to reproduce

1. I import a (simple) guitar tab from Guitar Pro (a .gp file). The tab has been written - let us say with a capo applied at fret 2. The guitar pro tab displays the fingering with respect to capo 2 - that's what guitarists expect. E.g. a C chord with capo applied at fret 2 "sounds" like a D chord but has a completely different fingering as compared with a standard D chord.
2. Import from .gp file goes well. Musescore displays the same fingering as Guitar pro and as a text line above the staff "capo fret 2" is displayed - just as in Guitar pro.
3. Now I save the score in .mscz format and close the file.
4. When re-reading the .mscz file, Musescore has changed the tab: The former C chord at fret 2 now has been changed to a D chord (with no capo at all) - which still sounds well, but that's not the right fingering of the arrangement.
   It also may happen that musescore generates TAB which is physically impossible to be played by a human hand.
   With other words: the .mscz file disregards the physical setting of a capo in an imported .gp file and computes a tab - I assume simply from the notes.

Screenshots/Screen recordings

No response

MuseScore Version

4.1.1

Regression

I don't know

Operating system

Windows 10

Additional context

No response