discrete slurs and ties

2012-05-23 Thread Werner LEMBERG
Due to this marvellous video http://www.youtube.com/watch?v=345o3Wu95Qo I have learned that short slurs and ties aren't engraved manually; instead, there are ready-to-use stamps. In other words, since the number of such stamps is limited, tie and slur shapes become discrete if their length is

Re: discrete slurs and ties

2012-05-23 Thread Janek Warchoł
On Wed, May 23, 2012 at 9:32 AM, Werner LEMBERG wrote: > > Due to this marvellous video > >  http://www.youtube.com/watch?v=345o3Wu95Qo > > I have learned that short slurs and ties aren't engraved manually; > instead, there are ready-to-use stamps.  In other words, since the > number of such stamp

Re: discrete slurs and ties

2012-05-23 Thread Werner LEMBERG
>> People can argue that this is an unnecessary limitation; lilypond >> can do a `better' job. However, I'm not sure whether we should do >> better... > > We should, definitely! > There are bad tie and slur shapes in Lily, but this is not due to > not having discrete lengths. Umm, yes. I've me

Re: discrete slurs and ties

2012-05-23 Thread David Kastrup
Werner LEMBERG writes: >>> People can argue that this is an unnecessary limitation; lilypond >>> can do a `better' job. However, I'm not sure whether we should do >>> better... >> >> We should, definitely! >> There are bad tie and slur shapes in Lily, but this is not due to >> not having discre

Re: discrete slurs and ties

2012-05-23 Thread Janek Warchoł
On Wed, May 23, 2012 at 11:15 AM, Werner LEMBERG wrote: > >> We should, definitely! >> There are bad tie and slur shapes in Lily, but this is not due to >> not having discrete lengths. > > Umm, yes. I've meant: Should lilypond do a `better' job than the > engravers working with those stamps? I u

Re: discrete slurs and ties

2012-05-23 Thread Werner LEMBERG
>> Frankly, I don't see the point in simulating well-craftedness by >> artificially introducing minor deficiencies associated with some of >> the better work. > > @Werner: i could live with an *option* doing this, but i doubt that > people are interested in writing it. And i think we have much, >

Re: Get the positions of a beam (or other grob with positions)

2012-05-23 Thread Janek Warchoł
Hi David, i'm writing just to let you know that the function changing arpeggio length: offsetArpeggioPositions = #(define-music-function (parser location offsets) (pair?) #{ \override Arpeggio #'positions = #(lambda (grob) (let* ((func (assoc-get 'positions (cdr (ly:grob-basic-p

Re: discrete slurs and ties

2012-05-23 Thread David Kastrup
Werner LEMBERG writes: >>> Frankly, I don't see the point in simulating well-craftedness by >>> artificially introducing minor deficiencies associated with some of >>> the better work. >> >> @Werner: i could live with an *option* doing this, but i doubt that >> people are interested in writing it

Re: Developing for LilyPond

2012-05-23 Thread m...@mikesolomon.org
On 22 mai 2012, at 22:15, David Nalesnik wrote: > > > On Tue, May 22, 2012 at 2:10 PM, m...@mikesolomon.org > wrote: > On 22 mai 2012, at 21:01, David Nalesnik wrote: > >> Hi Mike, >> >> On Tue, May 22, 2012 at 1:20 PM, m...@mikesolomon.org >> wrote: >> Hey David, >> >> You've been doing

Re: Get the positions of a beam (or other grob with positions)

2012-05-23 Thread Janek Warchoł
On Wed, May 23, 2012 at 1:02 PM, David Kastrup wrote: > Janek Warchoł writes: > >> I wish it was possible to add context to grob name in a more >> LilyPondish way (i.e. with a dot) > > It is conceivable as a parser extension, That's good news! > like 3/4 is nowadays generally read as '(3 . 4).

Re: Get the positions of a beam (or other grob with positions)

2012-05-23 Thread Thomas Morley
2012/5/23 Janek Warchoł : > On Wed, May 23, 2012 at 1:02 PM, David Kastrup wrote: >> Janek Warchoł writes: >> >>> I wish it was possible to add context to grob name in a more >>> LilyPondish way (i.e. with a dot) >> >> It is conceivable as a parser extension, > > That's good news! > >> like 3/4 i

Re: discrete slurs and ties

2012-05-23 Thread Janek Warchoł
On Wed, May 23, 2012 at 12:16 PM, Werner LEMBERG wrote: > >>> Frankly, I don't see the point in simulating well-craftedness by >>> artificially introducing minor deficiencies associated with some of >>> the better work. >> >> @Werner: i could live with an *option* doing this, but i doubt that >> p

Re: Get the positions of a beam (or other grob with positions)

2012-05-23 Thread Janek Warchoł
On Wed, May 23, 2012 at 1:43 PM, Thomas Morley wrote: > I tried it similar to `overrideProperty' from `music-functions-init.ly' > But I didn't manage to get rid of the ""-signs, when specifying the > coctext. Is this possible? > > \version "2.15.38" > > offsetPositions = > #(define-music-function

Re: Developing for LilyPond

2012-05-23 Thread David Nalesnik
Hi Mike, On Wed, May 23, 2012 at 12:47 AM, m...@mikesolomon.org wrote: > > [ ... ] Your patch is a post-processing corrective for when this fails. > However, the goal of LilyPond is twofold: > > 1) Provide users with the ability to tweak LilyPond's output when for some > reason the automation m

Re: Developing for LilyPond

2012-05-23 Thread Janek Warchoł
On Wed, May 23, 2012 at 5:16 PM, David Nalesnik wrote: > I find that the automation settings generally produce a good-looking result, > and looking through some of my scores I find that I usually let slurs, ties, > etc. alone, with an occasional override of 'positions.  For me this is > testament

Re: Developing for LilyPond

2012-05-23 Thread Kieren MacMillan
Hi all, Speaking of ugly slurs and slur controls… ;) Is there any easy way to get back the Slur #'attachment property we used to have? Cheers, Kieren. On 2012-May-23, at 16:51, Janek Warchoł wrote: > On Wed, May 23, 2012 at 5:16 PM, David Nalesnik > wrote: >> I find that the automation setti