Re: Small typo on LilyPond.org

[Graham Percival]

On Wed, Dec 07, 2016 at 11:54:33PM -, Phil Holmes wrote:
> If the documentation needed correcting, I'm in for a minimum 1.5
> hour build (sometimes 6 hours) and 5 hour upload (which also
> eats into my internet quota and stops my internet use at the
> time) to correct it.

Ouch, this might be misunderstood by some people.

- the website is AUTOMATICALLY regenerated HOURLY from our git
  repository.
- the website source is text.  In this case, the problem is:
  @emph{December 40, 2016}
- changing that line is the ONLY thing which is required to fix
  this problem.


As a nitpicky detail, this particular typo occurred within
  @ifset web_version
  ...
  @end ifset

so it has no impact on the documentation at all.  We can see that
by checking
http://lilypond.org/doc/v2.19/Documentation/web/

Also, I'm surprised that you considered updating the unstable
documentation -- if it's wrong, wouldn't we just wait for the next
unstable release?

Cheers,
- Graham

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

Re: Small typo on LilyPond.org

[Phil Holmes]

- Original Message - 
From: "Noeck" 

To: "Phil Holmes" ; 
Sent: Wednesday, December 07, 2016 10:06 PM
Subject: Re: Small typo on LilyPond.org





No problem.  Please feel free to provide a patch.


I would have a whole text based system. But this discussion is not wanted.

Btw, thanks a lot for your work, Phil!

Best,
Joram



Thanks.

Let me expand a little on my previous comment.

In the past, I've tried to fix simple typos like this by editing the files 
on lilypond.org directly.  This didn't work and made the situation worse. 
This time, I was concerned that simply changing the new "news" section and 
pushing to staging might correct part of the website, but not the 
documentation which might have also been wrong.  If the documentation needed 
correcting, I'm in for a minimum 1.5 hour build (sometimes 6 hours) and 5 
hour upload (which also eats into my internet quota and stops my internet 
use at the time) to correct it.  So my initial response was accurate - it 
seemed less hassle to wait a couple of weeks until my next upload, and 
guarantee to get it right without added effort.


I apologise if this seemed unhelpful.  It was an honest response to an 
honest mistake of mine.


--
Phil Holmes 



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

Re: exchange LyricHyphen with a "proper" hyphen

[Alexander Kobel]

On 2016-12-07 23:59, Thomas Morley wrote:

[...] So here a very first shot.
For now I let display the new _and_ the colored default LyricHyphen.
You'll see a drawback already: In tight situations the default gets
shortened until it vanishs. This is not possible or at least not
desirable for characters taken from a font, imho.
Iirc this was already mentioned in the discussion the tracker links to.
Maybe minimum-distance may help here, not tested though.


Yes, now that my memory is awake again, I seem to recall that I 
mentioned that few years ago already. At least shrinking should be 
undesirable for more than a very few percent of the width, similar to 
the microtype settings in the namesake LaTeX package.
Since I typically increase minimum-distance /and/ plan to revisit the 
magnetic-syllable-snap openlilylib snippet for this piece again, I hope 
that it won't be an issue.


Anyway, beautiful work, thanks a lot. I did not try it yet in real life, 
but will do so on the weekend and report back. In your test case, it 
works like a charm.



Cheers,
Alexander

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

Re: Chords in choral music(Re: Fixing LSR 888: center-on-words ignoring punctuation)

[Alexander Kobel]

On 2016-12-07 22:05, Simon Albrecht wrote:

On 07.12.2016 01:07, Alexander Kobel wrote:

chords with two adjacent notes (shifting one note). I know that this
should be a forbidden situation for vocal music


Why should it? I hardly think anybody should feel inclined to sing it
/non divisi/…


Of course, though some people seem to try their best to do so... ;-)
I meant that, IMHO, the cleaner way to notate such a situation is to use 
separate voices - after all, no singer should be able to sing two notes 
at once. In contrast to, say, a violin, which typically have a single 
note, but I've heard that sufficiently capable violinists are able to 
play (intentionally) (some well-chosen) chords.



Cheers,
Alexander

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

Re: Small typo on LilyPond.org

[Graham Percival]

On Wed, Dec 07, 2016 at 04:09:02PM -0700, SoundsFromSound wrote:
> Graham Percival-3 wrote
> > As always, I'm happy to mentor anybody who wants to contribute to
> > LilyPond.  There's plenty of work to go around, even for easy
> > typo-fixes like changing
> >   @emph{December 40, 2016}
> > to
> >   @emph{December 04, 2016}
> 
> Sorry if I started something by sending my initial email, I didn't think it
> was a super big issue -but I just figured it was a small simple

Thanks for the report!  Yes, this is a small simple thing to fix.

Cheers,
- Graham

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

Re: Small typo on LilyPond.org

[Thomas Morley]

