Keith OHara schreef op vr 11-03-2011 om 11:15 [-0800]: > On Fri, 11 Mar 2011 10:12:59 -0800, Jan Nieuwenhuizen <jann...@gnu.org> wrote:
> I know nothing about this, but some other people with similar goals are > http://www.classicalmidiconnection.com/2port.htm Right. Using many ports, (if fact, one port per track), it would be trivial to encode voices and map them to tracks. In fact, the current midi2ly implementation would do just that. It seems that this port extension is not implemented, generally. > To preserve more organizational information, use more Tracks. > There can be up to 65535 Tracks in a midi file. The correspondence could be: > single Port > Staff_performer <-> Channel > Voice <-> Track > > midi2ly puts each track on its own staff by default (which is probably > safest, and not a problem because re-arranging the variables in staves > is one of the easier things to do in LilyPond). To associate several > Tracks with one staff, you could write a staff-association into Track > Name ( event 0xFF03 ). I think this is the best solution, although I think it's a custom solution and thus clumsy? I'll be looking into this. I think I'll be doing No Port setting (ie, single port) midiInstrument <-> Channel (possibly with option: Staff_performer <-> Channel) Voice <-> Track Also, I'll be adding a midi test suite, mainly for midi2ly but this will test midi output too. Jan. -- Jan Nieuwenhuizen <jann...@gnu.org> | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
