Hi,
unfortunately I don't know anything about Slackware, but a live CD with the
latest stable version of lilypond would be great!
2008/8/29 Wilbert Berendsen <[EMAIL PROTECTED]>
> Op donderdag 28 augustus 2008, schreef Valentin Villenave:
> > the Nimblex guys seem to be ready to include LilyPond
Op maandag 25 augustus 2008, schreef Gilles Sadowski:
> $ convert test.png -transparent white test_tr.png
This will convert 'white' to '100% transparent', but not the shades of grey
created by the anti-aliasing algorithms in ghostscript.
After long fiddling I found a way to convert every shade
Op donderdag 28 augustus 2008, schreef Valentin Villenave:
> the Nimblex guys seem to be ready to include LilyPond in their
> distribution if we can help them doing so; they'd like
> (understandably) to have a KDE menu entry for it, so maybe it would be
> a good idea to include LilyKDE as well, wit
Hello,
I want to shorten the length of beamed stems in a four-voice piano
staff, but it seems that the beamed-stem-shorten-property doesn't take
effect. Could anyone give me a hint how to solve the problem using
Version 2.10.33?
Thanks,
Chris
__
Graham Percival wrote Thursday, August 28, 2008 1:18 PM
Oh, if you haven't carefully read NR 6, that might be good... although
it hasn't been touched yet, so I don't know if Trevor wants to hear
about any problems you find in it. That's up to him...
It will be quite a while before I get to N
Ralph, you wrote Thursday, August 28, 2008 3:07 PM
I've been indexing the Notation Reference sections as I learn they're
ready
- that is, announced as finished. I will check the Learning Manual files
you
mentioned. I do get them from Savannah. I don't have posting rights, as
far
a I know, so
Jonathan Kulp wrote
Perhaps we should add an example in Notation Reference where it talks
about "controlling the placement of chord fingerings" showing that even
for single notes you have to use a chord construct for the
fingeringOrientation to work. I didn't get to do this in fretted string
Hi.
> I am unable to get the attachment (I get http error 404). What am I missing?
A possible explanation was given in another post.
In any case, here is the script inline (just copy/paste the text between
the "---CUT---" marks in another file):
---CUT---
#!/usr/bin/perl -w
use IO::File;
my $
Kenny Stephens wrote:
> Gilles Sadowski harfang.homelinux.org> writes:
>
>
>> Here is a Perl script that counts the notes in LilyPond files (only the
>> English pitch names).
>> Example usage:
>> countLilyNotes.pl *.ly
>>
>> Best,
>> Gilles
>>
>> Attachment (countLilyNotes.pl): text/x-perl,
2008/8/23 Stefan Thomas <[EMAIL PROTECTED]>:
> You are right, nimblex looks great,it would be a good thing, if there could
> be included Lilypond!
Hi Stefan, hi everybody,
the Nimblex guys seem to be ready to include LilyPond in their
distribution if we can help them doing so; they'd like
(under
Gilles Sadowski harfang.homelinux.org> writes:
> Here is a Perl script that counts the notes in LilyPond files (only the
> English pitch names).
> Example usage:
> countLilyNotes.pl *.ly
>
> Best,
> Gilles
>
> Attachment (countLilyNotes.pl): text/x-perl, 665 bytes
>
I am unable to get the
Carl,
Perhaps we should add an example in Notation Reference where it talks
about "controlling the placement of chord fingerings" showing that even
for single notes you have to use a chord construct for the
fingeringOrientation to work. I didn't get to do this in fretted
strings because "fin
Hi Steven,
I did the documentation on guitar stuff so I'm familiar with this issue.
I suspect that what you're missing is a <> chord construct around
whatever it is that you want affected. When I was running through all
of the commands I noticed that the only way the \set
fingeringOrientatio
On Aug 28, 2008, at 8:50 AM, Steven Padalino wrote:
Hi,
Using Lilipond 2.10.33 with jEdit 4.3pre15 on Windows XP SP2.
The \set fingeringOrientations = #'(left) is not working. Finger
numbers continue to appear at the top or bottom of note stems.
I could easily be wrong but try #'(LEFT)
Hi,
Using Lilipond 2.10.33 with jEdit 4.3pre15 on Windows XP SP2.
The \set fingeringOrientations = #'(left) is not working. Finger numbers
continue to appear at the top or bottom of note stems.
I have the command positioned after the "staffClassicalGuitar = \new Staff"
command and before
Am 28.08.2008 um 17:11 schrieb Mike Blackstock:
Not being a singer, I assumed that vocal music never has beams -
Current style guides indicate that vocal music follows beaming rules
for instrument music.
wrong! I see that when notes are slurred, the slurred notes have
beams. Is there a
Mike Blackstock wrote:
Not being a singer, I assumed that vocal music never has beams -
wrong! I see that when notes are slurred, the slurred notes have
beams. Is there an easy way to indicate that if notes are within a
slur, they should be beamed, otherwise not?
No, there's no easy way, but
Not being a singer, I assumed that vocal music never has beams - wrong!
I see that when notes are slurred, the slurred notes have beams. Is
there an easy way to indicate that if notes are within a slur, they
should be beamed, otherwise not?
I suspect it can be done with 'override-auto-beam-set
Thanks, Trevor -
I've been indexing the Notation Reference sections as I learn they're ready
- that is, announced as finished. I will check the Learning Manual files you
mentioned. I do get them from Savannah. I don't have posting rights, as far
a I know, so I've been submitting them to Carl Soren
On 8/28/08, Kieren MacMillan <[EMAIL PROTECTED]> wrote:
>
> Is that the best use of my Lilypond volunteer time? I'm an
> experienced programmer (Java, a half-dozen scripting languages, etc.)
> *and* an advanced Lilypond user and working composer — should I be
> teaching myself Scheme and/or C++, an
Hi Graham,
for some reason refused to learn scheme and do bug fixes
That's the second time you've mentioned that in a couple of emails…
Is that the best use of my Lilypond volunteer time? I'm an
experienced programmer (Java, a half-dozen scripting languages, etc.)
*and* an advanced Lilypo
On 8/28/08, Mats Bengtsson <[EMAIL PROTECTED]> wrote:
>
> James E. Bailey wrote:
>> Speaking of which, how difficult would it be to collect a "known
>> issues" list? Something akin to the LSR, but for known issues for
>> which there are solutions. It would help tons when troubleshooting why
>> a pa
James E. Bailey wrote:
Speaking of which, how difficult would it be to collect a "known
issues" list? Something akin to the LSR, but for known issues for
which there are solutions. It would help tons when troubleshooting why
a particular output isn't what's expected.
Isn't the intention to
-
On 8/28/08, James E. Bailey <[EMAIL PROTECTED]> wrote:
>
> Thanks, it worked perfectly. You know, I looked at that in the
> documentation, but it never occurred to me that it was the same problem.
>
> Speaking of which, how difficult would it be to collect a "known
> issues" list? Something akin to
Thanks a lot for the hint with the change in
/usr/local/lilypond/usr/share/lilypond/current/scm/chord-name.scm
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
James E. Bailey Wednesday, August 27, 2008 10:51 PM
Wow, thanks. With that bit of information, I could change my code
appropriately.
\version "2.11.57"
{
\relative {
\voiceOne
\appoggiatura e'
\voiceOne
f4 e d c b a g f
}
}
Can this be mentioned somewhere in th
Dear Alexander,
the default paper size in my pdf program is a4. But I have to set there the
margins to 1.27 cm, 1.27 cm, 1.57 cm and 1.57 cm. Otherwise the lilypond
generated pdf file would be too large for a a4 paper.
2008/8/25 Alexander Kobel <[EMAIL PROTECTED]>
> Stefan Thomas wrote:
> > Dear
27 matches
Mail list logo
