[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes |
Date: |
Tue, 24 Jul 2012 04:22:05 +0000 |
Updates:
Labels: Patch-new
Comment #1 on issue 2672 by address@hidden: Patch: Midi fixes
http://code.google.com/p/lilypond/issues/detail?id=2672
First patch of four. When other MIDI midi events (such as an instrument
change) occur simultaneously with note(s), they should be placed in the
MIDI file before the note-on events, otherwise there is no way to
(reliably) affect the first note in a score.
S = { \key c \major \repeat unfold 2 { e'4 } e'2 }
A = { \repeat unfold 2 { e'4 } e'2 }
T = { \repeat unfold 2 { gis4 } gis2 }
B = { \repeat unfold 2 { e4 } e2 }
\score {
\new Staff = "Staff" \with { midiInstrument = #"choir aahs" } <<
\S \A \T \B >>
\midi { }
}
Version 2.15.41 produces piano for the first chord on most players, one
player chooses randomly choir or piano. The intent was for all notes to be
choir.
http://codereview.appspot.com/6420058
- [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 2012/07/17
- Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes,
lilypond <=
- Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 2012/07/24
- Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 2012/07/24
- Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 2012/07/26
- Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 2012/07/30
- Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 2012/07/30
- Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 2012/07/30