Re: missing noteheads
Michael Porcaro writes: > I installed lilypond 2.2.6 on my server. I am pretty new to unix. I > got the output to work, however the noteheads and other decorations do > not work. I really need help. I am trying to get this to work in > mediawiki using the wikitex extension. You should update to lilypond 2.6.4, esp. if you want to use it as a server. If you're new to unix, you should get advice on security. Also, please use the lilypond mailing lists. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: missing noteheads
Michael Porcaro writes:
> 1. (*) text/plain ( ) text/html
>
> Disregard my last error report. This is the right error report.
This is not a useful error report. Please send your test.ly file to
the list. Are you sure that you are using 2.2.6 syntax?
Jan.
>
> [EMAIL PROTECTED] [~/software]# lilypond --verbose test.ly
> lilypond (GNU LilyPond) 2.2.6
> Opening pipe `/usr/bin/lilypond-bin --version '
> Opening pipe `kpsexpand \$TEXMF'
> Opening pipe `kpsewhich -expand-path=\$T1FONTS'
> Invoking `/usr/bin/lilypond-bin -I /root/software -I /root/software -I
> /root/software -H dedication -H title -H subtitle -H subsubtitle -H
> footer -H head -H composer -H arranger -H instrument -H opus -H piece -H
> metre -H meter -H poet -H texttranslator -H textheight -H fontencoding
> -H latexheaders -H language -H latexpackages -H papersize -H pagenumber
> -H inputencoding -H latexoptions -H linewidth -H unit -H orientation
> --verbose test'
> lilypond_datadir: `/usr/share/lilypond'
> local_lilypond_datadir: `/usr/share/lilypond/2.2.6'
> localedir: `/usr/share/locale'
> LILYPONDPREFIX: `'
>
> [/usr/share/lilypond/2.2.6/scm/define-music-types.scm][/usr/share/lilypo
> nd/2.2.6/scm/output-lib.scm][/usr/share/lilypond/2.2.6/scm/c++.scm][/usr
> /share/lilypond/2.2.6/scm/chord-ignatzek-names.scm][/usr/share/lilypond/
> 2.2.6/scm/chord-entry.scm][/usr/share/lilypond/2.2.6/scm/chord-generic-n
> ames.scm][/usr/share/lilypond/2.2.6/scm/stencil.scm][/usr/share/lilypond
> /2.2.6/scm/new-markup.scm][/usr/share/lilypond/2.2.6/scm/bass-figure.scm
> ][/usr/share/lilypond/2.2.6/scm/music-functions.scm][/usr/share/lilypond
> /2.2.6/scm/part-combiner.scm][/usr/share/lilypond/2.2.6/scm/define-music
> -properties.scm][/usr/share/lilypond/2.2.6/scm/auto-beam.scm][/usr/share
> /lilypond/2.2.6/scm/chord-name.scm][/usr/share/lilypond/2.2.6/scm/define
> -context-properties.scm][/usr/share/lilypond/2.2.6/scm/translation-funct
> ions.scm][/usr/share/lilypond/2.2.6/scm/script.scm][/usr/share/lilypond/
> 2.2.6/scm/midi.scm][/usr/share/lilypond/2.2.6/scm/beam.scm][/usr/share/l
> ilypond/2.2.6/scm/clef.scm][/usr/share/lilypond/2.2.6/scm/slur.scm][/usr
> /share/lilypond/2.2.6/scm/font.scm][/usr/share/lilypond/2.2.6/scm/define
> -markup-commands.scm][/usr/share/lilypond/2.2.6/scm/define-grob-properti
> es.scm][/usr/share/lilypond/2.2.6/scm/define-grobs.scm][/usr/share/lilyp
> ond/2.2.6/scm/define-grob-interfaces.scm][/usr/share/lilypond/2.2.6/scm/
> page-layout.scm][/usr/share/lilypond/2.2.6/scm/paper.scm]
> Now processing `test.ly'
> Parsing...
> [/usr/share/lilypond/2.2.6/ly/init.ly[/usr/share/lilypond/2.2.6/ly/decla
> rations-init.ly[/usr/share/lilypond/2.2.6/ly/nederlands.ly][/usr/share/l
> ilypond/2.2.6/ly/drumpitch-init.ly][/usr/share/lilypond/2.2.6/ly/chord-m
> odifiers-init.ly][/usr/share/lilypond/2.2.6/ly/script-init.ly][/usr/shar
> e/lilypond/2.2.6/ly/scale-definitions-init.ly][/usr/share/lilypond/2.2.6
> /ly/grace-init.ly][/usr/share/lilypond/2.2.6/ly/midi-init.ly[/usr/share/
> lilypond/2.2.6/ly/performer-init.ly]][/usr/share/lilypond/2.2.6/ly/engra
> ver-init.ly][/usr/share/lilypond/2.2.6/ly/dynamic-scripts-init.ly][/usr/
> share/lilypond/2.2.6/ly/spanners-init.ly][/usr/share/lilypond/2.2.6/ly/p
> roperty-init.ly]][/root/software/test.ly
> /root/software/test.ly:1:1: error: parse error, unexpected '{':
> {
>
> ]((gc-time-taken . 24) (cells-allocated . 228837) (cell-heap-size .
> 471040) (bytes-malloced . 891467) (gc-malloc-threshold . 1223773)
> (gc-times . 21) (gc-mark-time-taken . 11) (gc-sweep-time-taken . 13)
> (cells-marked . 2221941) (cells-swept . 4783512) (cell-heap-segments
> (136865792 . 136816640) (136892416 . 136876032) (137009152 . 136943616)
> (137123840 . 137025536) (1077348352 . 1077200896) (1077516288 .
> 1077352448) (1077733376 . 1077520384) (1078065152 . 1077737472)
> (1080166400 . 1078069248) (1080838144 . 1080248320)))]
> /root/software/test.ly:2:0: warning: Braces don't match:
>
> c
> Failed files: test.ly
> lilypond: warning: `lilypond-bin' failed (status 1) (ignored)
>
>
> lilypond: error: LilyPond failed on input file test (exit status 1)
> Traceback (most recent call last):
> File "/usr/bin/lilypond", line 873, in ?
> run_lilypond (files, dep_prefix)
> File "/usr/bin/lilypond", line 296, in run_lilypond
> ly.exit (status)
> File "/usr/share/lilypond/2.2.6/python/lilylib.py", line 130, in exit
> raise _ ('Exiting (%d)...') % i
> Exiting (256)...
> Cleaning /tmp/@24308.0lilypond...
> [EMAIL PROTECTED] [~/software]#
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unusual Repeat Alternatives
Read the section on "Manual repeat commands" in the manual. /Mats Jennifer Clark wrote: I'm writing out some music at the moment which has an odd repeat structure in it. There are two distinct alternatives, a very long one and a short one. The long one is called after repeats 1 and 3, and the short one after repeat 2. So the music should look roughly like this: _ ___ | 1--3. :| | 2. The default method in lilypond for repeated alternatives labels the above as 1--2 and 3, assuming that the first alternative is played twice. I guess this is reasonable, but is there a way to override it to state the repeats in the correct way in this case? Thanks for your help, Jennifer -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: problem with position of bar rest
Just set the staff-position property:
\once \override MultiMeasureRest #'staff-position = #5
/Mats
liang seng wrote:
Hi, I have an interesting problem here. In the first bar of
"example.pdf", the bar rest of the upper voice is too close to the
notes on the lower voice. How do I move the rest vertically upwards? I
can't use pitched rests as the bar rest would move to the left side of
the bar.
Thank you.
Yours sincerely,
Seng
\version "2.6.3"
\relative {
\key c \major
\time 4/4
<< { R1 } \\ { e'2 d } >> R1^\fermataMarkup
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: First Measure bar
I hope you have a good reason to deviate from standard music typesetting
practice. As far as I can see, it's hard-coded into LilyPond to not typeset
the opening repeat at the beginning of a piece, but if there is a general
need for such an option, it should be easy to make this configurable.
/Mats
VSD wrote:
I have the same problem. I don't know if lilypond can do that, but I
use the following cheap trick:
{
\time 4/4
\partial 128 s128 % create an empty tiny partial measure before
the repeat
\repeat volta 2
{
c''2
c''
}
}
which works form me. I'd recommend you to use raggedright=##t in the
layout for a single bar score though.
On Thu, 20 Oct 2005 23:19:15 +0200, Kress, Stephen
<[EMAIL PROTECTED]> wrote:
All,
If I have a file with this:
{
\time 4/4
\repeat volta 2
{
c''2
c''
}
}
I get a single measure and a close repeat at the end of it. How do
I get LilyPond to put the openning repeat in there as well? I tried
this:
{
\time 4/4
\bar "|:"
\repeat volta 2
{
c''2
c''
}
}
but that puts the time signature inside the repeat. I tried moving the
\bar to various places but nothing would put it where I want it. I
would like to have the symbols in this order:
1. Clef
2. Time signature
3. Open repeat
4. The rest of the music.
Thanks for any help you can provide.
Stephen
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Unusual Repeat Alternatives
Thanks Mats, that has done the trick. I had read this section in the manual but hadn't realised it could do what I wanted to do. Doh! Jennifer Mats Bengtsson wrote: Read the section on "Manual repeat commands" in the manual. /Mats Jennifer Clark wrote: I'm writing out some music at the moment which has an odd repeat structure in it. There are two distinct alternatives, a very long one and a short one. The long one is called after repeats 1 and 3, and the short one after repeat 2. So the music should look roughly like this: _ ___ | 1--3. :| | 2. The default method in lilypond for repeated alternatives labels the above as 1--2 and 3, assuming that the first alternative is played twice. I guess this is reasonable, but is there a way to override it to state the repeats in the correct way in this case? Thanks for your help, Jennifer -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 267.12.4 - Release Date: 18/10/2005 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Fink's Lilypond 2.6.3 and tex backend
* Mats Bengtsson on Tuesday, October 18, 2005:
> Version 2.6 and later has much better support for other fonts.
I am experimenting now with 2.6.3 from the MacOS disk image (even
though I'd prefer to compile myself w/o gui but I can't get 2.6.4
to compile at the moment).
But:
$ lilypond-book -Flatex -oOut/ lilbook.tex
lilypond-book (GNU LilyPond) 2.6.3
Reading lilbook.tex...
Dissecting...
Traceback (most recent call last):
File
"/Users/chris/Applications/LilyPond.app//Contents/Resources/bin/lilypond-book",
line 1616, in ?
main ()
File
"/Users/chris/Applications/LilyPond.app//Contents/Resources/bin/lilypond-book",
line 1582, in main
chunks = do_file (file)
File
"/Users/chris/Applications/LilyPond.app//Contents/Resources/bin/lilypond-book",
line 1470, in do_file
[c.filter_text () for c in chunks])
File
"/Users/chris/Applications/LilyPond.app//Contents/Resources/bin/lilypond-book",
line 970, in filter_text
code = self.substring ('code')
File
"/Users/chris/Applications/LilyPond.app//Contents/Resources/bin/lilypond-book",
line 714, in substring
return self.match.group (s)
IndexError: no such group
As an aside: You can also see that I installed in my home folder
because lilycall.py makes a testwrite in the application folder.
So there should be a note exactly which permissions to change
when I want to use lilypond systemwide -- or the installer should
ask whether I want to use it systemwide and set permissions
accordingly.
c
--
_B A U S T E L L E N_ lesen! --->>
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: missing noteheads
Michael Porcaro writes:
Please stay on the mailing list.
> Wikitex doesn't work with 2.6.4 though. I need wikitex for mediawiki.
> I tried everything, but 2.2.6 is the only version that works with
> wikitex.
You tried everything? Wikitex is a shell script that has a number of
recipies to proces a text snippet to an imagi file. It is trivial to
update the lilypond command for lilypond 2.6. Just remove the
--no-pdf --no-ps options, see the patch below.
I'd advise you to look at lilypond's jail options before running this
as a server.
Jan.
===
RCS file: /cvsroot/wikipedia/wikitex/wikitex.sh,v
retrieving revision 1.16
diff -p -u -r1.16 wikitex.sh
--- wikitex.sh 16 Jun 2005 09:09:25 - 1.16
+++ wikitex.sh 21 Oct 2005 12:51:35 -
@@ -120,7 +120,7 @@ function fdp() {
}
function music() {
-wt_exec "lilypond --no-pdf --no-ps --png ${HASH}"
+wt_exec "lilypond --safe-mode --png ${HASH}"
for i in ${HASH}*${EXT}; do wt_exec "mogrify -trim ${i}"; wt_img
"${OUT}${i}"; done
wt_anch
STR="${STR}"$(printf '[listen]' "${OUT}${HASH}${MID}")
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Ossia staves getting them to work....
Hi Everyone...
I am typesetting a Violin Sonata by Locatelli and I
want to provide a written out stave above the violin showing how the sometimes
abbreviated part should be played.
I'm trying to use the \stopStaff and \startStaff
commands used in the 'Tips and Tricks' section but unfortunately this doesn't
seem to work as I get a whole new staff above the violin either with staff lines
or no staff lines but with a clef.
I've attached a snippet of the code so you can see
where I might have gone wrong.
Any help appreciated..
Regards,
Trent Johnston
% Created on Fri Oct 21 12:49:26 EST 2005
\version "2.7.12"
#(set-global-staff-size 16)
#(set-default-paper-size "a4")
triplet = \markup { \italic \tiny 3 }
sextup = \markup { \italic \tiny 6 }
\header {
title = "Sonata I"
composer = "Pietro Locatelli"
opus = "Op 8"
footer = "Sonata I"
}
\paper {
bottommargin = 3\cm
leftmargin = 2\cm
raggedbottom = ##f
raggedlastbottom = ##f
linewidth = 6.8\in
}
\include "english.ly"
staffViolin = \new Staff {
\time 4/4
\set Staff.midiInstrument="violin"
\key f \major
\clef treble
\relative c'' {
\override TupletBracket #'bracket-visibility = ##f
\override TupletBracket #'number-visibility = ##f
\override TextScript #'avoid-slur = #'inside
%bar 1
c4.^\markup { \large \bold Largo. } f8 e f r16 f,( c' f)
%bar 2
d8 c bf4 a r8 a'16( f)
%bar 3
g8 c, r f16( d) e8 a, r d16( bf)
%bar 4
c8 f, bf16( g') bf,( a) a8( g) r16 c,( g' bf)
%bar 5
bf16( g) a8 r16 d,( a' c) c( a) bf8 r16 g( d' f~)
%bar 6
f32 e[ g16.] f32[ a16.] g32[ bf16.] a32[ c16] \grace { d16[ c]} b8 g c c,
%bar 7
a'16( f) g( e) f4\trill e r8 c
%bar 8
d4. c'16( e,) f8 c f4~
%bar 9
f8 e16( d) c8[ e] d[ g,] g'4
%bar 10
g8 f16( e) f8 d ef2~
%bar 11
e8 d16( c) d8 c c4( c16 a') bf,( a)
%bar 12
bf2~ bf8 a a16[( bf32 a) e'16 g,]
%bar 13
fs8 d g c bf4 a
%bar 14
<< { gs8 e a a' a4( g } \\ {s2. bf,4 } >>
%bar 15
<< { g'8 f) c8_([ d32 c bf a64 g]) \grace f8 e16 d'_( c e,) f_( c') a_( f) } \\
{ a4 s2. } >>
%bar 16
d32( e16 f32) c( c'64 a f32 e64 d) \grace c8 bf8\trill[( bf32 a bf c)] bf8( a)
r16 f( c' ef)
%bar 17
\once \override TextScript #'avoid-slur = #'outside e16^\markup{ \teeny \flat
}( c) d8 r16 g,( d' f) f16( d) e!8 r16 c( g' bf)
%bar 18
bf16( a c, a') a( g c, g') g( f bf, f') f(e a, ef')
%bar 19
\once \override TextScript #'avoid-slur = #'outside e16^\markup{ \teeny \flat
}( d f, d') d( c f, c') b4 a~
%bar 20
a8 bf16( g) \grace a8 g8.\trill f16 e4 c'8 d
%bar 21
a4 g f2^\fermata \bar "||" \break
}}
Alt = \new Staff \with {
\remove "Time_signature_engraver"
fontSize = #-2
\override StaffSymbol #'staff-space = #(magstep -2)
firstClef = ##f
}
\relative c'{
\stopStaff
\skip 1*2
\startStaff
c32 c'( b c) a-. c( b c) g-. c( b c) f,-. c'( b c)
\stopStaff s2
\skip 1*10
\startStaff
c32 c'( b c) a-. c( b c) g-. c( b c) f,-. c'( b c)
\stopStaff
}
staffCello = \new Staff {
\set Staff.midiInstrument="cello"
\key f \major
\clef bass
\relative c {
\override TupletBracket #'bracket-visibility = ##f
\override TupletBracket #'number-visibility = ##f
\override TextScript #'avoid-slur = #'inside
%bar 1
f8 g a bf~ bf a16 g a8 f
%bar 2
bf8 a g c, f, f'16 g a8 f~
%bar 3
f8 e16 d e8 d8. s16 c bf c8 bf
%bar 4
bf8 a g f c4 e'
%bar 5
f4 fs4 g bf,
%bar 6
c8 d e f~ f e16 d e8 c
%bar 7
f8 e d g, c4 c'~
%bar 8
c8 bf16( a) bf4. a16( g) a8 f
%bar 9
g8 c, c'4. bf16( a) bf8 g
%bar 10
a8 d, d'4. c16( bf) c8 a
%bar 11
bf2~ bf8 a16( g) a8 fs
%bar 12
g8 f ef d cs cs cs cs
%bar 13
c4 b8 ef d4 d'~
%bar 14
d8 c16( b) c8 d e d e e,
%bar 15
f8 g a bf~ bf a16 g a8 f
%bar 16
bf8 a g c, f4 a,
%bar 17
bf4 b c e
%bar 18
f4 e d c
%bar 19
b a g f
%bar 20
bf bf'2 a8 bf
%bar 21
c,2 f,^\fermata
}
}
fb = \figuremode {
\context FiguredBass {
\override FiguredBass.NewBassFigure #'font-size = #-2
\set minimumVerticalExtent = #'(-2.5 . 1.0)
%= bar 1
s2 <4 2>8 <6>8 s4
%= bar 2
s4 <7>8 <7>8 s2
%= bar 3
<5 2>4. <5>8 <5 2>4 s8 <5>8
%= bar 4
<5 2>4 <6>4 <6 4>8 <5 3>8 <6>8 <5>8
%= bar 5
<9>8 <8>8 <6>8 <5>8 <9>8 <8>8 <6>8 <5>8
%= bar 6
<9>16 <8>16 <9>16 <8>16 <9>16 <8>16 <9>16 <8>16 <4! 2>8 <6>8 s4
%= bar 7
s4 <7>16 s <7 _!>8 s2
%= bar 8
<4 2>4 <3>8 <6 4>8 <5 2>8 s8 <6>4
%= bar 9
<7>4 <3>4 <2 5>4 <6>4
%= bar 10
<7>4 <3>4 <4 2->4 <_- 6>4
%= bar 11
<4>4 <3>4 <2 4->4 <6+>4
%= bar 12
<9>4 <5>4 <7>8 <6>8 s8 <6 5>8
%= bar 13
<4+ 2>4 <6>8 <6>16 s <6 4>4 <3- 5>4
%= bar 14
<6! 4+ 2>2 <6 4>4 <5- 3>4
%= bar 15
<9>8 <7>8 <6>8 <6>8 <4 2>8 <6>8 s4
%= bar 16
s4 <7>8 <7>
tetex version games
I just succeeded in something that took me several hours to figure out, so I thought I'd pass the magic words on here in case someone else needs to do it. This is on a debian Sid system where I would like to run lilypond 2.0. The problem was that an update script stupidly upgraded tetex to 3.0. I found that my lilypond 2.0 wouldn't work at all with tetex 3.0. Googling, I saw that support for tetex 3.0 was introduced in lilypond 2.4. So I decided to roll tetex back to 2.0. I don't back up system files, but my backup script does save output of "dpkg -l". Even after I managed to install the exact tetex-* packages that had been in place on the previous backup, I was still getting the error messages from latex that I'd gotten with tetex 3.0. (Don't bother trying to roll back tetex with apt-get -- the dependencies are remarkably screwed up, and dpkg goes into a loop.) The answer turns out to be that you do a purge of the 3.0 packages (dpkg -P --force-all) before installing the 2.0 packages (with dpkg using the packages in /var/cache/apt/archives). Now lilypond 2.0 seems to be happy again. However, I think you can for practical purposes date the demise of lilypond 2.0 (and 2.2) as supported packages on lilypond Sid to this week, when tetex 3.0 became the version supported by apt-get. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
missing noteheads
Hi, I installed lilypond 2.2.6 on my server. I am pretty new to unix. I got the output to work, however the noteheads and other decorations do not work. I really need help. I am trying to get this to work in mediawiki using the wikitex extension. Please help. I looked all over the internet to find answers, and I couldn’t get much help. Thanks. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: missing noteheads
Here is my error report, I forgot to send
it:
[EMAIL PROTECTED] [~]# lilypond
--verbose test.ly
lilypond (GNU LilyPond) 2.2.6
Opening pipe `/usr/bin/lilypond-bin
--version '
Opening pipe `kpsexpand
\$TEXMF'
Opening pipe `kpsewhich
-expand-path=\$T1FONTS'
Invoking `/usr/bin/lilypond-bin -I /root -I /root -I /root -H dedication
-H title -H subtitle -H subsubtitle -H footer -H head
-H composer -H arranger -H instrument -H opus -H piece -H metre
-H meter -H poet -H texttranslator -H textheight -H fontencoding -H latexheaders -H language -H latexpackages
-H papersize -H pagenumber
-H inputencoding -H latexoptions
-H linewidth -H unit -H orientation --verbose test'
lilypond_datadir: `/usr/share/lilypond'
local_lilypond_datadir: `/usr/share/lilypond/2.2.6'
localedir: `/usr/share/locale'
LILYPONDPREFIX: `'
[/usr/share/lilypond/2.2.6/scm/define-music-types.scm][/usr/share/lilypond/2.2.6/scm/output-lib.scm][/usr/share/lilypond/2.2.6/scm/c++.scm][/usr/share/lilypond/2.2.6/scm/chord-ignatzek-names.scm][/usr/share/lilypond/2.2.6/scm/chord-entry.scm][/usr/share/lilypond/2.2.6/scm/chord-generic-names.scm][/usr/share/lilypond/2.2.6/scm/stencil.scm][/usr/share/lilypond/2.2.6/scm/new-markup.scm][/usr/share/lilypond/2.2.6/scm/bass-figure.scm][/usr/share/lilypond/2.2.6/scm/music-functions.scm][/usr/share/lilypond/2.2.6/scm/part-combiner.scm][/usr/share/lilypond/2.2.6/scm/define-music-properties.scm][/usr/share/lilypond/2.2.6/scm/auto-beam.scm][/usr/share/lilypond/2.2.6/scm/chord-name.scm][/usr/share/lilypond/2.2.6/scm/define-context-properties.scm][/usr/share/lilypond/2.2.6/scm/translation-functions.scm][/usr/share/lilypond/2.2.6/scm/script.scm][/usr/share/lilypond/2.2.6/scm/midi.scm][/usr/share/lilypond/2.2.6/scm/beam.scm][/usr/share/lilypond/2.2.6/scm/clef.scm][/usr/share/lilypond/2.2.6/scm/slur.scm][/usr/share/lilypond/2.2.6/scm/font.scm][/usr/share/lilypond/2.2.6/scm/define-markup-commands.scm][/usr/share/lilypond/2.2.6/scm/define-grob-properties.scm][/usr/share/lilypond/2.2.6/scm/define-grobs.scm][/usr/share/lilypond/2.2.6/scm/define-grob-interfaces.scm][/usr/share/lilypond/2.2.6/scm/page-layout.scm][/usr/share/lilypond/2.2.6/scm/paper.scm]
warning: can't find file: `test'
lilypond:
warning: no LilyPond output found for `test'
Invoking `((
latex \\nonstopmode \\input test.latex >&2 ) >&- )'This is TeX, Version 3.14159 (Web2C 7.3.1)
LaTeX2e <2001/06/01>
Babel and hyphenation patterns for american, french, german, ngerman, i
talian, nohyphenation, loaded.
(test.latex (/usr/share/texmf/tex/latex/base/article.cls
Document Class: article 2001/04/21 v1.4e
Standard LaTeX document class
(/usr/share/texmf/tex/latex/base/size10.clo))
(/usr/share/texmf/tex/latex/misc/geometry.sty
(/usr/share/texmf/tex/latex/graphics/keyval.sty)
(/usr/share/texmf/tex/latex/config/geometry.cfg))
(/usr/share/texmf/tex/latex/base/inputenc.sty
(/usr/share/texmf/tex/latex/base/latin1.def))
(/usr/share/lilypond/2.2.6/tex/titledefs.tex
(/usr/share/lilypond/2.2.6/tex/feta20.tex))
LaTeX Warning: Unused global option(s):
[compat2].
No file test.aux.
(test.aux) )
No pages of output.
Transcript written on test.log.
Opening pipe `kpsewhich
feta20.pfa'
Invoking `dvips -Ppdf
-G0 -u +lilypond.map -otest.ps
test.dvi'This is dvips(k)
5.86 Copyright 1999 Radical Eye Software (www.radicaleye.com)
dvips: ! DVI
file can't be opened.
lilypond: error:
`dvips' failed (status 1)
Traceback (most recent call last):
File "/usr/bin/lilypond", line 919, in ?
run_dvips
(outbase, extra_init)
File "/usr/bin/lilypond", line 596,
in run_dvips
ly.system
(cmd)
File "/usr/share/lilypond/2.2.6/python/lilylib.py", line 335,
in system
exit
(status)
File "/usr/share/lilypond/2.2.6/python/lilylib.py", line 130,
in exit
raise
_ ('Exiting (%d)...') % i
Exiting (256)...
lilypond:
warning: can't find file: `test.dvi'
lilypond:
warning: can't find file: `test.midi'
lilypond:
warning: can't find file: `test.pdf'
Cleaning /tmp/@24222.0lilypond...
[EMAIL PROTECTED] [~]#
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: missing noteheads
Disregard the last error report. This is the right error report:
[EMAIL PROTECTED] [~/software]# lilypond --verbose test.ly
lilypond (GNU LilyPond) 2.2.6
Opening pipe `/usr/bin/lilypond-bin
--version '
Opening pipe `kpsexpand
\$TEXMF'
Opening pipe `kpsewhich
-expand-path=\$T1FONTS'
Invoking `/usr/bin/lilypond-bin -I /root/software -I /root/software -I
/root/software -H dedication -H title -H subtitle -H subsubtitle
-H footer -H head -H composer -H arranger -H instrument -H opus -H piece -H metre -H meter -H poet -H texttranslator
-H textheight -H fontencoding
-H latexheaders -H language -H latexpackages
-H papersize -H pagenumber
-H inputencoding -H latexoptions
-H linewidth -H unit -H orientation --verbose test'
lilypond_datadir: `/usr/share/lilypond'
local_lilypond_datadir: `/usr/share/lilypond/2.2.6'
localedir: `/usr/share/locale'
LILYPONDPREFIX: `'
[/usr/share/lilypond/2.2.6/scm/define-music-types.scm][/usr/share/lilypond/2.2.6/scm/output-lib.scm][/usr/share/lilypond/2.2.6/scm/c++.scm][/usr/share/lilypond/2.2.6/scm/chord-ignatzek-names.scm][/usr/share/lilypond/2.2.6/scm/chord-entry.scm][/usr/share/lilypond/2.2.6/scm/chord-generic-names.scm][/usr/share/lilypond/2.2.6/scm/stencil.scm][/usr/share/lilypond/2.2.6/scm/new-markup.scm][/usr/share/lilypond/2.2.6/scm/bass-figure.scm][/usr/share/lilypond/2.2.6/scm/music-functions.scm][/usr/share/lilypond/2.2.6/scm/part-combiner.scm][/usr/share/lilypond/2.2.6/scm/define-music-properties.scm][/usr/share/lilypond/2.2.6/scm/auto-beam.scm][/usr/share/lilypond/2.2.6/scm/chord-name.scm][/usr/share/lilypond/2.2.6/scm/define-context-properties.scm][/usr/share/lilypond/2.2.6/scm/translation-functions.scm][/usr/share/lilypond/2.2.6/scm/script.scm][/usr/share/lilypond/2.2.6/scm/midi.scm][/usr/share/lilypond/2.2.6/scm/beam.scm][/usr/share/lilypond/2.2.6/scm/clef.scm][/usr/share/lilypond/2.2.6/scm/slur.scm][/usr/share/lilypond/2.2.6/scm/font.scm][/usr/share/lilypond/2.2.6/scm/define-markup-commands.scm][/usr/share/lilypond/2.2.6/scm/define-grob-properties.scm][/usr/share/lilypond/2.2.6/scm/define-grobs.scm][/usr/share/lilypond/2.2.6/scm/define-grob-interfaces.scm][/usr/share/lilypond/2.2.6/scm/page-layout.scm][/usr/share/lilypond/2.2.6/scm/paper.scm]
Now processing `test.ly'
Parsing...
[/usr/share/lilypond/2.2.6/ly/init.ly[/usr/share/lilypond/2.2.6/ly/declarations-init.ly[/usr/share/lilypond/2.2.6/ly/nederlands.ly][/usr/share/lilypond/2.2.6/ly/drumpitch-init.ly][/usr/share/lilypond/2.2.6/ly/chord-modifiers-init.ly][/usr/share/lilypond/2.2.6/ly/script-init.ly][/usr/share/lilypond/2.2.6/ly/scale-definitions-init.ly][/usr/share/lilypond/2.2.6/ly/grace-init.ly][/usr/share/lilypond/2.2.6/ly/midi-init.ly[/usr/share/lilypond/2.2.6/ly/performer-init.ly]][/usr/share/lilypond/2.2.6/ly/engraver-init.ly][/usr/share/lilypond/2.2.6/ly/dynamic-scripts-init.ly][/usr/share/lilypond/2.2.6/ly/spanners-init.ly][/usr/share/lilypond/2.2.6/ly/property-init.ly]][/root/software/test.ly
/root/software/test.ly:1:1: error: parse
error, unexpected '{':
{
]((gc-time-taken
. 24) (cells-allocated . 228837) (cell-heap-size . 471040) (bytes-malloced . 891467) (gc-malloc-threshold
. 1223773) (gc-times . 21) (gc-mark-time-taken
. 11) (gc-sweep-time-taken . 13) (cells-marked .
2221941) (cells-swept . 4783512) (cell-heap-segments (136865792 . 136816640)
(136892416 . 136876032) (137009152 . 136943616) (137123840 . 137025536)
(1077348352 . 1077200896) (1077516288 . 1077352448) (1077733376 . 1077520384)
(1078065152 . 1077737472) (1080166400 . 1078069248) (1080838144 .
1080248320)))]
/root/software/test.ly:2:0: warning:
Braces don't match:
c
Failed files: test.ly
lilypond:
warning: `lilypond-bin' failed (status 1) (ignored)
lilypond: error:
LilyPond failed on input file test (exit status 1)
Traceback (most recent call last):
File "/usr/bin/lilypond", line 873, in ?
run_lilypond
(files, dep_prefix)
File "/usr/bin/lilypond", line 296,
in run_lilypond
ly.exit
(status)
File "/usr/share/lilypond/2.2.6/python/lilylib.py", line 130,
in exit
raise
_ ('Exiting (%d)...') % i
Exiting (256)...
Cleaning /tmp/@24308.0lilypond...
[EMAIL PROTECTED] [~/software]#
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: missing noteheads
It looks as if you have used a test file designed for LilyPond version 2.6.
The input syntax has changed since version 2.2.6 (which really is very
old by now). Please read the tutorial for version 2.2 to learn how to
produce a relevant test file for that version.
/Mats
Michael Porcaro wrote:
Disregard the last error report. This is the right error report:
[EMAIL PROTECTED] [~/software]# lilypond --verbose test.ly
lilypond (GNU LilyPond) 2.2.6
Opening pipe `/usr/bin/lilypond-bin --version '
Opening pipe `kpsexpand \$TEXMF'
Opening pipe `kpsewhich -expand-path=\$T1FONTS'
Invoking `/usr/bin/lilypond-bin -I /root/software -I /root/software
-I /root/software -H dedication -H title -H subtitle -H subsubtitle -H
footer -H head -H composer -H arranger -H instrument -H opus -H piece
-H metre -H meter -H poet -H texttranslator -H textheight -H
fontencoding -H latexheaders -H language -H latexpackages -H papersize
-H pagenumber -H inputencoding -H latexoptions -H linewidth -H unit -H
orientation --verbose test'
lilypond_datadir: `/usr/share/lilypond'
local_lilypond_datadir: `/usr/share/lilypond/2.2.6'
localedir: `/usr/share/locale'
LILYPONDPREFIX: `'
[/usr/share/lilypond/2.2.6/scm/define-music-types.scm][/usr/share/lilypond/2.2.6/scm/output-lib.scm][/usr/share/lilypond/2.2.6/scm/c++.scm][/usr/share/lilypond/2.2.6/scm/chord-ignatzek-names.scm][/usr/share/lilypond/2.2.6/scm/chord-entry.scm][/usr/share/lilypond/2.2.6/scm/chord-generic-names.scm][/usr/share/lilypond/2.2.6/scm/stencil.scm][/usr/share/lilypond/2.2.6/scm/new-markup.scm][/usr/share/lilypond/2.2.6/scm/bass-figure.scm][/usr/share/lilypond/2.2.6/scm/music-functions.scm][/usr/share/lilypond/2.2.6/scm/part-combiner.scm][/usr/share/lilypond/2.2.6/scm/define-music-properties.scm][/usr/share/lilypond/2.2.6/scm/auto-beam.scm][/usr/share/lilypond/2.2.6/scm/chord-name.scm][/usr/share/lilypond/2.2.6/scm/define-context-properties.scm][/usr/share/lilypond/2.2.6/scm/translation-functions.scm][/usr/share/lilypond/2.2.6/scm/script.scm][/usr/share/lilypond/2.2.6/scm/midi.scm][/usr/share/lilypond/2.2.6/scm/beam.scm][/usr/share/lilypond/2.2.6/scm/clef.scm][/usr/share/lilypond/2.2.6/scm/slur.scm][/usr/share/lilypond/2.2.6/scm/font.scm][/usr/share/lilypond/2.2.6/scm/define-markup-commands.scm][/usr/share/lilypond/2.2.6/scm/define-grob-properties.scm][/usr/share/lilypond/2.2.6/scm/define-grobs.scm][/usr/share/lilypond/2.2.6/scm/define-grob-interfaces.scm][/usr/share/lilypond/2.2.6/scm/page-layout.scm][/usr/share/lilypond/2.2.6/scm/paper.scm]
Now processing `test.ly'
Parsing...
[/usr/share/lilypond/2.2.6/ly/init.ly[/usr/share/lilypond/2.2.6/ly/declarations-init.ly[/usr/share/lilypond/2.2.6/ly/nederlands.ly][/usr/share/lilypond/2.2.6/ly/drumpitch-init.ly][/usr/share/lilypond/2.2.6/ly/chord-modifiers-init.ly][/usr/share/lilypond/2.2.6/ly/script-init.ly][/usr/share/lilypond/2.2.6/ly/scale-definitions-init.ly][/usr/share/lilypond/2.2.6/ly/grace-init.ly][/usr/share/lilypond/2.2.6/ly/midi-init.ly[/usr/share/lilypond/2.2.6/ly/performer-init.ly]][/usr/share/lilypond/2.2.6/ly/engraver-init.ly][/usr/share/lilypond/2.2.6/ly/dynamic-scripts-init.ly][/usr/share/lilypond/2.2.6/ly/spanners-init.ly][/usr/share/lilypond/2.2.6/ly/property-init.ly]][/root/software/test.ly
/root/software/test.ly:1:1: error: parse error, unexpected '{':
{
]((gc-time-taken . 24) (cells-allocated . 228837) (cell-heap-size .
471040) (bytes-malloced . 891467) (gc-malloc-threshold . 1223773)
(gc-times . 21) (gc-mark-time-taken . 11) (gc-sweep-time-taken . 13)
(cells-marked . 2221941) (cells-swept . 4783512) (cell-heap-segments
(136865792 . 136816640) (136892416 . 136876032) (137009152 .
136943616) (137123840 . 137025536) (1077348352 . 1077200896)
(1077516288 . 1077352448) (1077733376 . 1077520384) (1078065152 .
1077737472) (1080166400 . 1078069248) (1080838144 . 1080248320)))]
/root/software/test.ly:2:0: warning: Braces don't match:
c
Failed files: test.ly
lilypond: warning: `lilypond-bin' failed (status 1) (ignored)
lilypond: error: LilyPond failed on input file test (exit status 1)
Traceback (most recent call last):
File "/usr/bin/lilypond", line 873, in ?
run_lilypond (files, dep_prefix)
File "/usr/bin/lilypond", line 296, in run_lilypond
ly.exit (status)
File "/usr/share/lilypond/2.2.6/python/lilylib.py", line 130, in exit
raise _ ('Exiting (%d)...') % i
Exiting (256)...
Cleaning /tmp/@24308.0lilypond...
[EMAIL PROTECTED] [~/software]#
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Re: HELP ABOUT SLUR OFFSET
Hello list, hello Han-Wen, You wrote: > MX wrote: > >Hi all, bonjour à tous. > > > >1. How can I ajust the position of the beginning of the slur in the > >picture attached ? > > > >I tried to override the control-points property of the slur object but I > >couldn't find rules to use it and I just want to push sligtly the > >beginning of the slur, not the entire slur. The property Slur > >#'attachment-offsets seemed to do that easyly but it does not exist > >anymore in the 2.6.0 release. > > Slurs have been rewritten, and should in general give a much better > result. However, this situation might be an exception. You can move the > slur vertically with the #'positions property. > > For horizontal offsets, I would have to add some code. I could add that > as a sponsored feature (see http://lilypond-design.com/sponsor/ for more > information) I did ask me - without any answer - why You threw off this feature of slur attachment-offset. For me lilypond would be missing some important, if it wouldn't be possible to change the endpoints of slurs in an easy way. Normally I would say, okay, let's sponsor it (*), if there is no other way. But for the moment my personal situation doesn't allow me to spend anything, I'm sorry. (*) But nevertheless, I think, that the attachment-offset of Slurs might be a standard implementation of lilypond. Missing it after 2.2.x was the main reason for me to stop typesetting ... :-( And now it is very hard to hear, that in the 2.6.x lilypond is missing this again. :-( Don't misunderstand me: I still think, that lilypond is a very great work, and my heart is full of thanks to You (and Jan) for creating and developping it! :-) Best Regards Roland ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: First Measure bar
On 21-Oct-05, at 1:07 AM, Mats Bengtsson wrote:
I hope you have a good reason to deviate from standard music
typesetting
practice. As far as I can see, it's hard-coded into LilyPond to not
typeset
the opening repeat at the beginning of a piece, but if there is a
general
need for such an option, it should be easy to make this configurable.
No need -- just insert the bar manually.
{
\repeat 2 volta {
\bar "|:"
c1 c c
}
}
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Ossia staves getting them to work....
On 21-Oct-05, at 5:57 AM, Trent Johnston wrote:
I'm trying to use the \stopStaff and \startStaff commands used in the
'Tips and Tricks' section but unfortunately this doesn't seem to work
as I get a whole new staff above the violin either with staff lines or
no staff lines but with a clef.
You just need to do \new Staff { blah blah }
Search LSR for ossia; it has an example.
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: First Measure bar
Title: RE: First Measure bar
But this puts the opening time signature inside the repeats. When an open repeat is used in all the music I've ever seen, the time signature is outside (to the left of) the opening repeat.
-Original Message-
From: Graham Percival [mailto:[EMAIL PROTECTED]]
Sent: Fri 10/21/2005 1:54 PM
To: Mats Bengtsson
Cc: lilypond-user@gnu.org; VSD; Kress, Stephen
Subject: Re: First Measure bar
On 21-Oct-05, at 1:07 AM, Mats Bengtsson wrote:
> I hope you have a good reason to deviate from standard music
> typesetting
> practice. As far as I can see, it's hard-coded into LilyPond to not
> typeset
> the opening repeat at the beginning of a piece, but if there is a
> general
> need for such an option, it should be easy to make this configurable.
No need -- just insert the bar manually.
{
\repeat 2 volta {
\bar "|:"
c1 c c
}
}
Cheers,
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: First Measure bar
Jazz scores often print starting repeats. I really don't care too much if
this is standard or not. It's just more readable to me and the musicians I
use to work with (I don't use it for "classical" music though).
Since the trick below works easily, I don't see the need for such change.
On Fri, 21 Oct 2005 10:07:28 +0200, Mats Bengtsson
<[EMAIL PROTECTED]> wrote:
I hope you have a good reason to deviate from standard music typesetting
practice. As far as I can see, it's hard-coded into LilyPond to not
typeset
the opening repeat at the beginning of a piece, but if there is a general
need for such an option, it should be easy to make this configurable.
/Mats
VSD wrote:
I have the same problem. I don't know if lilypond can do that, but I
use the following cheap trick:
{
\time 4/4
\partial 128 s128 % create an empty tiny partial measure before
the repeat
\repeat volta 2
{
c''2
c''
}
}
which works form me. I'd recommend you to use raggedright=##t in the
layout for a single bar score though.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
