On Tue, Feb 06, 2018 at 09:38:51PM +0100, Jeanette C. wrote: > Feb 6 2018, Alexandre Ratchov has written: > ... > > Sorry, I was mistaken. There were patches to make this kind of > > mapping, but it was not commited because it broke other parts of > > midish. > Gravely? Otherwise, it would make a few things possible and easier. > Especially old synth like to talk a lot of SysEx. :) > ... It's all about allowing filters to convert any event to an event of different type. Example, pitch bend could be mapped to a controller, which is handy. But this introduces two problems: - certain event representation must change, which may break existing scripts - this brings few weired situations: exemple, how to convert pitch bend events to note events maintaining one-to-one correspondence? > > evpat mysysex {0xf0 0x3e 0x0e 0x00 0x1d v0 0xf7} > > fmap {ctl input_chan 72} {mysysex output_dev} > So the controller's value will get passed to v0, it's sort of a > positional argument, like shell variables $1, $2,... Thanks for the > example. Yes, v0 and v1 are the two parameters; this makes sysex messages look like other midi events, allowing sysex to be stored in tracks and used to control synths in real-time.Received on Wed, 7 Feb 2018 11:05:02 +0100
This archive was generated by hypermail 2.1.8 : Thu Feb 08 2018 - 01:48:07 CET