[EMAIL PROTECTED] writes:
> Thanks, this really does make the score look much nicer.
>
> Is there something I can do about lyric syllables on the first beat
> being drawn over the barline? (To see what I mean, see
see input/regression/lyrics-bar.ly
BTW, please don't take discussions that are o
>> Is there something I can do about lyric syllables on the first beat
>> being drawn over the barline? (To see what I mean, see
>
> see input/regression/lyrics-bar.ly
Aha! Yes, it works, although I could use still more space between the
barline and the words. However, applying this resulted
[EMAIL PROTECTED] writes:
> >> Is there something I can do about lyric syllables on the first beat
> >> being drawn over the barline? (To see what I mean, see
> >
> > see input/regression/lyrics-bar.ly
>
> Aha! Yes, it works, although I could use still more space between the
> barline and the
Hello all,
thanks for the answers and here is one more doubt. I wrote a piece with
chordnames above, but the the inverted chords get much near the next one.
So I tried to change the font with \property ChordNames.ChordName
#font-relative-size = #-5 or stg. but it seems only the modifiers
were cha
Hello Ohannes,
you must add
\midi {}
inside \score {} just after the \paper {} command. If you omit \midi
lilypond does no generate MIDI output.
You can convert .midi to .ly (the reverse) using midi2ly.
[]s
Felipe
On Mon, 1 Jul 2002, Ohannes Murat Berin wrote:
> I finally got lilypond work
I have mentioned this problem before, but I am
providing an example now. Chords in 1.5.60 needs a fixing. Look to the attached
example, the suprescript are way to separated above the chord name, specially in
simple chords ast C7, the 7 should not be that high.
I have looked for a property t
[EMAIL PROTECTED] writes:
> I have mentioned this problem before, but I am providing an example now. Chords in
>1.5.60 needs a fixing. Look to the attached example, the suprescript are way to
>separated above the chord name, specially in simple chords ast C7, the 7 should not
>be that high.
Th
On Mon, 2002-07-01 at 16:32, Han-Wen wrote:
> [EMAIL PROTECTED] writes:
> > Well, I don't understand TEX fonts, so somehow I have managed to
> > get my lilypond installation into a non-functional state
> > (after it was initially working). I compiled version 1.4.13 from
> > source on Red Hat 7.3 o
[EMAIL PROTECTED] writes:
> > > (after it was initially working). I compiled version 1.4.13 from
> > > source on Red Hat 7.3 on an Intel PIII system. xdvi has some problems
> > > finding fonts, it seems. The message I am now getting when I run
> > > xdvi is:
> $ set | egrep 'TEXMF|GS'
> GS_FONTPA
[EMAIL PROTECTED] writes:
> > > (after it was initially working). I compiled version 1.4.13 from
> > > source on Red Hat 7.3 on an Intel PIII system. xdvi has some problems
> > > finding fonts, it seems. The message I am now getting when I run
> > > xdvi is:
> $ set | egrep 'TEXMF|GS'
> GS_FONTPA
You owe it to yourself and your wealth to read this.
AS SEEN ON NATIONAL TV:
"Making over half a million dollars every 4 to 5 months
from your home for an investment of only $25 U.S. Dollars expense
one time"
THANKS TO THE COMPUTER AGE AND THE INTERNET!
BE A MILLIONAIRE LIKE OTHERS WITHIN A Y
I have been running Lilypond under Linux for 2 years quite successfully
and am now wanting to move to Windows. There are 2 reasons:
- our Linux machine is silent (no sound card), and we are making increasing
use of MIDI output.
- although I have learnt a great deal about music and typesetting t
"Peter Dixon" <[EMAIL PROTECTED]> writes:
> I have been running Lilypond under Linux for 2 years quite successfully
> and am now wanting to move to Windows. There are 2 reasons:
Sure, whatever gets you going. However,
> - our Linux machine is silent (no sound card), and we are making increasi
13 matches
Mail list logo