Dear friends,
Since I too need a "long fermata" to place between two (or more) notes,
I've searched around for a solution and I found this thread.
I now managed to draw the symbol in postscript. This is my first attempt
to use postscript: I can imagine this will be very far to be perfect!
Ho
Try \override DynamicText #'font-name = "Linux Libertine Bold" and omit
the font-series command. (I haven't tried this in your case, but I use
similar font-name commands for my own scores and they work fine).
Hope that helps,
David
On 05/23/2010 07:18 PM, Martin Hiendl wrote:
Hi!
I hope thi
Hi!
I hope this hasn't been brought up yet.
I tried to change the default dynamics font with the following command:
\score {
\new Staff \with {
\override DynamicText #'font-name = "Linux Libertine"
\override DynamicText #'font-series = #'bold
\override DynamicText #'font-size =
FYI --
From: sib...@major2nd.com
Subject: Exporting Sibelius data
Date: Sat, 22 May 2010 21:58:02 -0700 (PDT)
Dear fellow music hackers,
It seems that many of us independently came up with the idea of a Sibelius
plug-in that can write out the score data in a form suitable for further
processing.
On Sun, May 23, 2010 at 2:17 PM, Phil Holmes wrote:
> I'm currently working my way through the regression tests trying to find
> features only documented there, and have arrived at pedal-ped.ly. I've
> worked out how the pedalSustainStrings uses the pedal glyphs, but can't see
> that the followin
On Sun, May 23, 2010 at 1:17 PM, Phil Holmes wrote:
>
> \override Staff.SustainPedal #'padding = #-2
>
> has any effect at all. I can guess what it's trying to do, but doesn't seem
> to do anything. Anyone any thoughts?
This might be something that used to work before 2.11 added vertical
skyli
I'm currently working my way through the regression tests trying to find
features only documented there, and have arrived at pedal-ped.ly. I've
worked out how the pedalSustainStrings uses the pedal glyphs, but can't see
that the following line:
\override Staff.SustainPedal #'padding = #-2
h
I have downloaded 2.13.21 for OS X 10.5.8 and it no longer crashes.
I get the correct output (attached)
James
-Original Message-
From: lilypond-user-bounces+james.lowe=datacore@gnu.org on behalf of -Eluze
Sent: Sun 23/05/2010 12:13
To: lilypond-user@gnu.org
Subject: Re: Bug report -
Just confirmed it's OK with 2.13.21 here - so must have been fixed in the
current release - although I can't find a related bug report
--
Phil Holmes
- Original Message -
From: "James Lowe"
To: "James Lowe" ; "Phil Holmes"
; "LilyPond User Group"
Sent: Sunday, May 23, 2010 12:
Sorry I have 2.13.14
James
-Original Message-
From: lilypond-user-bounces+james.lowe=datacore@gnu.org on behalf of James
Lowe
Sent: Sun 23/05/2010 11:58
To: Phil Holmes; LilyPond User Group
Subject: RE: Bug report - stem lengths
If it helps anyone, I have reproduced the 'crash' on
it does not crash at my place - version 2.13.21 [windows vista home basic]
Phil Holmes wrote:
>
> The following causes LilyPond to crash with the log below the snippet:
>
> \relative c'' {
> \stemUp
> \override Stem #'details #'beamed-lengths = #'(6)
> c8[ c] c16[ c] c32[ c]
> \revert S
The following causes LilyPond to crash with the log below the snippet:
\relative c'' {
\stemUp
\override Stem #'details #'beamed-lengths = #'(6)
c8[ c] c16[ c] c32[ c]
\revert Stem #'details
c8[ c] c16[ c] c32[ c]
}
Log:
Interpreting music...
Preprocessing graphical objects...
Finding the
12 matches
Mail list logo
