![]() There are a number of other changes to how some of those interconnections work that probably make sense some day - not the least to make it possible to optimize things to not require relayout of the entire score every time you make a one-note change.ĭynamics, staff text, and system text need not be vertically aligned with respect to like elements in system indeed, it is common to see variable vertical alignment of dynamics, sometimes even requiring diagonal hairpins. The order in which things are laid out is a very sensitive thing, as many aspects of layout are interconnected. Lyrics are special in that if there is one lyric, there wil probably be a whole line of them, and they are all supposed to align vertically within a system.Īnyhow, these are the sort of changes probably best to discuss with Werner first. So even if we added some automatic code here, it needn't affect the entire system. Staff texts are easy enough to move one at a time if there are collisions, and there is no typesetting convention I know that says they must all be aligned vertically. So I think it makes more sense to tackle this one piece of the puzzle at a time. Really getting totally completely automatic layout is way beyond anything we are clsoe to right now, and based on how it works with LilyPond, would slow MuseScore to a crawl. And not just vertically - what about a staff text on one beat colliding with a staff text on the next? Or staff tyext colliding with articulations. Yes, automatic collision avoidance is a good thing in general, not just for lyrics. I propose that there be an option to make lyric positioning relative to the staff's lowest note in its system, instead of to the bottom of the staff. Manually adjust the vertical positions of colliding lyrics and the other lyrics in the system (best solution, though tedious, and system rearrangement will require redoing the correction).Manually adjust the vertical positions of the colliding lyrics (creating an awkward mid-system vertical position change, not suitable for multiple lines, may also require manual spacing of staff below), or.Globally set the "Lyrics top margin" setting to something higher (creating unnecessary space where there are no collisions, especially in other vocal parts),. ![]() The user must do one of the following to remove the collision: MuseScore doesn't currently do this automatically. ![]() In practice, the solution is to move the offending lyrics down as needed, but it's awkward for the line to jump in vertical position mid-system, so typically all of the staff's lyrics in the system are moved down to accommodate. Most of the time, this 2sp setting will work, but if the voice line falls more than two spaces below the staff (treble clef low-A or lower) there will be a collision. MuseScore's default "Lyrics top margin" setting is 2sp, meaning the top edge of lyrics will be placed two spaces under the staff. ![]()
0 Comments
Leave a Reply. |