segno on barline in 2.0.0
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.skipBars = ##t
\context Staff = clarinet <<
{
\notes {
\time 3/4
R4*3*8 \mark \segno
R4*3*2 \mark #`,segno
d'2\pp\fermata r4 \bar "||"
}
}
>>
>>
\paper {}
}
segno.pdf
Description: Adobe PDF document
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: individual tie directions in chords
>> 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 not
>>> follow the rule of curving away from staff center.
>>>
>>> i have not been able to find a way of controlling tie DIRECTION for
>>> individual notes in a chord. i suppose the method of placing the tie
>>> engraver at thread level (shown in regression/tie-chord-partial.ly)
>>> would work, but in the context of a succession of chords, where only
>>> one needs this treatment, isn't it difficult to switch between that
>>> and the regular use of the tie engraver?
>>>
>>> is there no simpler way to do this?
>>
>> I don't know whether it's simpler or not, but the best thing to
>> do IMHO is to render some or all of the chord as different
>> voices. daveA
>
> thanks, david.. would you be kind enough to give me an example of
> how to do this? i'm having trouble figuring out how to use different
> voices but still have it look like a chord rather than like polyphony.
>
> thanks!
> -p
ok, i've come up with this so far:
\score {
\notes \relative c' {
\context Staff { <<
\context Voice { << \tieUp g'~ e'~ >> << g, e' >> }
\new Voice {
\tieDown \property Voice.Stem \override #'transparent = ##t
\property Voice.NoteHead \override #'extra-offset = #'(-2.35 . 0)
\property Voice.Tie \override #'extra-offset = #'(-2.35 . 0)
f,~f }
>> }
}
\paper { raggedright = ##t
}
}
it works, but is rather full of manual fudging for my taste. there must be
a more elegant way.
thanks in advance for any suggestions!
-p
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: individual tie directions in chords
> 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 not
>> follow the rule of curving away from staff center.
>>
>> i have not been able to find a way of controlling tie DIRECTION for
>> individual notes in a chord. i suppose the method of placing the tie
>> engraver at thread level (shown in regression/tie-chord-partial.ly)
>> would work, but in the context of a succession of chords, where only
>> one needs this treatment, isn't it difficult to switch between that
>> and the regular use of the tie engraver?
>>
>> is there no simpler way to do this?
>
> I don't know whether it's simpler or not, but the best thing to
> do IMHO is to render some or all of the chord as different
> voices. daveA
thanks, david.. would you be kind enough to give me an example of how
to do this? i'm having trouble figuring out how to use different voices
but still have it look like a chord rather than like polyphony.
thanks!
-p
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: opinion on next install
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 comes from my release of gcc (g++-3.3.1 is not anymore compatible with g++-3.2) or from flex. How did the packagers ??? Good luck, Olivier Bryan Koschmann - GKT wrote: 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 ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Transposing chord names
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 D6/sus4/sus2/add3/add6/add6/add8/add#8/add10 !!! Not an easy chord to read. Laurie ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
feature request: better chord tremolo with whole notes
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 {
\notes \context Voice \relative c' {
\clef "bass"
\repeat "tremolo" 16 {g32 e32}
\repeat "tremolo" 4 {g32 e32} r4 r2
}
}
Pedro
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
tremolo warning
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
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
individual tie directions in chords
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 a way of controlling tie DIRECTION for
individual notes in a chord. i suppose the method of placing the tie
engraver at thread level (shown in regression/tie-chord-partial.ly) would
work, but in the context of a succession of chords, where only one needs
this treatment, isn't it difficult to switch between that and the regular
use of the tie engraver?
is there no simpler way to do this?
-p
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Manual correction?
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: sounding f is denoted by notated c', which corresponds with tuning of a normal French Horn in F. The transposition can be seen in the following output:" This cognative dissonance is present in the manuals for 1.8 and 2.0. Fortunately, the section in the notation manual on Transpose is correct. raybro ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: No time signature
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 doesn't suppress the bar numbers. I don't wan't to see these bar numbers. The final answer for removing the time signature, the bars AND the bar numbers (if any) is to put the next two rules into the Score context: \property Staff.TimeSignature = \turnOff \property Score.timing = \turnOff That does the job! I hope this closes this issue. I suggest to add this as an example in the manual, in the section about Time Signature, or to write a function for doing this, or to modify the function \time for accepting "none" as possible argument. Cheers. -- Pierre François (http://www.romanliturgy.org) Roemer Visscherstraat 46 NL-1054 EZ Amsterdam (Netherlands) + 31 20 616 58 46 ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: can't double-click test.ly under Windows XP and cgywin
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/Mike/Desktop/test I think the problem is that the file name contains spaces. Everything works OK if I put test.ly in the C:\ directory. I guess some quotes are missing somewhere! Thanks for your help. Mike Han-Wen Nienhuys writes: Many thanks for your help. I updated to 1.8.2 as you suggested, but still cannot double-click to process the file. Any suggestions? What program should Windows invoke when I open the file? It should use /cygwin/bin/bash to invoke /usr/bin/lily-wins, see the file /etc/postinstall/post-lilypond.sh[.done] This is the magick command: regtool set '/root/LilyPond/shell/open/command/' $ROOT'\bin\bash.exe --login -c '"'"'/usr/bin/lily-wins "%1"'"'" Could you run: bash -x /etc/postinstall/post-lilypond.sh* > LOG 2>&1 and if that does not help, send LOG to this list? + touch /tmp/.lilypond-install ++ find /var/lib/texmf /var/spool/texmf -name /var/cache/fonts 'feta*pk' -or -name 'feta*tfm' -or -name 'parmesan*pk' -or -name 'parmesan*tfm' find: paths must precede expression Usage: find [path...] [expression] + rm rm: too few arguments Try `rm --help' for more information. + rm -f /tmp/.lilypond-install ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
opinion on next install
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 ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Multi-measure rests again again
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 multimeasure excessively wide and actually steals space
from a following MM rest.
Ah, that seems to be a bug. I fixed it partially in 2.0 CVS.
For the moment, you might want to put the "allegro" atop the 72 \mark.
I tried this again with Ferenc's 2.0.0 deb's and don't see an improvement.
Also after the above example from the doco did you mean to show the
graphic for the example?
Thanks,
Paul
\score {
<<
\property Score.skipBars = ##t
\context Staff = clarinet <<
{
\notes {
\time 3/4 \mark "72"
<< s1*0^\markup{ Largo } R4*3*11 >>
\mark "73" R4*3*11 \mark "74" R4*3*2
d'2\pp\fermata r4 \bar "||"
}
}
>>
>>
\paper {}
}
mmtest2.pdf
Description: Adobe PDF document
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: r1 resting bars
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 shortly, but it does not cause me great grief at the moment! I didn't realize my last post on this hadn't been sent to the list. I don't think the spacing problem is fixed in 2.0.0. Paul Scott ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Question about rev. 1.8.2
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 ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
[Fwd: Re: trouble using lilypond-book]
-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 I did was: > 1. Manually delete *all* fonts; > 2. Download the font set (.deb) that most closely matches the > version of lilypond you have installed; > 3. Unpack and install (i.e., move) the font files to your lilypond > directory; > 4. Run texhash. > > Since I did that, everything on my installation appears to be working > as expected. > > Hope this helps! > Kieren. > ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
RE: r1 resting bars
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 not cause me great grief at the moment! Ralph -Original Message- From: Olivier Cloirec [mailto:[EMAIL PROTECTED] Sent: 26 September 2003 16:01 To: Ralph Little Cc: [EMAIL PROTECTED] Subject: Re: r1 resting bars 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 the bar. >Is this by design or is it a "bug"? > No, it's the normal comportment with "normal" rests. If you want it to be centered, you have to use a multi-measure rest (R1). Olivier >It does look a little odd. > >Cheers, >Ralphy > > > -- Our communications with you matter to us. This e-mail and any attachments are confidential and are sent on the basis of our copyright, e-mail and security policy which can be inspected by visiting http://www.tribaldata.co.uk/contact_index.asp. and clicking on the print friendly link. If you are not the intended recipient, please notify the sender and delete this message. Thank you. -- ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: r1 resting bars
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 the bar. Is this by design or is it a "bug"? No, it's the normal comportment with "normal" rests. If you want it to be centered, you have to use a multi-measure rest (R1). Olivier It does look a little odd. Cheers, Ralphy ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
r1 resting bars
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 look a little odd. Cheers, Ralphy -- Our communications with you matter to us. This e-mail and any attachments are confidential and are sent on the basis of our copyright, e-mail and security policy which can be inspected by visiting http://www.tribaldata.co.uk/contact_index.asp. and clicking on the print friendly link. If you are not the intended recipient, please notify the sender and delete this message. Thank you. -- ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Mark-bar number-ChoirStaff and tempo-mf clashes
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 block is set up like
\score { \notes
\context StaffGroup <<
\property Score.automaticMelismata = ##t
\addlyrics
\context Staff = Soprano {
\property Staff.instrument = "Soprano"
\property Staff.instr = "S"
\key a \major \sopMusic
}
\context Lyrics = sopLyrs { \sopWords }
\addlyrics
\context Staff = Alto {
\property Staff.instrument = "Alto"
\property Staff.instr = "A"
\key a \major \altoMusic
}
\context Lyrics = altoLyrs { \altoWords }
...
>>
\paper {
\translator {
\RemoveEmptyStaffContext minimumVerticalExtent = #'(30 . 3)
}
}
}
Best wishes,
Feri.
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: trouble using lilypond-book
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 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 created anyway which is alright when using the same ghostview file.ps command. You know what's wrong here? arie ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: strange conversion
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 were no syntax changes between version 1.7.28 and 1.8.0, so > LilyPond merely printed the number of the version for the last change > it made. > > That said, it might be nicer if it printed the number of its current > version to avoid this confusion. I can't think of any downside to > changing that behaviour, but I'll need to check with Han and/or Jan. > > Cheers, > - Graham I was wondering about that, thanks. Might I request adding the number of the current version but not removing the version of the last change? A comment would not only be easier to do but more reassuring if not more useful. % Last change version. Current version is "n-n-n": \version "n-n-n" daveA -- Br`er Fox told Br`er Rabbit that the Tar Baby had dissed him, and Fox made a dummy out of tar and put him in Rabbit's path. When the Tar Baby failed to return a civil greeting, Rabbit punched him with a right, a left, both feet and butted him with his forehead. Along came Br`er Fox who saw that he was thoroughly "stuck up". Br`er Fox is much smarter than Br`er Rabbit, and in spite of all Rabbit's pleas for help, no one is going to unstick him and throw him in the briar patch, so now Br`er Fox is liesurely eating Rabbit's liver. D. Raleigh Arnold dra@ http://www.openguitar.com [EMAIL PROTECTED] ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: trouble using lilypond-book
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 created anyway which is alright when using the same ghostview file.ps command. You know what's wrong here? arie > Olivier > > ario wrote: > > >I used lilypond-book 1.8.0 to create a latex file in RedHat 8. > >Then I ran latex on that file, creating a dvi file. > >This file was ok in xdvi. > >Then I ran dvips -Ppdf on the dvi file, resulting in warnings of all > >sorts, mainly regarding feta fonts (see below), and resulting in a ps > >file which, in ghostview, looks terrible (for instance: no note heads > >visible). > > > >What is wrong here, and, more important, how can I solve this? > > > >thanks, > >arie > > > > > >This is dvips(k) 5.86 Copyright 1999 Radical Eye Software > >(www.radicaleye.com) > >' TeX output 2003.09.26:0120' -> dostojnoSATB01.ps > >kpathsea: Running mktexpk --mfmode ljfour --bdpi 8000 --mag 1+0/8000 > >--dpi 8000 feta-nummer10 > >mktexpk: Mismatched mode ljfour and resolution 8000; ignoring mode. > >mktexpk: Can't guess mode for 8000 dpi devices. > >mktexpk: Use a config file, or update me. > >kpathsea: Appending font creation commands to missfont.log. > >dvips: Font feta-nummer10 at 8000 not found; scaling 600 instead. > >dvips: Such scaling will generate extremely poor output. > >dvips: Checksum mismatch in font feta-nummer10 > >kpathsea: Running mktexpk --mfmode ljfour --bdpi 8000 --mag 1+0/8000 > >--dpi 8000 feta20 > >mktexpk: Mismatched mode ljfour and resolution 8000; ignoring mode. > >mktexpk: Can't guess mode for 8000 dpi devices. > >mktexpk: Use a config file, or update me. > >dvips: Font feta20 at 8000 not found; scaling 600 instead. > >dvips: Checksum mismatch in font feta20 > >kpathsea: Running mktexpk --mfmode ljfour --bdpi 8000 --mag 1+0/8000 > >--dpi 8000 feta-din14 > >mktexpk: Mismatched mode ljfour and resolution 8000; ignoring mode. > >mktexpk: Can't guess mode for 8000 dpi devices. > >mktexpk: Use a config file, or update me. > >dvips: Font feta-din14 at 8000 not found; scaling 600 instead. > > > >. [1] [2] [3] [4] [5] [6] [7] [8] > > > > > > > > > >___ > >Lilypond-user mailing list > >[EMAIL PROTECTED] > >http://mail.gnu.org/mailman/listinfo/lilypond-user > > > > > > > > > > > > > > ___ > Lilypond-user mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/lilypond-user ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
