Style → General... → Measure

• Jan 26, 2016 - 21:58

The handbook's entry "Style → General... → Measure" is most unhelpful with its grand total of three sentences: "Sets measure spacing as well as margins. The measure spacing and minimum measure width are keys to controlling the number of measures per line. Changing the other settings would be unusual." Well, I guess I'm "unusual" since with nearly every score I write I find myself wanting not merely to change the measure style but also to increase distance between notes and barlines, among other settings. But without thorough documentation it's a constant battle of hit-or-miss.

So I have a proposal for the developers. If you will please give me a list of exactly what each Measure option does, I will turn it into usable, clear (English) prose that you can paste into the handbook for its next revision. I have a degree in technical writing; the result will be professional and require no further editing from you.


Comments

Hi Ironword,

I don't have a degree in technical writing, but I have a fair amount of experience with it. At the risk of being immodest, I think it's safe to say I've made a good many pages of the Handbook better, and a few wouldn't exist at all if not for me. (I also did a very small amount of rewriting on Marc Sabatella's "Mastering MuseScore", and I wrote the "Getting Started" one-page interactive tutorial.)

The entire "Layout and Formatting" documentation page is a terrifying beast that nobody has quite got up the courage to overhaul (see some discussion at https://musescore.org/en/node/64106). Ultimately, it's got to be done, and your help would be appreciated.

As to the specific question of the measure style settings, I think the only thing less than self-explanatory is the "sp" unit (which is documented at https://musescore.org/en/handbook/page-settings, mostly written by me). A "Minimum measure width" of 5sp means that a measure cannot be less than five staff spaces wide, and so on. Still, a bulleted list spelling this out for each parameter would be a good thing to have.

The exciting news is, you don't need to give the text to the developers for them to add to the Handbook, any more than you need to with Wikipedia. Anybody can edit any page, any time, and a new PDF version is automatically generated daily. So jump write in! (Ouch.) ;-)

In reply to by Isaac Weiss

> I don't have a degree in technical writing,
> but I have a fair amount of experience with it

I wasn't trying to boast--it was an attempt to wheedle you into coughing up the kind of information that (unhappily) my post did not, in the end, elicit. I knew it would take extra work for you to write it all down, so I wanted to dangle a carrot...in vain, as it turned out. OK, fine. I'm trying to finish up a Ph.D. and really didn't have time to do this, but bit the bullet anyway, sat down and did some systematic experimenting. This is what I've come up with. Please tell me what's wrong:

=======================
Many Musescore users find it helpful to make measures longer for ease of reading. Others merely want a bit more distance between bar lines at the beginning and ends of measures. Whatever your pleasure, Style > General > Measure permits you to adjust the distance between a number of relevant items. Before beginning, however, you need to know about the unit of measure Musescore uses in this dialog: the staff space, abbreviated sp. Without understanding the sp, you can't estimate the number of units necessary to create the distances you want. For a full description of the sp see Formatting > Page Settings (subsection "Staff space/scaling"), but in brief, this unit of measurement is determined by the small, vertical distance from one individual line in a staff to another. So in order to decide how many sps to specify for a particular change, take a good look that small vertical space and flip it over horizontally in your mind. You can then use that mental image of the horizontal sp to estimate how many of them your change will require.

Options

Minimum measure width:
sets the horizontal length of measures. With the exception of the distance between the beginning of the measure and the first note or rest, which is controlled by Barline to note distance or Clef/key right margin (below), Musescore will automatically re-space rests and notes evenly within the specified length. Anchored elements retain their localized anchor points and are respaced accordingly (in other words, fingerings, string numbers, lines, and so forth which are anchored to notes or rests will be moved along with those notes or rests). NOTE: there is little reason to use both this setting and the next, Spacing (1=tight), simultaneously. You can achieve similar results with either one. Using both is usually unnecessary.
Spacing (1=tight):
despite its general-sounding name, this option does not put space between absolutely everything in a measure. Rather, it controls the space after notes or rests (and thus has no effect on the space between the beginning of the measure and the first note or rest). As with Minimum measure width, anchored elements move along with their notes or rests.
Barline to note distance:
sets the distance between the bar line which begins a measure and the first note or rest in that measure. As the name indicates, works only for bar lines; does not work in measures at beginnings of lines, which do not have bar lines but instead clef signs and other front matter. To set the distance between such front matter and the first note or rest in a line's first measure, use Clef/key right margin (below).
Barline to grace note distance and Barline to accidental note distance:
these options set the distance between a bar line and the special anchored elements of grace notes and accidentals. Anchored elements are ignored by Barline to note distance (above), so if you wish grace notes or accidentals to be as far away from the bar line as regular notes, you must use these settings separately to specify that same distance.
Minimum note distance:
THIS CAN'T BE RIGHT, BUT I DON'T SEE ANY DIFFERENCE IN BEHAVIOR... Does the same thing as Spacing (above): sets the distance that comes after each note or rest. In other words, behaves exactly like Spacing in all ways.
Clef left margin:
sets the distance between the very beginning of each line and the clef sign, starting at the clef sign and spacing backward. (There is little reason to use this option.)
Key signature left margin:
sets the distance between the key signature and the clef sign. Begins at the key signature and spaces backward.
Time signature left margin:
sets the distance between the time signature and the front matter preceding it (normally the key signature, but if there is none, then the clef sign). Begins at the time signature and spaces backward.
Clef/key right margin:
sets the distance between the material at the beginning of each line (front matter such as the clef and key signature) and the first note or rest of the first measure, starting at the last symbol of the front matter and spacing forward. (Note: this option's name omits the time signature and thus implies that the time signature is ignored when computing distance. That is a misleading implication. If a time signature is present, it is the element from which the spacing begins.)
Clef to barline distance:
NO IDEA. I TRIED VARIOUS NUMBERS AND GOT NO REACTION WHATSOEVER.
Multimeasure rest margin:
NO IDEA. I SET UP A SECTION IN 4/4 WITH A LONGA REST, WHICH GAVE ME 4 WHOLE RESTS, THEN TRIED VARIOUS NUMBERS AND GOT NO REACTION WHATSOEVER.
Staff line thickness:
makes the lines on the staff thicker (and thus darker, if you need greater visibility on your printouts).

In reply to by Ironword

I don't have a lot of time to review it, but nice work! I notice there has been a bit of a misunderstanding regarding the "minimum measure width" setting, though (which shows the need for better documentation). Here's my suggested revision of the first few points:

================

Note: All settings related to measure width and note spacing are minimum values. Measures are automatically stretched, if necessary, to justify both margins.

Minimum measure width sets the minimum horizontal length of measures. In measures containing very little content (e.g., a single whole note or whole measure rest), the measure will only shrink as far as this minimum.
Spacing (1=tight) condenses or expands the space after notes or rests. For the space between the beginning of the measure and the first note or rest, see Barline to note distance (below).
Barline to note distance sets the distance between the barline which begins a measure and the first note or rest in that measure. For measures at beginnings of lines, which start with clefs instead of barlines, use Clef/key right margin (below).

In reply to by Ironword

I wouldn't say the word "spacing" is misleading. The space between margins and the music are like "margins", and I wouldn't expect or want them to be governed by the same rules. So I'd remove that statement. What is worth mentioning is that this forms the basis for what the "stretch" commands apply to.

Also, it is totally separate from minimum measure width - they actually have no bearing on each other. There could be every reason to want to modify these independently. So I'd remove those statements as well.

Minimimum note distance is definitely difference from spacing. Minimum note distance sets the minimum distance, and has only a minimal effect on notes that are not close to that minimum. Spacing affects everything equally.

Clef to barline distance - I would have assumed this should affect what it says it does: the distance form a clef (at the end of a measure) to the barline. But indee,d it doesn't seem to. If someone else can confirm it doesn't do something else, this is worth filing as a bug.

In reply to by Marc Sabatella

Thanks Marc, great help. Am incorporating everything, although I have a reservation about the following:

> I wouldn't say the word "spacing" is misleading. The space between
> margins and the music are like "margins", and I wouldn't expect
> or want them to be governed by the same rules. So I'd remove that
> statement.

Upon reflection I realize that you are correct to point out the name "Spacing" is not misleading. However, there's still a problem here. It's not with your "margin" analogy; I agree with it wholeheartedly. However, by that standard, Spacing should treat both margins the same, not just at the measure's beginning but also at its end. In other words, precisely because of the "margin" criterion, Spacing should ignore not only the beginning of the measure but also the end of the measure. However, that's not what happens. When Spacing applies its setting after all notes or rests no matter what, it essentially creates an end margin (after the last note) even though it certainly does not create a beginning margin. Any new user thinking in terms of your "margin" perspective--as indeed they should--will therefore encounter unexpected behavior.

But your right; the problem is not the setting's name but rather its behavior. So I'll keep a note about the behavior but revise it vis-a-vis expectations concerning margins as well as removing blame from the innocent moniker. And the related tip about the stretch commands is definitely a bonus.

In reply to by Ironword

True, it's a little more complicated than I said. Spacing affects the amount of space to the right of a note, including the last note of a measure. But still, the "margin" is separate.

In any case, the behavior is exactly as one would naturally assume and hope: a note of a given value gets a similar amount of space to the right regardless of where it is in the measure, but there is extra space at the end of the measure before the barline as given by that parameter. Any behavior other than this would be counter to how people would expect music to be laid out.

> Any behavior other than this would be counter to how
> people would expect music to be laid out.

You know, through all these years I'd never noticed that before. I had to actually look at some music with an eye specifically toward this issue. But lo and behold, the first note is indeed closer to the beginning barline than the last note is to the end, if other considerations (such as a bunch of 32nd notes) don't trump the requirement. In my head I had always assumed that the beginning and end "margins" would be exactly the same, without ever taking the time to ascertain what was actually going on. Nonetheless, I doubt I'm alone. Entering music into Musescore is a much different ball-game than writing out a sheet with a pencil, and it cannot hurt to make everything as clear as possible. After all, if this were already crystalline, I wouldn't need to write it up.

Anyhow, since nobody else has piped up, I'm assuming all the preliminary votes are in. Here's the new tally, heavily revised. The commentary may strike some folks as too basic, but in my experience scarcity of information is almost always a much greater problem than its overabundance. When you don't have a page limit, it's always best to err on the side of more (as long as it's not needlessly verbose). Thus...

========================

Many Musescore users find it helpful to make measures longer for ease of reading. Others merely want a bit more distance between bar lines at the beginning and ends of measures. Whatever your pleasure, Style > General > Measure helpfully allows you to adjust the distance between a number of relevant items. Before beginning, however, you need to know about two things: 1) Musescore's general spacing behavior, and 2) the unit of measure Musescore uses in this dialog:

  1. As you shrink or expand distances between notes and rests, Musescore will always attempt to keep the elements within each measure relatively spaced according to best engraving practice. The spacing commands you enter will always be secondary to this goal. In other words, you may specify a certain amount of space between notes, but Musescore will not apply your change in such a way as to make all notes perfectly equidistant. Such a result would conflict with convention. Per standard practice, Musescore will continue to allot less space to the right of shorter notes than longer notes. In addition, when you make changes, anchored elements retain their localized anchor points and are respaced accordingly so you need not worry about readjusting them separately (in other words, fingerings, string numbers, lines, and so forth which are anchored to notes or rests will be moved along with those notes or rests).
  2. The unit of measurement Musescore uses to work with musical measures is the staff space, abbreviated sp. Without understanding the sp, you can't estimate the number of units necessary to create the distances you want. For a full description of the sp see Formatting > Page Settings > Staff space/scaling , but in brief, this unit of measurement is determined by the small, vertical distance from one individual line in a staff to another. So in order to decide how many sps to specify for a particular change in a measure, you'll need to take a good look that small vertical space and flip it over horizontally in your mind. You can then use that mental image of the horizontal sp to estimate how many of them your change will require.

Options

Minimum measure width:
Sets the minimum horizontal length of measures. In measures containing very little content (e.g., a single whole note or whole measure rest), the measure will only shrink as far as this minimum.
Spacing (1=tight):
Condenses or expands the space after notes or rests. This setting thus affects not only space between notes but also between the last note and the ending barline. For the space between the beginning of the measure and the first note or rest, see Barline to note distance (below). Note: Spacing is the basis for the Stretch commands, which you can also use to adjust measure size and the amount of space between notes.
Barline to note distance:
Sets the distance between the barline which begins a measure and the first note or rest in that measure. For measures at beginnings of lines, which start with clefs instead of barlines, use Clef/key right margin (below).
Barline to grace note distance and Barline to accidental note distance:
These options set the distance between a bar line and the special anchored elements of grace notes and accidentals. Anchored elements are ignored by Barline to note distance (above), so if you wish grace notes or accidentals to be as far away from the bar line as regular notes, you must use these settings separately to specify that same distance.
Minimum note distance:
Specifies the smallest amount of space Musescore will allow after each note (but depending on other factors, more space will be allowed).
Clef left margin:
Sets the distance between the very beginning of each line and the clef sign, starting at the clef sign and spacing backward. (There is little reason to use this option.)
Key signature left margin:
Sets the distance between the key signature and the clef sign. Begins at the key signature and spaces backward.
Time signature left margin:
Sets the distance between the time signature and the front matter preceding it (normally the key signature, but if there is none, then the clef sign). Begins at the time signature and spaces backward.
Clef/key right margin:
Sets the distance between the material at the beginning of each line (front matter such as the clef and key signature) and the first note or rest of the first measure, starting at the last symbol of the front matter and spacing forward. (Note: this option's name omits the time signature and thus implies that the time signature is ignored when computing distance. That is a misleading implication. If a time signature is present, it is the element from which the spacing begins.)
Clef to barline distance:
CURRENTLY NOT WORKING.
Multimeasure rest margin:
This sets the distance between a multimeasure rest and the bar lines on either side.
Staff line thickness:
Makes the lines on the staff thicker (and thus darker, if you need greater visibility on your printouts).

NOTE CONCERNING THE FIRST TWO OPTIONS ABOVE, Minimum measure width AND Spacing (1=tight): These are the workhorse settings of the Measure dialog, the ones you'll almost always use. But some scores are simple, featuring few notes of differing duration (lead sheets or fake books, for example, often have quarter and eighth notes with nothing else). In such cases there is little reason to alter both of these settings simultaneously because Musescore's general spacing behavior means that you can achieve similar results with either of them. However, if your score is more complex, with halves, quarters, eighths, sixteenths well intermixed, then you'll need to decide on a balance between these options. As you do so, it is easy to ignore the "minimum" part of Minimum measure width and simply regard it as a setting that keeps all measures the same size. Avoid this mistake by always remembering the name's qualifier: the width is not absolute but rather a minimum. Minimum measure width, in other words, will always be subject to Musescore's basic spacing behavior as well as the requirement imposed by Spacing (1=tight). If you have more notes than will fit in the minimum width you've specified, or if Spacing (1=tight) is set high, Musescore will be forced to go beyond--perhaps well beyond--your Minimum measure width. An example will show how forgetting this can trip you up. Let's say you want to keep all your measures more or less the same size. If the first part of your score has only quarter notes and a few eighths, you may be tempted to set Spacing (1=tight) to, say, 2, which (depending on accidentals) will give you three to five measures per line if all other settings are left at default. Then you make the mistake of assuming that Minimum measure width will condense notes as necessary to keep measures the same size, trumping your setting for Spacing (1=tight). Thus in order to maintain uniformity no matter what happens, you set Minimum measure width to 20. That all works nicely for a page or so, but then you come in for a rude awakening. On the second page you have a sudden run of 16th notes filling a measure, and, oops, that measure turns out to span an entire line. It doesn't matter what you put into Minimum measure width because, again, that setting is a minimum, not a maximum. There is no maximum, which means that Musescore's general spacing behavior will always apply, as will the setting in Spacing (1=tight). The bottom line is this: if having notes a good distance apart is more important than having the measures be equally sized, then you'll want to increase Spacing (1=tight); if having the measures the same size is more important, then you'll wish to set Minimum measure width to your desired size and then reduce Spacing (1=tight) down to its minimum of 1 (Musescore won't allow you to go below that, as notes would soon run together). Within those two broad parameters, you'll most likely need to experiment until you find the settings that work best for the particular characteristics of the piece you're working on.

In reply to by Ironword

I have to say that seems very difficult to read through. In particular, most of the lead paragraphs and the last giant paragraph containing detailedadvice—rather than simple information—might have a place in a different part of the documentation (https://musescore.org/en/howto) as a "How to set measure width and spacing" page (linked to from the Handbook, of course), but I don't think it should go in the manual itself.

Or, this might be an opportunity to finally kickstart the Tutorials effort: https://musescore.org/en/tutorials

OK, I've waited nearly a week and the gamblin' man (You don't live "down in New Orleans", d'ya Zack? ;) has offered the only response, so I'm assuming all other parties concerned are fine with the text as is.

Yes, the introductory sentence is perhaps more appropriate for a tutorial than for a stripped-down, nothing-but-nuts-and-bolts manual; and the last paragraph does offer unabashed advice (of the kind I wished had been available when I first approached measures in Musescore). However, I strongly disagree with that characterization of the two beginning points (the list items). 1 & 2 offer information about how Musescore works, pure and simple; they don't tell users what to do with that information, and the handbook is definitely the place for it. Well, I guess the last two sentences in 2, about mentally readjusting sp horizontally, might be construed as "advice", but it's so fundamental to the usage of this dialog that IMHO it needs to stay. So I have now added everything to the handbook except the first sentence & last paragraph.

Re these final pieces of text: I am going to have to just leave it sitting here. If anyone else wishes to take up Zack's suggestion to put it elsewhere or use it as a tutorial springboard, please feel free. As I indicated above, I'm too busy at the moment to actually be doing stuff like this; it would be a very serious problem for me if I don't get my dissertation done. So I can't pursue this further. Others who can have my full blessing to alter the text in whatever manner they wish without feeling that I ought to be notified even for courtesy's sake.

In reply to by Ironword

I would like to assure all parties that my pasteboard-related activities are for entertainment purposes only, and no illegal or unethical activities are intended. ;-)

Thank you! One more suggestion: split that material off into its own Handbook page. The "Layout and formatting" page is just too big to handle. Scroll down to the bottom of the page and you'll find an "Add child page" link that will enable you to create a new page (call it something like "Style options: Measure"). Then edit the original page to cut and paste the content into the new one, leaving behind a link (like I did here: https://musescore.org/en/node/35896#layout-page-settings).

In reply to by Ironword

My take was the same as Zack's, so I didn't post. it seems overly long and tutorial-like than what I think is appropriate for the Handbook. And the length can be a detriment as well - people see long explanations and immediately check out rather than read. Short and to the point is best, I think. And yes, I know I am very often guilty of not following this advice :-)

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