[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 2986 in lilypond: [DOC]midiChannelMapping (int
|
From: |
lilypond |
|
Subject: |
Re: [Lilypond-auto] Issue 2986 in lilypond: [DOC]midiChannelMapping (introduced in 2.14) not documented in NR |
|
Date: |
Mon, 22 Apr 2013 02:06:06 +0000 |
Comment #2 on issue 2986 by address@hidden: [DOC]midiChannelMapping
(introduced in 2.14) not documented in NR
http://code.google.com/p/lilypond/issues/detail?id=2986
I looked into this when the original patch (issue 1548) was pushed, and
came to the same conclusion as you. The Staff_performer is what turns the
midiInstrument into a MIDI_ProgramChange command, so you do need to have a
Staff_performer for each voice. The author of the patch for issue 1548
didn't know about the engraver/performer system.
In a narrow sense, midiChannelMapping does what the "Changes" entry says;
the events in the resulting midi file do mark the voices as being on
separate channels.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings