Comment #5 on issue 1548 by jan.nieuwenhuizen: midi output should map
voices to channels
http://code.google.com/p/lilypond/issues/detail?id=1548
Having voices mapped to channels would be ideal from a musical pov and this
is what
the first implementation (8dc343b) did.
Now, it can be select
Comment #4 on issue 1548 by k-ohara5...@oco.net: midi output should map
voices to channels
http://code.google.com/p/lilypond/issues/detail?id=1548
and for the record,
The code as of version 2.13.55 does *not* assign each voice to its own midi
channel.
Instead, each uniquely-named voice is
Updates:
Status: Verified
Comment #3 on issue 1548 by percival.music.ca: midi output should map
voices to channels
http://code.google.com/p/lilypond/issues/detail?id=1548
I've added issue 1591 for the doc changes.
___
bug-lilypond mailing
Comment #2 on issue 1548 by k-ohara5...@oco.net: midi output should map
voices to channels
http://code.google.com/p/lilypond/issues/detail?id=1548
Do we want midi output to map voices to channels?
If anybody uses LilyPond to engrave orchestral scores, then there might be
more than 16 voice
Updates:
Status: Fixed
Comment #1 on issue 1548 by jan.nieuwenhuizen: midi output should map
voices to channels
http://code.google.com/p/lilypond/issues/detail?id=1548
Fixed in e5380f2 and 8dc343b
___
bug-lilypond mailing list
bug-lilypond
Status: Accepted
Owner: jan.nieuwenhuizen
Labels: Type-Defect
New issue 1548 by jan.nieuwenhuizen: midi output should map voices to
channels
http://code.google.com/p/lilypond/issues/detail?id=1548
lilypond merges all voices in one staff into one channel.
staffs are mapped to tracks and channe
