I came up with this example trying to get a segno on a barline. I tried
an old and a new way to do this. Can someone tell what's going on
and/or how to get a segno on a barline in 2.0.0?
TIA,
Paul Scott
#(define segno '(music "scripts-segno"))
\score {
<<
\property Score.skipBar
>> On Friday 26 September 2003 04:57 pm, you wrote:
>>> in the following:
>>>
>>> \score {
>>> \notes \relative c' {
>>> ~
>>> }
>>> \paper { raggedright = ##t}
>>> }
>>>
>>> it seems clear to me that the tie between g's should go up, to avoid
>>> colliding with the tie between f's. unfortunately,
> On Friday 26 September 2003 04:57 pm, you wrote:
>> in the following:
>>
>> \score {
>> \notes \relative c' {
>> ~
>> }
>> \paper { raggedright = ##t}
>> }
>>
>> it seems clear to me that the tie between g's should go up, to avoid
>> colliding with the tie between f's. unfortunately, that does no
Hello!
I'm trying to compile lilypond-2.0.0 but unsuccessfully :(((.
I'm using gcc-3.3.1.
It doesn't compile (even with the patch) with flex-2.5.4a.
It compiles with flex-2.5.31 but seems buggy (it segfaults when parsing
starts :( ).
I hope it will compile with flex-2.5.27...
I don't know if it c
I am unable to transpose chord names correctly.
If I enter chords as e1:m7 f1:maj7 etc then they print correctly on the
score but do not transpose with the rest of the score. My notes and key
signature do transpose correctly.
If I enter e-minor7 chord as <> then it transposes but displays
as D
How about having better support for chord tremolos when whole notes
are involved? In the example bellow, not only the beams in the first
measure should be placed bellow the noteheads, but they should be also
more inclined, like in the second measure. Any changes to see that in
2.1? :-)
\score {
Hi,
Why I get:
/tmp/repeat-volta.ly:14:39: warning: beam has less than two visible stems:
with the following code?
\score {
\notes \context Voice \relative c' {
\repeat "tremolo" 16 {e32\p ( c32)}
}
}
Pedro
___
Lilypond-user mailing list
in the following:
\score {
\notes \relative c' {
~
}
\paper { raggedright = ##t}
}
it seems clear to me that the tie between g's should go up, to avoid
colliding with the tie between f's. unfortunately, that does not follow
the rule of curving away from staff center.
i have not been able to find
In the section on "An orchestral part" in the reference manual,
hornNotes is called in the code with
\notes \transpose c' f \hornNotes
and referenced in the text as follows:
"The code \transpose f c' indicates that the argument, being \hornNotes,
should be transposed by a fifth downwards: sound
Pierre François wrote:
Hi,
Graham Percival wrote:
About a possible way for removing the time signature,
I found a way to suppress the time signature and the time bars,
that is to put:
\property Staff.TimeSignature = \turnOff
\property Score.defaultBarType = \turnOff
This does the job, but
LOG file is attached as requested.
I ran the regtool command you suggested. Now, if I tell windows open the
test.ly file with bash, it almost works. It invokes lily-wins, but
produces an error message when it tries to execute the following command:
cygpath -aw /cygdrive/c/Documents and Settings
Hi,
Quite awhile back, Lilypond had issues with gcc 3.x, in which I could
never get it to compile.
I am installing a new machine, and debating on Slackware 8.1 (gcc 2.95)
or 9 (gcc 3.2.x). Which would be better, to limit the problems I might
have?
Thanks,
Bryan
_
Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
Han-Wen Nienhuys wrote:
Added this to the doco:
If you want to have a text on the left end of a multi-measure rest,
attach the text to a zero-length skip note, i.e.
@example
s1*0^"Allegro"
R1*4
@end example
This makes the multime
Ralph Little wrote:
Thanks for the note about R1/r1. You are quite right.
A quick replace s/r1/R1/g should fix that :D
Regarding the Multi-measure rest issue, I thought that a change was added to
CVS.
I've just upgraded from 1.6.4 to 1.8.2 and I'm just getting over the shock!
Maybe I'll have a go
Hello.
I recently upgraded from rev. 1.4.x to 1.8.2, running under Cygwin. This
helps a lot since the latter recognizes the \\ separators for notating
momentary polyphony. However, now it does not seem to recognize
\forgetAccidentals anymore. Did something change?
-- Tim Duncan
-Forwarded Message-
> From: Kieren MacMillan <[EMAIL PROTECTED]>
> To: arie-lily <[EMAIL PROTECTED]>
> Subject: Re: trouble using lilypond-book
> Date: 26 Sep 2003 11:01:47 -0400
>
> Hello, Arie:
>
> I had the same problem(s), and after some work, it seems to have gone
> away.
>
> What
Thanks for the note about R1/r1. You are quite right.
A quick replace s/r1/R1/g should fix that :D
Regarding the Multi-measure rest issue, I thought that a change was added to
CVS.
I've just upgraded from 1.6.4 to 1.8.2 and I'm just getting over the shock!
Maybe I'll have a go shortly, but it does
Ralph Little wrote:
Hi,
[I got the strange wide spacing of multi-measure rests as well as Paul!
Until I upgrade, I will avoid using Multi-Measure rest markup]
Now, you can use it, can't you?
I have noticed that on 1.8.2 a single bar rest with r1 (4/4 time) results in
the rest not being centred in
Hi,
[I got the strange wide spacing of multi-measure rests as well as Paul!
Until I upgrade, I will avoid using Multi-Measure rest markup]
I have noticed that on 1.8.2 a single bar rest with r1 (4/4 time) results in
the rest not being centred in the bar.
Is this by design or is it a "bug"?
It does
Hello,
I could probably overcome these clashes but thought to point
them out in case you do not know about them. Why do not
these objects know about each other?
1. sopMusic = \notes { \tempo 4 = 96 cis''8^\mf ... }
results in
<>
2. later, \break \mark "A" cis''4. results in
<>where the score
I'm not sure, but -p is used for generate PDF files (it uses Type1
fonts) whereas -P generates PostScript output with bitmap fonts.
Look at your /usr/(local/)share/lilypond/1.8.0/fonts if there are "afm"
and "tfm" fonts...
Olivier
arie-lily wrote:
On Fri, 2003-09-26 at 02:23, Olivier Cloirec w
On Wednesday 24 September 2003 08:30 pm, Graham Percival wrote:
> On Thu, 25 Sep 2003 00:59:11 +0200
>
> ario <[EMAIL PROTECTED]> wrote:
> > So I wanted to convert a file, which has the statement
> > \version "1.6.10" in it, using
>
> -snip-
>
> > \version "1.7.28"
> >
> > How come???
>
> There wer
On Fri, 2003-09-26 at 02:23, Olivier Cloirec wrote:
> Is a simple .ly file works with a PostScript output?
NO, it doesn't. If I run
ly2dvi -P file.ly
and then view the file with
ghostview file.ps
it gives the same terrible result.
But... if I just run ly2dvi -p file.ly, a ps file is cr
23 matches
Mail list logo
