Re: Bravura svg font

[Nathan Ho]

On 2016-01-07 02:57, Paul Booker wrote:

Thanks Nathan,
Since posting, I've scanned the bug and devel groups, and it would 
appear I
am not being fashionable in wanting to do this. The trend seems to be 
toward

woff fonts for svg, is that the case?


Yes and no. The openlilylib font project mostly supersedes the SMuFL 
implementation. I haven't been keeping up on the project (since I 
haven't been using LilyPond much lately), but I'd wager it is superior 
for the specific case of typesetting music in Bravura/Profondo. When the 
site gets back up, I suggest you use their work.


However, the LilyJAZZ dynasty still lives on. The most serious use is 
probably Robert Piéchaud's commercial font November. The least serious 
use is the recent Christmas font adaptation by Leigh Verlag :)


Nathan

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

Re: Bravura svg font

[Simon Albrecht]

On 08.01.2016 00:31, Nathan Ho wrote:
The least serious use is the recent Christmas font adaptation by Leigh 
Verlag :) 


In case others be interested: 


Nice and funny :-) Thanks, Abraham (and Mark)!

Yours, Simon

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

Re: Strange beaming error

[Urs Liska]

Am 07.01.2016 um 10:16 schrieb David Kastrup:
> Urs Liska  writes:
>
>> Do you also have subdivideBeams = ##t somewhere?
>> If so please show the result with both 2.19.28 and .35..
>>
>> And if that's the case you should maybe send me (privately?) the full
>> piece so I could test with several builds before and after several
>> recent changes.
> It's not the first time the subdivision fixes had to be overhauled.  And
> if we keep up the way of dealing with them, I rather doubt it will be
> the last time.

Maybe I should clarify something about this history.

Beam subdivision wasn't ever correct in so far that at any subdivision
(only) one beam was left, and I reported this as a bug last April.
As issue 4355 this was fixed (not by me).

In November I noticed a new issue and realized it was an unnoticed side
effect of 4355.
I fixed this as issue 4664, only to notice that the behavior introduced
in 4355 didn't work anymore.

