Thank you,
Yes, as I want to make think fairly complex (bilingual+ music) , I shall
study more Scribus..
Provero...
PC
Federico Bruni a écrit :
Pierre Couderc wrote:
What is the best way for a book with Lilypond extracts in it?
I have tried LaTeX with lilypond book, but I get mixs of
Mmm, I note that you that you write : you'll have to split each pdf
produced by LilyPond.
I do not understand well, because in lilypond-books used with LaTex,
each individual staff is generated in an indivudual .pdf
Is it not the case with Scribus..?
Pierre
Federico Bruni a écrit :
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Grammostola == Grammostola Rosea rosea.grammost...@gmail.com writes:
Grammostola But I got this message:
Grammostola d...@debian:~/lilypondfiles$ lilywrap lilywraptest.ly
Grammostola /usr/local/lilypond/usr/bin/lilypond: unrecognized
Grammostola option: `--midi'
Here's an updated lilywrap
Ralph Palmer wrote Saturday, September 05, 2009 4:06 PM
I haven't had much time to do much Lilypond work on my new-ish
Ubuntu setup.
I'd like some advice on where to put a generic definitions.ly
file that I
want to include in most of my pieces. I'm afraid that if I put the
definitions.ly in
Following test code demonstrates the problem on my system. I obviously don't
need ignore-collision set for this particular example, but I do for the
score where I noticed the problem. Can I stop the merged noteheads from
getting filled in this situation?
\version 2.13.3
\relative d {
Peter Chubb wrote:
Grammostola == Grammostola Rosea rosea.grammost...@gmail.com writes:
Grammostola But I got this message:
Grammostola d...@debian:~/lilypondfiles$ lilywrap lilywraptest.ly
Grammostola /usr/local/lilypond/usr/bin/lilypond: unrecognized
Grammostola option:
Peter Chubb wrote:
Grammostola == Grammostola Rosea rosea.grammost...@gmail.com writes:
Grammostola But I got this message:
Grammostola d...@debian:~/lilypondfiles$ lilywrap lilywraptest.ly
Grammostola /usr/local/lilypond/usr/bin/lilypond: unrecognized
Grammostola option:
I'm notating a score similar to the SATB template provided in the learning
manual, where lyrics are above and below both staves of the system.
However, through large chunks of the song, the lyrics are all the same (and thus
can be printed once between the staves). The different lyrics only
Peter Chubb wrote:
Grammostola == Grammostola Rosea rosea.grammost...@gmail.com writes:
Grammostola But I got this message:
Grammostola d...@debian:~/lilypondfiles$ lilywrap lilywraptest.ly
Grammostola /usr/local/lilypond/usr/bin/lilypond: unrecognized
Grammostola option:
On 06.09.2009, at 12:29, Mark Engelberg wrote:
I'm notating a score similar to the SATB template provided in the
learning
manual, where lyrics are above and below both staves of the system.
However, through large chunks of the song, the lyrics are all the
same (and thus
can be printed
Am Sonntag, 6. September 2009 schrieb Mark Engelberg:
Right now, the way I'm dealing with this is to set up my ChoirStaff to have
four lyrics lines throughout the song, above and below each staff. Then, I
add a \skip 1 for every note for which no lyrics should be printed.
you could use _ to
Hello,
I am using centered dynamics for some scores (id=357). Now I need to use
a text for a dynamic change spread over several measures. I found an
appropriate snippet in LSR (id=456).
But I failed to combine both snippets. The hairpin is not replaced by
the text. What's going wrong here?
Jonathan Wilkes wrote:
I tried fooling around with tieWaitForNote
You didn't show your code, so it's not easy to guess what you tried.
I have no cross-staff experience, but it looks to me like
the cross-staff run is a lot better supported than
the cross-staff chord (where you have to
--- On Sun, 9/6/09, Robin Bannister r...@dataway.ch wrote:
From: Robin Bannister r...@dataway.ch
Subject: Re: tieWaitForNote across staves
To: Jonathan Wilkes jancs...@yahoo.com, lilypond-user
lilypond-user@gnu.org
Date: Sunday, September 6, 2009, 6:28 PM
Jonathan Wilkes wrote:
I
On Sun, Sep 06, 2009 at 12:23:28PM +0200, Grammostola Rosea wrote:
@ Valentin, yeah would be nice if we could improve the midi output by
default. I can remember I mentioned this before, but one comment (not
from you) was that Lilypond was mainly a notation typesetter... And
while been
On Sun, 6 Sep 2009 18:53:37 +0100
Graham Percival gra...@percival-music.ca wrote:
On Sun, Sep 06, 2009 at 12:23:28PM +0200, Grammostola Rosea wrote:
@ Valentin, yeah would be nice if we could improve the midi output by
default. I can remember I mentioned this before, but one comment (not
David Raleigh Arnold wrote:
On Sun, 6 Sep 2009 18:53:37 +0100
Graham Percival gra...@percival-music.ca wrote:
On Sun, Sep 06, 2009 at 12:23:28PM +0200, Grammostola Rosea wrote:
@ Valentin, yeah would be nice if we could improve the midi output by
default. I can remember I mentioned
It's not so straightforward and there is no 100% perfect solution. However,
several good approaches can be found on the LSR (http://lsr.dsi.unimi.it/ ).
Simply search for dynamics and the first snippet will be your man.
Very good. Thanks! Problem solved.
I should have thought at the LSR...
On Sun, Sep 06, 2009 at 01:49:12PM -0400, David Raleigh Arnold wrote:
On Sun, 6 Sep 2009 18:53:37 +0100
Graham Percival gra...@percival-music.ca wrote:
Of course there's nothing wrong with having both! However, nobody
else wants to work on midi output.
Again, why not get in touch with
Ok, here's my attempt at getting the cross stave ties from my previous
email. The problem I'm running into is that when I try to set a tie's
vertical position to get it into the RH staff, Lilypond starts a
Vaudeville shtick and moves the staff up beyond my reach (which I guess
is what you
Hi everybody,
Here's (at last) a new LilyReport:
Welcome to this sixteenth issue of the LilyPond Report!
While today’s instalment certainly took its time, here it is at last,
with many guests and contributions that will definitely make it up.
Before reading, here’s a little game for you: Who
Message: 8
Date: Sun, 6 Sep 2009 21:01:12 +0200
From: Valentin Villenave v.villen...@gmail.com
Subject: Re: The LilyPond Report, again!
To: Valentin Villenave v.villen...@gmail.com
Cc: Lilypond Users lilypond-user@gnu.org
Message-ID:
I don't want to be a nitpicker, but in Report 16, Jan's last name is
not always spelled correctly.
(Unless this was an inside joke and everybody is laughing at me now?) :-)
___
lilypond-user mailing list
lilypond-user@gnu.org
On Sun, Sep 06, 2009 at 12:57:41PM -0700, David Rogers wrote:
(Unless this was an inside joke and everybody is laughing at me now?) :-)
Sucker!
Cheers,
- Graham Parsifal.
___
lilypond-user mailing list
lilypond-user@gnu.org
On Sun, 06 Sep 2009 20:49:50 +0200
Grammostola Rosea rosea.grammost...@gmail.com wrote:
David Raleigh Arnold wrote:
On Sun, 6 Sep 2009 18:53:37 +0100
Graham Percival gra...@percival-music.ca wrote:
On Sun, Sep 06, 2009 at 12:23:28PM +0200, Grammostola Rosea wrote:
@
2009/9/5 Jonathan Wilkes jancs...@yahoo.com:
Is this bug #430?
No, but it has been fixed recently. I'll backport it to the stable
version in a moment so it'll be included in 2.12.3.
Also, what's the best way to make that slur in the bass clef look nice?
It seems to be colliding with the
On Sun, Sep 6, 2009 at 7:49 PM, David Raleigh Arnoldd...@openguitar.com wrote:
Again, why not get in touch with the developer(s) of midge? The
syntax is completely different, but it is *text-based* and GNU.
Perhaps the newly-created `midi' mailing list could provide us (and
them) with a
Grammostola == Grammostola Rosea rosea.grammost...@gmail.com writes:
Grammostola Peter Chubb wrote:
Grammostola When using lilywrap I get:
Grammostola lilywrap dynamics.ly /usr/local/bin/lilywrap: 23: Syntax
Grammostola error: ( unexpected
Hmmm. Are you using a non-standard /bin/sh ??? It
On Sun, Sep 6, 2009 at 9:57 PM, David Rogersdavidandrewrog...@gmail.com wrote:
I don't want to be a nitpicker, but in Report 16, Jan's last name is
not always spelled correctly.
Au contraire: it is *always* spelled uncorrectly. Which is quite more
consistent.
(Unless this was an inside joke
2009/9/4 Carl Sorensen c_soren...@byu.edu:
And perhaps we should avoid the \set Staff.instrumentName tweaks by defining
a \setInstrumentName command
setInstrumentName =
#(define-music-function (parser location instrument-name) (string?)
#{
\set Staff.instrumentName = $instrument-name
Peter == Peter Chubb lily.u...@chubb.wattle.id.au writes:
Peter You probably have dash installed as the system shell. Here's
Peter an updated verion of the script that will work with Dash, and
Peter will *still* work on POSIX compliant shells, but will no longer
Peter work with the traditional
I have a two page guitar score that had all its notes complete, and was
going through adding barring, faking the barring indications with square
arpeggio brackets in a voice with transparent noteheads, stems, accidentals,
dots, etc. Anyway, after adding half a dozen of these brackets, I added one
2009/9/6 Nick Payne nick.pa...@internode.on.net:
Programming error: unknown avoidance type
Continuing, cross fingers
errors showing up in the console output every time I build the score. The
PDF output still looks fine. I searched the documentation and mailing list
archives and didn't find
David Raleigh Arnold a écrit :
On Sun, 06 Sep 2009 20:49:50 +0200
Grammostola Rosea rosea.grammost...@gmail.com wrote:
David Raleigh Arnold wrote:
On Sun, 6 Sep 2009 18:53:37 +0100
Graham Percival gra...@percival-music.ca wrote:
On Sun, Sep 06, 2009 at 12:23:28PM +0200, Grammostola Rosea
Hi Patrick,
\new ChordNames {
\chordmode
{
g1 |
g16*6:sus4 g16*10 | \break
bes1 |
bes16*6:sus4 bes16*10 | \break
c1 |
c2:sus4 c2| \break
c1:m |
c1:m | \break
--- On Sun, 9/6/09, Neil Puttock n.putt...@gmail.com wrote:
From: Neil Puttock n.putt...@gmail.com
Subject: Re: Markup Causes Beaming Problem
To: Jonathan Wilkes jancs...@yahoo.com
Cc: lilypond-user@gnu.org
Date: Sunday, September 6, 2009, 10:38 PM
2009/9/5 Jonathan Wilkes
Instead of writing e.g. g16*6 you could have used g4.. A dotted
quarter note consists of six sixteenth notes. Instead of g16*10 you could
have used g8 s2 which is easier to read. You should consult the Learning
Manual p. 14-15 and the section Rhythm in the Notation Reference (p. 29-40)
Jonathan Wilkes wrote:
I see a cross-staff property for grobs
But this doesn't mean that every sort of grob has it, or uses it.
The file define-grob-properties.scm lists about a dozen grobs which do:
Beam, Stem, Slur, TupletBracket, among others, but not TieColumn.
So your TieColumn
Grammostola == Grammostola Rosea rosea.grammost...@gmail.com writes:
Grammostola David Raleigh Arnold wrote:
Again, why not get in touch with the developer(s) of midge? The
syntax is completely different, but it is *text-based* and GNU. It
is dedicated to midi, not notation. Why not find
Grammostola == Grammostola Rosea rosea.grammost...@gmail.com writes:
Grammostola David Raleigh Arnold wrote:
Again, why not get in touch with the developer(s) of midge? The
syntax is completely different, but it is *text-based* and GNU. It
is dedicated to midi, not notation. Why not find
How can I get LilyPond to display a clef at every measure? Here's what I have so
far:
\version 2.12.2
\paper {
#(set-paper-size a4)
}
#(set-global-staff-size 30)
\score {
{
\override Staff.BarLine #'break-visibility = #'#(#t #t #t)
s1 | s1 | s1 | s1 \break
s1 | s1 | s1 | s1 \break
s1
42 matches
Mail list logo
