Re: \tempo sticks out to the right
Werner LEMBERG wl at gnu.org writes: How can I avoid that the \tempo string sticks out to the right? I forbid line-breaks for the next one or two measures. \tempo a very long tempo string c4 c c c |\noBreak ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \tempo sticks out to the right
Il 29/04/2012 07:58, Werner LEMBERG ha scritto:
Attached is its output. How can I avoid that the \tempo string sticks
out to the right?
This is the only workaround that comes to my mind, but probably it's not
what you are looking for:
\tempo \markup {
\center-column {
\line { a very long }
\line { tempo string }
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \tempo sticks out to the right
How can I avoid that the \tempo string sticks out to the right? I forbid line-breaks for the next one or two measures. \tempo a very long tempo string c4 c c c |\noBreak Thanks, I've found this already by myself; one \noBreak is not enough, two \noBreak will do. However, this is not a solution, this is an ugly hack. Why doesn't handle `keep-inside-line' this situation? Can this be added? Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: programming error: cyclic dependency
On 04/28/2012 07:51 PM, m...@apollinemike.com wrote: On 28 avr. 2012, at 19:48, Peter O'Doherty wrote: Hi list, After updating my system to Ubuntu 11.10 (although I can't see why this is relevant but this is the only change I've made to the system recently), code which previously output no error is full of these errors: warning: programming error: cyclic dependency: calculation-in-progress encountered for #'positions (Beam) I don't see anything strange in the final pdf file so is this warning to be ignored? Many thanks, Peter Lots of work was done in beams in 2.13 and 2.15. If you could send a minimal example (of one beam, say) and the version number, it'll be easy to ID if the problem has been fixed in more recent versions. But this is a problem - it means that beam positions are being calculated to early in the LilyPond compilation process. I just upgraded to Ubuntu 12.04 and the error messages are gone. Don't quite understand that one. Thanks, Peter -- //= - Peter O'Doherty - http://www.peterodoherty.net - m...@peterodoherty.net - https://joindiaspora.com/people/70716 //= ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \tempo sticks out to the right
This is the only workaround that comes to my mind, but probably it's
not what you are looking for:
\tempo \markup {
\center-column {
\line { a very long }
\line { tempo string }
}
}
Indeed, this is a viable solution sometimes, e.g. in parts. Ideally,
\tempo should accept an optional argument to provide an alternative
markup for extremely tight situations.
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \tempo sticks out to the right
Werner,
2012/4/29 Werner LEMBERG w...@gnu.org:
Folks,
consider this example:
\version 2.15.37
\relative c'' {
c4 c c c |
c4 c c c |
c4 c c c |
c4 c c c |
c4 c c c |
c4 c c c |
\tempo a very long tempo string c4 c c c |
c4 c c c |
c4 c c c |
c4 c c c |
c4 c c c |
c4 c c c |
c4 c c c |
c4 c c c |
c4 c c c |
c4 c c c |
}
Attached is its output. How can I avoid that the \tempo string sticks
out to the right?
I think this is
http://code.google.com/p/lilypond/issues/detail?id=1133
James
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \tempo sticks out to the right
Attached is its output. How can I avoid that the \tempo string sticks out to the right? I think this is http://code.google.com/p/lilypond/issues/detail?id=1133 Mhmm, not really, I think. As can be seen in my example, lilypond increases the spacing in the bar, but the \tempo still sticks out to the right. It's certainly connected, but maybe two problems overlap. Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
\harmonicByFret #2.7
Hi, I was looking at this snippet: http://lsr.dsi.unimi.it/LSR/Item?id=819 can anyone explain which fret is 2.7? :-) This snippet is included in the documentation, inside a section for *fretted* instruments: http://lilypond.org/doc/v2.15/Documentation/notation/common-notation-for-fretted-strings#index-harmonic-indications-in-tablature-notation At first I thought it was an output bug, but then I see that it was intended. So I guess that, not surprisingly, I'm missing something about harmonics. Maybe this explanation could be added to the documentation. Thanks, Federico ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \harmonicByFret #2.7
Hi Federico, when you touch the string two thirds in between fret 2 and 3 the sounding pitch is two octaves and a seventh above the open string. So 2.7 is an approximation of 2.6… hth patrick Am 29.04.2012 um 13:32 schrieb Federico Bruni: Hi, I was looking at this snippet: http://lsr.dsi.unimi.it/LSR/Item?id=819 can anyone explain which fret is 2.7? :-) This snippet is included in the documentation, inside a section for *fretted* instruments: http://lilypond.org/doc/v2.15/Documentation/notation/common-notation-for-fretted-strings#index-harmonic-indications-in-tablature-notation At first I thought it was an output bug, but then I see that it was intended. So I guess that, not surprisingly, I'm missing something about harmonics. Maybe this explanation could be added to the documentation. Thanks, Federico ___ 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: \harmonicByFret #2.7
Il 29/04/2012 13:59, pls ha scritto: Hi Federico, when you touch the string two thirds in between fret 2 and 3 the sounding pitch is two octaves and a seventh above the open string. So 2.7 is an approximation of 2.6… hth patrick Hi Patrick, thanks, found both 2.3 and 2.7 :) I was puzzled because I've never found a piece using such harmonics. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Override of fingering font is ignored by \finger
2012/4/29 Nick Payne nick.pa...@internode.on.net:
See attached. Overriding the fingering font works fine for fingering
attached to a note but is ignored when using \finger in a markup, where the
default fingering font is still used.
\version 2.15.37
\relative c'' {
\override Staff.Fingering #'font-name = #'Arial Black
e-44 cis d\prall^\markup { \concat { \finger 4 \hspace #0.15 \tiny { / }
\finger 2 } }
}
Hi Nick,
in e-44 the fingering is an articulation.
\markup { \finger 2 } is TextScript. If you want an other font use
\override TextScript #'font-name = #'Arial Black
or more selectively
\markup { \override #'(font-name . Arial Black) \finger 2 }
HTH,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: \harmonicByFret #2.7
Am 29.04.2012 um 14:15 schrieb Federico Bruni: Il 29/04/2012 13:59, pls ha scritto: Hi Federico, when you touch the string two thirds in between fret 2 and 3 the sounding pitch is two octaves and a seventh above the open string. So 2.7 is an approximation of 2.6… hth patrick Hi Patrick, thanks, found both 2.3 and 2.7 :) I was puzzled because I've never found a piece using such harmonics. I can't think of a classical piece right now. I'm sure you can find these harmonics in loads of rock and metal scores... ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
top posting
I don't know what you're talking about. I tried posting this message twice, once with the example code after my message, and a second time with the example at the top. Both times I've gotten a top posting error. This is a new thread so there's nothing to post below. Any suggestions? Mike ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Lilypond 2.16 fedora 17
Hi, Any chance Lilypond 2.16 will be accepted in Fedora 17 ? -- MT ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond bug 2368
On Sat, Apr 28, 2012 at 7:49 PM, m...@apollinemike.com m...@apollinemike.com wrote: There's been a lot of back and forth on a few LilyPond lists about improving ties. I'm of the opinion that the system in place is sound (it is a similar system as that of slurs and beams), but what needs improvement is an understanding of how much factors are worth and where they make the difference. We've made some headway in slurs in 2.15 by removing unnecessary factors and decorolating them but we haven't been able to do the same yet for ties. So, my advice to everyone would be to play around with this details list. Surely i will experiment when i'll be finishing my tie report :) However, given how often current ties fail, i'm pretty sure that the current system is not good. I have a strong feeling that it's an overkill; from what i've already seen i could probably write a deterministic algorithm that would perform better in many cases and use half as much parameters. I may be wrong; however, i think that the core of the problem is that while slurs are really complicated and need advanced heuristics and guesswork, ties are significantly more straightforward. cheers, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond 2.16 fedora 17
Martin Tarenskeen m.tarensk...@zonnet.nl writes: Hi, Any chance Lilypond 2.16 will be accepted in Fedora 17 ? First it needs to get accepted in LilyPond. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond 2.16 fedora 17
Martin, On 29 April 2012 17:28, Martin Tarenskeen m.tarensk...@zonnet.nl wrote: Hi, Any chance Lilypond 2.16 will be accepted in Fedora 17 ? You need to talk to the/a Fedora Maintainer to get them to package it. No one as far as I know who contributes to the LP project does this actively. I'm not that technically savvy on this topic, but I seem to recall that because of LP's use of Guile 1.8 and not Guile 2.0 that it caused some headaches (they are not (very/at all) backward compatible) for another distribution package maintainer. James ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Problem with articulate.ly
Nick == Nick Payne nick.pa...@internode.on.net writes:
Nick The example below builds without error and gives the output I
Nick want. However, if I include articulate.ly, then the output is
Nick garbaged even though I haven't used \unfoldRepeats \articulate,
Nick and I get the following warnings in the log:
That's because you have a two-note argument to \appogiature. Use
\grace instead --- an appogiatura should only be one note. Articulate
changes the default meaning of appoggiatura so the ornament steals
time from the principal note not the preceding note.
Nick /home/nick/lilypond/examples/test.ly:8:59: warning: already have
Nick a beam \times 4/6 { a32[( g) fis( g) \appoggiatura { fis16 [ g]
Nick } a32 g] } warning: cannot end slur warning: unterminated slur
--
Dr Peter Chubb peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au Software Systems Research Group/NICTA
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
BarNumber-value?
Hi,
in 2.14.2 I used a function to manipulate the BarNumber-stencil. It
calls the value of the BarNumber as a string, via (ly:grob-property
grob 'text).
This doesn't work no longer with the latest devel-versions. (Due to
the changes in Issue 2059 ?)
(ly:grob-property grob 'text) now returns, e.g. (#procedure
line-markup (layout props args) (2))
How to do with 2.15.36?
Below a simplified example.
\version 2.14.2
\relative c'' {
\override Score.BarNumber #'break-visibility = #'#(#f #t #t)
\override Score.BarNumber #'stencil =
#(lambda (grob)
(let* ((stil (ly:text-interface::print grob))
(text (ly:grob-property grob 'text))
(nmbr (string-number text)))
(if (= (remainder nmbr 5) 0)
(ly:grob-set-property! grob 'color red)
(ly:grob-set-property! grob 'color black))
stil))
\repeat unfold 41 { c1 }
}
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: BarNumber-value?
Hi Harm,
On Sun, Apr 29, 2012 at 5:55 PM, Thomas Morley
thomasmorle...@googlemail.com wrote:
Hi,
in 2.14.2 I used a function to manipulate the BarNumber-stencil. It
calls the value of the BarNumber as a string, via (ly:grob-property
grob 'text).
This doesn't work no longer with the latest devel-versions. (Due to
the changes in Issue 2059 ?)
(ly:grob-property grob 'text) now returns, e.g. (#procedure
line-markup (layout props args) (2))
How to do with 2.15.36?
Below a simplified example.
\version 2.14.2
\relative c'' {
\override Score.BarNumber #'break-visibility = #'#(#f #t #t)
\override Score.BarNumber #'stencil =
#(lambda (grob)
(let* ((stil (ly:text-interface::print grob))
(text (ly:grob-property grob 'text))
(nmbr (string-number text)))
(if (= (remainder nmbr 5) 0)
(ly:grob-set-property! grob 'color red)
(ly:grob-set-property! grob 'color black))
stil))
\repeat unfold 41 { c1 }
}
Lucky guess, but replacing text in your definition of nmbr with the
following gets me a red number every five bars with 2.15.37:
(markup-string text)
-David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: BarNumber-value?
Hi David,
2012/4/30 David Nalesnik david.nales...@gmail.com:
Hi Harm,
On Sun, Apr 29, 2012 at 5:55 PM, Thomas Morley
thomasmorle...@googlemail.com wrote:
Hi,
in 2.14.2 I used a function to manipulate the BarNumber-stencil. It
calls the value of the BarNumber as a string, via (ly:grob-property
grob 'text).
This doesn't work no longer with the latest devel-versions. (Due to
the changes in Issue 2059 ?)
(ly:grob-property grob 'text) now returns, e.g. (#procedure
line-markup (layout props args) (2))
How to do with 2.15.36?
Below a simplified example.
\version 2.14.2
\relative c'' {
\override Score.BarNumber #'break-visibility = #'#(#f #t #t)
\override Score.BarNumber #'stencil =
#(lambda (grob)
(let* ((stil (ly:text-interface::print grob))
(text (ly:grob-property grob 'text))
(nmbr (string-number text)))
(if (= (remainder nmbr 5) 0)
(ly:grob-set-property! grob 'color red)
(ly:grob-set-property! grob 'color black))
stil))
\repeat unfold 41 { c1 }
}
Lucky guess, but replacing text in your definition of nmbr with the
following gets me a red number every five bars with 2.15.37:
(markup-string text)
-David
that's it.
Thanks again,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: lilypond-user Digest, Vol 113, Issue 99
\version 2.15.37
\relative c'' {
\override Score.BarNumber #'break-visibility = #'#(#f #t #t)
\override Score.BarNumber #'stencil =
#(lambda (grob)
(let* ((stil (ly:text-interface::print grob))
(text (ly:grob-property grob 'text))
((markup-string text) (string-number text)))
(if (= (remainder (markup-string text) 5) 0)
(ly:grob-set-property! grob 'color red)
(ly:grob-set-property! grob 'color black))
stil))
\repeat unfold 41 { c1 }
}
I try replacing nmbr with (markup-string text) as suggest by David Nalesnik
and I get the following error. Appreciate help.
Starting lilypond.exe 2.15.37 [lily_test-bar-number.ly]...
Processing `lily_test-bar-number.ly'
Parsing...
Interpreting music... [8][16][24][32][40]
Preprocessing graphical objects...lily_test-bar-number.ly:9:21: In procedure
memoization in expression (let* (# # #) (if # # ...) ...):
lily_test-bar-number.ly:9:21: In file lily_test-bar-number.ly, line 10: Bad
variable (markup-string text) in expression (let* ((stil
(ly:text-interface::print grob)) (text (ly:grob-property grob (quote text)))
((markup-string text) (string-number text))) (if (= (remainder
(markup-string text) 5) 0) (ly:grob-set-property! grob (quote color) red)
(ly:grob-set-property! grob (quote color) black)) stil).
Exited with return code 1.
Blessing in+,
Date: Sun, 29 Apr 2012 18:07:33 -0500
From: David Nalesnik david.nales...@gmail.com
To: Thomas Morley thomasmorle...@googlemail.com
Cc: lilypond-user lilypond-user@gnu.org
Subject: Re: BarNumber-value?
Message-ID:
CANn-nXk-uNvVRm+Brc7y-Yze7mXSMUOm-R1AvOXe=zxquo8...@mail.gmail.com
Content-Type: text/plain; charset=iso-8859-1
Hi Harm,
On Sun, Apr 29, 2012 at 5:55 PM, Thomas Morley
thomasmorle...@googlemail.com wrote:
Hi,
in 2.14.2 I used a function to manipulate the BarNumber-stencil. It
calls the value of the BarNumber as a string, via (ly:grob-property
grob 'text).
This doesn't work no longer with the latest devel-versions. (Due to
the changes in Issue 2059 ?)
(ly:grob-property grob 'text) now returns, e.g. (#procedure
line-markup (layout props args) (2))
How to do with 2.15.36?
Below a simplified example.
\version 2.14.2
\relative c'' {
\override Score.BarNumber #'break-visibility = #'#(#f #t #t)
\override Score.BarNumber #'stencil =
#(lambda (grob)
(let* ((stil (ly:text-interface::print grob))
(text (ly:grob-property grob 'text))
(nmbr (string-number text)))
(if (= (remainder nmbr 5) 0)
(ly:grob-set-property! grob 'color red)
(ly:grob-set-property! grob 'color black))
stil))
\repeat unfold 41 { c1 }
}
Lucky guess, but replacing text in your definition of nmbr with the
following gets me a red number every five bars with 2.15.37:
(markup-string text)
-David
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.gnu.org/archive/html/lilypond-user/attachments/20120429/866be2bf/attachment.html
--
Date: Mon, 30 Apr 2012 01:41:36 +0200
From: Thomas Morley thomasmorle...@googlemail.com
To: David Nalesnik david.nales...@gmail.com
Cc: lilypond-user lilypond-user@gnu.org
Subject: Re: BarNumber-value?
Message-ID:
cabsfgyxbjtasrhfucmdvvnevrqzftsg17jsas7rwwezxtsv...@mail.gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Hi David,
2012/4/30 David Nalesnik david.nales...@gmail.com:
Hi Harm,
On Sun, Apr 29, 2012 at 5:55 PM, Thomas Morley
thomasmorle...@googlemail.com wrote:
Hi,
in 2.14.2 I used a function to manipulate the BarNumber-stencil. It
calls the value of the BarNumber as a string, via (ly:grob-property
grob 'text).
This doesn't work no longer with the latest devel-versions. (Due to
the changes in Issue 2059 ?)
(ly:grob-property grob 'text) now returns, e.g. (#procedure
line-markup (layout props args) (2))
How to do with 2.15.36?
Below a simplified example.
\version 2.14.2
\relative c'' {
? ? ? ?\override Score.BarNumber #'break-visibility = #'#(#f #t #t)
? ? ? ?\override Score.BarNumber #'stencil =
? ? ? ? ? ? ? ? ?#(lambda (grob)
? ? ? ? ? ? ? ? ? ?(let* ((stil (ly:text-interface::print grob))
? ? ? ? ? ? ? ? ? ? ? ? ? (text (ly:grob-property grob 'text))
? ? ? ? ? ? ? ? ? ? ? ? ? (nmbr (string-number text)))
? ? ? ? ? ? ? ? ? ?(if (= (remainder nmbr 5) 0)
? ? ? ? ? ? ? ? ? ? ? (ly:grob-set-property! grob 'color red)
? ? ? ? ? ? ? ? ? ? ? (ly:grob-set-property! grob 'color black))
? ? ? ? ? ? ? ? ? ?stil))
? ? ? ?\repeat unfold 41 { c1 }
}
Lucky guess, but replacing text in your definition of nmbr with the
following gets me a red number every five bars with 2.15.37:
(markup-string text)
-David
that's it.
Thanks again,
Harm
--
___
lilypond-user mailing list
Re: lilypond-user Digest, Vol 113, Issue 99
Hi,
On Sun, Apr 29, 2012 at 8:37 PM, MING TSANG tsan...@rogers.com wrote:
\version 2.15.37
\relative c'' {
\override Score.BarNumber #'break-visibility = #'#(#f #t #t)
\override Score.BarNumber #'stencil =
#(lambda (grob)
(let* ((stil (ly:text-interface::print grob))
(text (ly:grob-property grob 'text))
((markup-string text) (string-number text)))
(if (= (remainder (markup-string text) 5) 0)
(ly:grob-set-property! grob 'color red)
(ly:grob-set-property! grob 'color black))
stil))
\repeat unfold 41 { c1 }
}
I try replacing nmbr with (markup-string text) as suggest by David
Nalesnik and I get the following error. Appreciate help.
This is how to do it:
\relative c'' {
\override Score.BarNumber #'break-visibility = #'#(#f #t #t)
\override Score.BarNumber #'stencil =
#(lambda (grob)
(let* ((stil (ly:text-interface::print grob))
(text (ly:grob-property grob 'text))
(nmbr (string-number (markup-string text
(if (= (remainder nmbr 5) 0)
(ly:grob-set-property! grob 'color red)
(ly:grob-set-property! grob 'color black))
stil))
\repeat unfold 41 { c1 }
}
Best,
David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Pondings
Hey LilyPond users, On the LilyPond website's upper righthand corner, we'll be starting in a few days a Pondings column. This column will house a rotating cast of tweet-sized messages about LilyPond-related projects. Anyone can submit a Ponding, and I encourage you to do so! Three ground rules: 1) Keep it pertinent. A ponding needs to be something that makes LilyPond look good - a concert featuring LilyPond typeset works, pedagogy about LilyPond, published articles/theses, conference about LilyPond, blog about LilyPond, a website that uses LilyPond somehow, etc.. 2) Keep it profanity-free. 3) Keep it informational. No calls to action (i.e. come see concert X, donate to tour Y) aside from click here to read more or check it out. This does not mean that a linked site cannot have donation buttons, ticket sales, or be housed on a ticket/donation site (i.e. Ticketmaster, Kickstarter). But the content of the tweet and linked material should provide information and generally create a positive vibe around LilyPond. I'm in charge of maintaining this corner, so send me your Pondings (anything in valid HTML is fine - make sure its tweet-sized) and I'll put them up on the site! Cheers, MS ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