As it turned out this wasn't my fault in 4664, but a few weeks after
4355 the behavior had been partially reverted (in
0382ed88b53cb24e76a1935e18df32cc87174428 "Adjust beam subdivision to
only occur at baseMoment", without further explanation and seemingly
without a tracker item.

So I gave the issue more thought and hoped to fix the issue properly.

>
> I suggest that you write down the rules, _all_ rules, that are supposed
> to be governing subdivision.  On paper.  As a simple recipe of the "if
> this condition is met, do this, else if that condition is met, do that,
> else ... otherwise ..." kind.

Basically this is what I did, but there were cases I couldn't imagine.
One of them is when baseMoment equals the actual note duration.

The obvious issue of the OP was a case where this is actually improper
LilyPond coding:

\set subdivideBeams = ##t
\set baseMoment = #(ly:make-moment 1/16)
c16 c c c

just makes no sense. And this is why I didn't give that case more thought.
But with

\set subdivideBeams = ##t
\set baseMoment = #(ly:make-moment 1/16)
c16 c c64 c c c c32 c

It *does* make sense to have beam subdivision points at every note (the
first three ones).

The other case that deserves further attention is when the beam is
shortened, but not at the end but at the beginning (i.e. r32 c c c).

So I think I'll follow your suggestions above and below, considering
these cases and do my best to identify other (corner) cases.

>
> _Then_ you check the examples making problems.  On paper.  Does LilyPond
> follow the rules?  If so, the rules may need changing.  Where the rules
> cannot sensibly changed to accommodate conflicting but equally valid
> cases, we'll have to introduce manual intervention methods that are to
> be used for a well-defined and humanly recognizable subset of cases.
>
> If LilyPond does _not_ follow the rules on paper however, the
> implementation is broken.  How did it manage to escape scrutiny several
> times?  Perhaps a rewrite is required where the logic of the code can
> trace the human-accessible rules so closely that there is no doubt about
> the code matching the rules.
>
> Oh, and that paper with the rules?  Once the code follows it, the
> content of the paper belongs in code comments and possibly a manual.

Well, I think I have covered *most* rules, and these are documented
pretty extensively in the code comments and the regtests.

Urs

>


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

Fwd: Concerts in Berlin with LilyPond scores

[Colin Campbell]

Forwarding to the User group, as it's more appropriate there, and for 
wider distribution. All the best for the concerts, Aurélien, and thanks 
for letting us know.


Cheers,
Colin




 Forwarded Message 
Subject:Concerts in Berlin with LilyPond scores
Date:   Thu, 7 Jan 2016 17:22:23 + (UTC)
From:   Aurélien Bello 
To: bug-lilyp...@gnu.org



Hi,
I would be glad if you could announce several orchestral
concerts which will use LilyPond scores:

- 22.01.2016, 8pm
Kammermusiksaal der Philharmonie, Berlin
Junge Kammerphilharmonie Berlin
Bruno Delepelaire, violoncello
Aurélien Bello, conductor


*Liszt (arr. A. Bello): Fantasie und Fuge über das Thema b-a-c-h
Shostakovich: Concerto for Cello and Orchestra Nr. 1 op. 107
*Ravel (arr. A. Bello): Menuet sur le nom de Haydn
*Debussy (arr. A. Bello): Hommage à Haydn
*Dukas (arr. A. Bello): Prélude élégiaque sur le nom de Haydn
Haydn: Symphony Nr. 103 in E-flat major "Drum roll"

(* LilyPond scores)



28.02.2016, 2.30pm and 4pm
Philharmonie Berlin
23.03.2016, 2pm and 6pm
Festspielhaus Baden-Baden
Berliner Philharmoniker
Raphael Haeger, conductor

Debussy: La Boîte à Joujoux
new orchestration for 15 musicians by Aurélien Bello



Thanks a lot for announcing!
Long life to LilyPond,

Yours,

Aurélien

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


--
I've learned that you shouldn't go through life with a catcher's mitt on both 
hands.
You need to be able to throw something back.
-Maya Angelou, poet (1928- )



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

Re: Fwd: Concerts in Berlin with LilyPond scores

[Urs Liska]

Am 07.01.2016 um 23:50 schrieb Colin Campbell:
> Forwarding to the User group, as it's more appropriate there, and for
> wider distribution. All the best for the concerts, Aurélien, and
> thanks for letting us know.

That's partially true.
lilypond-user is the better place to let more people know, but actually
I think Aurélien asked for an entry (entries) in the "pondings" on
lilypond.org's front page.

Urs

>
> Cheers,
> Colin
>
>
>
>
>  Forwarded Message 
> Subject:  Concerts in Berlin with LilyPond scores
> Date: Thu, 7 Jan 2016 17:22:23 + (UTC)
> From: Aurélien Bello 
> To:   bug-lilyp...@gnu.org
>
>
>
> Hi, 
> I would be glad if you could announce several orchestral 
> concerts which will use LilyPond scores:
>
> - 22.01.2016, 8pm
> Kammermusiksaal der Philharmonie, Berlin
> Junge Kammerphilharmonie Berlin
> Bruno Delepelaire, violoncello
> Aurélien Bello, conductor
>
>
> *Liszt (arr. A. Bello): Fantasie und Fuge über das Thema b-a-c-h 
> Shostakovich: Concerto for Cello and Orchestra Nr. 1 op. 107
> *Ravel (arr. A. Bello): Menuet sur le nom de Haydn
> *Debussy (arr. A. Bello): Hommage à Haydn
> *Dukas (arr. A. Bello): Prélude élégiaque sur le nom de Haydn
> Haydn: Symphony Nr. 103 in E-flat major "Drum roll"
>
> (* LilyPond scores)
>
>
>
> 28.02.2016, 2.30pm and 4pm
> Philharmonie Berlin
> 23.03.2016, 2pm and 6pm
> Festspielhaus Baden-Baden
> Berliner Philharmoniker
> Raphael Haeger, conductor
>
> Debussy: La Boîte à Joujoux
> new orchestration for 15 musicians by Aurélien Bello
>
>
>
> Thanks a lot for announcing! 
> Long life to LilyPond,
>
> Yours,
>
> Aurélien 
>
> ___
> bug-lilypond mailing list
> bug-lilyp...@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>
> -- 
> I've learned that you shouldn't go through life with a catcher's mitt on both 
> hands. 
> You need to be able to throw something back. 
> -Maya Angelou, poet (1928- )
>
>
>
>
> ___
> 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: Bravura svg font

[Nathan Ho]

On 2016-01-06 11:23, Paul Booker wrote:

Hi,
I'm a new use of lilypond-windows on Win 8.1 64bit and Win 7. First of 
all,
thanks for wonderful software; I'm generating many snippets for 
educational

purposes.
My main problem so far is getting the bravura alternative font to 
appear. I

don't mind trying a few things, but this problem has me stumped.


Hi Paul,

I'm responsible for this issue as the maintainer of the SMuFL 
implementation. Thanks for reporting the bug; I'll get on this tomorrow.


By the way, there is another way to get Bravura (and a whole host of 
other fonts) in LilyPond. It should be available at 
fonts.openlilylib.org but that site seems to be down for the moment.


Nathan

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

Re: Strange beaming error

[David Kastrup]

Urs Liska  writes:

> Before testing further I assume the current issue is due to *not*
> using the latest state (which isn't in a release yet).

Why are there different states?  Did the original plan fail on paper or
did it never reach paper?  Or was it not correctly implemented?

> But of course I'll test with the material and with all iterations of
> the code once I have it.

"Iterations of the code" makes me queasy.  It suggests that there is no
plan but instead one pokes the code until it happens to work most of the
time.  Then it cannot be documented, maintained, or changed because
nobody really knows the reason that it works.

I am aware that large amounts of code come into being in that manner,
partly because of resource limitations.

And there is some justification for it in the "reaping" phase of a
product, where the main issue is selling it while investing the least
amount of work (Sibelius anyone?).

LilyPond is not due for the reaper yet.

-- 
David Kastrup

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

Re: Strange beaming error

[Urs Liska]

Am 7. Januar 2016 10:16:29 MEZ, schrieb David Kastrup :
>Urs Liska  writes:
>
>> Do you also have subdivideBeams = ##t somewhere?
>> If so please show the result with both 2.19.28 and .35..
>>
>> And if that's the case you should maybe send me (privately?) the full
>> piece so I could test with several builds before and after several
>> recent changes.
>
>It's not the first time the subdivision fixes had to be overhauled. 
>And
>if we keep up the way of dealing with them, I rather doubt it will be
>the last time.
>
>I suggest that you write down the rules, _all_ rules, that are supposed
>to be governing subdivision.  On paper.  As a simple recipe of the "if
>this condition is met, do this, else if that condition is met, do that,
>else ... otherwise ..." kind.
>
>_Then_ you check the examples making problems.  On paper.  Does
>LilyPond
>follow the rules?  If so, the rules may need changing.  Where the rules
>cannot sensibly changed to accommodate conflicting but equally valid
>cases, we'll have to introduce manual intervention methods that are to
>be used for a well-defined and humanly recognizable subset of cases.
>
>If LilyPond does _not_ follow the rules on paper however, the
>implementation is broken.  How did it manage to escape scrutiny several
>times?  Perhaps a rewrite is required where the logic of the code can
>trace the human-accessible rules so closely that there is no doubt
>about
>the code matching the rules.
>
>Oh, and that paper with the rules?  Once the code follows it, the
>content of the paper belongs in code comments and possibly a manual.


Before testing further I assume the current issue is due to *not* using the 
latest state (which isn't in a release yet).

But of course I'll test with the material and with all iterations of the code 
once I have it.

Urs
-- 
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: Strange beaming error

[David Kastrup]

Chris Yate  writes:

> On 7 January 2016 at 00:49, Thomas Morley  wrote:
>
>> Btw, your images are inline _not_ attached.
>>
>
> Are inlined images not OK here? ...or were you just being pedantic?
> ;-)

They were inlined into the HTML part only rather than attached as a
separate MIME part with an inline disposition.

As a result, a number of readers will not be able to see them (for
example, I had to switch my default viewing modes around after being
made aware by Thomas that there was supposed to be an included graphic)
and the list archives are not likely to offer them either since they
tend to trash the HTML parts.

So your method of attachment is not likely to work well for a lot of
purposes (probably the only worse way would be to make it a background
image of the mail).  I would strongly suggest that you try to figure out
one that would be more likely to work with the bulk of readers.

-- 
David Kastrup

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

Re: Strange beaming error

[David Kastrup]

Urs Liska  writes:

> Do you also have subdivideBeams = ##t somewhere?
> If so please show the result with both 2.19.28 and .35..
>
> And if that's the case you should maybe send me (privately?) the full
> piece so I could test with several builds before and after several
> recent changes.

It's not the first time the subdivision fixes had to be overhauled.  And
if we keep up the way of dealing with them, I rather doubt it will be
the last time.

I suggest that you write down the rules, _all_ rules, that are supposed
to be governing subdivision.  On paper.  As a simple recipe of the "if
this condition is met, do this, else if that condition is met, do that,
else ... otherwise ..." kind.

_Then_ you check the examples making problems.  On paper.  Does LilyPond
follow the rules?  If so, the rules may need changing.  Where the rules
cannot sensibly changed to accommodate conflicting but equally valid
cases, we'll have to introduce manual intervention methods that are to
be used for a well-defined and humanly recognizable subset of cases.

If LilyPond does _not_ follow the rules on paper however, the
implementation is broken.  How did it manage to escape scrutiny several
times?  Perhaps a rewrite is required where the logic of the code can
trace the human-accessible rules so closely that there is no doubt about
the code matching the rules.

Oh, and that paper with the rules?  Once the code follows it, the
content of the paper belongs in code comments and possibly a manual.

-- 
David Kastrup

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

list of thicknesses affected by changing StaffSymbol.thickness

[Kieren MacMillan]

Hello all,

Is there a single list somewhere in the documentation, of all the grobs whose 
sizes are tied to StaffSymbol.thickness?
(Optimally, that list would also include each grob’s default 
multiplier/thickness.)

Thanks,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


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

RE: Strange beaming error

[Chris Yate]

On 7 Jan 2016 1:31 am, "Mark Stephen Mrotek"  wrote:

>
> Chris:
>
>
> What is the time signature? 6/8?
>
> Or is it 2/4 grouped as if in tuplets?
> Mark

Mark,

Yes, it's 6/8.
Although it changes to 4/4 for one movement - the one before this problem
occurs (that may or may not be coincidental), and there's partial bars at
the beginning and end of most of the movements

Chris

---
On 7 January 2016 at 09:05, David Kastrup  wrote:

> Chris Yate  writes:
> > Are inlined images not OK here? ...or were you just being pedantic?
> > ;-)
>
> They were inlined into the HTML part only rather than attached as a
> separate MIME part with an inline disposition.
>
> As a result, a number of readers will not be able to see them (for
> example, I had to switch my default viewing modes around after being
> made aware by Thomas that there was supposed to be an included graphic)
> and the list archives are not likely to offer them either since they
> tend to trash the HTML parts.
>
> So your method of attachment is not likely to work well for a lot of
> purposes (probably the only worse way would be to make it a background
> image of the mail).  I would strongly suggest that you try to figure out
> one that would be more likely to work with the bulk of readers.


OK, noted, thanks.  I'm now rather accustomed to using webmail, and it's
arguably a failing of the webmail client if it doesn't attach a
drag-dropped file properly.  Whilst I don't want to start a holy war on
this point, I'd hazard a guess that the *bulk* of readers nowadays, by
which I mean email clients designed for humans to read, are perfectly
capable of reading HTML emails.

The main exception I can see (and it's a good one) is a list archive. Would
attachments be archived too? Inline replies vs top posting is the same
argument IMO.

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

Re: Include total page count in page number

[tisimst]

Thank you! That will at least get me by for now.

- Abraham

On Thu, Jan 7, 2016 at 7:09 AM, Jan-Peter Voigt [via Lilypond] <
ml-node+s1069038n185643...@n5.nabble.com> wrote:

> Hi Abraham,
>
> I created a short sketch, how this might be realized. In this example,
> the result counts one page high - I didn't simply decrease the value,
> because I don't know, if it might reach other peaks.
> But I think, the idea is sketched. The two markdown commands could be
> merged to one "\full-pages" command, but that shall be done, when this
> technique proves stable ;-)
>
> Cheers
> Jan-Peter
>
> Am 07.01.2016 um 13:51 schrieb Abraham Lee:
>
> > Greetings, all!
> >
> > Is there any kind soul out there that will show me how to get the total
> > page count so I can include that with the current page number (like
> > "1/3" ... "3/3")?
> >
> > Thanks,
> > Abraham
> >
> >
> > ___
> > lilypond-user mailing list
> > [hidden email] 
> > https://lists.gnu.org/mailman/listinfo/lilypond-user
> >
>
> ___
> lilypond-user mailing list
> [hidden email] 
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
> *pagenumber.ly * (1K) Download Attachment
> 
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://lilypond.1069038.n5.nabble.com/Include-total-page-count-in-page-number-tp185641p185643.html
> To start a new topic under User, email ml-node+s1069038n...@n5.nabble.com
> To unsubscribe from Lilypond, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Include-total-page-count-in-page-number-tp185641p185644.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: Bravura svg font

[Nathan Ho]

On 2016-01-07 15:49, Simon Albrecht wrote:


In case others be interested:

Nice and funny :-) Thanks, Abraham (and Mark)!

Yours, Simon


There aren't enough novelty music fonts out there. Once I was a kid and 
I entered "Take Me Out to the Ballgame" in Finale PrintMusic, then 
edited it in Paint to make the noteheads baseballs and to make the clefs 
wear little baseball caps.


Nathan

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

Re: How to reproduce this?

[Chris Yate]

Hi there,There's a few things wrong here...

I'd start by getting the voices separated. So  something like:

<<
   \quaver_triplet_stuff
% this will be voice 1 and stems-up
\\
   \chord_notes
% this will be voice 2, but you'll have to hide the stems. exercise for the
reader ;-)
>>

Chord notation here
http://www.lilypond.org/doc/v2.19/Documentation/notation/chord-notation

...



On 7 January 2016 at 16:06, Carl-Henrik Buschmann 
wrote:

> Hi,
>
> I'm a Lilypond newbie switching over from Sibelius. As part of my self
> tutoring I have tried my hand at reproducing a example (written in Sib) i
> used in my thesis:
>
> http://i.imgur.com/SboviWR.png
>
> I'm a bit stuck and i hope you guys can give me a nudge.
> This is my feeble attempt:
>
> \version "2.18.2"
> \language "german"
>
> <<
> \chords {
>   f2 gis4 dis b
> }
>
> \relative c'' {
>   \tuplet 3/2 { c8 c c }
>   \tuplet 3/2 { c c c }
>   \tuplet 3/2 { dis dis dis }
>   \tuplet 3/2 { dis dis dis } | %m1
>   fis4
> }
>
> \\
> \relative c' {
>   < f a c >2 < gis bis dis >4 < fisis ais dis > | %m1
>   < fis b dis >4
> }
> \addlyrics {
>   V2 bVII III/IV I
> }
> >>
>
> Product:
> http://i.imgur.com/Ot3HNE2.png
>
> I have many problems:
>
> 1) The chords are at the bottom.
> 2) The chords have the wrong font.
> 3) I have NO idea how to properly write roman numeral analysis, lyrics is
> not the way to go it seems.
> 4) The dottet phrasing line.
> 5) The 1. and 2. voice crash.
>
> Help?
>
> Buschmann
> ___
> 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: Strange beaming error

