Marc Sabatella wrote
>  (as a personal reply...)
> On Apr 3, 2013, at 4:04 AM, "Maurizio M. Gavioli" 
> <
> [email protected]
> >
>  wrote:
>> 2) as more general solution, an "above-staff Y" and a "below-staff Y"
>> parameters could be used, the former relative to the top line and the
>> latter
>> relative to the bottom line.
> 
> Yes, yes, yes please!  As you observe, this is a common request for
> lyrics, and it's a pretty major hurdle for some types of music, to the
> point where I find it hard to recommend MuseScore for people doing vocal
> arrangemens for this reason.

If the 'core devs' (lasconic? Werner?) agree, I can go on along this path.


> You'd probably also want a way to specify which is the default to be used
> for that element type.

This could be definitely useful, but can be left to a second pass. For now,
I would leave elements at their built-in default position, with an option
(contextual menu? inspector?) to change it, possibly also in bulk.


>> 3) As an in-between solution, to avoid adding more parameters, the
>> current Y
>> offset parameter could be interpreted both as relative to the top line
>> for
>> Placement ABOVE and as negated-relative to the bottom line for Placement
>> BELOW. For instance, an Y offset = -4 would mean 4sp above the top line
>> for
>> Placement ABOVE and 4sp below the bottom line for Placement BELOW.
> 
> That works, if adding a parameters is considered a big deal.  I know there
> are always concerns about backward compatibility.  We'd have to decide if
> existing scores with negative Y values should be left as is (neagtive
> above staff values) or if we should try to convert these into below-staff
> values.

This is true for any solution, as David observed. Again this could be a
second (third?) pass: let old imported score keep their settings (old "Y
offset" => new "above-staff Y offset", same value). If cases where this is
inappropriate turn out to be frequent enough or cumbersome enough to adapt,
we can improve the import later.


> One thing to consider relating to lyrics specifically.  Currently,
> ordinary below-staff lyrics always allocate extra vertial space.  I have
> long thought this a mistake.  We don't do this for chord symbols or
> dynamics or anything else, and it makes it very hard to get predictable
> page formatting.  But given that there was no easy way to increase between
> two given staves globally (you need spacers within each system), I could
> grudgingly accept this as the only way to allow for lyrics within an
> otherwise tightly-space score.  Now that it *is* possible to manually
> adjust space between two given staves globally so that the staves that
> need more space can have it, I think it should be possible to defeat this
> automatic extra vertical space allocated for lyrics.

Personally, I have mixed feelings with this 'feature': I agree that it makes
page formatting aleatory, but in most occasions is a useful shortcut.

Anyway, I think that currently two elements are missing:
1) The possibility to set the lyrics line height (unless it is a recent
addition, I can't check right now)
2) The additional staff space is never exposed as a parameter; it can only
managed by manual (and approximate) dragging of the staff.


> [...] as soon as you allow for the possibility of above staff and below
> staff lyrics, you have to ask yourself if you want to reimplement the
> automatic vertical spacing allocating for the above staff lyrics.

Do you mean that this 'feature' could be reimplemented as an (automatic?)
change in the staff above or below space parameter? It makes sense!

Thanks,

Maurizio



--
View this message in context: 
http://dev-list.musescore.org/Elements-below-and-above-the-staff-tp7577993p7578008.html
Sent from the MuseScore Developer mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Mscore-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

Reply via email to