Re: Big Measures in Large Ensemble

2009-08-06 Thread Joe Neeman
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 > >

Re: Big Measures in Large Ensemble

2009-08-06 Thread Werner LEMBERG
>> 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 htt

Re: website: why do you use lilypond?

2009-08-06 Thread Tim Rowe
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

Re: website: why do you use lilypond?

2009-08-06 Thread David Stocker
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 an

Re: TextSpanner Line Padding

2009-08-06 Thread Jonathan Wilkes
--- 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 >

Re: Big Measures in Large Ensemble

2009-08-06 Thread Neil Puttock
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 co

Re: conditionally eliminating lyric extender

2009-08-06 Thread Trevor Daniels
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.

Re: cannot end slur

2009-08-06 Thread Trevor Daniels
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, \( .. \) ins

Re: conditionally eliminating lyric extender

2009-08-06 Thread Kieren MacMillan
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 e

Re: TextSpanner Line Padding

2009-08-06 Thread Kieren MacMillan
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.

Re: website: why do you use lilypond?

2009-08-06 Thread Graham Percival
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

Re: Big Measures in Large Ensemble

2009-08-06 Thread Joe Neeman
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