Re: review new info on file layout

[Graham Percival]

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 still confusing 
though,

since lyricsto never can be part of anything sequential)


I agree with Erik -- now the highest view of the music expression is
{
  \new Staff { vocal }
  \new Lyrics \lyricsto vocalstaff { \lyrics }
  \new PianoStaff
}

correct?  And I should change the vocal templates to match this?


The intuitive idea behind my proposal is that the second argument
of the \lyricsto construct is the Lyrics context, whereas with your
proposal it's only the lyrics expression. Of course, there might be
situations where you have several \lyricsto within the same Lyrics
context, so then your proposal makes more sense. However, in such
situations, I would normally use something like:
\lyricsto partI \context Lyrics = lyr {...}
\lyricsto partII \context Lyrics = lyr {...}
\lyricsto partIII \context Lyrics = lyr {...}


Recall that this is an example for newbies (unless you two have moved 
on to talking about general lily syntax by now :).  If somebody wants 
to do complicated stuff, they can read chapter 7 of the manual, instead 
of just chapters 3 and 4.  :)



I think the shorthand without score is highly relevant:
- Lots of music is just short snippets. See e.g. regression tests, 
LSR and bug archive.


That's only true for the small group of people like you and me who
spend more time answering mailing list questions and handling bug
reports than on typesetting any real music. It's clearly a 
suboptimization

to adapt the syntax too much to such unnormal use of the program.


Yes, but it also applies to the manual.  We already explain that 
examples from the manual need {} or even \relative c' { }   to compile.


I agree that we shouldn't force people to remember lots of extra 
syntax that the program itself can figure out. However, I've seen lots 
of confusion on the mailing list because \score

is now optional.


Hopefully this confusion will be lessened with the new chapter 4.  I 
may revisit the tutorial with this in mind, too.


- Graham



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: midi output bug?

[Johannes Schindelin]

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



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: midi output bug?

[c.m.bryan]

> 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.

Thanks a bunch!

-chris


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: midi output bug?

[Johannes Schindelin]

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.

Could it be that you have something as strange as

\time 4/1000

in your .ly file?

Ciao,
Dscho

P.S.: I fixed the two instances of the time signature in your midi file, 
and since it is so small attached it.

P.P.S.: The culprit seems to be the int2hex method of String_convert, 
which converts a large number to more digits than length_i (and in this 
case even worse: to an odd number of digits).

P.P.P.S.: I don't see how Midi_time_signature::to_string() could print 
the literal "3e8" if den == 1000, since it calls intlog2, which would try 
to divide as often as possible by 2, and return the number of divisions 
(i.e. if den == 1000 it would return 3, since 1000/2/2/2 = 125).


score-repaired.midi
Description: MIDI audio
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: midi output bug?

[c.m.bryan]

> 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? And if it is not too much hassle, could you provide a
> sample .ly file which produces such a midi?

My apologies for not giving that information!

I'm using version 2.4.5 on fedora core 3 linux, because it's the
latest binary provided by Planet CCRMA, and I haven't had the time to
wrestle with the source.

And the .ly is below.  The \include statements are note lists with no
extra commands.  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...

Thanks for the help.

-

\version "2.4.2"

#(set-global-staff-size 16)

