Bigger staves and notes

• Oct 17, 2011 - 10:53
Type
Graphical (UI)
Severity
S4 - Minor
Status
closed
Project

I transcribe music for a partially sighted chorister and may start doing it for other choristers with different sight problems in a couple of months. The RNIB is developing a standard called Modified Stave Notation.

Being able to print lyrics etc in Arial 14pt is great and goes a very long way.

Can the MuseScore interface control the spacing (and even the thickness) of the stave lines? Some partially sighted people would also like bigger note heads and thicker note stems and beams. (This would imply bigger clefs, key signatures and time signatures, too, but that is not nearly so important, except for presentation.)

Thanks in anticipation,
John


Comments

Thanks Jo-jo Schmitz. . I'll use that. I was hoping that there would be more detailed controls, but I assume you would have told me if there had been.

Thanks
John

You can have a much more detailed control via Menu/Style/Edit General Style and .../Edit Text style, but that affects only newly created stuff and may still not cover everything you need.

What more detail do you need? The scaling factor affects everything equally bybdefault, but you're always welcome to change the sizes of any particular elements, either globally through the Style settings or individually through right click menus.

I had searched (as best I could) for changes to the styles that enlarge the staves vertically and thicken the lines, and even change note head and stem size, but some of the present ones are not obvious as to what they do. Worse, nothing happened when I clicked Apply (I now know to save and reload to see the effect).

Is there anywhere I can alter the number of inches/millimetres that equals one 'sp'? So many things are defined in 'sp' units that changing the size of an 'sp' might be all I needed.
Thanks
John

Status (old) active closed

That's exactly what the space /scaling factor in Layout / Page Settings does. "sp" is literally the size of a space.

In the future, general support questions are best asked in the forum, not the issue tracker. The issue tracker is for outright bugs, or feature requests where you have already ascertianed exactly what the program can and cannot do and have specific proposals for extending it.

I'm guess it will turn out that one or two settings you'd like to customize still will turn out not to be in 1.1. Some of them are probably already customizable in 2.0, so do consider installing one of the nightly builds to try. Then, if something still seems missing, and after discussion in the forums you find there is no acceptable workaround, *then* post specific feature request sin the tracker.