[Chris Yate]

On 7 January 2016 at 17:12, Mark Stephen Mrotek 
wrote:

> Chris,
>
>
>
> As I mentioned in a previous reply, make sure that identical “\set
> Timining” instructions are in both the upper and lower staff.
>
> Once this is done, recompile and check for accuracy.
>
>
>
> Mark
>
>
>
Thanks for the suggestion - I tried that but it didn't help.

In a general case I wouldn't always want the same beaming in each hand, so
if the output is sensitive to that it's probably a bug...

Anyway, Urs Liska has a Gist with my current code on this project, and I
gather is going to do a regression test in case there's a recent bug in
Lilypond.

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

Re: How to reproduce this?

[Pierre Perol-Schneider]

Hi Buschmann,

How about :

\version "2.18.2"
%\language "german"

\layout {
  \context {
\ChordNames
\override ChordName.font-family = #'serif
\override ChordName.font-size = #0
  }
}

<<
  \chords {
f2 gis4 dis b
  }
  <<
\relative c'' {
  \numericTimeSignature
  \voiceOne
  \tuplet 3/2 { c8 c c }
  \tuplet 3/2 { c c c }
  \tuplet 3/2 { dis dis dis }
  \tuplet 3/2 { dis dis dis } | %m1
  fis4
}
\new Voice = "Chords"
\relative c' {
  \voiceTwo
  \slurDashed
  \override Stem.stencil = ##f
  < f a c >2
  \override NoteColumn.force-hshift = #1
  < gis bis dis >4 ^( < fisis ais dis >)^( | %m1
  \revert NoteColumn.force-hshift
  < fis b dis >4)
}
  >>
  \addlyrics \lyricsto "Chords" {
V2
\markup\concat { \raise #.4 \small\flat VII }
\markup\center-column {
  \concat { \raise #.7 \small\sharp III }
  IV
}
I
  }
>>


Cheers,
Pierre

2016-01-07 17:06 GMT+01:00 Carl-Henrik Buschmann :

> Hi,
>
> I'm a Lilypond newbie switching over from Sibelius. As part of my self
> tutoring I have tried my hand at reproducing a example (written in Sib) i
> used in my thesis:
>
> http://i.imgur.com/SboviWR.png
>
> I'm a bit stuck and i hope you guys can give me a nudge.
> This is my feeble attempt:
>
> \version "2.18.2"
> \language "german"
>
> <<
> \chords {
>   f2 gis4 dis b
> }
>
> \relative c'' {
>   \tuplet 3/2 { c8 c c }
>   \tuplet 3/2 { c c c }
>   \tuplet 3/2 { dis dis dis }
>   \tuplet 3/2 { dis dis dis } | %m1
>   fis4
> }
>
> \\
> \relative c' {
>   < f a c >2 < gis bis dis >4 < fisis ais dis > | %m1
>   < fis b dis >4
> }
> \addlyrics {
>   V2 bVII III/IV I
> }
> >>
>
> Product:
> http://i.imgur.com/Ot3HNE2.png
>
> I have many problems:
>
> 1) The chords are at the bottom.
> 2) The chords have the wrong font.
> 3) I have NO idea how to properly write roman numeral analysis, lyrics is
> not the way to go it seems.
> 4) The dottet phrasing line.
> 5) The 1. and 2. voice crash.
>
> Help?
>
> Buschmann
> ___
> 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: How to reproduce this?

