Re: Unintelligible MIDI output

2003-10-07 Thread David Raleigh Arnold
On Monday 06 October 2003 08:11 am, Mats Bengtsson wrote: > By default, LilyPond uses a new MIDI channel for each stave. > If you want to squeeze in more parts in the available 16 > MIDI channels, I guess it's easiest to define a separate > \score{} context for the MIDI version of your music. > As

Re: Unintelligible MIDI output

2003-10-07 Thread Marcelo Gomes de Queiroz
Thanks, Mats, for your answer. I wonder if it wouldn't be very nice, from the user-interface point-of-view, if Lilypond generated a warning, or even an error message, every time a wrong MIDI output was created, and let the user know about his/her mistake. This is an unnoticed erroneous outpu

Re: Unintelligible MIDI output

2003-10-06 Thread Mats Bengtsson
By default, LilyPond uses a new MIDI channel for each stave. If you want to squeeze in more parts in the available 16 MIDI channels, I guess it's easiest to define a separate \score{} context for the MIDI version of your music. As long as you have used identifiers for all the different parts, it's

Unintelligible MIDI output

2003-10-03 Thread Marcelo Gomes de Queiroz
Hello! I have been struggling the past few weeks with an example that produced a very odd MIDI output. Unfortunately it is an awfully large orchestral example, and I can't reproduce it with a small file. The main file is orchestra.ly. The music lasts for about 4 minutes and 40 seconds. The midi