Lyrics style doesn't take

• Dec 22, 2013 - 04:56

I had to plug two verses into a song and reset the style via text properties so that the lyrics were 12 point italicized (they're in Latin). Then I went back to try to put in the English lyrics. But it seems that, even though I've reset the style via the menus and saved and closed and reopened the file, when I go back to enter the English lyrics, they're set at 9.69 points. And when I changed one syllable to 12 point and advanced to the next syllable, it was back to 9.69 points even though the style is supposedly set to 12 points. I really don't want to be hacking individual syllables. I noticed a forum entry on this from about four years ago; however, even then there was no answer to the situation. Is there a way to change properties for selected lyrics without changing properties for all lyrics? This would be ever so handy, especially for situations, such as mine, where you have lyrics in more than one language. Thanks, all.


What's your overall scaling set to (Layout / Page Settings / Space)? Font sizes are generally scaled according to that. So if you've reduced the space to around 1.5mm from its default of 1.764 (?) , that would have the result you describe.

Otherwise, it would help if you posted your score in order for us to see what might be going on.

I have a piece in four voices, the text is the same for all (SATB).
I put the lyrics between SA and TB;
Then I put the alternatives lyrics in a different voice, eg, T;
Select them: More> same staff;
Right-click> Text Properties> size, eg 14, OK;
Right-click> Text Properties> Ctrl + drag and arrange them in their place.
I did not understand if that is what you are looking for...but it can be a cue

Attachment Size
Size.png 18.58 KB

In reply to by km2002

It would be preferable, I think, set the size of the text before inserting the lyrics (lytics odd / even lines).
In your case I tried to insert the lyrics (second line) on the second voice;
Thus it is possible to select them separately, and subsequently change the size independently.
On what is already done:
Hold down Ctrl;
With the mouse, click on the individual syllables that you want to change (become all blue);
Right-click> properties Text> Increase text size.

Attachment Size
12.png 108.65 KB
PBEH O Saving Victim B.mscz 4.43 KB

In reply to by Shoichi

I knew I could select each syllable singly and change them all at once. I was trying to avoid that. This is a pretty short piece of music; can you imagine the hassle if I had to do that over a nine-page piece!?

In reply to by km2002

I think best way to handle this would be to alternate the language so you can take advantage of the odd/even lyric styles.

There are many requests and ideas for a more flexible selection facility. For this particular case, an easy possibility would be to add a "same verse" checkbox to the Select / More dialog from the right click menu.

In reply to by km2002

Yes, it's your Space setting that is the issue here. That isn't the overall MuseScore default; it's only used for certain templates. Or if you previously changed the default in Edit / Preferences / Score. If you like your music that small, you can leave that setting that way, but do realize that *is* pretty small and many would find it hard to read, so if you didn't do this deliberately, you might consider upping it.

Anyhow, as I mentioned previously, MuseScore automatically scales fonts according to this setting. So if you want your font to end up at 12 points while keeping your music as small as it is, you should set the font in the text style to 15 points, and then when it is scaled down it will come out around 12 points.

In reply to by Marc Sabatella

This piece started out using the Lead Sheet template; whatever is its default is this piece's default. WYSIWIG, as they used to say. So what scale setting makes everything come out at 100% of value so I don't have to play mathematical games? And perhaps more to the point, why isn't the scale set in percentages so I don't have to make these guesses? Besides, I noticed that this also defaulted to tabloid paper, which was a setting I used for a completely alien item I created (a template for a jazz ensemble score, which needs the larger paper). So things will get wacky when I knock it down to letter size (I'm going to have to adjust the measures per system and other stuff). So a lot of changes will happen to this particular piece; but first things first, and perhaps I should go over to the suggestions forum: Why not set scaling in percentage points rather than make composers guess as to what mm or in value gets you 12 points = 12 points and not 15 points sort of = 12 points?

In reply to by km2002

A display of what the scaling percentage for any given Space setting would be is a good idea, but the basic setting itself cannot be a percentage - that's a meaningless number unless you know what that percentage is applied to. In other words, saying "80%" wouldn't tell you how big your score was - only that it was 80% as big as some unspecified default. The setting is in actual measurement - how big is the space between staff lines, in millimeters. The default, as I mentioned above, is 1.764 - that's what makes font sizes come out literally. But normally, one wouldn't really have reason to care what the exact font size would be - you'd set it to whatever ends up *looking* right. You'd eyeball something that looks good relatively to the current score size, and then if you later change the score size, the text would scale with it. It's pretty unusual to have a preconceived notion that you want exactly 12 point font regardless of how big your music is.

BTW, tabloid is *not* the default for the lead sheet template - you must have modified that inadvertently. The default is Letter. But since your score is not in fact a lead sheet, it probably wasn't a good choice to have started with.

In reply to by Marc Sabatella

I'll take your word that the original default is not tabloid. However, it is what it is on my computer. And every template on my computer shows a last modified of 1/30/2013 10:33 AM; so I haven't overwritten the last batch of templates I got from the source. (IIRC, these would all have come from my original 1.3 install; even my executable is dated 2/27/2013.) Therefore, I have no idea where it's picking up tabloid as a default page size. As I think I mentioned, the only template I know to have been created in tabloid was one I created for jazz ensemble scores.

And my score is a lead sheet with a bass staff added via the Lead Sheet > Add Staff plugin. As has been mentioned in other posts throughout this site (and I think I'm in on one of those from a few months ago), to date MuseScore has no native two-staff SATB (or, if you prefer, SA/TB) template, and from the looks of things, few ways to create such a staff that are not awkward. So that's how we get to this score.

In reply to by km2002

So you got me curious, and I think I know what's up with the page size. I was wrong when I said the lead sheet template sets the page size to Letter. In fact, it doesn't set the page size at all. Meaning, it simply inherits the default page size you have in Edit / Preferences / Score. I've set mine to be Letter, apparently you've set yours to be Tabloid.

Not sure what you mean about it being awkward to create your own two-staff SATB score. It's actually quite simple - create from scratch, add two instruments, both voice (or whatever instrument you like, really) then delete the instrument names. Or, for that matter, use the provided Chord SATB template then remove the two unused staves. Or just create a score for Piano as your instrument. There are actually lots of easy ways of getting a two-staff score for SATB writing.

Anyhow, the deal with the Lead Sheet template is that is is specifically designed to recreate the look of the fakebooks that try to cram 1000 tunes into 400 pages or whatever. So it goes with an extremely small print size. That's why I think of it as being appropriate for virtually any other use. By contrast, the Jazz Lead Sheet template goes more for the look of the Real Book or New Book - somewhat bigger than average notation, significantly bigger than average chord symbols.

In reply to by Marc Sabatella

OK, I can see where the inheritance comes, especially since I haven't played with Edit > Preferences > Score since I created my jazz ensemble template. What I and, if I interpret correctly, at least one other poster sought was a template that was set up for trebles and basses where Voice 1 would insert soprano and tenor voices and Voice 2 alto and bass. I found a forum response where there was a mechanism to take the four-part choir SATB template, which as you noted uses four separate staves (you did mean "Choir SATB" when you wrote "Chord SATB," right?), and slam-dance the alto voice into the soprano and the bass voice into the tenor. But that was time consuming in the extreme: Just try scoring the entire Glory to God in four lines and slam-dance them into two. And if I just use two lines, then my alto and bass lines render in protest of going outside the vocal range to notate those parts on the soprano and tenor lines. My preference is to have the lines labeled; you can't do that bit of marginalia without using the part properties to get the instrument names (unless there's something I don't know, which I'll admit is a distinct possibility since I'm not familiar with each and every in and out of MS). And when I edited the part properties to create the double labels (soprano over alto on the treble; tenor over bass on the bass), the parts converted to soprano and tenor and that's when I saw red (in more ways than one). But that's a whole nother score that includes an organ part.

Oh, and I'll admit that historically the tenor part is notated in treble clef. As a tenor I can read that notation. But I prefer the notation in its native range, in the bass clef; and the vast majority of tenor material I've read over the last 15 years has been notated in the bass clef.

As to the build that blew up on me, had to be more than a year ago; however, IIRC, I was under a time crunch and didn't have time to locate a semi-stable build. I just cut my losses and moved on; and then 1.3 came out earlier this year.

In reply to by km2002

The SATB template won't mark notes as being outside their range, as no range is set for any of its staves.
I did post a closed score SA/TB template a while ago, that does this and does take into account the upper range of soprano resp. tenor and the lower range of alto resp. bass.

In reply to by km2002

I am still confused. Changing Changing staff names is trivial - right click, staff properties, change name. Not sure what you were doing wrong, but changing names affects nothing about range checking or anything else. Also, I have no idea why you are talking about starting from a four staff score and then "slam-dancing" them into two. Why not just create the two staff score in the first place? Now, it *is* true that MuseScore does not provide a way to get independent range-checking of voices. So you'd have to define the range for the top staff to be the union of the alto and soprano (which is also dead simple to do), but that means you wouldn't get complaints about soprano too low or alto too high - only soprano too high or alto too low. But then, starting from the lead sheet template doesn't solve any of these problems - all it does is make your music an inappropriately small size and force you to add the second staff manually.

It could be worth a separate thread explaining in more detail what you are trying to do. Mostly likely you are missing something and there is a very simple way to get it. And once you've set it up once, save that as a template for yourself and you can use it over and over - no need to wait for MuseScore to provide the template for you.

I've been waiting for 2.0; I hope it won't be much longer. I tried running one of the nightly builds; but the whole experience left me running 1.3, deleting the build, and waiting for 2.0 to be released. So many problems on my computer, I never went back to a nightly again.

In reply to by km2002

How long ago was that? The builds were not very usable until maybe within the last year, and they continue to go through temporary bouts of major instability (like recently when they changed the whole music font mapping, but they should actually be reasonably solid overall these days. Bugs to be sure, and I wouldn't recommend them for real work. But they should look more promising than discouraging by now. Anyhow, people are all trying to fix problems as quickly as they can, but it's very important to actually report the problems you see, because it's entirely possible they are problems others haven't run into and thus they can't be fixed until someone reports them

Do you still have an unanswered question? Please log in first to post your question.