Re: Move tie to the end(top) of the stem

[Janek Warchoł]

2014-04-22 0:43 GMT+02:00 Simon Albrecht :
>
>> On Apr 21, 2014, at 5:01 PM, Knute Snortum  wrote:
>>
>>> I have a piece I'm typesetting where an internal voice needs a tie, but
>>> \tieDown isn't enough.  The tie spanner needs to be at the bottom (in this
>>> case) of the stems.  Here is a snippet that illustrates the problem:
>>>
>>> \version "2.18.2"
>>> \new Staff {
>>> \key bes \major
>>> \time 5/4
>>> <<
>>> {
>>> 4  
>>> 8[   ]
>>> } \\
>>> {
>>> \override Stem.length = #8.0
>>> \stemDown ees'2.
>
> [Alternatively, use the override inserted below.]
> \once\override Tie.staff-position = #-9
>
>>> ees'4 ~ ees'8 r8
>>> }
>>> }

This is a very bad idea and an engraving error: moving the tie like
this makes it look like a slur.
Conor's solution is the way to go.

best,
Janek

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Organ Fingering Notation

[Brian Barker]

At 11:19 21/04/2014 -0700, Zack Noname wrote:
There is a fingering symbol that I don't know the name of (and so it 
is hard to look up in the documentation without a name) ...
If I want the alto voice on the treble staff played with the left 
hand there is a symbol that looks like [ without the bottom line and 
if I want the note on the bass clef played with the right hand its a 
[ without the upper line ...


Anyone know what I'm "talking" about?


Interestingly, Elaine Gould knows what you are talking about but also 
doesn't know their name:
A verbal instruction may indicate that notes are to be taken with 
the other hand. ... Alternatively, such notes may be shown with an 
incomplete bracket, extending vertically from the notehead upwards 
for right-hand notes, downwards for left-hand notes. (at p. 305)


Brian Barker  



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Move tie to the end(top) of the stem

[Conor Cook]

You’re welcome.  But Simon’s definitely looks better :)

~Conor Cook

On Apr 21, 2014, at 7:59 PM, Knute Snortum  wrote:

> That's it, Simon!  Thanks.  And thanks for the suggestion, Conor.  That did 
> look better.
> 
> 
> Knute Snortum
> (via Gmail)
> 
> 
> On Mon, Apr 21, 2014 at 3:43 PM, Simon Albrecht  
> wrote:
> Alternatively, use the override inserted below.
> 
> Best, Simon
> 
> Am 22.04.2014 00:40, schrieb Conor Cook:
> 
> Does the tie need to connect the eeses?  This looks good, but maybe not to 
> your specs.
> 
> \version "2.18.2"
> \new Staff {
> \key bes \major
> \time 5/4
> <<
> {
> 4  
> 8[   ]
> } \\
> {
> \override Stem.length = #8.0
> \stemDown ees'2. ees'4^~ ees'8 r8
> }
> }
> 
> Best,
> Conor Cook
> 
> On Apr 21, 2014, at 5:01 PM, Knute Snortum  wrote:
> 
> I have a piece I'm typesetting where an internal voice needs a tie, but 
> \tieDown isn't enough.  The tie spanner needs to be at the bottom (in this 
> case) of the stems.  Here is a snippet that illustrates the problem:
> 
> \version "2.18.2"
> \new Staff {
> \key bes \major
> \time 5/4
> <<
> {
> 4  
> 8[   ]
> } \\
> {
> \override Stem.length = #8.0
> \stemDown ees'2.
> \once\override Tie.staff-position = #-9
> 
> ees'4 ~ ees'8 r8
> }
> }
> 
> Knute Snortum
> (via Gmail)
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Newbie problem in my first or second score

[Steve Lane]

Neat — I'll see if I can track it down.

From: Daniel Rosen mailto:drose...@gmail.com>>
Date: Monday, April 21, 2014 5:39 PM
To: Steve Lane 
mailto:sl...@soliantconsulting.com>>, 
"lilypond-user@gnu.org" 
mailto:lilypond-user@gnu.org>>
Subject: RE: Newbie problem in my first or second score

That was an accepted notational practice at the time for appoggiaturas. There’s 
a pretty interesting discussion of this in the New Grove Dictionary of Music 
and Musicians article on “Ornaments,” § 9.i.

DR

From: Steve Lane [mailto:sl...@soliantconsulting.com]
Sent: Monday, April 21, 2014 9:12 AM
To: lilypond-user@gnu.org
Subject: Re: Newbie problem in my first or second score

Thanks, David and Federico — easy fix! All layout engines have their 
architectural weak spots, so that 's no surprise I guess.

I guess the rendering of that first sixteenth as a grace note in this piece is 
somewhat arbitrary anyway, since the first measure is always playes simply as 
four sixteenths. Doubtless some historical reason.

Thanks again,

SGL

From: David Nalesnik mailto:david.nales...@gmail.com>>
Date: Monday, April 21, 2014 8:08 AM
To: Steve Lane mailto:sl...@soliantconsulting.com>>
Cc: "lilypond-user@gnu.org" 
mailto:lilypond-user@gnu.org>>
Subject: Re: Newbie problem in my first or second score

Hi Steve,

On Mon, Apr 21, 2014 at 7:02 AM, Steve Lane 
mailto:sl...@soliantconsulting.com>> wrote:
Hello all:

So I am trying to lay out the first bars of Mozart's Sonata K 333. The first 
measure is a partial measure. No matter what I try so far, I'm getting an extra 
time and key signature in the bass clef, in addition to the bass clef first 
displaying as treble, then adding a bass clef in:

[cid:image001.png@01CF5D88.2B54B1E0]