2016-12-08 0:09 GMT+01:00 SoundsFromSound :
> Graham Percival-3 wrote
>> On Wed, Dec 07, 2016 at 10:46:14PM +0100, Noeck wrote:
>>> Am 07.12.2016 um 11:24 schrieb Phil Holmes:
>>> > it would be too much effort to fix something so minor
>>>
>>> From my naive point of view, there is something inherently wrong with a
>>> website system if it is too much effort to correct a typo...
>>
>> I agree, but thankfully that's not the case here.  I'm looking
>> forward to receiving your patch, Noeck!  :)
>>
>> As always, I'm happy to mentor anybody who wants to contribute to
>> LilyPond.  There's plenty of work to go around, even for easy
>> typo-fixes like changing
>>   @emph{December 40, 2016}
>> to
>>   @emph{December 04, 2016}
>>
>> Cheers,
>> - Graham
>>
>> ___
>> lilypond-user mailing list
>
>> lilypond-user@
>
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
> Sorry if I started something by sending my initial email, I didn't think it
> was a super big issue -but I just figured it was a small simple HTML
> oversight or something. Wasn't my intention to make this anything big,
> sorry. I have no experience (or insider-knowledge on) how LilyPond.org HTML
> is maintained from within regarding protocol and chain of command.
>
> Just trying to help.



No need to feel sorry about anything here.
You _did_ help!!

Reporting such issues is the very first step to get it fixed.

More, if we find a method how those issues could be fixed with lesser
effort, that would be great.
Already some ongoing discussion.

So I consider your report _very_ helpful.


Thanks,
  Harm

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

Re: New LilyPond website

[Simon Albrecht]

On 07.12.2016 23:01, John Roper wrote:

Am 07.12.2016 um 11:24 schrieb Phil Holmes:
it would be too much effort to fix something so minor

> From my naive point of view, there is something inherently wrong with a

website system if it is too much effort to correct a typo...
Joram

LOL doesn't this sound familiar?


I’d be sure it was a conscious allusion.
Best, Simon

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

Re: Small typo on LilyPond.org

[SoundsFromSound]

Graham Percival-3 wrote
> On Wed, Dec 07, 2016 at 10:46:14PM +0100, Noeck wrote:
>> Am 07.12.2016 um 11:24 schrieb Phil Holmes:
>> > it would be too much effort to fix something so minor
>> 
>> From my naive point of view, there is something inherently wrong with a
>> website system if it is too much effort to correct a typo...
> 
> I agree, but thankfully that's not the case here.  I'm looking
> forward to receiving your patch, Noeck!  :)
> 
> As always, I'm happy to mentor anybody who wants to contribute to
> LilyPond.  There's plenty of work to go around, even for easy
> typo-fixes like changing
>   @emph{December 40, 2016}
> to
>   @emph{December 04, 2016}
> 
> Cheers,
> - Graham
> 
> ___
> lilypond-user mailing list

> lilypond-user@

> https://lists.gnu.org/mailman/listinfo/lilypond-user

Sorry if I started something by sending my initial email, I didn't think it
was a super big issue -but I just figured it was a small simple HTML
oversight or something. Wasn't my intention to make this anything big,
sorry. I have no experience (or insider-knowledge on) how LilyPond.org HTML
is maintained from within regarding protocol and chain of command.

Just trying to help.



-
composer | sound designer 
LilyPond Tutorials (for beginners) --> http://bit.ly/bcl-lilypond
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Small-typo-on-LilyPond-org-tp197725p197788.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: exchange LyricHyphen with a "proper" hyphen

[Thomas Morley]

2016-12-07 22:03 GMT+01:00 Simon Albrecht :
> On 07.12.2016 11:45, Alexander Kobel wrote:
>>
>> I'm not sure whether Harm's proof of concept also involved
>> pre-compile-time modifications.
>
>
> It certainly didn’t; Harm is a Schemer, not a C++ guy :-)

Indeed.

So here a very first shot.
For now I let display the new _and_ the colored default LyricHyphen.
You'll see a drawback already: In tight situations the default gets
shortened until it vanishs. This is not possible or at least not
desirable for characters taken from a font, imho.
Iirc this was already mentioned in the discussion the tracker links to.
Maybe minimum-distance may help here, not tested though.

\version "2.19.52"

