David Bobroff scripsit:
> \markup{\italic "rit."}
Thank a lot.
BTW, I have meanwhile found another possibility ("raise" to place the markup a
little higher):
^#'((bold italic) ((raise . 1.2) "ritt."))
Regards
Milan Horak
Wanting to add a "ritt." mark to a piece, I have encountered a problem. I have
already done it in some piese earlier, but it was long ago and I am quite
sure the ancient version of LilyPond I used printed this "ritt." in nice
italics. Now, I get only a normal roman (and ugly) "ritt." and seem n
Zbyněk Burget scripsit:
> is here somebody from Czech or Slovak? I need help with some little
> problems in lilypond and my english is ... no very good :-(
> Is here somebody who can help me?
Maybe I can help you. / Ja Vam mozna mohu pomoci.
I am czech and use LilyPond. / Jsem Cech a uzivam Lily
[EMAIL PROTECTED] scripsit:
> I'm using lilypond inside a latex text. I tried in the
> different ways explained in the Manual of lilypond but when
> I compile the file
> there are some problems with the fonts of the lyrics.
> The lilypond file inside the file.tex dosn't show the fonts
> with accen
Mats Bengtsson scripsit:
> Answer 3: Remove the time signatures and the space for them
> from a single stave (warning, this method may lead to strange
> crasches):
> \property Staff.TimeSignature = \turnOff
THIS works! Without crashes!
Thank you a lot!
> I hope these answers apply also t
Hallo,
could somebody tell me, how the time signature engraving could be switched
off? In older versions of LilyPond, the cadenza-switch did it. In the version
I use now (1.6.4), the cadenza-switch switches the bar check off, but the
default time signature (C) is still engraved.
Regards
clive CATTERALL scripsit:
> I have tried altering
>
> \midi { \tempo 4=120}
>
> up to
>
> \midi { \tempo 4=240}
>
> with no noticeable effect.
I had the same problem under Linux (RedHat) / KDE. A friend of mine having the
same configuration had no problems. MIDI files built by him und by me we
David Boersma scripsit:
> Now the Soprano and Alto are in the same Voice context. The \voiceOne and
> \voiceTwo macros changes properties of this context. Apparently the
> \voiceTwo macro is processed after the \voiceOne, so those settings
> overwrite immediately those of voiceOne.
> ...
> \contex
Mats Bengtsson scripsit:
> You have to explicitly create separate Voice contexts for each
> line of music. Now, both sobran and alt end up in the same context
> and the \voiceTwo command overrides the \voiceOne command.
>
>\notes <
> \context Voice=sopran {\vo
Graham Percival wrote:
> I'm confused -- do you have a \version "1.x.y" inside your file? If not,
> why not add that and let convert-ly do its stuff?
I have tried this method. But, convert-ly produces files with as many errors
as the non-converted files have. Thus, convert-ly seemed not to be a
10 matches
Mail list logo