Missing font or what - Text (TempoText) & Fingering (StringNumber) Palette
Drag'n'drop TempoText gives missing note in text. Also, d'n'd (Guitar) String number from FingeringPalette gives only number, without that cute little circle which should surround D number like mother's womb surrounds the fetus. Ok, g0ne bit of track... :)
Viva 'l MuseScore! (Of course this is mainly valid for its creators...)
| Attachment | Size |
|---|---|
| [Chi] MScore 2 Bug Report 003 - Tempo Text missing note.pdf | 332.13 KB |
Comments
I can't reproduce. Can you try to delete your palette file?
Close MuseScore, delete C:\Users\YOURUSERNAME\AppData\Local\MuseScore\MuseScoreNightly and restart MuseScore, try again to add a tempo and a fingering.
In reply to I can't reproduce. Can you by [DELETED] 5
... above folder (it is actually MuseScoreDevelopment), run MScoreNightly, no difference. That is, deleting folder does not resolve issue. Am I missing some font perhaps?
Best regards,
Simon
In reply to Deleted... by aum7
For the quarter note, the font is included in MuseScore and you see the quarter note in the palette don't you?
In reply to For the quarter note, the by [DELETED] 5
... see notes in Palette and on 'paper' (staff) too.
I have opened file 'written' in MScore 1.3, which has chord names above bars. While there (MS 1.3) flat sign is visible, in MS 2 it is replaced with 'blank-o-square'.
So, complete musical symbology is unavailable in text etc. See attached file.
Best regards,
Simon
In reply to Yes, I do... by aum7
It's always helpful to include the actual score, not just a picture of it. But from the picture, it appeara you might have tried inserting the actual flat sign into your chord symbols rather than using "b" which is automatically turned into a flat sign if the chord symbol is recognized (and for 2.0, virtually everything will be recognized). Trying to use the actual lat sign causes MuseScore *not* to recognize the chord, so it's counterproductive. While it probably still should have worked, I think you'll find things work if you create your chord symbols correctly.
The reason it may nit have here is that MuseScore previously used a non-standard location for the flat sign. It was changed for 2.0 to the standard Unicode location, and at least in some cases thus is fixed up for you automatically. Like flat signs in ordinary text. But flat signs in chord aymbols - whch should never happen, because you are supposed to type "b" - are not automatically fixed up.
Anyhow, again, without seeing your actual score, this is all just guessing, but if it's only chord symbols that are giving you problems, then that would probably be why.
Oh, another possibility - perhaps you downloaded an old version of the Mscore font at some point and tried installing it yourself? You're not really supposed to install these fonts yourself - they are hardcoded into MuseScore. But if you had an old version installed, that could also explain this.
In reply to It's always helpful to by Marc Sabatella
Attached is some updated 'playing' with MScore 2, I have tried changing the font used for ChordNames, no success. Same issue, no flat or sharp character in actual Chord Names in staff.
Also found weird behaviour if I drag StringNumber from Palette. Please see attached file.
Attached is also MScore file where this happens. Written in MScore 1.3, saved as file with different name, then opened in MScore 2.
Cheers,
Simon
In reply to OK, here it is... by aum7
OK, then I'm back to my guess at the bottom of my previous post: do you perhaps have an old version of MScore or MScore1 isntalled on your system? You shouldn't have *any* version of those fonts.
In reply to OK, then I'm back to my guess by Marc Sabatella
... I do have MScore 1.3 installed and using it. I am addicted (LOL!), you can NOT make me un-install it! LOL! Days go by much faster with this B'n'B (beauty and the beast). It helps me learn MUCH faster than anything I tried so far (I am self-learner, primarily of guitar), and with added GuitarTABLATURES (Huraiii!) and PlayPanel Loop function (Double Huraiii!) I see my future of guitar player REALLY BRIGHT IN FRONT OF ME! LOL!
Must admit you guys fascinate me with all your efforts and time spending for free, to make this program (which is brilliant, intuitive, easy to use, also looks VERY nice, very helpful) ever and ever better! Bow!
You do not really expect me to uninstall MScore 1.3? Not an option. It would break my heart.
Beside, MScore 2 is actually not installed at all, it runs in (do not know how to properly say that) stand-alone mode?
Best regards,
Simon
S love nia
In reply to Of course... by aum7
Marc talks about the font MScore or MScore1, not any Version of MuseScore.
In reply to OK, then I'm back to my guess by Marc Sabatella
Right. To be clear: MuseScore is the program, MScore is one of the fonts it uses, MScore1 is another font it uses. MuseScore - both version 1.,3 and 2.0 - comes with both of these fonts compiler into the program. You are *not* supposed to install the fonts yourself, and in fact, it is (deliberately, I assume) rather difficult to get at them in order to install them anyhow. So you wouldn't have installed those fonts and not remembered. But if you *did* install those fonts, that would probably explain your problem. MuseScore 2.0 would be using the (old) installed version instead of the (new) version complied into the program, and that won't work.
In reply to Right. To be clear: by Marc Sabatella
... got it. Thank you! No MuseScore uninstallation. There is a God! LOL!
Actually I use MScore as a name for MuseScore software.
Now, I did not installed any MScore fonts, neither do I have them installed in my Font folder.
But I did used Cambria font (well, I like it, and I do not like TimesNewRoman), and did tried switching back to TimesNewRoman font, but no avail.
Don't know, I have no more ideas what would cause the issue.
In reply to Right. To be clear: by Marc Sabatella
Do I have to do anything particular to 'uninstall' older versions of NightBuilds, like using
cleanup-nightlybuild.bat?
One more thing - I have MuseScoreNightly .exe file (and complete folder, that is) on external disk. Could that be a problem for fonts?
In reply to It's always helpful to by Marc Sabatella
Attached is file with some tweaking around Harmony Properties. I will not attach original .mszc file since it is attached already in previous post.
Now, I did tried to make new ChordName (since original file is from MScore 1.3 version) - select ChordName - hit Delete - select first note in bar - click Insert - Text - Chord Name, then Edit Mode - enter (press key) 'A' - hit ESC (exit Edit Mode) - right-click ChordName - select Harmony Properties - select '...(Flat)' & 'Maj7'; result is the same. No 'flat' character, just square.
Quote:
"but if it's only chord symbols that are giving you problems" - nope, StringNumbers are missing circle too.
May the Code be with you (and consequently with all MScore 2 users),
Simon
In reply to Issue update by aum7
Problem with chords seems to be simply that the font you selected doesn't support the Unicode flat symbol. Also you are using the old 1.3 chord name style files. Scores created from scratch using the defaults should work fine. But that doesn't explain the other issues.
In reply to Problem with chords seems to by Marc Sabatella
... I have made, Master Marc. And indeed sharps or flats now do appear. But... there are other issues now. Extensions are not working - at all.
I have deleted MuseScoreDevelopment folder from my OS.
But if problem is 'old' MScore v1.3 style file, then whatever MScore 1.3 file I will open in MScore 2, it will have corrupt ChordNames? This basically means that v1.3 and 2 are not compatible?
And, yes, Fingering drag-dropped from Palette now also works fine.
Update on-the-fly:
Extensions are missing because Style - ChordNames - list is empty. When I try to Load some style, program CRASHes.
Perhaps Tablatures staff needs thorough revision? Not sure...
In reply to Score from scratch... by aum7
First: there have been major changes to how chord symbols work going from 1.3 to 2.0. But it should and does work to load a 1.3 score into 2.0 as long as the score was created correctly, with no hard coded flat signs (which cause the chord to be unrecognized). Shouldn't matter if 1.3 is still installed or not. Not sure how your score got into the state it was, but that shouldn't happen normally. I'll look into it, since I did most of the new chord symbol stuff.
Style / Chordname is not for sure going to be in the final release - it's no longer really needed with the other changes, although it would be kind of cool if it worked. Not sure where or how you tried to load a style or what type of style you tried to load, but you should not have had reason to do that. If a score is empty, then Style / Chordnames is supposed to empty. It will only display the chords actually being used. But there issues with the font sizing. You really shouldn't need it; it's just a way of tweaking the visual appearance of chords (superscripting etc) that is better done through other means.
The Harmony Properties dialog is also very obsolete now (was already fairly obsolete in 1.X; it's more so now) and may or may not be preserved.
Entering chord symbols should now be as simple as Ctrl+K then type away. There are some interesting options in Style / General / Chordname that some users might be interested in (German root naming, etc) but most people will probably never have a need to change anything form the default. At most, selecting between Standard and Jazz styles (the Jazz style forces uses of MuseJazz font and applies some special formatting) or choosing the height above staff in Style / General / Chordname, or changing the overall font properties in Style / Text / Chordname.
In reply to Score from scratch... by aum7
Looking at your score 101_Jazz_Guitar_Licks_Night_2.mscz, I think I might see the problem although I don't know what caused it. For some reason, your score is hard coded - with a full explicit pathname - to load the old 1.3 version of the chord description file stdchords.xml. Normally a score would just contain a relative link to the chord description file if it's one of the standard ones like that. So when loading a 1.3 score into 2.0, it would normally load with 2.0 version of the chord description file, which would contain the correct location for the flat sign, and you'd be good to go.
So it's the fact that your score is explicitly forcing MuseScore to use the 1.3 version of stdchords.xml rather than its own version of stdchords.xml that is the problem here.
What I don't know is how that happened. Can you trace how this file got created? Score created from scratch in 1.3, saved, opened in 2.0, saved again, but maybe something else besides? Because when I try that, I get the relative link as I expect.
Maybe this does have something to do with your 2.0 installation being on an external drive?
In reply to Looking at your score by Marc Sabatella
... please let me know where should I put MuseScoreNightly folder (extracted from downloaded file)?
Currently it is on partition (E:) of main HD, and this partition does NOT contain OS, just my files that I work on.
Should I put it on partition which contains OS (C:)? Under ProgramFiles (x86)? Though I think it does not matter really?
I enter chord names like:
click-select a note, hit Ctrl-K, enter ex. 'cb6/9', press Esc.
I get 'Cb6' (C-flat_character-6; flat sign is generated); 6/9 is not recognized, since ChordNames list is empty (see above attached file). If I try to Load styles (from the same downloaded folder, under sub-folder Styles), I get CRASH.
I also tried copying chord styles files (cchords_muse.xml & co.) from above original downloaded folder (on partition E:) to C:\Users\Chi\Documents\MuseScoreDevelopment\Styles. Then tried to load ChordNames (stdchords.xml), still get CRASH when I hit OK.
Thumbs Up!
Simon
In reply to First... by aum7
I'm just guessing about the installation issue. I have no abolsultey no diea how you ended up with a hardcoded pathname in your score. As I said, that's not normal. Perhaps you could explain how you created that score and see if it's reprodducible? Because as I said, if you simply create a regular score in 1.3, put regular chords in it, then open it in 2.0, it does work. So you must have done something more than that.
6/9 with the slash is indeed not recognized because the parsers sees the slash and thinks it's a slash chord. So you need to enter 69. If using the Jazz style, this will automatically be rendered nicely.
As for loading styles, that facility is not for chord description files. It is for style files you create via the corresponding save style command. Trying to load a chord description file shouldn't crash, but it sholdn't do anything in particular, either. Perhaps if you expalined what you are actually trying to do? Chord description files are specified using Style / General Chordname, just as in 1.3. Don't use Load Style.
In reply to I'm just guessing about the by Marc Sabatella
... and tried to reproduce the bug, but no avail. That is, this time (create file from scratch, save as, open in MScore 2) it worked as it should.
I will try copy-paste score from previous file. If I do not raise an alert, this matter is FIXED.
No need to check on attachment, except if your lattest issue of MuseScore Times (or Financial Times) is late. LOL!
Thumbs up!
Simon
S love nia
In reply to I'm just guessing about the by Marc Sabatella
Quote:
"So you must have done something more than that."
Reply:
Actually it crossed my mind...
"I have sinned, father!"
"What have you done, my son?"
"Well, it seems I have applied Style from MScore 1.3 to MScore 2.0 via Style - Load Style, and caused nothing but a trouble to fair people."
"Learn two more Jazz Guitar licks today and you will be forgiven."
"Thank you, thank you, father!" (crying)
LOL!
Mea culpa! Will not repeat!
Best regards,
Simon
In reply to I have sinned, father! by aum7
OK, that probably explains what happens. Still, it would be nice if we were able to reproduce this so we can see about the possibility of fixing it. Can you reproduce this, and if so, give specific step by instructions on how to do so?
In reply to OK, that probably explains by Marc Sabatella
... I created 'custom' Style in MS 1.3, that is, I have changed ALL text font to Cambria, and saved style as 'Chi Cambria [style 1.3].mss', then opened MS 2, some .mscz file, and applied that style to this file in MS 2.
I can not recreate the issue.
Attached are MScore 1.3 style files and pdf report.
Thumbs up,
Have fun,
Simon
S love nia
In reply to Basically... by aum7
It's now not possible anymore to apply a 1.3 style in the current development version. See #22451: MuseScore should make it impossible to load styles made in previous version
In reply to I can't reproduce. Can you by [DELETED] 5
... previous scores (Part I), everything works normally, Fingering, StringNumbers, everything works as expected.
I must learn 2 more licks now. LOL.
FIXED!
:)