Re: official GNU LilyPond maintainer

[Thomas Morley]

2016-12-27 6:25 GMT+01:00 Graham Percival :
> With David stepping down, LilyPond is left without an official GNU
> maintanier.  Does anybody want to do fill this role?  The relevant
> documentation is:
> https://www.gnu.org/prep/standards/html_node/index.html
> https://www.gnu.org/prep/maintain/html_node/index.htm
>
> If nobody is interested in the position, I am willing to take it
> up again.



That would be great!

Cheers,
  Harm

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

Re: [PATCH [uploaded to Rietveld]] Automatic lyric extenders

[Alexander Kobel]

On 2016-12-27 21:25, Trevor Daniels wrote:

Alexander Kobel wrote Monday, December 26, 2016 1:00 AM

Oh well, it's late. I didn't spot measure 7, with the 8( 8) in alto.
Same there.
And, of course, you should have an extender there in the second verse,
and you should have extenders in measure 1 (was/was/shall) an measure 9
(shall/shall/was); but that's a limitation of the satb-template (or,
rather, a lack of voice assignment) that's beyond this patch to correct.


Well spotted!  In fact there are several other places where the lyric
alignment was wrong.  At the time I posted it it was a work-in-progress
(for Christmas 2017, in fact), but thank you for helping with the final
tweaks :)  For interest, I attach the latest version, hopefully now almost
correct, albeit several messy tweaks!  Can you spot any other improvements?


To be honest, I'm not sure whether I should be proud of spotting some - 
after this year's last rehearsal, six beers and two schnapps, and an 
obscene level of alcohol blocking my mind. But still, opening the PDF on 
my smartphone, the first thing that came to my mind is: there must be 
something wrong with the kerning of Lily's extenders. And the 
antialiasing of the Android PDF reader sucks, the lines have different 
thickness...

But no, there's fake extenders.

Not sure if it's any good to become too aware of certain details... ;-)


It will make a useful test as the various improvements to LP which you
outline below take effect.  One day maybe all the tweaks can be removed.


In fact, to solve this, one would need a simultaneous assignment of the
lyrics to all four voices they apply to. Basically, a \addlyrics
\lyricsto ChoirStaff.


That would indeed be a great improvement - once it can be made to work!


Yes. Unfortunately, that'll be the only cure to the workarounds, or 
really annoying manual voice-switching within the lyrics.



(Note 1 to whom it may concern, including myself: once this works, the
satb and ssaattbb templates should be changed to associate the Verse*
lyrics with the entire ChoirStaff, and *Lyrics with the corresponding
Staff per default.)


I'd be happy to make this change as soon it it becomes available.


Great to hear. I've never used the templates, mostly to circumvent that 
restriction. I think I'll be a happy user once the extender is fixed...



(Note 2 to whom it may concern, including myself: we should have auto
extender regtests for \lyricsto ctx = name, for at least ctx = Voice,
Staff, ChoirStaff.)


Yes.


Essentially, my recent bug report should be enough for a regtest.


