Re: MIDI interface (feature request)
On 20 Mar 2009, at 02:34, Kees van den Doel wrote: One idea is to generate some other format, perhaps Scala seq files, which in turn can produce MIDI files. When there is microtonal information present, Scala can use special algorithms to assign MIDI channels, and also keep track of different synth capabilities. I'm not sure how that format stands up with respect to LilyPond information in general, but such a format could be developed in a way directly that MIDI output cannot. That would be very useful for other reasons too. Currently I can't tune my lilypond generated Persian midi in scala because the pitchbends generated from lilypond for the microtones are ignored when producing a scale .seq file. I have discussed it with Manual Op de Coul, and he think it is a good idea, but the problem is finding someone that can do the hook within LilyPond. The format is here http://www.huygens-fokker.org/scala/seq_format.html You might check if it is rich enough for what you are doing. Hans ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI interface (feature request)
Hans Aberg wrote: On 20 Mar 2009, at 02:34, Kees van den Doel wrote: One idea is to generate some other format, perhaps Scala seq files, which in turn can produce MIDI files. When there is microtonal information present, Scala can use special algorithms to assign MIDI channels, and also keep track of different synth capabilities. I'm not sure how that format stands up with respect to LilyPond information in general, but such a format could be developed in a way directly that MIDI output cannot. That would be very useful for other reasons too. Currently I can't tune my lilypond generated Persian midi in scala because the pitchbends generated from lilypond for the microtones are ignored when producing a scale .seq file. I have discussed it with Manual Op de Coul, and he think it is a good idea, but the problem is finding someone that can do the hook within LilyPond. The format is here http://www.huygens-fokker.org/scala/seq_format.html One problem in LilyPond is that the part of the code currently handling the MIDI output, is much less flexible than the code handling ordinary printed output. On the other hand, this code is in general much less involved than the code for the printed output, so in the end it's perhaps not more difficult of time-consuming than to add another output format for the printed output, at least if you don't have the ambition to add the same flexibility for the sound output backend as for the printed output backend. /Mats ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI interface (feature request)
On 20 Mar 2009, at 09:59, Mats Bengtsson wrote: in scala because the pitchbends generated from lilypond for the microtones are ignored when producing a scale .seq file. I have discussed it with Manual Op de Coul, and he think it is a good idea, but the problem is finding someone that can do the hook within LilyPond. The format is here http://www.huygens-fokker.org/scala/seq_format.html One problem in LilyPond is that the part of the code currently handling the MIDI output, is much less flexible than the code handling ordinary printed output. On the other hand, this code is in general much less involved than the code for the printed output, so in the end it's perhaps not more difficult of time-consuming than to add another output format for the printed output, at least if you don't have the ambition to add the same flexibility for the sound output backend as for the printed output backend. The idea is to make an interface so that those interested in programming the printing program need not engage with those interested in generating sound output programs, and vice versa. There are also programs like http://people.bath.ac.uk/masjpf/CDP/csinfopg.htm http://chuck.cs.princeton.edu/ one might use for generating sound output. So the format might be more general than Scala seq files. A user might want to add interpretations directly into the score or tweak the sequence file that LilyPond writes. Hans ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI interface (feature request)
- Original Message - From: Hans Aberg hab...@math.su.se Date: Wednesday, March 18, 2009 4:42 am Subject: Re: MIDI interface (feature request) To: Kees van den Doel kvand...@shaw.ca Cc: bug-lilypond@gnu.org On 18 Mar 2009, at 02:27, Kees van den Doel wrote: Not sure I understand, I need a vibrato, not a trill. Well, how do you want realize your vibrato, MIDI-wise? Set MIDI controller number 1 to a non-zero value on the channel. In abc I can write: %%MIDI controller 1 127 Kees ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI interface (feature request)
On 18 Mar 2009, at 19:26, Kees van den Doel wrote: Well, how do you want realize your vibrato, MIDI-wise? Set MIDI controller number 1 to a non-zero value on the channel. Aren't you using a synth with a vibrato channel then? Of course. Not sure what you are thinking of with all these questions. Point is that if I could generate MIDI messages in the score I could do what I want. Kees ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI interface (feature request)
On 19 Mar 2009, at 09:57, Mats Bengtsson wrote: One technical problem of such a general feature, is that some MIDI commands that are intended to apply to all MIDI tracks should be inserted in track 0, whereas other MIDI commands (that contain a channel number) should be inserted in the same track as the corresponding music. Another complication (at least conceptually) is the different concepts used in LilyPond and MIDI and how they are mapped to each other. By default, MIDI channels correspond to Staff contexts in LilyPond, but this can be changed by redefining the context definitions in LilyPond. A final complication is the lack of standardization of MIDI. See http://lists.gnu.org/archive/html/bug-lilypond/2003- 10/msg00069.html for some related information. One idea is to generate some other format, perhaps Scala seq files, which in turn can produce MIDI files. When there is microtonal information present, Scala can use special algorithms to assign MIDI channels, and also keep track of different synth capabilities. I'm not sure how that format stands up with respect to LilyPond information in general, but such a format could be developed in a way directly that MIDI output cannot. That would be very useful for other reasons too. Currently I can't tune my lilypond generated Persian midi in scala because the pitchbends generated from lilypond for the microtones are ignored when producing a scale .seq file. Kees ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI interface (feature request)
On 19 Mar 2009, at 00:41, Kees van den Doel wrote: Aren't you using a synth with a vibrato channel then? Of course. Not sure what you are thinking of with all these questions. Point is that if I could generate MIDI messages in the score I could do what I want. Yes, I see that now. I was thinking of entering it in a musical way. But it is good if one can have all sort of MIDI output tweaks - time bends, too, for example, otherwise people may try to handle by writing strange meters. Hans ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI interface (feature request)
One technical problem of such a general feature, is that some MIDI commands that are intended to apply to all MIDI tracks should be inserted in track 0, whereas other MIDI commands (that contain a channel number) should be inserted in the same track as the corresponding music. Another complication (at least conceptually) is the different concepts used in LilyPond and MIDI and how they are mapped to each other. By default, MIDI channels correspond to Staff contexts in LilyPond, but this can be changed by redefining the context definitions in LilyPond. A final complication is the lack of standardization of MIDI. See http://lists.gnu.org/archive/html/bug-lilypond/2003-10/msg00069.html for some related information. /Mats Hans Aberg wrote: On 19 Mar 2009, at 00:41, Kees van den Doel wrote: Aren't you using a synth with a vibrato channel then? Of course. Not sure what you are thinking of with all these questions. Point is that if I could generate MIDI messages in the score I could do what I want. Yes, I see that now. I was thinking of entering it in a musical way. But it is good if one can have all sort of MIDI output tweaks - time bends, too, for example, otherwise people may try to handle by writing strange meters. Hans ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- = Mats Bengtsson Signal Processing School of Electrical Engineering Royal Institute of Technology (KTH) SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: mats.bengts...@ee.kth.se WWW: http://www.s3.kth.se/~mabe = ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI interface (feature request)
On 19 Mar 2009, at 09:57, Mats Bengtsson wrote: One technical problem of such a general feature, is that some MIDI commands that are intended to apply to all MIDI tracks should be inserted in track 0, whereas other MIDI commands (that contain a channel number) should be inserted in the same track as the corresponding music. Another complication (at least conceptually) is the different concepts used in LilyPond and MIDI and how they are mapped to each other. By default, MIDI channels correspond to Staff contexts in LilyPond, but this can be changed by redefining the context definitions in LilyPond. A final complication is the lack of standardization of MIDI. See http://lists.gnu.org/archive/html/bug-lilypond/2003-10/msg00069.html for some related information. One idea is to generate some other format, perhaps Scala seq files, which in turn can produce MIDI files. When there is microtonal information present, Scala can use special algorithms to assign MIDI channels, and also keep track of different synth capabilities. I'm not sure how that format stands up with respect to LilyPond information in general, but such a format could be developed in a way directly that MIDI output cannot. Hans ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI interface (feature request)
On 18 Mar 2009, at 02:27, Kees van den Doel wrote: Not sure I understand, I need a vibrato, not a trill. Well, how do you want realize your vibrato, MIDI-wise? Hans ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI interface (feature request)
On 18 Mar 2009, at 19:26, Kees van den Doel wrote: Well, how do you want realize your vibrato, MIDI-wise? Set MIDI controller number 1 to a non-zero value on the channel. Aren't you using a synth with a vibrato channel then? Hans ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: MIDI interface (feature request)
On 17 Mar 2009, at 02:32, Kees van den Doel wrote: I would like to see a general method to insert MIDI command in the score. My specific need is to add vibrato to certain notes by setting the appropriate controller. My application is Persian music where vibrato is a must on certain notes. First you can write something like %mytrill = layout-definition mytrill = midi-definition and then comment the one you don't use in two different compiles for PDF and MIDI. The second step might be to combine these two definitions into one, which can recognize the two \layout and \midi contexts. I don't know if that is possible, but perhaps somebody here could tell. Hans ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