#(define (lh-test-stencil arg)
 (lambda (grob)
   (if (ly:stencil? (ly:lyric-hyphen::print grob))
   (let* ((stil (ly:lyric-hyphen::print grob))
  (x-ext (ly:stencil-extent stil X))
  (dash-period (ly:grob-property grob 'dash-period))
  (arg-stil (grob-interpret-markup grob arg))
  (arg-stil-x-ext (ly:stencil-extent arg-stil X))
  (length-to-print (interval-length x-ext))
  (guess (max 0 (truncate (/ length-to-print dash-period
  (guessed-args-line-length (* guess dash-period))
  (line-length-diff (- length-to-print guessed-args-line-length))
  (line-length-diff-for-each-arg (/ line-length-diff guess))
  (first-arg-length (+ dash-period line-length-diff-for-each-arg))
  (first-arg-end-coord
  (/ (* first-arg-length
(- (interval-length x-ext)
   (interval-length arg-stil-x-ext)))
 length-to-print))
  (list-of-starts
(map
  (lambda (n) (* n first-arg-end-coord))
  (iota (+ 1 guess)
 (ly:stencil-translate-axis
   (apply
 ly:stencil-add
 (map
   (lambda (x-val) (ly:stencil-translate-axis arg-stil x-val X))
   list-of-starts))
   (car x-ext) X))
   (ly:grob-suicide! grob

%%%
%% EXAMPLES
%%%

\paper { ragged-right = ##f }

\layout {
  \context {
\Score
\override NonMusicalPaperColumn #'line-break-permission = ##f
  }
}

newLH =
#(define-music-function (mrkp)(markup?)
#{
  \override LyricHyphen.after-line-breaking =
#(lambda (grob)
  (if (ly:stencil? (ly:lyric-hyphen::print grob))
  (ly:grob-set-property! grob 'stencil
(ly:stencil-add
  (stencil-with-color (ly:lyric-hyphen::print grob) red)
  ((lh-test-stencil mrkp ) grob)
#})


tstI = { c'2. c'4 }
tstII = { c'1 \break c'1 }
tstIII = { c'1 \break r1 c'1 }

lhTest =
#(define-music-function (mkp m i)(markup? ly:music? index?)
#{
<<
  \new Voice \repeat unfold $i $m
  \new Lyrics
\with { \newLH $mkp }
\lyricsto "" { \repeat unfold $i { voo -- doo }  }
>>
#})

\lhTest "~" \tstI 1
\lhTest "~" \tstI 2
\lhTest "~" \tstI 3
\lhTest "~" \tstI 4
\lhTest "~" \tstI 5
\lhTest "~" \tstI 6
\lhTest "~" \tstI 7
\lhTest "~" \tstI 8
\lhTest "~" \tstI 9
\lhTest "~" \tstI 10
\lhTest "~" \tstI 11
\lhTest "~" \tstI 12


\lhTest "~" \tstII 1

\lhTest "~" \tstIII 1

Cheers,
  Harm

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

Re: exchange LyricHyphen with a "proper" hyphen

[Noeck]

Dear Harm,

> Anyway, I tried some coding resulting in the attached image.

Wow. I should know it better by now, but time after time I am astonished
at what you are able to achieve.

Cheers,
Joram


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

Re: How to build LilyPond.app on macOS?

[Graham Percival]

On Wed, Dec 07, 2016 at 08:49:55PM +1100, Andrew Bernard wrote:
> I have offered on more than one occasion on the list to do the Python port. I
> have been knocked back, to be more accurate, strongly discouraged, each time.
> As somebody with over forty years of software development experience, I have
> the skills required, but not only that I have the time and the motivation, and
> the inclination to help.

If you are serious, then I would be happy to provide any mentoring
you require.  My rough guess is that it will take 30-60 hours to
make the change.

1) add python 3.x to our Grand Unified Builder:
https://github.com/gperciva/gub
Depending on how well python 3 crafted its build system, this
might require additional patches to their source tarball.
Hopefully it can be cross-compiled with only
./configure --options, though.
We currently have 30 different patches for python in GUB, although
those are spread between 2.4, 2.5, and 2.6.

This step is much more of "sysadmin task" or "unix developer" task
rather than a "python developer" task.  You'll run the script,
wait for a build failure, track down the missing dependency and/or
new ./configure --option required to build on the platform (for
example, cross-compiling for i386 or OSX, while running Linux
amd64), then repeat.

I'm guessing 20-40 hours for this part.


2) (could be simultaneous with 1): update our python scripts to
run in python3.  Ideally, ensure that they can run in 2 or 3 --
otherwise the coordination will be iffy and disruptive to other
developers.

I'm guessing 5-10 hours for this.



3) Make the switch, and fix whatever weirdness appears when people
use it "in the wild".

I'm guessing 5-10 hours.


If you're still interested, let's talk more!

Cheers,
- Graham

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

Re: Small typo on LilyPond.org

[Noeck]

> No problem.  Please feel free to provide a patch.

I would have a whole text based system. But this discussion is not wanted.

Btw, thanks a lot for your work, Phil!

Best,
Joram

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

Re: Small typo on LilyPond.org

[Graham Percival]

On Wed, Dec 07, 2016 at 10:46:14PM +0100, Noeck wrote:
> Am 07.12.2016 um 11:24 schrieb Phil Holmes:
> > it would be too much effort to fix something so minor
> 
> From my naive point of view, there is something inherently wrong with a
> website system if it is too much effort to correct a typo...

I agree, but thankfully that's not the case here.  I'm looking
forward to receiving your patch, Noeck!  :)

As always, I'm happy to mentor anybody who wants to contribute to
LilyPond.  There's plenty of work to go around, even for easy
typo-fixes like changing
  @emph{December 40, 2016}
to
  @emph{December 04, 2016}

Cheers,
- Graham

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

Re: Small typo on LilyPond.org

[Phil Holmes]

- Original Message - 
From: "Noeck" 

To: 
Sent: Wednesday, December 07, 2016 9:46 PM
Subject: Re: Small typo on LilyPond.org



Am 07.12.2016 um 11:24 schrieb Phil Holmes:

it would be too much effort to fix something so minor


From my naive point of view, there is something inherently wrong with a
website system if it is too much effort to correct a typo...

Joram



No problem.  Please feel free to provide a patch.

--
Phil Holmes

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

Re: New LilyPond website

[John Roper]

>>Am 07.12.2016 um 11:24 schrieb Phil Holmes:
>> it would be too much effort to fix something so minor

>From my naive point of view, there is something inherently wrong with a
>website system if it is too much effort to correct a typo...

>Joram

LOL doesn't this sound familiar?

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

Re: Openlilylib snippets announcement

[Noeck]

Hi,

while I encourage everyone to use git (and I think it is no problem for
Andrew), perhaps it would make sense to explain the installation using
zip files, too. Github offers zip files under "Clone or download" and I
think thats a good alternative for people not familiar with git. In
addition, this link is independent of the commit and contains the branch
name, so the documentation (readme) could directly point to
https://github.com/openlilylib/snippets/archive/master.zip for example.

Best,
Joram

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

Re: Melismata question

[Jacques Menu Muzhic]

Hello Abraham,

Thanks for the precision!

JM

> Le 7 déc. 2016 à 18:16, tisimst  a écrit :
> 
> Hi, Menu!
> 
> On Wed, Dec 7, 2016 at 10:12 AM, Menu Jacques [via Lilypond] <[hidden email] 
> > wrote:
> Hello folks,
> 
> The NR tells we can use « __ » to indicate a melismata after the end of a 
> word,
> 
> Actually, it's just a single underscore that does this. A double underscore 
> indicates that you want a lyric extender line to appear after the previous 
> syllable.
> 
> HTH,
> Abraham 
> 
> View this message in context: Re: Melismata question 
> 
> 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

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

Re: Small typo on LilyPond.org

[Noeck]

Am 07.12.2016 um 11:24 schrieb Phil Holmes:
> it would be too much effort to fix something so minor

>From my naive point of view, there is something inherently wrong with a
website system if it is too much effort to correct a typo...

Joram

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

Chords in choral music(Re: Fixing LSR 888: center-on-words ignoring punctuation)

[Simon Albrecht]

On 07.12.2016 01:07, Alexander Kobel wrote:
chords with two adjacent notes (shifting one note). I know that this 
should be a forbidden situation for vocal music


Why should it? I hardly think anybody should feel inclined to sing it 
/non divisi/…


Best, Simon

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

Re: exchange LyricHyphen with a "proper" hyphen

[Simon Albrecht]

On 07.12.2016 11:45, Alexander Kobel wrote:
I'm not sure whether Harm's proof of concept also involved 
pre-compile-time modifications.


It certainly didn’t; Harm is a Schemer, not a C++ guy :-)

Best, Simon

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

Re: optimized paper definitions for a tablet 10.10 "

[Herbert Liechti]

Hi Abraham

That was very quick :-) Thank you very much. Works perfect.

My margin settings:

  left-margin = 0.15\in
  right-margin = 0.15\in
  bottom-margin = 0.04\in
  top-margin = 0.04\in


Best regards
Herbert




2016-12-07 18:45 GMT+01:00 tisimst :

> Herbert,
>
> On Wed, Dec 7, 2016 at 10:19 AM, Herbert Liechti [via Lilypond] <[hidden
> email] > wrote:
>
>> I recently bought  an Android Lenovo YOGA Book tablet and I like to use
>> it on stage for viewing my sheets. I'm using an app MobileSheets for
>> organzing the pdf files. I was wondering if anyone has made a paper
>> definition (like A4) in lilypond for such a device. A tablet needs a
>> minimum of margins.
>>
>
> I don't own this myself (though I have been tempted many times), so here's
> a best estimate based on some images I could find online to get
> measurements from. It should get you pretty close (if showing full-screen):
>
> %%'
>
> #(set! paper-alist (cons '("YOGA" . (cons (* 5.33 in) (* 8.55 in)))
> paper-alist))
>
> \paper {
>   #(set-paper-size "YOGA")
>   % tweak these to taste
>   left-margin = 0.25\in
>   right-margin = 0.25\in
>   bottom-margin = 0.25\in
>   top-margin = 0.25\in
> }
>
> \repeat unfold 20 { c'4 d' e'8 f' g' a' }
>
> %%
>
> HTH,
> Abraham
>
> --
> View this message in context: Re: optimized paper definitions for a
> tablet 10.10 "
> 
> 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
>
>


-- 
herbert.liec...@thinx.ch,  ThinX AG,  Bielstrasse 69,  CH-4500 Solothurn
Tel +41 (0)32 623 81 66, Mobile +41 (0)76 334 81 66, http://www.thinx.ch
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: tag - midi

[bart deruyter]

Hans,

that's pretty cool :-), it first got me confused because I did not see it
in frescobaldi, the midi player doesn't show the midifiles, but I checked
the directory where the .ly file is 'et voila' :-) there it was.

Great, this possibility is a good thing to know. I've read on this list
that lilypond is not optimal for use on a webserver, but just imagine the
possibilities of these kinds of things. For example automatically generated
exercises for ear training having audio and notation, with an input box
where the user can enter notes and then check the results.. :-D ..

but that is out of the scope of this email, I get excited about these
endless opportunities for lilypond :-).

thanks again,

Bart



http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 

2016-12-07 12:53 GMT+01:00 Hans Aikema :

>
> > On 7 Dec 2016, at 08:31, bart deruyter  wrote:
> >
> > Hi all,
> >
> > I'm sorry for this late reply, it has been quite busy here.
> >
> > here is a minimal example:
> >
> > <..>
> >
> > As expected, I get two midi files, but they both contain the music of
> the entire score. The midi blocks don't follow the \keepWithTag rules.
> >
> > What I'd like to see is one score, two different midi files, each
> containing only the music enclosed in the tags.
> >
> > is something similar possible? Maybe I forgot some essential extra
> code...
> >
> > Using different score blocks for each part seems a bit much to get one
> pdf for the full score and chopped midi files.
> >
> Bart,
>
> With pure lilypond you will need the additional Score blocks. Both \layout
> and \midi render whatever is the current score (they do not consume a music
> expression to render, but rather take the current score to render.
> Another option would require scheme code to dynamically build your midi
> score blocks. I recently discoverd the rehearsalMidi function hidden in the
> treasures of openlilylib which now is a great asset in my toolbox for
> creating rehearsal midi (and mp3 with a timidity++/lame toolchain) files
> for my choir. As I suspected (after some trial and error.. my first steps
> into scheme coding) it can be easily adapted for your needs of outputting
> separate midis for tagged music. See the attached file for the function. It
> needs to be included in your actual files. Your minimal snippet would be
> converted into:
>
> \include "tagmidi.ly"
>
> altoVoice = \relative c' {
>
> \tag #'A {c'2  g |} \tag #'B {e'4 d  c2 }|
>   \bar "|."
> }
>
> \score {
>   \new Staff \with {
> midiInstrument = "piano"
>   } { \altoVoice }
>
>   \layout { }
> }
>
> \tagMidi \altoVoice #'A
> \tagMidi \altoVoice #’B
>
> Which I think is more consise and less error-prone once you start getting
> more samples into a single file and gives you suffixes to the midi-files
> that match the tags.
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: BBC SO playing from a Lilypond score

[Jeffery Shivers]

The score looks beautiful - congrats!

On Wed, Dec 7, 2016 at 6:07 PM, Dominic  wrote:

> Hi everyone,
>
> Tonight (7.30pm on BBC Radio 3), the BBC Symphony Orchestra will be giving
> the premiere performance of Diana Burrell's 'Concerto for Brass and
> Orchestra'. I typeset the score and parts entirely using Lilypond 2.19 a
> few
> months ago. Lilypond helped me achieve lots of things that would have been
> very awkward in other software, such as cross-staff stems, tuplets over
> barlines, augmented unisons, reliably cued parts, and automatically
> calculated page-turns (with rests on the bottom right pages)... all handled
> in a completely robust and reliable manner.
>
> I've got absolutely no idea how the piece will sound; I entered it from the
> composer's manuscript and never exported a MIDI file.
>
> Image of the first page attached:
>
>  >
>
> Dominic
>
>
>
> --
> View this message in context: http://lilypond.1069038.n5.
> nabble.com/BBC-SO-playing-from-a-Lilypond-score-tp197758.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
>



-- 

Jeffery Shivers
 jefferyshivers.com
 soundcloud.com/jefferyshivers
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: How to build LilyPond.app on macOS?

[Trevor Daniels]

Carl Sorensen wrote Wednesday, December 07, 2016 4:39 PM

On 12/7/16 2:49 AM, "Andrew Bernard"  wrote:

>>I have offered on more than one occasion on the list to do the Python
>>port. I have been knocked back, to be more accurate, strongly
>>discouraged, each time. As somebody with over forty years of software
>>development experience, I have the skills required, but not only that I
>>have the time and the motivation, and the inclination to help. I have
>>maintained for a long time that a Python upgrade is valuable, especially
>>after not having a current version of Python prevented me from doing some
>>task quite some time ago (I no longer remember which! But no matter.). I
>>am perfectly aware that the outcome of the work is Œnothing changes¹ ­
>>but this is not the point. It provides the way forward for lilypond to
>>keep current with Python. I currently have the time and energy to do this
>>work. Is there anybody at all who would support this idea? Surely this
>>has to be done at some point in time. Why not now? After all, we are
>>attacking the guile 2 matter currently, and similar arguments have been
>>made against doing that in the past.
>
>The proper place to have this discussion is on the -devel list, not the
>-user list.  I say this not as a complaint, but as a help.
>
>If you'd like to update python, by all means have a go at it!  We always
>welcome changes from people who have something they want to do and do it
>well.
>
>We wouldn't be excited about having somebody say "you ought to change to
>Python 2.7", but I'd personally be happy to have somebody say "I'm willing
>to change to Python 2.7".  It will be a big job, but if you're up for it,
>great!
>
>I'm looking forward to your contributions!

I agree with Carl - yes, it's an enormous job, but as soon as someone
starts it gets a little smaller.  Even just investigating what needs to
be done and documenting it would be a great start.

Some devs don't read the -user list, so posting your offer on the -devel
list would get more feedback.

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

BBC SO playing from a Lilypond score

[Dominic]

Hi everyone,

Tonight (7.30pm on BBC Radio 3), the BBC Symphony Orchestra will be giving
the premiere performance of Diana Burrell's 'Concerto for Brass and
Orchestra'. I typeset the score and parts entirely using Lilypond 2.19 a few
months ago. Lilypond helped me achieve lots of things that would have been
very awkward in other software, such as cross-staff stems, tuplets over
barlines, augmented unisons, reliably cued parts, and automatically
calculated page-turns (with rests on the bottom right pages)... all handled
in a completely robust and reliable manner.

I've got absolutely no idea how the piece will sound; I entered it from the
composer's manuscript and never exported a MIDI file.

Image of the first page attached:

 

Dominic



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/BBC-SO-playing-from-a-Lilypond-score-tp197758.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: optimized paper definitions for a tablet 10.10 "

[tisimst]

Herbert,

On Wed, Dec 7, 2016 at 10:19 AM, Herbert Liechti [via Lilypond] <
ml-node+s1069038n197755...@n5.nabble.com> wrote:

> I recently bought  an Android Lenovo YOGA Book tablet and I like to use it
> on stage for viewing my sheets. I'm using an app MobileSheets for organzing
> the pdf files. I was wondering if anyone has made a paper definition (like
> A4) in lilypond for such a device. A tablet needs a minimum of margins.
>

I don't own this myself (though I have been tempted many times), so here's
a best estimate based on some images I could find online to get
measurements from. It should get you pretty close (if showing full-screen):

%%'

#(set! paper-alist (cons '("YOGA" . (cons (* 5.33 in) (* 8.55 in)))
paper-alist))

\paper {
  #(set-paper-size "YOGA")
  % tweak these to taste
  left-margin = 0.25\in
  right-margin = 0.25\in
  bottom-margin = 0.25\in
  top-margin = 0.25\in
}

\repeat unfold 20 { c'4 d' e'8 f' g' a' }

%%

HTH,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/optimized-paper-definitions-for-a-tablet-10-10-tp197755p197757.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

optimized paper definitions for a tablet 10.10 "

[Herbert Liechti]

Hello

I recently bought  an Android Lenovo YOGA Book tablet and I like to use it
on stage for viewing my sheets. I'm using an app MobileSheets for organzing
the pdf files. I was wondering if anyone has made a paper definition (like
A4) in lilypond for such a device. A tablet needs a minimum of margins.

Thanks for the feedback
best regards
Herbert
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Melismata question

[tisimst]

Hi, Menu!

On Wed, Dec 7, 2016 at 10:12 AM, Menu Jacques [via Lilypond] <
ml-node+s1069038n197753...@n5.nabble.com> wrote:

> Hello folks,
>
> The NR tells we can use « __ » to indicate a melismata after the end of a
> word,
>

Actually, it's just a single underscore that does this. A double underscore
indicates that you want a lyric extender line to appear after the previous
syllable.

HTH,
Abraham




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Melismata-question-tp197753p197754.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

Melismata question

[Menu Jacques]

Hello folks,

The NR tells we can use « __ » to indicate a melismata after the end of a word, 
such as « chro, » in the sample below.

But having that severeal times seems to have no effect. As a matter of style, 
is it best to have only one occurrence, or one per note after the one starting 
the melismata?

Thanks for the help!

JM

—

\version "2.19.44"

P_POne_S_One_V_One = \relative {
  {
| % 1
\clef "treble"
g'4 ( f4 ) d4 ( f4 e4 ) f4 ( g4 f4 ) g4 f4
a4 a4 ( c4 b4 a4 ) c4 ( g4 a4 g4 ) g4 (
a4 ) g4 ( f4 ) a4 ( c4 ) a4 g4
\bar "||"


  }
}

P_POne_S_One_V_One_L_One = \lyricmode {
  %{ "1" %}
Quem que -- ri -- tis
in se -- pul -- "chro," __ __  __  __ __
o Chri -- sti -- co -- "lae?" }

\score {
  <<
  \new StaffGroup {
\new Staff <<
  \context Voice = "P_POne_S_One_V_One" { \P_POne_S_One_V_One }
  \new Lyrics \lyricsto "P_POne_S_One_V_One" \P_POne_S_One_V_One_L_One
>>
  }
  >>

  \layout {
% Uncomment and adapt next line as needed (default is 20)
% #(layout-set-staff-size 20)
  }

  \midi {
% to be completed
  }
}

—

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

Re: How to build LilyPond.app on macOS?

[Carl Sorensen]

Andrew,

On 12/7/16 2:49 AM, "Andrew Bernard"  wrote:

>I have offered on more than one occasion on the list to do the Python
>port. I have been knocked back, to be more accurate, strongly
>discouraged, each time. As somebody with over forty years of software
>development experience, I have the skills required, but not only that I
>have the time and the motivation, and the inclination to help. I have
>maintained for a long time that a Python upgrade is valuable, especially
>after not having a current version of Python prevented me from doing some
>task quite some time ago (I no longer remember which! But no matter.). I
>am perfectly aware that the outcome of the work is Œnothing changes¹ ­
>but this is not the point. It provides the way forward for lilypond to
>keep current with Python. I currently have the time and energy to do this
>work. Is there anybody at all who would support this idea? Surely this
>has to be done at some point in time. Why not now? After all, we are
>attacking the guile 2 matter currently, and similar arguments have been
>made against doing that in the past.

The proper place to have this discussion is on the -devel list, not the
-user list.  I say this not as a complaint, but as a help.

If you'd like to update python, by all means have a go at it!  We always
welcome changes from people who have something they want to do and do it
well.

We wouldn't be excited about having somebody say "you ought to change to
Python 2.7", but I'd personally be happy to have somebody say "I'm willing
to change to Python 2.7".  It will be a big job, but if you're up for it,
great!

I'm looking forward to your contributions!

Thanks,

Carl

> 
> 
> 
> 


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

Re: Openlilylib snippets announcement

[Urs Liska]

Am 7. Dezember 2016 13:51:26 MEZ, schrieb "N. Andrew Walsh" 
:
>Maybe someone on the list can help me quickly, because I *always* lose
>the
>instructions:
>
>On Tue, Nov 22, 2016 at 3:00 PM, Urs Liska  wrote:
>
>>
>>
>> 1)
>> openLilyLib snippets (and packages) are designed to be includable.
>That
>> means once you have "installed" openLilyLib (by downloading/cloning
>and
>> adding it to LilyPond's include path) you can access the
>functionality
>> exposed in openLilyLib. Snippets from the LSR have to be copied and
>> pasted in your own files.
>>
>
>How do I actually install the oll repository locally? I don't see any
>instructions at https://github.com/openlilylib for how to do this. I
>assume
>it's with the 'git remote add' command, but I don't see this explicitly
>stated anywhere. Can one of you please help?

Hm.
https://github.com/openlilylib/snippets
*does* have a README with instructions.

What you want is git clone (not remote add).

Clone
https://github.com/openlilylib/snippets into an arbitrary oll root directory 
and add "snippets" to thr include path.

Additionally you (specifically, for the Kayser scores) want at least the

oll-core
scholarly
breaks 
page-layout

repositories in addition.
For these you have to add the root directory to Lily's include path.

HTH
Urs

>
>Cheers,
>
>A

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

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

Re: Openlilylib snippets announcement

[N. Andrew Walsh]

Maybe someone on the list can help me quickly, because I *always* lose the
instructions:

On Tue, Nov 22, 2016 at 3:00 PM, Urs Liska  wrote:

>
>
> 1)
> openLilyLib snippets (and packages) are designed to be includable. That
> means once you have "installed" openLilyLib (by downloading/cloning and
> adding it to LilyPond's include path) you can access the functionality
> exposed in openLilyLib. Snippets from the LSR have to be copied and
> pasted in your own files.
>

How do I actually install the oll repository locally? I don't see any
instructions at https://github.com/openlilylib for how to do this. I assume
it's with the 'git remote add' command, but I don't see this explicitly
stated anywhere. Can one of you please help?

Cheers,

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

Re: tag - midi

[Hans Aikema]

> On 7 Dec 2016, at 08:31, bart deruyter  wrote:
> 
> Hi all,
> 
> I'm sorry for this late reply, it has been quite busy here.
> 
> here is a minimal example:
> 
> <..>
> 
> As expected, I get two midi files, but they both contain the music of the 
> entire score. The midi blocks don't follow the \keepWithTag rules.
> 
> What I'd like to see is one score, two different midi files, each containing 
> only the music enclosed in the tags.
> 
> is something similar possible? Maybe I forgot some essential extra code...
> 
> Using different score blocks for each part seems a bit much to get one pdf 
> for the full score and chopped midi files.
> 
Bart,

With pure lilypond you will need the additional Score blocks. Both \layout and 
\midi render whatever is the current score (they do not consume a music 
expression to render, but rather take the current score to render.
Another option would require scheme code to dynamically build your midi score 
blocks. I recently discoverd the rehearsalMidi function hidden in the treasures 
of openlilylib which now is a great asset in my toolbox for creating rehearsal 
midi (and mp3 with a timidity++/lame toolchain) files for my choir. As I 
suspected (after some trial and error.. my first steps into scheme coding) it 
can be easily adapted for your needs of outputting separate midis for tagged 
music. See the attached file for the function. It needs to be included in your 
actual files. Your minimal snippet would be converted into:

\include "tagmidi.ly"

altoVoice = \relative c' {

\tag #'A {c'2  g |} \tag #'B {e'4 d  c2 }| 
  \bar "|."
}

\score {
  \new Staff \with {
midiInstrument = "piano"
  } { \altoVoice }

  \layout { }
}

\tagMidi \altoVoice #'A
\tagMidi \altoVoice #’B

Which I think is more consise and less error-prone once you start getting more 
samples into a single file and gives you suffixes to the midi-files that match 
the tags.
 

tagmidi.ly
Description: Binary data
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: exchange LyricHyphen with a "proper" hyphen

[Alexander Kobel]

Hi Knut,

thanks for looking into that. IIUC (and without looking into your code - 
is it on Github or otherwise publicly avaiable?), it seems that you 
essentially add a text-interface to LyricHyphen. That's what would have 
been my idea as well, if I were up to it.


Rebuilding is not a problem - I usually use a self-compiled version 
anyway, though I try to avoid relying on it too much. But this would be 
a change that you can do once and for all in a separate style file, and 
if you use a vanilla version, you can just resort to not include that part.


I'm not sure whether Harm's proof of concept also involved 
pre-compile-time modifications. If not, that would be an ever better 
option for my taste. Otherwise, I'll come back to you... ;-) Thanks!



Cheers,
Alexander


On 2016-12-07 11:37, Knut Petersen wrote:

Hi Alexander!


every now and then, I use a font for lyrics where the hyphen is quite
different from Lilypond's LyricHyphen (in particular, sometimes it's
slightly slanted). That combined with lyrics where a hyphen has to
appear looks, well, ugly. (Recent example: a repetition of part of a
word that has to be written as { ro -- sen-, ro -- sen -- rot }.)

I failed with [...]



Did anyone ever successfully try to do that, or has an idea how to
approach such a tweak?


Yes, there is a solution in my local git repository. To activate the
code you would include something like

 \override Lyrics.LyricText #'font-size = #+1.5

  \override Lyrics.LyricHyphen.use-markup = ##t
  \override Lyrics.LyricHyphen.text = "-"
  \override Lyrics.LyricHyphen #'font-size = #'1.5
  \override Lyrics.LyricHyphen #'font-name = "OffenbacherSchwab OT"
  \override Lyrics.LyricHyphen #'minimum-distance = #0.8

into \layout{}. It's on top of some other changes either not published
or not accepted, but I could tear it out.

Of course, you would need to rebuild lilypond as the solution requires
changes to the c++ sources.

cu,
 Knut


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

Re: exchange LyricHyphen with a "proper" hyphen

[Knut Petersen]

Hi Alexander!

every now and then, I use a font for lyrics where the hyphen is quite different from Lilypond's LyricHyphen (in particular, sometimes it's slightly slanted). That combined with lyrics where a hyphen has to appear looks, well, ugly. (Recent example: a repetition of part of a word that has to be 
written as { ro -- sen-, ro -- sen -- rot }.)


I failed with [...]



Did anyone ever successfully try to do that, or has an idea how to approach 
such a tweak?


Yes, there is a solution in my local git repository. To activate the code you 
would include something like

 \override Lyrics.LyricText #'font-size = #+1.5

  \override Lyrics.LyricHyphen.use-markup = ##t
  \override Lyrics.LyricHyphen.text = "-"
  \override Lyrics.LyricHyphen #'font-size = #'1.5
  \override Lyrics.LyricHyphen #'font-name = "OffenbacherSchwab OT"
  \override Lyrics.LyricHyphen #'minimum-distance = #0.8

into \layout{}. It's on top of some other changes either not published or not 
accepted, but I could tear it out.

Of course, you would need to rebuild lilypond as the solution requires changes 
to the c++ sources.

cu,
 Knut

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

Re: Small typo on LilyPond.org

[Phil Holmes]

- Original Message - 
From: "SoundsFromSound" 

To: 
Sent: Wednesday, December 07, 2016 2:01 AM
Subject: Small typo on LilyPond.org


Just wanted to give you guys a little heads up, I noticed a small typo on 
the

LilyPond home page at the bottom under "News":


LilyPond 2.19.52 released - December 40, 2016 <-- 40, instead of 04
Two LilyPond projects in Google Summer of Code 2016 - April 23, 2016
LilyPond 2.18.2 released! - March 23, 2014
LilyPond 2.18.0 released! - December 29, 2013

In case someone can fix it, not the end of the world but figured I'd share


I did spot it but concluded it would be too much effort to fix something so 
minor that will be fixed anyway in the next release.


--
Phil Holmes 



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

Re: How to build LilyPond.app on macOS?

[Urs Liska]

Am 07.12.2016 um 10:49 schrieb Andrew Bernard:
> Why not now? After all, we are attacking the guile 2 matter currently,
> and similar arguments have been made against doing that in the past.

Probably because we will be doing it just before LilyPond will be kicked
from major distributions that don't support the old Python anymore.

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

Re: How to build LilyPond.app on macOS?

[Andrew Bernard]

Hello Graham,

 

> On Tue, Dec 06, 2016 at 07:25:44PM +0100, Mojca Miklavec wrote:

> > 

> > I can luckily skip that part :)

> > Including instructions to fetch Python 2.6.

> > (I really wonder why LilyPond nowadays ships with Python 2.6.)

 

> Changing it to something else would require updating all our

> scripts, cross-compiling the newer version of python on all 8 (or

> so) architectures, and testing the whole thing.  This is a

> non-trivial undertaking, especially since (ideally) the end result

> is "things work exactly the way they did before spending 100 hours

> on this task".

 

> That's why technical debt is so hard to combat: it takes a lot of

> effort, and there's usually no immediate payoff.  Sure, it would

> help things in 1, 2, 5, or 10 years down the road.

 

I'd like to change the subject line of this new thread, but just now needed
to leave it in context as a reply.

 

I have offered on more than one occasion on the list to do the Python port.
I have been knocked back, to be more accurate, strongly discouraged, each
time. As somebody with over forty years of software development experience,
I have the skills required, but not only that I have the time and the
motivation, and the inclination to help. I have maintained for a long time
that a Python upgrade is valuable, especially after not having a current
version of Python prevented me from doing some task quite some time ago (I
no longer remember which! But no matter.). I am perfectly aware that the
outcome of the work is 'nothing changes' - but this is not the point. It
provides the way forward for lilypond to keep current with Python. I
currently have the time and energy to do this work. Is there anybody at all
who would support this idea? Surely this has to be done at some point in
time. Why not now? After all, we are attacking the guile 2 matter currently,
and similar arguments have been made against doing that in the past.

 

Andrew

 

 

 

 

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