Cheerio, Miss Sophie! (Sorry, can't help. Not sure if you share our 
nation's yearly half-an-hour of British humour with "Dinner for One" on 
the isles - it's Germany's traditional New Year's Eve TV entertainment...)

Alexander

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

Re: Free alternatives to Rietveld?

[Simon Albrecht]

Thanks for the heads-up on previous discussions, now I know more about 
the pitfalls.


Also I see now that the ultimate free alternative would likely be the 
one Jan N. brought up in that old discussion, namely exchanging patches 
via e-mail only. Which makes sense with git’s design, however the 
side-by-side diff features of Rietveld are excellent and I wouldn’t miss 
them.


I hope my problems with the Google login will soon cease (I wrote a 
complaint and didn’t hold back my annoyment too much).


Best,
Simon


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

Re: Automatic LyricExtenders (issue 313240043 by perpeduumimmob...@gmail.com)

[Knut Petersen]

Am 27.12.2016 um 03:01 schrieb perpeduumimmob...@gmail.com:

On 2016/12/26 19:14:00, pkx166h wrote:

On 2016/12/25 21:53:55, akobel wrote:
> Bottom line: I withdraw both proposals.



Can you then re-submit a new patch or delete the one(s) that are

invalid?

Sorry, I'm a bit drawn up between my position as the Rietveld-proxy of
Knut and my own Alexander-role as a commenter.
I forwarded all patches by Knut, and I withdrew my two comments from #5
and the one from the mailing list that Knut answered in #6. 


I'll prepare a new patchset in a few days, thanks for the comments that were 
posted up to now.

Cheers,
 Knut

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

Re: Delete new LSR-snippet?

[Trevor Daniels]

Knut Petersen wrote Friday, December 23, 2016 11:53 PM

Harm, would this be a better snippet for the LSR?

>> I seem to remember a post or maybe an LSR entry for placing
>> divisi arrows at the end of a staff.  Maybe this could be
>> adapted to achieve the same effect more reliably?
>>
>> Found it  - LSR 650.  It modifies the barline stencil.
> 
> Something like the following code  could be a base:
> 
> \version "2.19.53"
> 
> mpBarLine = {
>   \once \override Staff.BarLine #'stencil =
> #(lambda (grob) (ly:stencil-combine-at-edge (ly:bar-line::print grob) X 
> RIGHT
> (grob-interpret-markup grob mpBarLineMarkup) 0))
>   \break
> }
> 
> mpBarLineMarkup = \markup \with-dimensions #'(0 . 0) #'(0 . 0) {
>   \line {\hspace #3 \override #'(line-width . 20)
>  \justify{This is a marginal note}
>   }
> }
> 
> \paper {
>   left-margin = 2\cm
>   line-width = 14\cm
>   indent = 0\cm
>   ragged-right = ##f
> }
> 
> {
>   \repeat unfold 16 { c'' 4 } \break
>   \repeat unfold 16 { c'' 4 } \mpBarLine
>   \repeat unfold 16 { c'' 4 } \bar "|."
> }
> 
> \layout {}

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

Re: [PATCH [uploaded to Rietveld]] Automatic lyric extenders

[Trevor Daniels]

Alexander Kobel wrote Monday, December 26, 2016 1:00 AM


> Oh well, it's late. I didn't spot measure 7, with the 8( 8) in alto. 
> Same there.
> And, of course, you should have an extender there in the second verse, 
> and you should have extenders in measure 1 (was/was/shall) an measure 9 
> (shall/shall/was); but that's a limitation of the satb-template (or, 
> rather, a lack of voice assignment) that's beyond this patch to correct.

Well spotted!  In fact there are several other places where the lyric
alignment was wrong.  At the time I posted it it was a work-in-progress
(for Christmas 2017, in fact), but thank you for helping with the final
tweaks :)  For interest, I attach the latest version, hopefully now almost
correct, albeit several messy tweaks!  Can you spot any other improvements?
It will make a useful test as the various improvements to LP which you 
outline below take effect.  One day maybe all the tweaks can be removed.
 
> In fact, to solve this, one would need a simultaneous assignment of the 
> lyrics to all four voices they apply to. Basically, a \addlyrics 
> \lyricsto ChoirStaff.

That would indeed be a great improvement - once it can be made to work!

> (Note 1 to whom it may concern, including myself: once this works, the 
> satb and ssaattbb templates should be changed to associate the Verse* 
> lyrics with the entire ChoirStaff, and *Lyrics with the corresponding 
> Staff per default.)

I'd be happy to make this change as soon it it becomes available.
 
> (Note 2 to whom it may concern, including myself: we should have auto 
> extender regtests for \lyricsto ctx = name, for at least ctx = Voice, 
> Staff, ChoirStaff.)

Yes.

Trevor
\version "2.19.52"

#(set-global-staff-size 17)

\header {
  title = "As Joseph was A-Walking"
  subtitle = ""
  subsubtitle = ""
  composer = "Trad."
  arranger = "arr. R.R.Terry"
  poet = ""
  revisionDate = \markup {
%"4 Dec 2016"  % first draft
"27 Dec 2016"  % tweaks to lyrics alignments
  }
}

TwoVoicesPerStaff = ##t

SopranoMidiInstrument = "voice oohs"
AltoMidiInstrument = "voice oohs"
TenorMidiInstrument = "choir aahs"
BassMidiInstrument = "choir aahs"

sd = \once \slurDashed
td = \once \tieDashed
la = \once \override LyricText.self-alignment-X = #LEFT
nudgeR =
#(define-music-function (alignment) (number?)
#{ \once \override LyricText.parent-alignment-X = #alignment #})

Time = {
  \set melismaBusyProperties = #'()
  \numericTimeSignature
  \time 6/8
  \key ees \major
  \tempo "Andante" 4. = 56
  \repeat volta 2 {
\partial 8
s8 |
s2.*7 |
s4. s4
  }
  \break
  \repeat volta 2 {
s8 |
s2.*7 |
s4. s4
  }
}

