lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problematic commit


From: Jonathan Wilkes
Subject: Re: problematic commit
Date: Wed, 27 Oct 2010 15:18:04 -0700 (PDT)


--- On Wed, 10/27/10, Valentin Villenave <address@hidden> wrote:

> From: Valentin Villenave <address@hidden>
> Subject: Re: problematic commit
> To: "Jonathan Wilkes" <address@hidden>
> Cc: address@hidden
> Date: Wednesday, October 27, 2010, 9:02 PM
> On Wed, Oct 27, 2010 at 6:49 PM,
> Jonathan Wilkes <address@hidden>
> wrote:
> > I'm interested to know how successful your sales pitch
> has been.  I did a free software talk a few weeks ago but
> talked mostly about Pure Data and Ardour, plus
> music-oriented distros of GNU/Linux.
> 
> I suspect that it may be (ever so slightly!) easier than
> "selling"
> LilyPond, since graphical applications have a little more
> "bling" than
> austere text-oriented apps like LilyPond.
> 
> (Oh, you were referring to Pure Data. Ok, never mind.)

Actually Pd has an ever-growing set of GUI 
objects-- you can see some of them being shown 
off in the image on Pd's Wikipedia page.

> 
> > If your audience cringes at \include "italiano.ly",
> what do they do when they learn how to put "ca." in front of
> a metronome marking, or change the direction of a tie after
> a line break?
> 
> ? I have no idea what you're referring to. Is that
> something you need
> to do with Finale? (If so, it may give me a nice argument
> when people
> object that LilyPond is too complex :-)

Well, no, I'm referring to Lilypond here.  
What I mean is that 
a) "\tempo 4=72" looks easy, but if someone 
asks how to get that tempo but have it 
display as quarter note = "ca. 72", as far as I 
know one has to have two two \tempo commands, 
one as above, and then followed with the 
"\tempo \markup" idiom.  Then you have to 
deal with why "\note" has two different arg 
types (one string and one number).

b) There are situations where a slur starts 
above the notes, and after a line break it 
would look better going in the opposite 
direction.  I don't see that in many professional scores, so maybe this is just 
my 
own little peculiarity, but the same problem 
holds for slurs over linebreaks where there is 
a collision or spacing issue and one wants 
to adjust the slur only after the break.

I'm just curious in general how your audience 
has responded to the way in which some small 
details are tweaked in Lilypond.

-Jonathan

> 
> Cheers,
> Valentin
> 






reply via email to

[Prev in Thread] Current Thread [Next in Thread]