String data changes not synced between score and part

• May 22, 2018 - 13:06
Reported version
2.1
Type
Functional
Severity
S4 - Minor
Status
by design
Project

It is not possible to change the tuning of tablature (lute and guitar).
I make a new score with guitar 6-string tablature and open the part also. Then I tune the deepest string to G.
If I now give in "0", I would expect to have "0" on the string.
But I get "3" which shows, that in the tablature notation the tuning has not been taken.

It is possible to change a tuning, if I close the parts.
But I think, it should work with open parts also!
Version 2.1 and 2.2 have that bug.

In the master it seems to be possible to tune the strings, when parts are opened, but the parts will keep the former tuning.
So here also the parts should be tuned to the partiture's tuning.


Comments

In reply to by Jojo-Schmitz

OK, I have now downloaded 2.2.1 and it also shares this bug.
I tested it in the following way:
- establish a new score with guitar tablature only.
- set up the part with "new all".
Then I input a G on the deep E string, which gives a 3.
Now I change tuning of the deepest string to "G", which should result in a "0" on this string, but as long as the part is open, the number will stay as 3. In the tuning the new tuning is already saved, but it isn't shown.

As soon as I delete the part, the tab will change to 0 as it should.

OS: Linux Mint 18.3, Arch.: x86_64, MuseScore version (64-bit): 2.2.1, revision: 51b8386

Status (old) active needs info
Status active needs info
Reported version 2.1

I still can't reproduce, when I change the tuning the 3 changes into a 0 as soon as I leave that string data dialog

I'm not using parts though

Status (old) needs info by design
Status needs info by design

But indeed the part doesn't get the changed tuning, you need to change the tuning twice, for score and part, or generate the part after the tuning change. And I believe this is by design.