SopranoMusic = \relative {
  ees'8 |
  g4 bes8 c4 d8 |
  \sd ees4\=1(\=2( bes8\=1) g4\=2) bes8 |
  c4 ees8 d4 c8 |
  bes4.~ 4 c16( d) |
  \sd ees4( d8) c( d) ees |
  \sd bes4\=1(\=2( g8\=1) ees4\=2) f8 |
  \sd g8\=1(\=2( f\=1) ees\=2) \sd bes'4( g8) |
  ees4.~ 4

  ees8 |
  g4 bes8 c4 d8 |
  \sd ees4( bes8) g4 bes8 |
  c4 ees8 d4 c8 |
  bes4.~ 4 c16( d) |
  \sd ees4( d8) c( d) ees |
  \sd bes4\=1(\=2( g8\=1) ees4\=2) f8 |
  \sd g8\=1(\=2( f\=1) ees\=2) \sd bes'4( g8) |
  ees4.~ 4
}

AltoMusic = \relative {
  bes8 |
  ees4 8 4 f8 |
  \sd g4\=1(\=2( f8\=1) ees4\=2) 8 |
  ees4 8 aes4 8 |
  aes4.( g4) ees8 |
  \td ees4~ 8 ees( f) g |
  \sd f4\=1(\=2( d8\=1) ees4\=2) 8 |
  \td ees4~ 8 \sd d\=1(\=2( c\=1) d\=2) |
  ees4( c8 bes4)

  bes8 |
  ees4 8 4 f8 |
  \sd g4( f8) ees4 8 |
  ees4 8 aes4 8 |
  aes4.( g4) ees8 |
  \td ees4~ 8 ees( f) g |
  \sd f4\=1(\=2( d8\=1) ees4\=2) 8 |
  \td ees4~ 8 \sd d\=1(\=2( c\=1) d\=2) |
  ees4( c8 bes4)
}

TenorMusic = \relative {
  g8 |
  bes4 8 aes 4 8 |
  \td \sd bes4~( 8 4) g8 |
  aes4 g8 aes4 c8 |
  f8.( d16 bes8 ees4) c8 |
  \td bes4~ 8 aes4 bes8 |
  \sd \td bes4~( 8 g4) c8 |
  \sd bes4( g8) \sd aes4( bes8) |
  g4( aes8 g4)

  g8 |
  bes4 8 aes 4 8 |
  \td bes4~ 8 4 g8 |
  aes4 g8 aes4 c8 |
  f8.( d16 bes8 ees4) c8 |
  \td bes4~ 8 aes4 bes8 |
  \sd \td bes4~( 8 g4) c8 |
  \sd bes4( g8) \sd aes4( bes8) |
  g4( aes8 g4)
}