The code is as follows (I didn't see how to make it tinier):

\version "2.18.2"
\include "english.ly"

keyTime = { \key bf \major \time 4/4 }

upper = \relative c''' {
  \partial 4 \grace g16 f8 ef16 d |
}

lower = {
  \partial 4 r4 |
}

\score {
  \new PianoStaff <<
\new Staff = "upper" { \clef "treble" \keyTime \upper }
\new Staff = "lower" { \clef "bass" \keyTime  \lower }
  >>
}


Any help appreciated :-)


Welcome to LilyPond!

Sorry you had to discover so quickly perhaps the most persistent bug in the 
program.

It's easily fixed, though: add a corresponding grace spacer to the other part 
at the same point.

\partial 4 \grace s16 r4

--David

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Move tie to the end(top) of the stem

[Knute Snortum]

That's it, Simon!  Thanks.  And thanks for the suggestion, Conor.  That did
look better.


Knute Snortum
(via Gmail)


On Mon, Apr 21, 2014 at 3:43 PM, Simon Albrecht wrote:

> Alternatively, use the override inserted below.
>
> Best, Simon
>
> Am 22.04.2014 00:40, schrieb Conor Cook:
>
>  Does the tie need to connect the eeses?  This looks good, but maybe not
>> to your specs.
>>
>> \version "2.18.2"
>> \new Staff {
>> \key bes \major
>> \time 5/4
>> <<
>> {
>> 4  
>> 8[   ]
>> } \\
>> {
>> \override Stem.length = #8.0
>> \stemDown ees'2. ees'4^~ ees'8 r8
>> }
>> }
>>
>> Best,
>> Conor Cook
>>
>> On Apr 21, 2014, at 5:01 PM, Knute Snortum  wrote:
>>
>>  I have a piece I'm typesetting where an internal voice needs a tie, but
>>> \tieDown isn't enough.  The tie spanner needs to be at the bottom (in this
>>> case) of the stems.  Here is a snippet that illustrates the problem:
>>>
>>> \version "2.18.2"
>>> \new Staff {
>>> \key bes \major
>>> \time 5/4
>>> <<
>>> {
>>> 4  
>>> 8[   ]
>>> } \\
>>> {
>>> \override Stem.length = #8.0
>>> \stemDown ees'2.
>>>
>> \once\override Tie.staff-position = #-9
>
>  ees'4 ~ ees'8 r8
>>> }
>>> }
>>>
>>> Knute Snortum
>>> (via Gmail)
>>> ___
>>> lilypond-user mailing list
>>> lilypond-user@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: too wide score after upgrading 2.18.1 to 2.18.2

[Vaughan McAlley]

On 22 April 2014 09:06, Marcin Gryszkalis  wrote:
>
> On 20.04.2014 23:02, Janek Warchoł wrote:
> > https://github.com/openlilylib/snippets/tree/master/notation-snippets/adjust-horizontal-spacing
>
> That's it, worked like a charm :) I thought one can only use 1/(2^n) as
> moment... Thanks
>
> regards
> --
> Marcin Gryszkalis, PGP 0xA5DBEEC7
> jabber jid:m...@fork.pl, gg:2532994
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

Just out of curiosity, is there any list of changes between 2.18.0 and 2.18.2?

(I can’t find it if it exists...)

Vaughan

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Orchestral score: bottom staff position

[Gilberto Agostinho]

Hello LilyPonders,

I am current writing a orchestral score with a lot of instruments on it,
meaning that I will always have only a single system per page (no hidden
staves). The thing is, the distance between the bottom staff (the Double
Bass in my case) and the bottom of the page keeps changing from page to
page. I am looking for a way of keeping it constant, i.e. always expand the
whole system until the bottom, so the distance between the last staff and
the bottom of the page will be effectively only the margin. In summary,
something similar to what ragged-bottom does, but concerning staves and not
systems. 

I thought the answer would lie somewhere in 4.4.1 Flexible vertical spacing
within systems or 4.1.4 Flexible vertical spacing \paper variables, but I
simply cannot find it. Could anyone please point me in the right direction?
Thank you very much.

Regards,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Orchestral-score-bottom-staff-position-tp161720.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: too wide score after upgrading 2.18.1 to 2.18.2

[Marcin Gryszkalis]

On 20.04.2014 23:02, Janek Warchoł wrote:
> https://github.com/openlilylib/snippets/tree/master/notation-snippets/adjust-horizontal-spacing

That's it, worked like a charm :) I thought one can only use 1/(2^n) as
moment... Thanks

regards
-- 
Marcin Gryszkalis, PGP 0xA5DBEEC7
jabber jid:m...@fork.pl, gg:2532994


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Move tie to the end(top) of the stem

[Simon Albrecht]

Alternatively, use the override inserted below.

Best, Simon

Am 22.04.2014 00:40, schrieb Conor Cook:

Does the tie need to connect the eeses?  This looks good, but maybe not to your 
specs.

\version "2.18.2"
\new Staff {
\key bes \major
\time 5/4
<<
{
4  
8[   ]
} \\
{
\override Stem.length = #8.0
\stemDown ees'2. ees'4^~ ees'8 r8
}
}

Best,
Conor Cook

On Apr 21, 2014, at 5:01 PM, Knute Snortum  wrote:


I have a piece I'm typesetting where an internal voice needs a tie, but 
\tieDown isn't enough.  The tie spanner needs to be at the bottom (in this 
case) of the stems.  Here is a snippet that illustrates the problem:

\version "2.18.2"
\new Staff {
\key bes \major
\time 5/4
<<
{
4  
8[   ]
} \\
{
\override Stem.length = #8.0
\stemDown ees'2.

\once\override Tie.staff-position = #-9

ees'4 ~ ees'8 r8
}
}

Knute Snortum
(via Gmail)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Move tie to the end(top) of the stem

[Conor Cook]

Does the tie need to connect the eeses?  This looks good, but maybe not to your 
specs.

\version "2.18.2"
\new Staff {
\key bes \major
\time 5/4
<<
{
4  
8[   ]
} \\
{
\override Stem.length = #8.0
\stemDown ees'2. ees'4^~ ees'8 r8
}
>>
}

Best,
Conor Cook

On Apr 21, 2014, at 5:01 PM, Knute Snortum  wrote:

> I have a piece I'm typesetting where an internal voice needs a tie, but 
> \tieDown isn't enough.  The tie spanner needs to be at the bottom (in this 
> case) of the stems.  Here is a snippet that illustrates the problem:
> 
> \version "2.18.2"
> \new Staff {
> \key bes \major
> \time 5/4
> <<
> {
> 4  
> 8[   ]
> } \\
> {
> \override Stem.length = #8.0
> \stemDown ees'2. ees'4 ~ ees'8 r8
> }
> >>
> }
> 
> Knute Snortum
> (via Gmail)
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Move tie to the end(top) of the stem

[Knute Snortum]

I have a piece I'm typesetting where an internal voice needs a tie, but
\tieDown isn't enough.  The tie spanner needs to be at the bottom (in this
case) of the stems.  Here is a snippet that illustrates the problem:

\version "2.18.2"

\new Staff {

\key bes \major

\time 5/4

<<

{

4  

8[   ]

} \\

{

\override Stem.length = #8.0

\stemDown ees'2. ees'4 ~ ees'8 r8

}

>>

}

Knute Snortum
(via Gmail)
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

RE: Newbie problem in my first or second score

[Daniel Rosen]

That was an accepted notational practice at the time for appoggiaturas. There's 
a pretty interesting discussion of this in the New Grove Dictionary of Music 
and Musicians article on "Ornaments," § 9.i.

DR

From: Steve Lane [mailto:sl...@soliantconsulting.com]
Sent: Monday, April 21, 2014 9:12 AM
To: lilypond-user@gnu.org
Subject: Re: Newbie problem in my first or second score

Thanks, David and Federico - easy fix! All layout engines have their 
architectural weak spots, so that 's no surprise I guess.

I guess the rendering of that first sixteenth as a grace note in this piece is 
somewhat arbitrary anyway, since the first measure is always playes simply as 
four sixteenths. Doubtless some historical reason.

Thanks again,

SGL

From: David Nalesnik mailto:david.nales...@gmail.com>>
Date: Monday, April 21, 2014 8:08 AM
To: Steve Lane mailto:sl...@soliantconsulting.com>>
Cc: "lilypond-user@gnu.org" 
mailto:lilypond-user@gnu.org>>
Subject: Re: Newbie problem in my first or second score

Hi Steve,

On Mon, Apr 21, 2014 at 7:02 AM, Steve Lane 
mailto:sl...@soliantconsulting.com>> wrote:
Hello all:

So I am trying to lay out the first bars of Mozart's Sonata K 333. The first 
measure is a partial measure. No matter what I try so far, I'm getting an extra 
time and key signature in the bass clef, in addition to the bass clef first 
displaying as treble, then adding a bass clef in:

[cid:image001.png@01CF5D88.2B54B1E0]

The code is as follows (I didn't see how to make it tinier):

\version "2.18.2"
\include "english.ly"

keyTime = { \key bf \major \time 4/4 }

upper = \relative c''' {
  \partial 4 \grace g16 f8 ef16 d |
}

lower = {
  \partial 4 r4 |
}

\score {
  \new PianoStaff <<
\new Staff = "upper" { \clef "treble" \keyTime \upper }
\new Staff = "lower" { \clef "bass" \keyTime  \lower }
  >>
}


Any help appreciated :-)


