Re: tie in wrong space?

yes, it doesn't look very well and it's hard to read in populated scores imho. hopefully this is easy to fix and there are some plans to improve this sideeffect of the last tie re-implementation... On Wed, 28 Sep 2005 22:54:12 +0200, Graham Percival <[EMAIL PROTECTED]> wrote: I haven't re

Re: error generating png files

On Tue, 23 Aug 2005 21:31:18 +0200, Mats Bengtsson <[EMAIL PROTECTED]> wrote: Please run lilypond --verbose --png test.ly to get a more informative error message and send it to the mailing list. ouch! I should have done this before asking. Sorry. The problem seems to be that I have the Cent

Re: line break error in tied chords

Sorry, the example is for version 2.7.7, not 2.7.6 as stated in the ly file The following example gives the following error several times in the log: programming error: infinity or NaN encountered while converting Real number continuing, cross fingers programming error: setting to zero conti

line break error in tied chords

The following example gives the following error several times in the log: programming error: infinity or NaN encountered while converting Real number continuing, cross fingers programming error: setting to zero continuing, cross fingers if there's no \break then there's no error. Note that ther

tie not printed in tied chords

Hi, in the following example, in the first tied chord the B is not tied, or the tie is just over the staff line (?). Besides this, the other tied chords in the example are ok, but look somewhat strange to me. In the second tied chord, the tie for the E looks strange under the dot, and in

error generating png files

When running one of the following commands using lilypond windows native (2.6.0 or 2.7.6): lilypond.exe -f png test.ly lilypond.exe --png test.ly I get the following log: Processing `C:/music/tst.ly' Parsing... Interpreting music... [8][10] Preprocessing graphical objects...Calculating lin

Re: 2.5.31: Clefs as outlines, not glyphs

I think this happens to the vertical braces too, as in e.g. the brace which connects two staves in any piano score. On Wed, 22 Jun 2005 00:17:16 +0200, Bertalan Fodor <[EMAIL PROTECTED]> wrote: % Smaller clefs are embedded as outlines, not font elements. Very easy to see in Acrobat, sw

Re: Tablatures are not well displayed

Hola Benja, the answer is in this thread: http://lists.gnu.org/archive/html/bug-lilypond/2005-06/msg00041.html greetings, Vincent On Tue, 21 Jun 2005 18:25:20 +0200, Benjamín Valero Espinosa <[EMAIL PROTECTED]> wrote: Thanks for your help. I've upgraded to 2.5 version, but now I have ano

Re: scheme function doesn't work anymore

Ah, it works now in 2.5.31. Thanks! On Tue, 14 Jun 2005 20:26:12 +0200, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: VSD wrote: Thanks for the answer. Indeed \mychords are within a \score block. The exact input file is: %% ChordOffset = #(def-music-function (parser lo

Re: scheme function doesn't work anymore

issing? Vincent (Confused) On Tue, 14 Jun 2005 17:30:41 +0200, Mats Bengtsson <[EMAIL PROTECTED]> wrote: I hope you include \mychords within a \score{...} block, otherwise you won't get any output. I tried your lines of code extended with \score{\mychords} and certainly get some o

scheme function doesn't work anymore

I was successfully using the following simple scheme function in all the 2.5.x series until 2.5.29-1 (all win native under WXP): ChordOffset = #(def-music-function (parser location offset) (pair?) #{ \override ChordNames.ChordName #'extra-offset = #$offset #} ) mychords = \chor

printfirstpagenumber has no effect

setting the value of printfirstpagenumber to ##t in the \paper section (nor in \layout) doesn't print the first page number unless I set firstpagenumber to be > 1 curiously, if I set firstpagenumber = 0, the first page has number 0 as expected, but then page "1" doesn't print thes page numb

Re: missing text in pdf :header meter = "text"

I recently reported that bug in this thread: http://lists.gnu.org/archive/html/bug-lilypond/2005-06/msg00044.html but I got no reply. You can easlily fix it yourself by editing titling-init.ly and adding something like \fromproperty #'header:meter somewhere inside the definition of bookTit

Re: Default title layout

btw the meter property in titling-init.ly is missing, it's not shown in headers. Note that the image corresponding to the example given in the section "creating titles" in the manual does not contain the meter property, although it's set in the example. Again, it's easy to fix, but missin

TabNoteHead position

Hi, I think that the position of the TabNoteHeads in tablatures is incorrect. By default, lily places the fret numbers are placed *above* the strings, but that's confusing, and usually they are placed *over* the strings. The examples in the manual itself at "Tablatures basic" and "Non-guita

Default title layout

Hi, in titling-init.ly (2.5.27 win native), bookTitleMarkup is defined as: bookTitleMarkup = \markup { \override #'(baseline-skip . 3) \column { \fill-line { \fromproperty #'header:dedication } \column { \override #'(baseline-skip . 3.5) (...) shouldn't the 2n

error in slash chords?

Hi, I've found that when entering perfect major chords with a bass note added explicitly (e.g: " c:/b+ "), lilypond produces the following error: programming error: Improbable offset for stencil: -1.#INF00 staff space If the chord has any modifier (c:m/b+ etc) there's no error. It don't app