On 14-May-06, at 3:48 PM, Anthony W. Youngman wrote:
Looking at the manual, codas and segnos are under "Articulation",
symbols that modify notes. Fine, except to me this seems completely
wrong - they should be over bar-lines and modify the flow of music -
they're like the ":" that means "repe
When using instrument names for staffs in a StaffGroup, the name is printed too
close to the bar. I tried putting \override InstrumentName #'space-alist =
#'((left-edge extra-space . 2.0)) in a Score context in the layout block as
suggested by the docs but it didn't change anything.
Cheers,
Cal
In message <[EMAIL PROTECTED]>, Mats
Bengtsson <[EMAIL PROTECTED]> writes
Sorry to sound so negative, but even if you found a bug in version 2.6,
nobody will care to fix it, since we have a new stable version
2.8.
That's fair enough, provided it *has* been spotted and fixed. I know
Cygwin lag
Hi,
I would like to ask all of you, if there is a possibility to format Stanza
Numbers using \markup commands, and altering their position relative to the
lyrics (X or Y). If yes, which is the way to do it?
Please, help!
--
View this message in context:
http://www.nabble.com/Formatting-Stanza-Num
You don't say how you did your TimeSig staff, but my guess is that it's
very hard to achieve this automatically. Wait a second, maybe you could
include the music of the piano staves
as invisible notes in the extra context that you use for the time
signature. However, if you send some of your cur
Quoting "Anthony W. Youngman" <[EMAIL PROTECTED]>:
In message <[EMAIL PROTECTED]>, Mats
Bengtsson <[EMAIL PROTECTED]> writes
I really recommend you to upgrade to the latest stable version,
2.8.x. If find the Cygwin command interface convenient, you can
still use the
"native" Windows version a
Thanks!!
- Original Message -
From: "Mats Bengtsson" <[EMAIL PROTECTED]>
To: "Trent Johnston" <[EMAIL PROTECTED]>;
Cc:
Sent: Monday, May 15, 2006 7:44 PM
Subject: Re: Beam Positions
| This clearly looks like a bug, so I forward it to bug-lilypond.
|
|/Mats
|
| Quoting Trent Johnst
This clearly looks like a bug, so I forward it to bug-lilypond.
/Mats
Quoting Trent Johnston <[EMAIL PROTECTED]>:
Hello again,
I'm having trouble with changing the lengths of beams. When I use:
\once \override Beam #'positions = #'(1 . 1.5)
in the below example I get a strange beamed g
Hello list, hello Graham,
You wrote:
> From the documentation, 13.2:
> "Running dvips will produce some warnings about fonts; these are
> harmless and may be ignored."
>
> Does that help?
Oh, yes, it does.
I've thought something like that, but wasn't shure. :-)
Thanks and Best Regards
Hello list, hello Trent,
You wrote:
> I'm having trouble with changing the lengths of beams. When I use:
>
> \once \override Beam #'positions = #'(1 . 1.5)
>
> in the below example I get a strange beamed group. The 32nd beamed notes
> stick out. No matter how I adjust the numbers the 32nd no
Dear developer team and friends of Lilpond,
yesterday i installed the most up to date precompiled lilypond version for Win
(v2.8.2-1). I have no phython installed other than the one that was delivered
by the lilypond-setup.
To verify the installation i ran basic examples from the documentation.
Hello all,
from the doc:
"All units dimensions are measured in staff spaces."
I noticed that I cannot change this the usual way e.g.
"bottom-margin = 2 \cm" in the paper block.
Also from the doc:
"You can also define these values in Scheme. ...,
#(define bottom-margin (* 2 cm))"
This does al
12 matches
Mail list logo