BassMusic = \relative {
  ees8 |
  ees8.( f16) g8 aes8.( g16) f8 |
  \sd ees4\=1(\=2( d8\=1) ees4\=2) 8 |
  aes,4 c8 f4 ees8 |
  d4.( ees4) aes8 |
  \td g4~ 8 aes4 ees8 |
  \sd d4\=1(\=2( bes8\=2) c4\=1) aes8 |
  \sd bes4( c8) \td bes4~ 8 |
  c8.( bes16 aes8 ees'4)

  ees8 |
  ees8.( f16) g8 aes8.( g16) f8 |
  \sd ees4( d8) ees4 8 |
  aes,4 c8 f4 ees8 |
  d4.( ees4) aes8 |
  \td g4~ 8 aes4 ees8 |
  \sd d4\=1(\=2( bes8\=2) c4\=1) aes8 |
  \sd bes4( c8) \td bes4~ 8 |
  c8.( bes16 aes8 ees'4)
}

VerseOne = \lyricmode {
  \set stanza = "1."
  As \la Jo -- seph \la "was __" a -- walk -- _ ing,
  He heard an an -- gel sing, __ _
  This _ __ night __ _ shall _ be born __ _ _
  Our hea -- _ ven -- \la ly __ _ \nudgeR #-3 King. __ _

  \set stanza = "4."
  He \la nei -- ther \la shall __ be ro -- _ cked
  In sil -- ver or in gold, __ _
  But _ in a woo -- _ den cra -- _ dle
  That rocks __ _ _ \la "on___" the \nudgeR #-3 mould. __ _
}

VerseTwo = \lyricmode {
  

Re: Offer to help development: Convert MIDI to Lilypond

[Graham Percival]

On Tue, Dec 27, 2016 at 08:43:34AM +0100, k...@aspodata.se wrote:
> Graham:
> > That is correct; the python midi2ly conversion is quite
> > independent of the rest of LilyPond.  As a result, it is an
> > excellent place to begin!  :)
> 
> So I propose that a better course of action would be to research

Thank you for the suggestion.

At the moment, it appears that midi.c is broken on at least one
architecture.  Fixing it would be a pain, and would do nothing to
reduce the problem it poses.  Moving to a completely python
solution would represent a solid step forward, both in terms of
reducing technical debt, and also in terms of a new contributor
getting familiar with our development process.

At that point, an interested person -- perhaps yourself? -- could
offer further patches which improved the quality of the lilypond
code.

Cheers,
- Graham

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

Re: Free alternatives to Rietveld?

[Graham Percival]

On Tue, Dec 27, 2016 at 02:39:09PM +, James wrote:
> On Tue, 27 Dec 2016 13:33:11 +0100
> Simon Albrecht  wrote:
> 
> > Whatever the reason for this weirdness, I think it would really be 
> > better if we had a code review tool which didn’t rely on external
> > login providers. Is there really no free alternative?
> 
> We had a 'similar' discussion back in 2013
> 
> http://lists.gnu.org/archive/html/lilypond-devel/2013-09/msg00351.html

Heh, yes!

I'm aware of problems with the existing setup -- in fact, my first
few patches were delayed by half a week because I had problems
setting it up.  Quite apart from the loss of time, that was a huge
drain on my energy and motivation.

A week ago, I started investigating alternatives.  As always, my
primary motivation is *not* adding any additional burden to our
experienced developers.  I have not yet reached the point at which
it would be useful to discuss any proposals on -devel, though.

(As we can see from the 2013 emails, a very wide-ranging
discussion quickly becomes bogged down and fails to produce
results.  If anybody is very interested in the "alternatives"
question and is willing to do 2-5 hours of work that will probably
end up being discarded, feel free to contact me off-list.)

Cheers,
- Graham

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

Re: Arrow-glyphs in Feta (was: \arrow markup command)

[tisimst]

Hi, Simon!

On Tue, Dec 27, 2016 at 9:11 AM, Simon Albrecht-2 [via Lilypond] <
ml-node+s1069038n198583...@n5.nabble.com> wrote:

> On 23.12.2016 22:34, Simon Albrecht wrote:
> > Why does the Feta font have one glyph for each of the 4 directions in
> > which an arrow head generated with \arrow-head can point? Why not
> > simply rotate one glyph in the first place? (I’m sure the Metafont
> > code does just that, though it would strike me more logical to do it
> > on a ‘higher’ level.)
>
> Can anyone comment on this Feta question?


Here's what I could tell from looking at the source code. The function
first creates one barb of the arrow, then mirrors it vertically to create
the full arrowhead. Without any other transformations, this creates the
right-pointing arrowhead. Each of the other glyphs follow the same steps to
this point, and then transforms the glyph, either by negative scaling or by
rotation, to get the others. This applies for both open and closed
arrowheads.

HTH,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/arrow-markup-command-tp198440p198587.html
Sent from the Dev mailing list archive at Nabble.com.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Arrow-glyphs in Feta (was: \arrow markup command)

[Simon Albrecht]

On 23.12.2016 22:34, Simon Albrecht wrote:
Why does the Feta font have one glyph for each of the 4 directions in 
which an arrow head generated with \arrow-head can point? Why not 
simply rotate one glyph in the first place? (I’m sure the Metafont 
code does just that, though it would strike me more logical to do it 
on a ‘higher’ level.) 


Can anyone comment on this Feta question?

Best, Simon

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

Re: Free alternatives to Rietveld?

[James]

On Tue, 27 Dec 2016 13:33:11 +0100
Simon Albrecht  wrote:

> Hello everybody,
> 
> just now I tried to login with Google in order to close my two recent 
> Rietveld reviews. However, Google decided that despite entering a 
> verification code from e-mail it couldn’t confirm me being authorised
> to login. So I’m currently out. Maybe they want to force me to give a 
> mobile phone number?
> 
> Whatever the reason for this weirdness, I think it would really be 
> better if we had a code review tool which didn’t rely on external
> login providers. Is there really no free alternative?
> 

We had a 'similar' discussion back in 2013

http://lists.gnu.org/archive/html/lilypond-devel/2013-09/msg00351.html

(just in case anyone is interested).

James

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

Re: Free alternatives to Rietveld?

[Simon Albrecht]

On 27.12.2016 14:09, Urs Liska wrote:

While we're at it: is there really no tool that integrates with Git directly?

I find it pretty inconvenient and partly unreliable that the author is 
responsible himself that what is pushed actually is what has been reviewed.


Well, I had a brief look at some of the free tools on 
, and IIUC 
most of them are intended mainly for hosting the source code and also 
integrate a tool for code review. So sensibly they would do just that 
which you request.
So one /conceivable/ solution would be developing a code review tool for 
Savannah.


Best, Simon

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

Re: Free alternatives to Rietveld?

[Urs Liska]

Am 27. Dezember 2016 13:33:11 MEZ, schrieb Simon Albrecht 
:
>Hello everybody,
>
>just now I tried to login with Google in order to close my two recent 
>Rietveld reviews. However, Google decided that despite entering a 
>verification code from e-mail it couldn’t confirm me being authorised
>to 
>login. So I’m currently out. Maybe they want to force me to give a 
>mobile phone number?
>
>Whatever the reason for this weirdness, I think it would really be 
>better if we had a code review tool which didn’t rely on external login
>
>providers. Is there really no free alternative?

While we're at it: is there really no tool that integrates with Git directly?

I find it pretty inconvenient and partly unreliable that the author is 
responsible himself that what is pushed actually is what has been reviewed.

Urs

>
>Best, Simon
>
>
>___
>lilypond-devel mailing list
>lilypond-devel@gnu.org
>https://lists.gnu.org/mailman/listinfo/lilypond-devel

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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

Re: Free alternatives to Rietveld?

[Thomas Morley]

Hi Simon,

2016-12-27 13:33 GMT+01:00 Simon Albrecht :
> Hello everybody,
>
> just now I tried to login with Google in order to close my two recent
> Rietveld reviews. However, Google decided that despite entering a
> verification code from e-mail it couldn’t confirm me being authorised to
> login. So I’m currently out.

just checked with on of my Rietveld-issues which I forgot to close ...
No problems here.
So I can't help.

> Maybe they want to force me to give a mobile
> phone number?

They always want my phone number. I never gave it to them and I'll never do so.
Every time they ask I simply do "Go back one page" in my
FireFox-browser and continue from there.
So far it always worked.

Cheers,
  Harm

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

Free alternatives to Rietveld?

[Simon Albrecht]

Hello everybody,

just now I tried to login with Google in order to close my two recent 
Rietveld reviews. However, Google decided that despite entering a 
verification code from e-mail it couldn’t confirm me being authorised to 
login. So I’m currently out. Maybe they want to force me to give a 
mobile phone number?


Whatever the reason for this weirdness, I think it would really be 
better if we had a code review tool which didn’t rely on external login 
providers. Is there really no free alternative?


Best, Simon


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

PATCHES - Countdown for December 27th

[James]

Hello,

Here is the current patch countdown list. The next countdown will be on
December 30th.

A quick synopsis of all patches currently in the review process can be
found here:

http://philholmes.net/lilypond/allura/




Push:


5016 Web: minor improvements to the ‘Bug reports’ page - Simon Albrecht
https://sourceforge.net/p/testlilyissues/issues/5016
http://codereview.appspot.com/319880043


5015 Point to `\resetRelativeOctave` in NR 1.1.1.b - Simon Albrecht
https://sourceforge.net/p/testlilyissues/issues/5015
http://codereview.appspot.com/312210043


Countdown: No patches on Countdown at this time.


Review: No patches in Review at this time.


New: No New patches at this time.


Regards,

James

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

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

PATCHES - Countdown for December 27th

[James]

Hello,

Here is the current patch countdown list. The next countdown will be on
December 30th.

A quick synopsis of all patches currently in the review process can be
found here:

http://philholmes.net/lilypond/allura/




Push:


5016 Web: minor improvements to the ‘Bug reports’ page - Simon Albrecht
https://sourceforge.net/p/testlilyissues/issues/5016
http://codereview.appspot.com/319880043


5015 Point to `\resetRelativeOctave` in NR 1.1.1.b - Simon Albrecht
https://sourceforge.net/p/testlilyissues/issues/5015
http://codereview.appspot.com/312210043


Countdown: No patches on Countdown at this time.


Review: No patches in Review at this time.


New: No New patches at this time.


Regards,

James

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

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