flat = \markup { \raise #0.4 \smaller \musicglyph #"accidentals--2" }
sharp = \markup { \raise #0.6 \smaller \musicglyph #"accidentals-2" }
textcodaysym = \markup { \hspace #1 \raise #1.1 \musicglyph #"scripts-coda"}

StaffA = \relative c' {
\time 1000/4
\include "StaffA_retuned.ly"
}
StaffB = \relative c' {
\time 1000/4
\include "StaffB_retuned.ly"
}

\score {
\simultaneous {
\set Score.skipBars = ##t
\set Score.melismaBusyProperties = #'()
\context Staff="StaffA" \StaffA
\context Staff="StaffB" \StaffB
}
\layout {
linewidth = 170.000 \mm
textheight = 250.000 \mm
}
\midi { \tempo 4=55 }
}


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: midi output bug?

[Johannes Schindelin]

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 // = 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

only that it seams somehow a 0 nibble crept in, shifting some numbers, and 
somehow another nibble was shifted in.

I never had such problems.

> 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!

Well, if you suspect that it might be an old version, how about telling us 
which one you use? And if it is not too much hassle, could you provide a 
sample .ly file which produces such a midi?

Ciao,
Dscho



___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

midi output bug?

[c.m.bryan]

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
with a scala developer, he seemed to have pinpointed a problem with
the midi file output from scala.  He said:

"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."

Do you know what that "unexpected running status" could be? You can
check out the midi file here:

cmbryan.com/score_midi.midi

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!

Thanks in advance,

-chris


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Han-Wen Nienhuys]

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 /usr/local/bin/lilypond is a binary file.  With 
the GUB versions I have D/L'd it is a script which at least has a 
double / which seems wrong but even when I correct that I get the 
same error.


This is all on two different machines both running Debian sid.




Hmmm... what does

  ldd /usr/local/lilypond/usr/bin/lilypond say ?



Result is attached.



workaround: add

export LD_LIBRARY_PATH=/usr/local/lilypond/usr/lib

to the wrapper script.

--
 Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Paul Scott]

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/lilypond is a binary file.  With 
the GUB versions I have D/L'd it is a script which at least has a 
double / which seems wrong but even when I correct that I get the 
same error.


This is all on two different machines both running Debian sid.



Hmmm... what does

  ldd /usr/local/lilypond/usr/bin/lilypond say ?


Result is attached.

Paul







linux-gate.so.1 =>  (0xe000)
libdl.so.2 => /lib/tls/libdl.so.2 (0xb7f4a000)
libguile.so.16 => not found
libgmp.so.3 => /usr/lib/libgmp.so.3 (0xb7f19000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xb7ef4000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xb7ebd000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb7e83000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb7e7e000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb7df9000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb7dca000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb7d5d000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7d49000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7c6c000)
libm.so.6 => /lib/tls/libm.so.6 (0xb7c45000)
libc.so.6 => /lib/tls/libc.so.6 (0xb7b0e000)
/lib/ld-linux.so.2 (0xb7f64000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb7aee000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7ae3000)
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: OS X linker errors

[Don Blaheta]

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 is like a potato only in that it's not anything like a
potato."--Kevin Price


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Han-Wen Nienhuys]

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 while still typesetting lyrics nicely, 
then it is at least a low-priority far-future bug.


Maybe I should just move the bug to the future branch?


yes.

--
 Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Erik Sandberg]

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.ly Sun Feb  5 00:45:52 2006
> @@ -1,5 +1,5 @@
> -%
> -%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 while still typesetting lyrics nicely, 
then it is at least a low-priority far-future bug.

Maybe I should just move the bug to the future branch?

-- 
Erik


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: music macros?

[Erik Sandberg]

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 the
> annotation of a music function.  Then we could also soft-code the
> definition of \lyrics, \lyricsto, \figures, etc.

I realise that this is a very cool idea. Perhaps it can be used to soft-code 
pitch functions (such as \transpose) as well?

Could we also make Lily_lexer::lookup_identifier_symbol softcodable, in a 
similar way? This would solve lots of problems, and add support for local 
variables in a natural way (it would probably be easy to write a \let macro, 
for instance).
It would also make it cleaner to create macros (\for, \lamda, etc).

Hm... It might even be possible to use identifier lookup overrides to 
soft-code the entire macro concept: \relative could override the identifier 
lookup to a function which maps any function to a wrapper, that delays the 
function application until the end of the \relative call.

This way, there would be no real point in postponing macro or function calls 
to after parsing; functions calls can simply be delayed whenever anyone wants 
to delay them.

(we may still want to add explicit support for macros in the parser, in case 
the softcoded \relative hack becomes too hairy)

-- 
Erik


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[Han-Wen Nienhuys]

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 the 
GUB versions I have D/L'd it is a script which at least has a double / 
which seems wrong but even when I correct that I get the same error.


This is all on two different machines both running Debian sid.


Hmmm... what does

  ldd /usr/local/lilypond/usr/bin/lilypond say ?


--
 Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: circling marks

[Erlend Aasland]

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 can easily do:\mark \markup{ \circle "65" }but I would like to use something like:\set Score.markFormatter = #format-mark-circle-numbersThe attached file shows my current attempt.  I want:
\mark "65"to work not just \mark \defaultCan someone give me some hints to finish this?TIA,Paul Scott___lilypond-devel mailing list
lilypond-devel@gnu.orghttp://lists.gnu.org/mailman/listinfo/lilypond-devel


markcircle.patch
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: showing page numbers during output creation

[Jan Nieuwenhuizen]

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.

-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: OS X linker errors

[Jan Nieuwenhuizen]

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 strong, so I'm not sure exactly what T and U stand
> for, but it does look like the symbol is there, at least.

T=text, U=undefined :-)

Jan.

-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org


___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

collision with and alignment of rehearsal marks

[Werner LEMBERG]

[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, obviously...

  IMHO it would be best if rehearsal marks were included in the
  collision resolution algorithm.  Can a user force LilyPond to do
  that?

. Shouldn't the argument of rehearsalMarkAlignSymbol be rather a list
  of symbols?

\set Score.rehearsalMarkAlignSymbol = #'(bar
 key-signature
 (clef . 3))

  If there is a bar, align with the bar.  If there is a key signature,
  align with the key signature.  If there neither a bar nor a key
  signature but a clef, align with the clef, using a horizontal offset
  of 3 units.  Otherwise, use the default location.

  This example is rather realistic -- if there is a repeat bar
  starting a line, the rehearsal number should be positioned on it and
  not on the clef.

. What actually is the default location of a rehearsal mark at the
  beginning of a staff and in the middle?  It's not documented.

. Currently, the location of rehearsal marks at the beginning of a
  line appears to be completely unpredictable if
  rehearsalMarkAlignSymbol isn't set (see attached files).  Looks like
  a bug...


Werner
\version "2.7.31"

#(set-default-paper-size "a4")
#(set-global-staff-size 18)

\paper {
  indent = 0.0\mm
}

klar = \relative c' {
  \set Score.markFormatter = #format-mark-box-numbers

  \mark \default \time 3/2 f8[ f' r f,] d[ f r f] g[ f a f] |
  r8 f'[ r f,] d[ f r f] g[ f a f] |
  r8 f[ g f] a[ f r f] g[ f a f] |
  g8[ a c a] g[ f d f] c[ d f g] |

  a8[ c d f] r g[ e d] f[ r a, c] |
  \time 2/2 d8[ f r g] e[ d f] r |
  \time 3/2 c8[ r d] r f[ g r g] e[ d f] r |
  \mark \default \time 11/8 f,8[ d r d] a[ d r d] b[ d g] |

  \mark \default d8[ f r d] a[ d r f] b,[ d g] |
  d8[ f r d] a[ d r f] b,[ d g] |
  \time 3/4 f8[ d a f' b, g'] |
  \time 11/8 f8[ d r f] a,[ d r f] b,[ d g] |

  \time 1/2 f8[ d g c,] |
  \mark \default \time 5/4 a'8[ d, r a'] c[ f, r c'] d[ g,] |
  a8[ d, r a'] c[ f, r c'] d[ g,] |
  \time 1/2 c8[ f, d' g,] |
  \time 5/4 a8[ d, r a'] c[ f, r c'] b[ g] |

  a8[ d, r a'] c[ f, r c'] b[ g] |
  \time 1/2
}


\score {
  \new Staff \relative c' {
\klar
  }
}

% EOF

___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

showing page numbers during output creation

[Werner LEMBERG]

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