Welcome to LilyPond!

Sorry you had to discover so quickly perhaps the most persistent bug in the 
program.

It's easily fixed, though: add a corresponding grace spacer to the other part 
at the same point.

\partial 4 \grace s16 r4

--David

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Liederkreis, Op.39 by Robert Schumann

[Ole Schmidt]

Hi,

I want to make transcriptions for bassclarinet from some "Liederkreis" op.39 
Robert Schumann songs, are there any .ly files around?

Thanks!

ole






___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Organ Fingering Notation

[Shane Brandes]

In mathematics they are called floor and ceiling brackets, in music
they are probably still some sort of bracket. There is a request from
2002 for a half bracket. I don't know how to find them in LilyPond
documentation either. There is a Unicode u+2308 and u+2309 for the
floor and ceiling brackets so you could use them as markup.

Shane

On Mon, Apr 21, 2014 at 2:19 PM,   wrote:
> Hi All - New to the list but have used lilypond for years.  I have been
> setting some baroque organ works for some of my students.  There is a
> fingering symbol that I don't know the name of (and so it is hard to look up
> in the documentation without a name) ... I'm hoping that if I describe it,
> someone in the musical typesetting world will know its name and can point me
> to how to recreate it in lilypond ...
>
> If I want the alto voice on the treble staff played with the left hand there
> is a symbol that looks like [ without the bottom line and if I want the note
> on the bass clef played with the right hand its a [ without the upper line
> ...
>
> Anyone know what I'm "talking" about?
>
> Thanks
>
> Zack
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Organ Fingering Notation

[zvm]

Hi All - New to the list but have used lilypond for years.  I have been 
setting some baroque organ works for some of my students.  There is a 
fingering symbol that I don't know the name of (and so it is hard to look up 
in the documentation without a name) ... I'm hoping that if I describe it, 
someone in the musical typesetting world will know its name and can point me 
to how to recreate it in lilypond ...


If I want the alto voice on the treble staff played with the left hand there 
is a symbol that looks like [ without the bottom line and if I want the note 
on the bass clef played with the right hand its a [ without the upper line 
...


Anyone know what I'm "talking" about?

Thanks

Zack

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: voice solfege sequence

[MING TSANG]

Hi, Thomas,

On Monday, April 21, 2014 10:17:36 AM, Thomas Morley  
wrote:
 
2014-04-21 13:47 GMT+02:00 MING TSANG :
> Hi, Thomas:
> On Monday, April 21, 2014 4:32:34 AM, Thomas Morley
>  wrote:
> 2014-04-20 23:46 GMT+02:00 MING TSANG :
>
>> Thank you for modify the solfege-engraver.
>> I copy and paste into the .ly file and ran.  Result: The below staff seems
>> working, but "\xup" suppose to put the solfege above staff and now it is
>> put
>> below the staff instead - and the stacking is not right.  Any idea?
>
> Hi Ming,
>
> I can't reproduce the image you posted.
> On my machine, the attached code returns the attached image.
> Please tell me whats wrong with it.
>
> Cheers,
>
>   Harm
>
> Thank you for the attachments.  I desk check your .ly file with my .ly file
> and discover my f.ly file miss the following line:
> "  (set! (ly:grob-property newgrob 'direction) dir)  "
> After I copy and paste the line to my .ly file, it works.  Thank you very
> much.
> BTW can the notehead color be retained to show on solfege above the staff?

Should work if you comment
(ly:event-set-property! event-copy 'tweaks '())

(not tested, thogh)


> Emmanuel,
> Ming
>
>


Yes, it works. Thank you.
Emmanuel,
Ming.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Customizing the position of the dots in repeat bar lines

[Marc Hohl]

Am 21.04.2014 17:01, schrieb Paul Morris:

Paul Morris wrote

And another one, now with dot-positions supplied as an argument.


Submitted to the LSR, with a second example added:
http://lsr.di.unimi.it/LSR/Item?id=913


Looks nice, thanks for submitting!

Marc


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Whiteout box function by Thomas Morley / need help

[Thomas Morley]

2014-04-21 16:40 GMT+02:00 Karol Majewski :
> Harm,
>
> this change is related to issue 621:
> http://code.google.com/p/lilypond/issues/detail?id=621
>
> Now, I do not accept this solution. It is simply against the rules. 
> DynamicText shouldn't have influence on spacaing. Therefore I prefer whiteout.
>
> So I use:
>
> \context {
>   \Staff
>   \override DynamicText.extra-spacing-width = #'(+inf.0 . -inf.0)
> }


Ahh, ok.
Now I understand your remark here
http://lists.gnu.org/archive/html/lilypond-user/2014-04/msg00204.html

The following will give different result for extra-spacing-width
depending on presence of spanbars:

\version "2.19.4"

dynamic-text-extra-spacing-width-info =
  \override DynamicText.after-line-breaking =
#(lambda (grob)
   (newline)(write (ly:grob-property grob 'extra-spacing-width)))

m = \new Staff { c1 \dynamic-text-extra-spacing-width-info c\f }

<< \m \m >>
\new StaffGroup << \m \m >>

Will look in the whiteout-function ...

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Customizing the position of the dots in repeat bar lines

[Paul Morris]

Paul Morris wrote
> And another one, now with dot-positions supplied as an argument.

Submitted to the LSR, with a second example added:
http://lsr.di.unimi.it/LSR/Item?id=913

-Paul





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Customizing-the-position-of-the-dots-in-repeat-bar-lines-tp161666p161697.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Hairping length

[Helge Kruse]

Am 21.04.2014 09:53, schrieb Jan-Peter Voigt:
>
> \relative c'' { c4 b\<  bes\! \override Hairpin.to-barline = ##f a\< 
 | g\! }


Am 21.04.2014 09:55, schrieb Janek Warchoł:


I think to-barline property of hairpins should help you.


Thanks to all, this helps. I wasn't aware of that property and that I 
have to disable something to make the hairpin work for all position of 
the notes.


Regards
Helge



smime.p7s
Description: S/MIME Kryptografische Unterschrift
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Whiteout box function by Thomas Morley / need help

[Karol Majewski]

Harm,

this change is related to issue 621:
http://code.google.com/p/lilypond/issues/detail?id=621

Now, I do not accept this solution. It is simply against the rules. DynamicText 
shouldn't have influence on spacaing. Therefore I prefer whiteout.

So I use:

\context {
  \Staff
  \override DynamicText.extra-spacing-width = #'(+inf.0 . -inf.0)
}

Note that your previous function (the one that contains 
flexible-stencil-whiteout) works well with DynamiText. But the drawback is that 
it doesn't allow to set left and right X-extent.

-- Karol




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: voice solfege sequence

[Thomas Morley]

2014-04-21 13:47 GMT+02:00 MING TSANG :
> Hi, Thomas:
> On Monday, April 21, 2014 4:32:34 AM, Thomas Morley
>  wrote:
> 2014-04-20 23:46 GMT+02:00 MING TSANG :
>
>> Thank you for modify the solfege-engraver.
>> I copy and paste into the .ly file and ran.  Result: The below staff seems
>> working, but "\xup" suppose to put the solfege above staff and now it is
>> put
>> below the staff instead - and the stacking is not right.  Any idea?
>
> Hi Ming,
>
> I can't reproduce the image you posted.
> On my machine, the attached code returns the attached image.
> Please tell me whats wrong with it.
>
> Cheers,
>
>   Harm
>
> Thank you for the attachments.  I desk check your .ly file with my .ly file
> and discover my f.ly file miss the following line:
> "  (set! (ly:grob-property newgrob 'direction) dir)  "
> After I copy and paste the line to my .ly file, it works.  Thank you very
> much.
> BTW can the notehead color be retained to show on solfege above the staff?

Should work if you comment
(ly:event-set-property! event-copy 'tweaks '())

(not tested, thogh)

> Emmanuel,
> Ming
>
>

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Whiteout box function by Thomas Morley / need help

[Thomas Morley]

2014-04-21 16:02 GMT+02:00 Thomas Morley :
> Hi Karol,
>
> sorry coming back to you that late.
>
> 2014-04-21 13:22 GMT+02:00 Karol Majewski :
>> Although I know nothing about scheme, I've managed to slim down this 
>> function, so that there are no optional arguments. Now I'll try to find out 
>> why it doesn't work for DynamicText grob.
>>
> It seems thee was some change in the source concerning DynamicText.
>
> Look at the attached images produced from the following code with
> 2.18.0 and 2.19.4
>
> \new StaffGroup
> <<
> \new Staff \relative c' {
> c1

Please note, the images from my last post were made without the
'X-offset-override:

> \override DynamicText #'X-offset = #-20
> \once \override DynamicText #'whiteout = ##t
> c\f
> c
> }
> \new Staff \relative c' {
> c1 c c
> }
>>>
>
> It seems now to be impossible to move DynamicText across BarLines.
> (You can use 'extra-offset ofcourse, though it's usually a bad idea.)
>
> Obviously, it was made to avoid any BarLine/DynamicText collisions.
> If it always works, there would be no more need for any whiteout
> function for DynamicText.
>
> Do you encounter collisions anywhere?
> If yes, please report.
>
> Cheers,
>   Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Whiteout box function by Thomas Morley / need help

[Thomas Morley]

Hi Karol,

sorry coming back to you that late.

2014-04-21 13:22 GMT+02:00 Karol Majewski :
> Although I know nothing about scheme, I've managed to slim down this 
> function, so that there are no optional arguments. Now I'll try to find out 
> why it doesn't work for DynamicText grob.
>
It seems thee was some change in the source concerning DynamicText.

Look at the attached images produced from the following code with
2.18.0 and 2.19.4

\new StaffGroup
<<
\new Staff \relative c' {
c1
\override DynamicText #'X-offset = #-20
\once \override DynamicText #'whiteout = ##t
c\f
c
}
\new Staff \relative c' {
c1 c c
}
>>

It seems now to be impossible to move DynamicText across BarLines.
(You can use 'extra-offset ofcourse, though it's usually a bad idea.)

Obviously, it was made to avoid any BarLine/DynamicText collisions.
If it always works, there would be no more need for any whiteout
function for DynamicText.

Do you encounter collisions anywhere?
If yes, please report.

Cheers,
  Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Newbie problem in my first or second score

[Steve Lane]

Thanks, David and Federico — easy fix! All layout engines have their 
architectural weak spots, so that 's no surprise I guess.

I guess the rendering of that first sixteenth as a grace note in this piece is 
somewhat arbitrary anyway, since the first measure is always playes simply as 
four sixteenths. Doubtless some historical reason.

Thanks again,

SGL

From: David Nalesnik mailto:david.nales...@gmail.com>>
Date: Monday, April 21, 2014 8:08 AM
To: Steve Lane mailto:sl...@soliantconsulting.com>>
Cc: "lilypond-user@gnu.org" 
mailto:lilypond-user@gnu.org>>
Subject: Re: Newbie problem in my first or second score

Hi Steve,


On Mon, Apr 21, 2014 at 7:02 AM, Steve Lane 
mailto:sl...@soliantconsulting.com>> wrote:
Hello all:

So I am trying to lay out the first bars of Mozart's Sonata K 333. The first 
measure is a partial measure. No matter what I try so far, I'm getting an extra 
time and key signature in the bass clef, in addition to the bass clef first 
displaying as treble, then adding a bass clef in:

[cid:83EBF439-2841-4760-BBD0-2FAB1A935715]

The code is as follows (I didn't see how to make it tinier):

\version "2.18.2"
\include "english.ly"

keyTime = { \key bf \major \time 4/4 }

upper = \relative c''' {
  \partial 4 \grace g16 f8 ef16 d |
}

lower = {
  \partial 4 r4 |
}

\score {
  \new PianoStaff <<
\new Staff = "upper" { \clef "treble" \keyTime \upper }
\new Staff = "lower" { \clef "bass" \keyTime  \lower }
  >>
}


Any help appreciated :-)


Welcome to LilyPond!

Sorry you had to discover so quickly perhaps the most persistent bug in the 
program.

It's easily fixed, though: add a corresponding grace spacer to the other part 
at the same point.

\partial 4 \grace s16 r4

--David

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Newbie problem in my first or second score

[Federico Bruni]

Hi Steve

It's an old issue called "grace synchronization":
https://code.google.com/p/lilypond/issues/detail?id=34

2014-04-21 14:02 GMT+02:00 Steve Lane :

> The code is as follows (I didn't see how to make it tinier):
>
>  \version "2.18.2"
> \include "english.ly"
>
>  keyTime = { \key bf \major \time 4/4 }
>
>  upper = \relative c''' {
>   \partial 4 \grace g16 f8 ef16 d |
> }
>
>
add a \grace with spacer rest here as a workaround


>  lower = {
>   \partial 4 \grace s16 r4 |
> }
>
>  \score {
>   \new PianoStaff <<
> \new Staff = "upper" { \clef "treble" \keyTime \upper }
> \new Staff = "lower" { \clef "bass" \keyTime  \lower }
>   >>
> }
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Newbie problem in my first or second score

[David Nalesnik]

Hi Steve,


On Mon, Apr 21, 2014 at 7:02 AM, Steve Lane wrote:

>  Hello all:
>
>  So I am trying to lay out the first bars of Mozart's Sonata K 333. The
> first measure is a partial measure. No matter what I try so far, I'm
> getting an extra time and key signature in the bass clef, in addition to
> the bass clef first displaying as treble, then adding a bass clef in:
>
>
>  The code is as follows (I didn't see how to make it tinier):
>
>  \version "2.18.2"
> \include "english.ly"
>
>  keyTime = { \key bf \major \time 4/4 }
>
>  upper = \relative c''' {
>   \partial 4 \grace g16 f8 ef16 d |
> }
>
>  lower = {
>   \partial 4 r4 |
> }
>
>  \score {
>   \new PianoStaff <<
> \new Staff = "upper" { \clef "treble" \keyTime \upper }
> \new Staff = "lower" { \clef "bass" \keyTime  \lower }
>   >>
> }
>
>
>  Any help appreciated :-)
>
>
Welcome to LilyPond!

Sorry you had to discover so quickly perhaps the most persistent bug in the
program.

It's easily fixed, though: add a corresponding grace spacer to the other
part at the same point.

\partial 4 \grace s16 r4

--David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Newbie problem in my first or second score

[Steve Lane]

Hello all:

So I am trying to lay out the first bars of Mozart's Sonata K 333. The first 
measure is a partial measure. No matter what I try so far, I'm getting an extra 
time and key signature in the bass clef, in addition to the bass clef first 
displaying as treble, then adding a bass clef in:

[cid:83EBF439-2841-4760-BBD0-2FAB1A935715]

The code is as follows (I didn't see how to make it tinier):

\version "2.18.2"
\include "english.ly"

keyTime = { \key bf \major \time 4/4 }

upper = \relative c''' {
  \partial 4 \grace g16 f8 ef16 d |
}

lower = {
  \partial 4 r4 |
}

\score {
  \new PianoStaff <<
\new Staff = "upper" { \clef "treble" \keyTime \upper }
\new Staff = "lower" { \clef "bass" \keyTime  \lower }
  >>
}


Any help appreciated :-)

Thanks,

Steve Lane
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: voice solfege sequence

[MING TSANG]

Hi, Thomas:
On Monday, April 21, 2014 4:32:34 AM, Thomas Morley  
wrote:
 
2014-04-20 23:46 GMT+02:00 MING TSANG :

> Thank you for modify the solfege-engraver.
> I copy and paste into the .ly file and ran.  Result: The below staff seems
> working, but "\xup" suppose to put the solfege above staff and now it is put
> below the staff instead - and the stacking is not right.  Any idea?

Hi Ming,

I can't reproduce the image you posted.
On my machine, the attached code returns the attached image.
Please tell me whats wrong with it.

Cheers,

  Harm


Thank you for the attachments.  I desk check your .ly file with my .ly file and 
discover my f.ly file miss the following line:
"  (set! (ly:grob-property newgrob 'direction) dir)  "
After I copy and paste the line to my .ly file, it works.  Thank you very much.
BTW can the notehead color be retained to show on solfege above the staff?  
Emmanuel,
Ming___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Whiteout box function by Thomas Morley / need help

[Karol Majewski]

Although I know nothing about scheme, I've managed to slim down this function, 
so that there are no optional arguments. Now I'll try to find out why it 
doesn't work for DynamicText grob.

Harm, thanks in advance for any hints. Perhaps we can mix your function with 
flexible-stencil-whiteout (see my first post).

%

\version "2.19.5"

moreWhiteout =
#(define-music-function
  (parser location adds)
  (pair?)
  (define
(interval-add iv-1 iv-2)
(cons
  (+
(car iv-1)
(car iv-2))
  (+
(cdr iv-1)
(cdr iv-2
  (define more-stencil-whiteout
(lambda
  (grob)
  (let*
((stil
(ly:text-interface::print grob))
  (x-ext
(ly:stencil-extent stil X))
  (y-ext
(ly:stencil-extent stil Y))
  (add-to-x-ext
(if
  (pair?
(car adds))
  (car adds) adds))
  (add-to-y-ext
(if
  (pair?
(cdr adds))
  (cadr adds) '(0 . 0)))
  (new-stil
(ly:make-stencil
  (ly:stencil-expr stil)
  (interval-add x-ext add-to-x-ext)
  (interval-add y-ext add-to-y-ext new-stil)))
  #{
\once \override DynamicText . layer = #10
\once \override DynamicText . whiteout = ##t
\once \override DynamicText . stencil = #more-stencil-whiteout
  #})

%%%
%% EXAMPLE
%%%

musicI = { \time 2/4 \repeat unfold 16 b8 }

musicII = {
  r2
  %% apply to X- and Y-axis
  \moreWhiteout #'((-2 . 0.5)(0 . 2))
  b4 \ff b
  r2
  %% apply to X-axis only
  \moreWhiteout #'(-2 . 0.5)
  b4 \mf b
}


\new StaffGroup <<
  \new Staff \relative c'' \musicI
  \new Staff \relative c'' \musicII
>>

%


-- Karol



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: voice solfege sequence

[Thomas Morley]

2014-04-20 23:46 GMT+02:00 MING TSANG :

> Thank you for modify the solfege-engraver.
> I copy and paste into the .ly file and ran.  Result: The below staff seems
> working, but "\xup" suppose to put the solfege above staff and now it is put
> below the staff instead - and the stacking is not right.  Any idea?

Hi Ming,

I can't reproduce the image you posted.
On my machine, the attached code returns the attached image.
Please tell me whats wrong with it.

Cheers,
  Harm
\version "2.19.4"

\language "english"

%%%\include "include_solfege-engraver.ly"
#(define syllables '("do" "re" "mi" "fa" "so" "la" "ti"))
#(define syls '("d" "r" "m" "f" "s" "l" "t"))
#(define numR➀ '("➀" "➁" "➂" "➃" "➄" "➅" "➆"))
#(define number '("1" "2" "3" "4" "5" "6" "7"))
#(define numR➑ '("➊" "➋" "➌" "➍" "➎" "➏" "➐"))

#(define (solfege-engraver lst dir)
   (make-engraver 
 (acknowledgers
  ((note-head-interface engraver grob source)
   (let* (
  (context (ly:translator-context engraver))
  (tonic-pitch (ly:context-property context 'tonic))
  (tonic-index (ly:pitch-notename tonic-pitch))
  (event (ly:grob-property grob 'cause))
  (event-copy (ly:event-deep-copy event))
  (grob-pitch (ly:event-property event 'pitch))
  (grob-index (ly:pitch-notename grob-pitch))
  (delta (modulo (- grob-index tonic-index) 7))
  (name (list-ref lst delta))
  (newgrob (ly:engraver-make-grob engraver 'TextScript event-copy)))

 ;; clear 'tweaks for newgrob
 (ly:event-set-property! event-copy 'tweaks '()) 
 (if (string= name "Hb")  (set! name "B"))
 ;; Give newgrob 'outside-staff-priority depending on 
 ;; grob 'staff-position
 (set! (ly:grob-property newgrob 'outside-staff-priority)
   (+ (ly:grob-property newgrob 'outside-staff-priority)
  (* dir (ly:grob-property grob 'staff-position
 (set! (ly:grob-property newgrob 'text) name)
 (set! (ly:grob-property newgrob 'direction) dir) )


xup = \with { \consists #(solfege-engraver syllables UP) }
xdown = \with { \consists #(solfege-engraver syllables DOWN) }
zup= \with { \consists #(solfege-engraver syls UP) }
zdown= \with { \consists #(solfege-engraver syls DOWN) }
nup= \with { \consists #(solfege-engraver number  UP) }
ndown= \with { \consists #(solfege-engraver number  DOWN) }
rup= \with { \consists #(solfege-engraver numR➀ UP) }
rdown= \with { \consists #(solfege-engraver numR➀ DOWN) }
sup= \with { \consists #(solfege-engraver numR➑ UP) }
sdown= \with { \consists #(solfege-engraver numR➑ DOWN) }
%end
clors =
#(define-music-function (parser location which color music)
((procedure? car) color? ly:music?)
  (music-map
(lambda (mus)
  (if (music-is-of-type? mus 'event-chord)
  (let* ((evt-chrd-nts (event-chord-notes mus)))
   (if (> (length evt-chrd-nts) 1)
   (let ((first-nh (which evt-chrd-nts)))
 #{ \tweak #'color #color #first-nh #})
   mus)
mus)
  mus))
music)) % default #first #last is the top notehead 
%
 boo =
#(define-music-function
  (parser location color the-music)
  (color? ly:music?)
#{
  \temporary 
  \override NoteHead.color = #color
 
  #the-music
  \revert NoteHead.color
  
#})%\boo#blue {..}

SA = {
  d''4. d''8 d''8 8 8 f'8 |%m73
  <<{\voiceOne a'2 a'4 f'8 e'8}\new Voice{\voiceTwo \boo#red {c'4 d'4 f'4 f'4} }>> \oneVoice |%m74
  d'4. 8 8 8 q4 |%m75
}

verseA = \lyricmode {
  re re re mi re fa la la fa mi re so so so re  
}


<<
\new Staff \with { \xup

  } <<
  \new Voice = "soprano" { 
  \voiceOne \clors #first #red \SA 
  }
  >>
  \new Lyrics \lyricsto "soprano" \verseA
>>

<<
\new Staff \with { \xdown

  } <<
\new Voice = "soprano"  { \voiceOne \clors #first #blue \SA }
  >>
  \new Lyrics 
\lyricsto "soprano" \verseA
>>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Hairping length

[Pierre Perol-Schneider]

2014-04-21 9:43 GMT+02:00 Helge Kruse :

> Hello,
>

Hi Helge
Same as Jan-Peter and Janek.
Check here :
http://www.lilypond.org/doc/v2.18/Documentation/notation/expressive-marks-attached-to-notes#dynamics
(go to selected snippets)

~Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Hairping length

[Janek Warchoł]

2014-04-21 9:43 GMT+02:00 Helge Kruse :
> Hello,
>
> I just read about some open Mutopia requests
> (https://github.com/chrissawer/The-Mutopia-Project/issues/355) and started
> typesetting for fun. Unfortunately the fun vanished after some measures of
> issue #361.
>
> So here comes the Lilypond related problem:
>
> \version "2.18.0"
> \relative c'' {
>   \time 2/4
>   \key e\major
>   r8 r r e(\< |
>   fis4)\! r|
>   r8 e(\< fis4)\!
> }


I think to-barline property of hairpins should help you.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Hairping length

[Jan-Peter Voigt]

Hello Helge,

just a shorty

\relative c'' { c4 b\< bes\! \override Hairpin.to-barline = ##f a\< | g\! }


HTH
Jan-Peter



On 21.04.2014 09:43, Helge Kruse wrote:
> So here comes the Lilypond related problem:
>
> \version "2.18.0"
> \relative c'' {
>   \time 2/4
>   \key e\major
>   r8 r r e(\< |
>   fis4)\! r|
>   r8 e(\< fis4)\!
> }
>
> This chunk shows two hairpins. Obviously the first is too short. It
> should have been longer then the second because of the additional bar
> line. 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Hairping length

[Helge Kruse]

Hello,

I just read about some open Mutopia requests 
(https://github.com/chrissawer/The-Mutopia-Project/issues/355) and 
started typesetting for fun. Unfortunately the fun vanished after some 
measures of issue #361.


So here comes the Lilypond related problem:

\version "2.18.0"
\relative c'' {
  \time 2/4
  \key e\major
  r8 r r e(\< |
  fis4)\! r|
  r8 e(\< fis4)\!
}

This chunk shows two hairpins. Obviously the first is too short. It 
should have been longer then the second because of the additional bar 
line. I "managed to fix" the problem with this code:


\relative c'' {
  \time 2/4
  \key e\major
  r8 r r
<<
{ \oneVoice e( | fis4)  } \\
{ s8\< | s8 s\! }
>> r4 |
  r8 e(\< fis4)\!
}

But I think this can't be the solution. Is there a better way to 
circumvent the problem?



Best Regards
Helge





smime.p7s
Description: S/MIME Kryptografische Unterschrift
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Locating X/Y positions of staves and bars in PNG output

[Urs Liska]

Am 21.04.2014 09:09, schrieb Mike Solomon:

On Apr 21, 2014, at 1:17 AM, David Hinkle  wrote:


I'm working on a new GPL web application designed to help new people learn to 
sing using the new FFT capabilities of HTML5.  (Git hub links below if you're 
interested).

I'd like to use Lilypond to generate scores for display in the app.  In order 
to show the user the feedback about where they're singing I'd like to 
superimpose that feedback on the score, but I need to know the X/Y positions of 
the bars and staves.

I'm willing to go so far as to modify Lilypond to export this information when 
it generates an PNG but I'd like to ask the list first if they have any other 
ideas, and if not, maybe they could point me to the best place to start 
tinkering with Lilypond source to get the information exported.

My Proof of concept:
https://github.com/drachs/singingPractice

A live example of precisely identifying the frequency of a tone and displaying 
it on a staff.  Blue line is the precise frequency based on a curve fit of the 
FFT, red bars are fft output.   White lines are bass and treble clef staff 
lines.  (Staff lines are spread further out as the frequency gets higher

https://rawgit.com/drachs/singingPractice/2d53330f77122a435063b57dd5322418851510a4/notedisplay.html


LilyPond may not be the best tool to do what you want.

For short examples, check out the GUIDO server.

http://guidoeditor.grame.fr

It sends scores to a server in realtime and recuperates either a canvas or a 
png (http://guidoeditor.grame.fr/png.html).  The public API has methods that 
generate what are called
Time2GraphicMap, which give you this type of XY information.

GUIDO is available at http://sourceforge.net/p/guidolib/code/ci/master/tree/.

For LilyPond, I’d recommend using the SVG to get data about where things are 
placed globally.


Yes, this could give you the information you need, in addition you 
_might_ be able to use JavaScript to post-process the results in the 
browser.


You may have a look at
https://github.com/PeterBjuhr/frescobaldi/tree/svg-edit/frescobaldi_app/svgview

and particularly
https://github.com/PeterBjuhr/frescobaldi/blob/svg-edit/frescobaldi_app/svgview/editsvg.js

to get a feeling what might be possible.
This is a completely different task but it shows you the interaction 
between JavaScript and a LilyPond-SVG. You may start reading the 
DraggableObject constructor.


HTH
Urs



Cheers,
MS



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Locating X/Y positions of staves and bars in PNG output

[Mike Solomon]

On Apr 21, 2014, at 1:17 AM, David Hinkle  wrote:

> I'm working on a new GPL web application designed to help new people learn to 
> sing using the new FFT capabilities of HTML5.  (Git hub links below if you're 
> interested).
> 
> I'd like to use Lilypond to generate scores for display in the app.  In order 
> to show the user the feedback about where they're singing I'd like to 
> superimpose that feedback on the score, but I need to know the X/Y positions 
> of the bars and staves.
> 
> I'm willing to go so far as to modify Lilypond to export this information 
> when it generates an PNG but I'd like to ask the list first if they have any 
> other ideas, and if not, maybe they could point me to the best place to start 
> tinkering with Lilypond source to get the information exported.
> 
> My Proof of concept:
> https://github.com/drachs/singingPractice
> 
> A live example of precisely identifying the frequency of a tone and 
> displaying it on a staff.  Blue line is the precise frequency based on a 
> curve fit of the FFT, red bars are fft output.   White lines are bass and 
> treble clef staff lines.  (Staff lines are spread further out as the 
> frequency gets higher
> 
> https://rawgit.com/drachs/singingPractice/2d53330f77122a435063b57dd5322418851510a4/notedisplay.html

LilyPond may not be the best tool to do what you want.

For short examples, check out the GUIDO server.

http://guidoeditor.grame.fr

It sends scores to a server in realtime and recuperates either a canvas or a 
png (http://guidoeditor.grame.fr/png.html).  The public API has methods that 
generate what are called 
Time2GraphicMap, which give you this type of XY information.

GUIDO is available at http://sourceforge.net/p/guidolib/code/ci/master/tree/.

For LilyPond, I’d recommend using the SVG to get data about where things are 
placed globally.

Cheers,
MS___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user