Re: Big Measures in Large Ensemble
On Sun, 2009-08-02 at 19:30 +0200, Werner LEMBERG wrote: > > There is a problem, however -- a > > slight extra space appears where the invisible fake-barlines > > (possible break-points) are. And the obvious way of correcting > > that didn't work. I'll ask the other developers if there's a way > > to fix that. > > I've reported this already: > > http://code.google.com/p/lilypond/issues/detail?id=462 > > Maybe Joe can now `fiddle' with it, as announced :-) As per usual, it turned out to be more complicated than I expected. But it's fixed in git now. Joe ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Big Measures in Large Ensemble
>> Maybe Joe can now `fiddle' with it, as announced :-) > > As per usual, it turned out to be more complicated than I > expected. But it's fixed in git now. Great! Will test soon. Werner ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: website: why do you use lilypond?
2009/8/4 Graham Percival : > On Mon, Aug 03, 2009 at 02:52:25PM +0100, Tim Rowe wrote: >> A pop example presents obvious copyright issues. > > No; an *existing* commercial pop example has copyright issues. > Using a copyleft pop song would be fine as long as we include the > copyleft license issues (attribution, etc). Inventing a new pop > song sidesteps all the above. True, but we haven't invented new copyright pieces for classical, Gregorian chant, etc. I would have thought it better to have a recognisable pop song on the web site if we can. Elvis Presley might not exactly be current, but he was certainly popular! Or we could go back to earlier pop: "She was poor but she was honest..." ;-) -- Tim Rowe ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: website: why do you use lilypond?
I did some guitar ensemble (4 guitars) arrangements of Joplin rags some years ago that are now published (Maple Leaf Rag, Cascades) by Doberman-Yppan. I can check with them to see if we can use passages as examples for LilyPond Tablature if you like. Also, I wouldn't be averse to working up any new arrangements of Joplin rags for guitar--solo or ensemble--provided they're in the public domain. What would be the timeline for such an endeavor? David Federico Bruni wrote: Tim Rowe wrote: 2009/8/1 Federico Bruni : I'd be really glad to help with the tablature example. I think a modern piece would be better in this case, as tablature are used by modern guitarists. What about a Scott Joplin ragtime arranged for guitar? (it is in the public domain) I guess a good example should show the best features of tablature support in Lilypond.. There are any other requirements? Scott Joplin rags may be public domain, but are any guitar arrangements of them? Or were you offering to do one? I'm not sure at all, but... .. I think that an arrangement of a public domain piece of music can be copyrighted just if it's a kind of 'original' elaboration by the musician; I mean something different, somehow. As far as I use an arrangement which is very close to the original music, it should be fine, shouldn't? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: TextSpanner Line Padding
--- On Thu, 8/6/09, Kieren MacMillan wrote: > From: Kieren MacMillan > Subject: Re: TextSpanner Line Padding > To: "Jonathan Wilkes" > Cc: "David Stocker" , lilypond-user@gnu.org > Date: Thursday, August 6, 2009, 6:06 AM > Hi Jonathan, > > > One more question: I'm also trying to use an "a > tempo" > > at the end (right) of the spanner. If I use a > hard space there, it > > won't align properly with the note it is attached to. > > Any advice on that would be appreciated. > > Can you use a hard space and then compensate by increasing > the bound padding by the width of a space? > > Cheers, > Kieren. Hi Kieren, Is bound padding #'(bound-details right padding) or #'bound-padding? It seems like some of the properties are missing in the IR. The notation reference explains some properties for spanners (like line breaking properties) that I don't see for TextSpanner- or any of the related interfaces- in the IR. -Jonathan ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Big Measures in Large Ensemble
2009/8/6 Joe Neeman :
> As per usual, it turned out to be more complicated than I expected. But
> it's fixed in git now.
Nice work, Joe; it's a great fix.
I had a go at fixing it myself, but gave up after ending up with notes
colliding with clefs and multiple `no spring ...' errors. :)
A few comments:
Don't you think \bar "empty" should behave in the same way as \bar ""?
Though it's treated differently in bar-line.cc (it's ignored
completely, so returns an empty stencil), I think users will expect it
to reflect its naming.
I notice the spacing for volte which don't start or end at a barline
is tighter (it matches the behaviour without volte), though this is
probably preferable (as an aside, the volta brackets are right at the
top of the page in the pdf, which looks like a spacing bug).
\relative c'' {
\repeat volta 2 { \time 4/4 c4^"cuivre"_\fermata }
\alternative {
{
d-4_\markup { \italic "cantabile" }
}
{ e }
}
\acciaccatura { c16 }
f4\ff^""^\markup { \large "Largo" } \mark "B" g s2.
c,4 d \bar ":|" e \acciaccatura c8 f4 g
}
Regards,
Neil
<>___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: conditionally eliminating lyric extender
Kieren I'm not sure I understand the need for this. Maybe I'm missing something (it wouldn't be unusual :) I would not normally use a lyric extender unless the syllable had an extended duration over several notes or was sung to a long note. This occurs far less frequently than a 2-note melisma. And this seems to be the standard practice in the vocal scores I'm familiar with. Do you attach lyric extenders unconditionally to every syllable sung to a melisma? I'm afraid I don't know the answer to your question though. Trevor - Original Message - From: "Kieren MacMillan" To: "LilyPond Development" ; "Lilypond-user Mailinglist" Sent: Wednesday, August 05, 2009 6:34 PM Subject: conditionally eliminating lyric extender Hello all, I want to [automagically] conditionally eliminate lyric extenders when (1) the end of the syllable which has the extender is after [i.e., to the right of] the melisma's last note; and, (2) the distance to the following syllable is less than the minimum extender length [plus some reasonable padding value?]. [Yes, I'm aware of Ross etc. and traditional rules of engraving — I also know that there are exceptions to every rule, and I think the one I'm suggesting is reasonable.] For an example of the current default (v 2.13.3), I've attached a screenshot of my setting of Shakespeare's "Pardon, goddess of the night". It should be immediately obvious why I think the default is not optimal: in the case of "songs" and "Round", I would *definitely* want to eliminate the extender, and I might even want to eliminate it after "-bout". My question is, what would be required to fix this? Can it be done in the .scm files, or does it require a C++ modification? Thanks, Kieren. ___ lilypond-devel mailing list lilypond-de...@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: cannot end slur
Carl Sorensen wrote Tuesday, August 04, 2009 2:05 PM On 8/4/09 5:35 AM, "Reinhold Kainhofer" wrote: Am Dienstag, 4. August 2009 01:29:56 schrieb Trevor Daniels: Stupid of me! I gave the correct analysis of your problem but the wrong solution! You should use a phrasing slur, \( .. \) instead of a slur, ( .. ). Then the acciaccatura slur doesn't get in the way. But on the other hand, it is not detected as a melisma for the lyrics any longer, so each of the "slurred" notes will still be assigned a lyrics syllable, which is in general not what you want. So, as a first workaround, should the slur in acciaccatura be changed to a phrasing slur? I don't think so. In the example which started this thread the slur should have been a phrasing slur anyway, which with your suggested change would have then presented the same problem in reverse. Also it would be unusual to have an acciaccatura which was _not_ part of a melisma, so it really does need to be slurred to the following note or else it would take a syllable for itself. Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: conditionally eliminating lyric extender
Hi Trevor, I'm not sure I understand the need for this. I would not normally use a lyric extender unless the syllable had an extended duration over several notes or was sung to a long note. This occurs far less frequently than a 2-note melisma. Do you attach lyric extenders unconditionally to every syllable sung to a melisma? Yes: 1. According to the engraving histories/guides I've read, there should be an extender after *every* [final] melisma syllable regardless of how short (including negative) that extender line would end up being. 2. One can't possibly know in advance how wide the final engraved note spacing will be relative to the length of the lyric syllable — hence one should *always* include extenders so that Lilypond can DTRT depending on the spacing requirements [of different editions, alternative system breaks, etc.]. this seems to be the standard practice in the vocal scores I'm familiar with. Recently, I've seen a lot of scores that don't use extenders *ever*... but I think this is a horrible practice which makes sight- singing more difficult. Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: TextSpanner Line Padding
Hi Jonathan, Hi Kieren, Is bound padding #'(bound-details right padding) or #'bound- padding? In 2.13.3, I'm pretty sure it's #'(bound-details right padding). Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: website: why do you use lilypond?
On Thu, Aug 06, 2009 at 07:10:21PM +0100, Tim Rowe wrote: > 2009/8/4 Graham Percival : > > On Mon, Aug 03, 2009 at 02:52:25PM +0100, Tim Rowe wrote: > >> A pop example presents obvious copyright issues. > > > > No; an *existing* commercial pop example has copyright issues. > > Using a copyleft pop song would be fine as long as we include the > > copyleft license issues (attribution, etc). Inventing a new pop > > song sidesteps all the above. > > True, but we haven't invented new copyright pieces for classical, > Gregorian chant, etc. Those aren't covered by copyright. > I would have thought it better to have a > recognisable pop song on the web site if we can. Elvis Presley might > not exactly be current, but he was certainly popular! I don't think that any of his songs would become available until 2050 or so -- assuming the big media companies don't extend copyright again in a few years. > Or we could go back to earlier pop: "She was poor but she was honest..." ;-) If that's a reference to my "let's obey copyright law, even if we have poorer examples", then yes. If that's a reference to a pre-1926 pop song, then it obviously went over my head. :) Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Big Measures in Large Ensemble
On Thu, 2009-08-06 at 23:03 +0100, Neil Puttock wrote:
> 2009/8/6 Joe Neeman :
>
> > As per usual, it turned out to be more complicated than I expected. But
> > it's fixed in git now.
>
> Nice work, Joe; it's a great fix.
>
> I had a go at fixing it myself, but gave up after ending up with notes
> colliding with clefs and multiple `no spring ...' errors. :)
>
You probably made the same mistake that I made initially: if you prune a
breakable column then you've pruned it's broken pieces (ie. the
line-ending and line-beginning pieces, which shouldn't be pruned) in
addition to it's mid-line piece.
> A few comments:
>
> Don't you think \bar "empty" should behave in the same way as \bar ""?
> Though it's treated differently in bar-line.cc (it's ignored
> completely, so returns an empty stencil), I think users will expect it
> to reflect its naming.
How about just checking for an empty extent, like in the attached patch?
>
> I notice the spacing for volte which don't start or end at a barline
> is tighter (it matches the behaviour without volte), though this is
> probably preferable
That wasn't intentional; I'll take a closer look to make sure it doesn't
have undesirable consequences.
> (as an aside, the volta brackets are right at the
> top of the page in the pdf, which looks like a spacing bug).
Yeah, grobs that live in System mess up the spacing problem.
Joe
diff --git a/lily/spacing-determine-loose-columns.cc b/lily/spacing-determine-loose-columns.cc
index 90db1e0..7fddb84 100644
--- a/lily/spacing-determine-loose-columns.cc
+++ b/lily/spacing-determine-loose-columns.cc
@@ -111,7 +111,8 @@ is_loose_column (Grob *l, Grob *col, Grob *r, Spacing_options const *options)
{
extract_grob_set (h, "elements", helts);
for (vsize k = helts.size (); k--;)
- if ("" != robust_scm2string (helts[k]->get_property ("glyph-name"), ""))
+ // Only non-empty bar lines count.
+ if (h->extent (h, X_AXIS).length () > 0)
return false;
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
