-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi all,
First of all, let me say that I'm very impressed with lilypond and I appreciate all of the hard work that the developers have poured into it. And with that, here's some criticism: ;-)
After much head-scratching and searching of the lilypond mailing list archives, I've failed to come up with a decent workaround to the following problem (this is with 2.0.3):
I have a piece of music where a chord is tied to some notes with differing time values:
<c fs a>-- ~ << { a'2 } \\ { <c, fs>4 <c fs> } >>Now I know about Mats' workaround, and it works, sort of:
<c fs a>-- ~ << { a'2 } \\ \context Voice = mn { <c, fs>4 <c fs> } >>The only problem with this approach is that lily only connects the two lower notes (which makes sense, that's what I told her to do :-p). You can, of course, do this:
<c fs a>-- ~ << \context Voice = mn { a'2 } \\ \context Voice = mn { <c,
fs>4 <c fs> } >>But then it combines the half note head onto the quarter notes' vertical line--most definitely *not* what I want. Now I know that I could back up the split a little, but I *want* the chord notes that come before the tie to all be on the same vertical line...
Now I may be a little naive when it comes to lily's internals, but it
seems to me that even though the notes that follow the tie are in
different voice contexts that lily *should* be able to tell that they
are tied to the preceeding note/chord notes very easily without having
to make the user jump through hoops as per above--after all, they are in
the same \notes{} context. Is this possible? Or would it require major
changes in lily's internal structure?Again, this is with 2.0.3, but judging from what I've seen (and not seen) I don't think it has been changed at all. I could be wrong about that. ;-)
- -- Shamus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA7tqcmE5b/O3JjkYRAmJeAJsH+g66zQO/q0ly0EY6v6qMwpLwXACgrnHH ih/qIy+6sMlb+/BuzhgYft8= =i/jG -----END PGP SIGNATURE-----
_______________________________________________ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
