MS3 Fretboard diagram previews in palette always show 6 strings
I am in a custom workspace with a palette for ukulele chords (downloaded from https://musescore.org/sites/musescore.org/files/2017-12/Ukulele%20Chord…). It might be commonly known that ukulele has only 4 strings, not 6 like a guitar.
Whenever I create a new fretboard diagram (with 4 strings of course) and drag it into my chords palette it appears as a 6-string diagram in the palette; the workplace xml clearly shows that the newly stored diagram is lacking the <strings>4</strings> tag, apparently the default value is 6.
However, when I drag the new diagram (appearing as 6-string diagram in the palette) into my score it only has 4 strings and looks as intended.
Is there any quick workaround known (apart from probably manually editing the workplace xml file) or will I have to wait for the next release with a fix?
[edit]
forgot to add: Windows 10 Home 64bit (v1809 build 17763.292), Musescore 3.0.2.5315 rev a8b90a8
Comments
Load this palette for ukulele chords (you must have a custom workspace for load it):
Ukulele Chords.mpal
See: https://musescore.org/en/handbook/palettes-and-workspaces#custom-palett…
In reply to Load this palette for… by cadiz1
Thx, but this seems to be exactly the same one I already had installed - in any case it shows the same behaviour:
1. drag a chord from the palette into your score
2. edit it in the score
3. Ctrl+Shift drag it to the palette and it will appear with 6 strings
4. drag this new chord into your score and it will appear there with 4 strings
(Admittedly I skipped steps 1 & 2 for this screenshot, I simply used an existing chord)
![musescore3.jpg]( "musescore3.jpg")
Hmm...
![4_string_fretboard.png]( "4_string_fretboard.png")
I tried on a development build:
My palette shows a fretboard with 4 strings, but the score shows 6.
(OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0.4013, revision: 94e01a8)
In reply to Hmm... I tried on a… by Jm6stringer
As expected here with current dev. version: 3ba972d
and with 3.0.2 (Windows10)
In reply to As expected here current dev… by cadiz1
I've been prompted for, and still accept, updates for dev. version. Apparently I am somehow not current.
So string issue is fixed.
(BTW: I still use MuseScore 2, I only use dev. version for bug verification)
In reply to Hmm... I tried on a… by Jm6stringer
3.0.0.4013?? A pretty old development build...
In reply to 3.0.0.4013?? by Jojo-Schmitz
I see now... although I've been accepting updates all along when prompted upon opening.
So I thought I remained up to date.
In reply to Hmm... I tried on a… by Jm6stringer
thx for reminding me, I added some version numbers to my original post:
Windows 10 Home 64bit (v1809 build 17763.292), Musescore 3.0.2.5315 rev a8b90a8
OK folks, call me crazy if you want: I seem unable to reproduce the issue in a new score.
But I can well reproduce the behaviour in an existing score (created in MS3) where I started off with one of the default guitar diagrams which I reduced to 4 strings.
This is weird....
In reply to OK folks, call me crazy if… by the_mnbvcx
Please attach this "existing score"
In reply to Please attach this "existing… by cadiz1
here you go....
In the meantime I created a new score and copied the existing parts; when I pasted the ukulele all chord diagrams were 6-stringed again. I now replaced them all with correct 4string ones derived from the ukulele palette.
So my current problem is solved even though I have no idea why it occurred at all.
When I first created the file I started off with guitar as instrument and only later changed it to ukulele - it seems somehow the guitar info was not completely replaced (?)