Open wongjoel opened 1 year ago
A bit easier to reproduce, must have to do with the MuseJazz style:
My first reaction (as the person who originally implemented most of this) was that I was surprised the appearance setting (standard/jazz/custom) affected Nashville numbers at all. Most things about XML files is really specific to chord symbols. But I guess somehow I did manage to get it to work in a reasonable way in MU3 (at least not as obviously terrible), and this is definitely a regression.
That said, I am not convinced what MU3 did was actually good either. While it is presumably simple to just fix the regression, it is at least worth considering giving Nashville their own rendering rules. Which for now could be just what is in chord_std.xml, and thus completely ignored the chord symbol style settings. And then if/when we add customizable rendering rules for chord symbols, we could have separate customizable rules for Nashville.
As far as where the problem is happening, this line seems potentially suspect to me - not that it's obviously wrong, just that it clearly affects size and it was added post-MU3:
Chord symbols really need some love, and the more problems I see with them, the more it seems to me that default sizing (and then providing more flexible controls to modify each chord symbol individually) is the crux of the problem.
Bumping this to a high priority for the shortlist. It would be a fix for 4.3 at the earliest.
In the current appimage, OS: Debian GNU/Linux 12 (bookworm), Arch.: x86_64, MuseScore version (64-bit): 4.2.0-233521125, revision: github-musescore-musescore-eb8d33c
Nashville Numbers formatted in Jazz chord style actually do not display modifiers or roots. If you edit the chord, the -7/ will reaapear, and it is played correctedly, but the score displays and prints incorrectly.
@nathan-stewart I'm not completely understanding your comment (bear in mind I don't have much experience with Nashville Numbers)
Are you saying if you put in Nashville Number "1/3" the three disappears? Can you share a video or an example score with instructions to reproduce?
The screen shot shows - all of the 2's are actually 2- and if you edit it, it will appear. I should have shown that instead of the 1/3 as some of those are bare 1 and some have a 3 root. They play correctly, but render as shown nashville_number_format_bug.zip
They render correctly in standard style - I just like the font for Jazz - I don't really need the full up style for NN.
The "-" is there, as is the /3" - they are just tiny, as noted in the original repoort.
The different "Appearance" settings were never designed to work with Nashville numbers and simply should not be used in that context. If you want to use Nashville numbers, stick to the "Standard" setting under Appearance, but then change font to MuseJazz Text if desired (in Format / Style / Text styles / Nashville number).
That said, again, I would still say it's a bug that the Appearance section affects Nashville numbers in any way at all - it's really only relevant for chord symbols.
Ah, I had to zoom in to see it, thanks Marc!
Describe the bug Nashville Numbers render correctly with
chords_std.xml
, but when switching tochords_jazz.xml
, the font size of chord modifiers (slash, sus, minor, etc.) is extremely small.To Reproduce Steps to reproduce the behavior:
Expected behavior Chord modifiers should be sized according to the Chord, same as when using the default chord style in
chords_std.xml
Screenshots Behaviour with
chords_std.xml
:Behaviour with
chords_jazz.xml
:Platform information
OS: Windows 10 Version 2009, Arch.: x86_64, MuseScore version (64-bit): 4.0.1-230121751, revision: github-musescore-musescore-9b70a8c
Additional context I suspect this is a problem with
chords_std.xml
, sincechords_std.xml
works just fine, but I can't work out where the file sets the size of the chord modifiers.