Hi there,
after just reading all these important threads partially, I want to jump
in. I want to encourage Urs' position - and if I understand correctly,
Carl does not object ;)
The lilypond way of working made it easy for me, to spot errors in a
score I received as musicXML. There where several partial bars, which
where actually not right. And Lilypond gave the right warnings.
When I am back into lily-business, I want to extend the edition-engraver
to do act on the content. Say, I want to add a crescendo in Context X
from measure 27 3. 4th to measure 29 2. 4th or the like. Other topics
are beaming, slurs, ties and so on (it should be doable ;) ).
But there is still one aspect missing: If I want to delete measure X
from all parts of a score, I am adviced to organize my code carefully
before that. So IMO this might be a topic rather for documentation than
for an additional feature.
Cheers, Jan-Peter
Am 27.04.2015 um 15:23 schrieb Urs Liska:
There are some advantages to the LilyPond way of doing it. LilyPond
easily supports different time signatures in different staffs. Music is
easily copied, because it has no absolute timing information.
There are also disadvantages to the LilyPond way. It is common for
people
to think things like "the crescendo should cover measures 2-4". There is
no way to express this kind of relationship in LilyPond.
I'm not convinced that LilyPond should add a "measure" object to its
language.
I would strongly oppose to *replacing* the current approach with a
container based approach (I don't think you are even considering that,
I just want to make that clear). Apart from the polymetrics stuff the
container imposes significant limitations with regard to items
crossing the measure boundaries. Or (in the case of Finale and
Sibelius at least) with incomplete measures.
AFAICS from blog post etc. it is really painful to talk one of these
programs into writing tuplets over bars (maybe even beams over
barlines?), and when you try to edit existing music and delete
something from a measure you can't really leave that measure without
the program complaining (or doing stupid things).
For a concept of "measures 2-4" we already have a powerful technology
right before us: the edition-engraver. It is not fully mature and
ready to be included in LilyPond itself. But apart from providing
means to completely separate content from separation it is also good
at injecting stuff "measure-wise".
For example right now it is possible to write:
\editionModList full-score Score
\break
#'(7 16 22 (27 2/4) 30)
to apply line breaks (or whatever) at this list of measures (including
partial measures)
What would be good to have is a notion of "select everything in
measures 2-4 - over all possible parts" as this is something that is
currently more or less impossible.
Urs
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
