- Original Message -
From: "Nick Payne"
To:
Sent: Monday, April 30, 2012 7:39 AM
Subject: tuplet number placement and ornament
In the following, even though I've turned off the tuplet bracket
stencil, the tuplet number is still placed as though the stencil was
there:
\version "2.1
In the following, even though I've turned off the tuplet bracket
stencil, the tuplet number is still placed as though the stencil was there:
\version "2.15.37"
\relative c'' {
\set tupletSpannerDuration = #(ly:make-moment 1 4)
\override TupletBracket #'stencil = ##f
\times 2/3 { g8
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 r
Hi,
On Sun, Apr 29, 2012 at 8:37 PM, MING TSANG 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-propert
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
Hi David,
2012/4/30 David Nalesnik :
> Hi Harm,
>
> On Sun, Apr 29, 2012 at 5:55 PM, Thomas Morley
> 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
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 t
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
> "Nick" == Nick Payne 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:
Tha
Martin,
On 29 April 2012 17:28, Martin Tarenskeen 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 technic
Martin Tarenskeen 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/li
On Sat, Apr 28, 2012 at 7:49 PM, 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
> under
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
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?
Mi
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
2012/4/29 Nick Payne :
> 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 =
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 puzzle
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:
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-str
>> 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
Werner,
2012/4/29 Werner LEMBERG :
>
> 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
> 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
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 er
>> 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 i
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 l
Werner LEMBERG 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
lilypon
26 matches
Mail list logo