[Jacques Menu]

Hello Abraham,

Thanks, that works fine!

JM

> Le 7 janv. 2016 à 19:47, Abraham Lee  a écrit :
> 
> Jacques,
> 
> 
> 
> On Thu, Jan 7, 2016 at 11:42 AM, Jacques Menu  > wrote:
> Hello Pierre,
> 
> This doesn’t compile on 2.19.33 though.
> 
> Thanks for all the help you provide to the rest of us!
> 
> Try this out:
> 
> %<---
> 
> \version "2.19.31"
> 
> \layout {
>   \context {
> \ChordNames
> \override ChordName.font-family = #'roman
> \override ChordName.font-size = #0
>   }
> }
> 
> \score {
>   <<
> \new ChordNames \chords {
>   f2 gis4 dis b
> }
> \new Staff <<
>   \new Voice \relative c'' {
> \numericTimeSignature
> \voiceOne
> \tuplet 3/2 { c8 c c }
> \tuplet 3/2 { c c c }
> \tuplet 3/2 { dis dis dis }
> \tuplet 3/2 { dis dis dis } | %m1
> fis4
>   }
>   \new Voice = "chrds" \relative c' {
> \voiceTwo
> \tieDashed
> \set melismaBusyProperties = #'()
> \override Stem.stencil = ##f
> < f a c >2 
> \override NoteColumn.force-hshift = #1
> < gis bis dis^~>4 < fisis ais dis^~> | %m1
> \revert NoteColumn.force-hshift
> < fis b dis >4
>   }
> >>
> \new Lyrics \lyricsto "chrds" {
>   V
>   \markup\concat { \raise #.5 \small \flat VII }
>   \markup\center-column {
> \concat { \raise #.9 \small \sharp III }
> IV 
>   }
>   I
> }
>   >>
> }
> 
> %<---
> 
> HTH,
> Abraham 

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

Variable names

[Johan Vromans]

I assume there have been discussions on extending the syntax for LP
identifiers to include dashes and underscores. My personal opinion is that
a non-alpha separator is good to have, but two different separators may
quickly become confusing. Is it 'set_variable' or 'set-variable'?

Given the relation between LP and Guile, I'd suggest to only allow the dash
and disallow the underscore (by syntax rule, not just by convention).

-- Johan

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

How to reproduce this?

[Carl-Henrik Buschmann]

Hi,

I'm a Lilypond newbie switching over from Sibelius. As part of my self tutoring 
I have tried my hand at reproducing a example (written in Sib) i used in my 
thesis:

http://i.imgur.com/SboviWR.png

I'm a bit stuck and i hope you guys can give me a nudge. 
This is my feeble attempt:

\version "2.18.2"
\language "german"

<<
\chords { 
  f2 gis4 dis b 
}

\relative c'' {
  \tuplet 3/2 { c8 c c }
  \tuplet 3/2 { c c c }
  \tuplet 3/2 { dis dis dis }
  \tuplet 3/2 { dis dis dis } | %m1
  fis4
}

\\
\relative c' {
  < f a c >2 < gis bis dis >4 < fisis ais dis > | %m1
  < fis b dis >4
}
\addlyrics { 
  V2 bVII III/IV I 
}
>>

Product:
http://i.imgur.com/Ot3HNE2.png

I have many problems:

1) The chords are at the bottom.
2) The chords have the wrong font.
3) I have NO idea how to properly write roman numeral analysis, lyrics is not 
the way to go it seems.
4) The dottet phrasing line.
5) The 1. and 2. voice crash. 

Help?

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

Re: Variable names

[H. S. Teoh]

On Thu, Jan 07, 2016 at 08:59:22PM +0100, Johan Vromans wrote:
> I assume there have been discussions on extending the syntax for LP
> identifiers to include dashes and underscores. My personal opinion is
> that a non-alpha separator is good to have, but two different
> separators may quickly become confusing. Is it 'set_variable' or
> 'set-variable'?
> 
> Given the relation between LP and Guile, I'd suggest to only allow the
> dash and disallow the underscore (by syntax rule, not just by
> convention).
[...]

I think extending identifiers to include '-' and '_' is a bad idea. They
introduce ambiguities in cases like:

c1\myCustomMarkup_"text"-\pp-\moreCustomMarkup-.


T

-- 
Customer support: the art of getting your clients to pay for your own 
incompetence.

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

Rewriting an expression that uses ly:make-simple-closure

[Paul Morris]

Hi all,  Here’s a tricky one…  I’m working on updating a piece from the Mutopia 
Project[1] (from LilyPond 2.16.1 to 2.19.35) and it uses the following:

centermarkup = {
  \once \override TextScript.self-alignment-X = #CENTER
  \once \override TextScript.X-offset =#(ly:make-simple-closure
`(,+
  ,(ly:make-simple-closure (list
ly:self-alignment-interface::centered-on-x-parent))
  ,(ly:make-simple-closure (list
ly:self-alignment-interface::x-aligned-on-self
}

But ly:make-simple-closure is no longer around[2].  So how to rewrite this 
without it?

It seems to be documented (barely) in the 2.18 extending manual:
http://www.lilypond.org/doc/v2.18/Documentation/extending/callback-functions.html

Looking in the source code I find the example given there from define-grobs.scm:

(X-offset . ,(ly:make-simple-closure
  `(,+
,(ly:make-simple-closure
  (list 
ly:self-alignment-interface::centered-on-x-parent))
,(ly:make-simple-closure
  (list 
ly:self-alignment-interface::x-aligned-on-self)

and see it has now become the following in 2.19.35:

(X-offset . ,ly:self-alignment-interface::aligned-on-x-parent)

So would the following be an equivalent rewrite?

centermarkup = {
  \once \override TextScript.self-alignment-X = #CENTER
  \once \override TextScript.X-offset = 
  #ly:self-alignment-interface::aligned-on-x-parent
}

I can’t see a difference in the minimal example below (taken from the piece).

Thanks,
-Paul

[1] http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=1938
[2] https://lists.gnu.org/archive/html/lilypond-devel/2015-09/msg00273.html


%%
\version "2.18"

centermarkup = {
  \once \override TextScript.self-alignment-X = #CENTER
  \once \override TextScript.X-offset =
  #(ly:make-simple-closure
`(,+
   ,(ly:make-simple-closure (list
 
ly:self-alignment-interface::centered-on-x-parent))
   ,(ly:make-simple-closure (list
 
ly:self-alignment-interface::x-aligned-on-self
}

centermarkup-new  = {
  \once \override TextScript.self-alignment-X = #CENTER
  \once \override TextScript.X-offset = 
  #ly:self-alignment-interface::aligned-on-x-parent
}

{
  \key fis \minor
  \time 3/2

  fis2  \once \override Voice.TextScript.extra-offset = #'(0.0 . -1.1 ) 
eis1^\markup { \override #'( baseline-skip . 1.3 ) \column { \finger " 4" 
\finger " 1" \concat {  \musicglyph #"scripts.tenuto" \hspace #0.8  \musicglyph 
#"scripts.turn" } } }-\tweak stencil ##f \turn | % 19

  fis2 \centermarkup  \once \override Voice.TextScript.extra-offset = #'(0.0 . 
-1.1 ) eis1^\markup { \override #'( baseline-skip . 1.3 ) \column { \finger " 
4" \finger " 1" \concat {  \musicglyph #"scripts.tenuto" \hspace #0.8  
\musicglyph #"scripts.turn" } } }-\tweak stencil ##f \turn | % 19

  fis2 \centermarkup-new  \once \override Voice.TextScript.extra-offset = 
#'(0.0 . -1.1 ) eis1^\markup { \override #'( baseline-skip . 1.3 ) \column { 
\finger " 4" \finger " 1" \concat {  \musicglyph #"scripts.tenuto" \hspace #0.8 
 \musicglyph #"scripts.turn" } } }-\tweak stencil ##f \turn | % 19
}

%%%




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

Re: How to reproduce this?

[Carl-Henrik Buschmann]

Thank you, much obliged!

1)
I didnt get...

  \addlyrics \lyricsto "Chords" {
V2 
\markup\concat { \raise #.4 \small\flat VII } 
\markup\center-column {
  \concat { \raise #.7 \small\sharp III }
  IV 
}
I
  }

...to work though:

http://i.imgur.com/aVeeG1V.png

2)
How do i raise the stems to make room for the dotted slurs?

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

Re: How to reproduce this?

[Carl-Henrik Buschmann]

Thats it! Thank you, this was inspiring.


Buschmann 

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

Re: How to reproduce this?

[Abraham Lee]

Jacques,



On Thu, Jan 7, 2016 at 11:42 AM, Jacques Menu  wrote:

> Hello Pierre,
>
> This doesn’t compile on 2.19.33 though.
>
> Thanks for all the help you provide to the rest of us!
>

Try this out:

%<---

\version "2.19.31"

\layout {
  \context {
\ChordNames
\override ChordName.font-family = #'roman
\override ChordName.font-size = #0
  }
}

\score {
  <<
\new ChordNames \chords {
  f2 gis4 dis b
}
\new Staff <<
  \new Voice \relative c'' {
\numericTimeSignature
\voiceOne
\tuplet 3/2 { c8 c c }
\tuplet 3/2 { c c c }
\tuplet 3/2 { dis dis dis }
\tuplet 3/2 { dis dis dis } | %m1
fis4
  }
  \new Voice = "chrds" \relative c' {
\voiceTwo
\tieDashed
\set melismaBusyProperties = #'()
\override Stem.stencil = ##f
< f a c >2
\override NoteColumn.force-hshift = #1
< gis bis dis^~>4 < fisis ais dis^~> | %m1
\revert NoteColumn.force-hshift
< fis b dis >4
  }
>>
\new Lyrics \lyricsto "chrds" {
  V
  \markup\concat { \raise #.5 \small \flat VII }
  \markup\center-column {
\concat { \raise #.9 \small \sharp III }
IV
  }
  I
}
  >>
}

%<---

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

Re: Strange beaming error

[Urs Liska]

Am 07.01.2016 um 18:24 schrieb Chris Yate:
> On 7 January 2016 at 17:12, Mark Stephen Mrotek  > wrote:
>
> Chris,
>
>  
>
> As I mentioned in a previous reply, make sure that identical “\set
> Timining” instructions are in both the upper and lower staff.
>
> Once this is done, recompile and check for accuracy.
>
>  
>
> Mark
>
>
>
> Thanks for the suggestion - I tried that but it didn't help. 
>
> In a general case I wouldn't always want the same beaming in each
> hand, so if the output is sensitive to that it's probably a bug... 
>
> Anyway, Urs Liska has a Gist with my current code on this project, and
> I gather is going to do a regression test in case there's a recent bug
> in Lilypond.

I've nearly tracked it down to input coding, but couldn't finish it
before having to leave ...

I'll send something later tonight.

Urs

>
> Chris
>
>
> ___
> 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: How to reproduce this?

[Jacques Menu]

Hello Pierre,

This doesn’t compile on 2.19.33 though.

Thanks for all the help you provide to the rest of us!

JM

Starting lilypond 2.19.33 [Untitled]...
Processing 
`/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-mmxLK7/tmpXWfERQ/document.ly'
Parsing...
/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-mmxLK7/tmpXWfERQ/document.ly:41:14
 : error: syntax error, 
unexpected \lyricsto, expecting \sequential or \simultaneous or << or '{'
\addlyrics
\lyricsto "Chords" {
/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-mmxLK7/tmpXWfERQ/document.ly:50:3
 : error: Unfinished 
main input
>>
/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-mmxLK7/tmpXWfERQ/document.ly:13:1
 : error: errors found, 
ignoring music expression

<<
fatal error: failed files: 
"/var/folders/jc/xrpy67_x6_vcjfzpzds_9_6mgn/T/frescobaldi-mmxLK7/tmpXWfERQ/document.ly"
Exited with return code 1.


> Le 7 janv. 2016 à 19:23, Pierre Perol-Schneider 
>  a écrit :
> 
> Oops, my fault, I forgot about the slur.
> So here it goes,
> 
> \version "2.18.2"
> %\language "german"
> 
> \layout {
>   \context {
> \ChordNames
> \override ChordName.font-family = #'serif
> \override ChordName.font-size = #0
>   }
> }
> 
> <<
>   \chords {
> f2 gis4 dis b
>   }
>   <<
> \relative c'' {
>   \numericTimeSignature
>   \voiceOne
>   \tuplet 3/2 { c8 c c }
>   \tuplet 3/2 { c c c }
>   \override Beam.positions = #'(4 . 4)
>   \tuplet 3/2 { dis dis dis }
>   \tuplet 3/2 { dis dis dis } | %m1
>   fis4
> }
> \new Voice = "Chords"
> \relative c' {
>   \voiceTwo
>   \slurDashed
>   \set melismaBusyProperties = #'()
>   \override Stem.stencil = ##f
>   < f a c >2 
>   \override NoteColumn.force-hshift = #1
>   < gis bis dis >4 ^( < fisis ais dis >)^( | %m1
>   \revert NoteColumn.force-hshift
>   < fis b dis >4)
> } 
>   >>
>   \addlyrics \lyricsto "Chords" {
> V2 
> \markup\concat { \raise #.4 \small\flat VII } 
> \markup\center-column {
>   \concat { \raise #.7 \small\sharp III }
>   IV 
> }
> I
>   }
> >>
> 
> Cheers,
> Pierre
> 
> 2016-01-07 18:55 GMT+01:00 Carl-Henrik Buschmann  >:
> Thank you, much obliged!
> 
> 1)
> I didnt get...
> 
>   \addlyrics \lyricsto "Chords" {
> V2
> \markup\concat { \raise #.4 \small\flat VII }
> \markup\center-column {
>   \concat { \raise #.7 \small\sharp III }
>   IV
> }
> I
>   }
> 
> ...to work though:
> 
> http://i.imgur.com/aVeeG1V.png 
> 
> 2)
> How do i raise the stems to make room for the dotted slurs?
> 
> ___
> 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: How to reproduce this?

[Malte Meyn]

Am 07.01.2016 um 21:59 schrieb Simon Albrecht:
> \offset positions #'(.5 . .5) Beam

I’ve never seen that function before and I don’t find it in the
documentation. Since when does this exist? (it’s defined in
music-functions-init.ly)

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

Re: How to reproduce this?

[Malte Meyn]

Am 07.01.2016 um 22:53 schrieb Malte Meyn:
> 
> 
> Am 07.01.2016 um 21:59 schrieb Simon Albrecht:
>> \offset positions #'(.5 . .5) Beam
> 
> I’ve never seen that function before and I don’t find it in the
> documentation. Since when does this exist? (it’s defined in
> music-functions-init.ly)
> 

git blame tells me this comes from commit a82d8622 in April 2013, so
this is new in version 2.18.

It’s documented neither in the Changes, nor in the Learning Manual nor
in the Notation Reference.

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

Re: How to reproduce this?

[Simon Albrecht]

On 07.01.2016 23:00, Malte Meyn wrote:


Am 07.01.2016 um 22:53 schrieb Malte Meyn:


Am 07.01.2016 um 21:59 schrieb Simon Albrecht:

 \offset positions #'(.5 . .5) Beam

I’ve never seen that function before and I don’t find it in the
documentation. Since when does this exist? (it’s defined in
music-functions-init.ly)


git blame tells me this comes from commit a82d8622 in April 2013, so
this is new in version 2.18.

It’s documented neither in the Changes, nor in the Learning Manual nor
in the Notation Reference.


It has the automatic documentation in NR A.19, but still, you need to 
know it exists… Yes, we should document it. See 
.


Yours, Simon

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

Re: How to reproduce this?

[Simon Albrecht]

On 07.01.2016 19:23, Pierre Perol-Schneider wrote:

Oops, my fault, I forgot about the slur.
So here it goes,

\version "2.18.2"
%\language "german"

\layout {
  \context {
\ChordNames
\override ChordName.font-family = #'serif
\override ChordName.font-size = #0
  }
}

<<
  \chords {
f2 gis4 dis b
  }
  <<
\relative c'' {
  \numericTimeSignature
  \voiceOne
  \tuplet 3/2 { c8 c c }
  \tuplet 3/2 { c c c }
  \override Beam.positions = #'(4 . 4)
  \tuplet 3/2 { dis dis dis }
  \tuplet 3/2 { dis dis dis } | %m1


For the five preceding lines, I’d rather do:
  \tuplet 3/2 4 {
c8 c c c c c
\offset positions #'(.5 . .5) Beam
dis dis dis dis dis dis
\revert Beam.positions
  } | %m1

Easier to read, write and maintain.

Best, Simon

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

Re: Include total page count in page number

[Thomas Morley]

2016-01-07 16:55 GMT+01:00 Jan-Peter Voigt :
> Ah, yes
> To use \page-ref is another option. You just need a label at the end of the
> last score.
>
> Chefredakteur
> Jan-Peter
>
> Am 7. Januar 2016 15:43:26 MEZ, schrieb Robin Bannister :
>>
>>   tisimst wrote:
>>>
>>>  Thank you! That will at least get me by for now.
>>
>>
>>
>> See also
>> http://lists.gnu.org/archive/html/lilypond-user/2010-08/msg00403.html
>>
>>
>> Cheers,
>> Robin


Another aproach:

http://lilypond.1069038.n5.nabble.com/Custom-footers-td142761.html#a143356

Cheers,
  Harm

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

Re: Strange beaming error

[Urs Liska]

Hi Chris,

OK, I've now compiled your score (thanks for the gist, looks nice BTW)
and went through the beaming issues I could see.

First of all I must say that the new subdivision logic (introduced in
2.19.35) seems to do what I wanted and is actually an improvement:
Compare 01.png to 02.png and 03.png and tell me which one gives you a
more immediate idea of the music ...
(and just in case anyone is in doubt: 01 is the new one and how it
should be done, 02 is 2.19.34, and 03 is 2.19.19 (and any older version).

###

First issue I saw is shown in 04.png (m. 21)
Note that the music is in 6/8.
I'm not sure this qualifies as a bug as it is actually wrongly coded with
\set Timing.baseMoment = (ly:make-moment 1/16)
\set Timing.beatStructure = #'(6 6)

You should change that to
\set baseMoment = (ly:make-moment 1/8)
\set beatStructure = #'(3 3)
, then the result is correct as per 05.png.
But I suggest you don't subdivide here at all (as you have correctly do
in the l.h.) - or if you would consider subdivisions as the way to go
then at least do it in both hands.

###

However, a possible issue is shown in 06.png.
Here it may be wrong that the first beam has a beamlet instead of two
beams. This is a case for David's suggestion to write down *all* rules.
The issue is that the durations are the same as baseMoment - but here it
is used correctly (other than with the first example). This notation is
very useful if you have a single trailing note on a beam after a
subdivision, but here it seems slightly strange.

###

I couldn't reproduce the issue shown in your initial message, though.

###

Is there any issue I overlooked?

Best
Urs

Am 07.01.2016 um 00:53 schrieb Chris Yate:
> Hi, 
>
> I'm wondering whether anyone can shed some light on the attached image.
>
> LH of the piano here is:
>
> {
>  bf,16 (ef g8) r8
>   c,16 g' c, g' bf, g'
>   \clef bass
> }
>
> I have a suspicion this may have something to do with the Timing /
> beat moment and beat structure, but it's inconclusive. This section of
> the music has:
>
>   \set Timing.baseMoment = #(ly:make-moment 1/16)
>   \set Timing.beatStructure = #'( 6 6 )
>
> There are no barline errors, but I'm seeing this in the output quite a
> lot: 
>
> programming error: mis-predicted force, 108.120472 ~= 101.465263
>
> continuing, cross fingers
>
> programming error: mis-predicted force, 108.120472 ~= 105.654382
>
> continuing, cross fingers
>
> programming error: mis-predicted force, 108.120472 ~= 101.465263
>
> continuing, cross fingers
>
>
>
> Previously I was getting a similar issue where I had bars of 6
> quavers, which were grouped in 3's -- and the middle of the second
> group was getting a spurious semiquaver beam. I seem to fixed it,
> though I'm not sure what the cause was.
>
> Thanks in advance,
>
> Chris
>
> Inline images 1
>
>
> ___
> 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