Re: review new info on file layout

On 4-Feb-06, at 1:59 AM, Mats Bengtsson wrote: Quoting Erik Sandberg <[EMAIL PROTECTED]>: Then I'd propose this instead: \new Lyrics { \lyricsto mytune { ... } } because it feels relevant to me to consequently create contexts as top-level as possible. (hm.. the outer {} in my example are stil

Re: midi output bug?

Hi, On Tue, 7 Feb 2006, c.m.bryan wrote: > I did a crazy-long time sig because I couldn't remember the cadenza > command, and it was just a quick sketch. Maybe that's the problem... Exactly. A midi file can represent only up to 255 beats per measure. Ciao, Dscho __

Re: midi output bug?

> P.S.: I fixed the two instances of the time signature in your midi file, > and since it is so small attached it. That did it!! No more 1000/4 for me ;) Sorry for not suspecting that before, but I don't know a lot about midi files, and I wasn't aware that they contained meter information. Than

Re: midi output bug?

Hi, On Mon, 6 Feb 2006, c.m.bryan wrote: > The strangest part is that I've had success with this procedure > before, so something has changed, maybe in a lilypond upgrade? Any > help would be appreciated! Me again. Something jumped into my eye: the number 0x3e8. It is exactly 1000 in decimal.

Re: midi output bug?

> 4d 54 72 6b // = MTrk > 00 00 00 40 // = chunk length (64) > 00 0f f5 80 43 e8 02 12 08 // = probably fscked up time signature > > A midi time signature would look like > > 00 ff 58 04 04 02 18 08 > Well, if you suspect that it might be an old version, how about telling us > which one you use?

Re: midi output bug?

Hi, On Mon, 6 Feb 2006, c.m.bryan wrote: > "It turns out Scala is right, your midi file is wrong. > There's an unexpected running status inside. So you may > have to report a bug for Lilypond." It appears that your midi has this as start of the second track: 4d 54 72 6b // = MTrk 00 00 00 40 //

midi output bug?

Hello everyone, I've been trying to use lilypond to render midi files which I can then retune with a program called scala (http://www.xs4all.nl/~huygensf/scala/). The midi file which lilypond gives me seems ok, and is playable by timidity, but scala chokes on it and gives me an error. I talking

Re: 2.7.30-1, 2.7.31-2 Lilypond script error?

Paul Scott wrote: Han-Wen Nienhuys wrote: Paul Scott wrote: With GUB (i386) versions 2.7.30-1 and 2.7.31-2 invoking lilypond (/usr/local/bin/lilypond) gives: /usr/local/bin/lilypond: line 3: 8611 Illegal instruction "/usr/local/lilypond/usr/bin/lilypond" "$@" With the CVS version /u

Re: 2.7.30-1, 2.7.31-2 Lilypond script error?

Han-Wen Nienhuys wrote: Paul Scott wrote: With GUB (i386) versions 2.7.30-1 and 2.7.31-2 invoking lilypond (/usr/local/bin/lilypond) gives: /usr/local/bin/lilypond: line 3: 8611 Illegal instruction "/usr/local/lilypond/usr/bin/lilypond" "$@" With the CVS version /usr/local/bin/lilypo

Re: OS X linker errors

Quoth Jan Nieuwenhuizen: > Don Blaheta writes: > > > 5840 T FT_Load_Sfnt_Table > > > 59fc T _FT_Load_Sfnt_Table > > Your version has a leading underscore... So does the version the linker claims to be looking for. :P -- -=-Don [EMAIL PROTECTED]-=- "And her face

Re: lily-bugs/bugs GNUmakefile c-clef-clef.ly crash...

Erik Sandberg wrote: -%Thomas Scharkowski +%fixed: not a bug; the 8 has no dimension to make lyrics come closer to the staff. see define-grobs.scm (hwn) +%Thomas Scharkowsk This _is_ still a bug: If lily's architecture isn't currently powerful enough to avoid all collisions between clefs whi

Re: lily-bugs/bugs GNUmakefile c-clef-clef.ly crash...

On Sunday 05 February 2006 01.45, Han-Wen Nienhuys wrote: > CVSROOT: /cvsroot/lilypond > Module name: lily-bugs > Branch: > Changes by: Han-Wen Nienhuys <[EMAIL PROTECTED]>06/02/05 00:45:52 > --- lily-bugs/bugs/c-clef-clef.ly:1.3 Mon Oct 3 08:48:00 2005 > +++ lily-bugs/bugs/c-clef-clef

Re: music macros?

On Saturday 04 February 2006 14.43, Han-Wen Nienhuys wrote: > As #( .. ) is handled in the lexer, not the parser, I think they will > have to be done directly. > > BTW, looking at the parser, I see another option for deconstructing it > further. It might be possible to add lexer-mode switches to th

Re: 2.7.30-1, 2.7.31-2 Lilypond script error?

Paul Scott wrote: With GUB (i386) versions 2.7.30-1 and 2.7.31-2 invoking lilypond (/usr/local/bin/lilypond) gives: /usr/local/bin/lilypond: line 3: 8611 Illegal instruction "/usr/local/lilypond/usr/bin/lilypond" "$@" With the CVS version /usr/local/bin/lilypond is a binary file. With

Re: circling marks

HiYou can use this patch (touching scm/translation-functions.scm) in order to get format-mark-circle functions.Perhaps this patch should be applied in order to make it easier to use this kind of rehearsal marks? Regards,  Erlend AaslandOn 1/29/06, Paul Scott <[EMAIL PROTECTED]> wrote: In 2.7.29 I c

Re: showing page numbers during output creation

Werner LEMBERG writes: > I would like to see, say, > > Layout output to `foo.ps' [1][2][3] > > similar to TeX. Is this possible? Not without writing some code. IIRC, lilypond now prints the measures where the page breaks fall. That tells you more than just the number of pages alone. Jan. -

Re: OS X linker errors

Don Blaheta writes: > freetype *6*? I've got 2.1.9 That's ok. 6 is the major interface number of the dynamic library, usually the package is named after that. > > 5840 T FT_Load_Sfnt_Table > 59fc T _FT_Load_Sfnt_Table Your version has a leading underscore... > My linker-fu is not st

collision with and alignment of rehearsal marks

[lilypond 2.7.31] Some problems with rehearsal marks. . Now that I can say \set Score.rehearsalMarkAlignSymbol = #'clef I wonder what I must do to globally avoid collisions between, say, treble clefs and boxed rehearsal marks. Using the `padding' property isn't a good solution, obvio

showing page numbers during output creation

I would like to see, say, Layout output to `foo.ps' [1][2][3] similar to TeX. Is this possible? Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel