I'm trying to use midi2ly on my MacBook Pro running OSX 10.6.5.
It seems that midi2ly was not compiled properly, as it's saying that
I have the wrong architecture. This despite the fact that I can run
Lilypad just fine (I have the right distro, I'm quite sure.)
Is there any way someone could
Updates:
Status: Fixed
Labels: fixed_2_13_44
Comment #4 on issue 1456 by Carl.D.Sorensen: timeSignatureSettings does not
apply to any context except for those containing a Timing_translator
http://code.google.com/p/lilypond/issues/detail?id=1456
Fix pushed in commit 878c21f14a
Comment #9 on issue 1268 by joeneeman: [PATCH] span-bar problem
http://code.google.com/p/lilypond/issues/detail?id=1268
I've tracked the problem down to Bar_line::compound_barline, which tries to
center the bar line around the center of the staff (see lines 119 and
below).
___
Comment #3 on issue 1460 by joeneeman: systems-per-page is broken
http://code.google.com/p/lilypond/issues/detail?id=1460
Ok, I think this is fixed now also.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug
Comment #2 on issue 1301 by bordage.bertrand: Strange collision of note and
clef
http://code.google.com/p/lilypond/issues/detail?id=1301
A simple workaround :
\new PianoStaff <<
\new Staff \relative c' { \times 2/3 {g'4 a2}}
\new Staff \relative c' {
\clef bass fis,,8[ cis' \bar "" \cle
Comment #6 on issue 855 by percival.music.ca: fix the command index
http://code.google.com/p/lilypond/issues/detail?id=855
"is now a bad time"? on a personal note, definitely, since I have a bad
fever, am in pain, and have less patience than normal. On a project-wide
note, I think that any
Comment #4 on issue 409 by bordage.bertrand: collision tie and time
signature
http://code.google.com/p/lilypond/issues/detail?id=409
Can we consider this as being a bug ?
Many famous editors assume this collision, especially in modern or
contemporary music.
For example, I just saw this in
