Apologies if I was unclear, but see below for the patch. For the most part, it's taken from Jean-Francois' freeze patch. Sound from the adc~ is frozen and then "played" through midi input and gizmo. There's a facility to cross fade between two jitter matrices. It basically works in Max5, but it's quite flakey in the live port. Rather than using the adc~ I am loading two jxf files created with the Max 5 version. No doubt the patching is clumsy, as I don't really know what I'm doing with the pfft and jitter stuff.
nice trick, but I'm not sure if it really works in practice. You'd need to load an instrument in front of the audio device which passes midi through from the track input to the audio device. But I believe that's not possible..
You need to access your midi controller from your patch.
You have to connect a [live.path control_surfaces N] (N is the "number" of your control surface -this have to be configured in LIve's preferences-) to a live.observer, and send a "property value" message to it. Have a look at the Live.Api_explorer.amxd patch from (I forgot his name) I've attached. It will help you going to your control surface, find the right path and gives you information about what you can expect to do with it.
I've also attached a little patcher I've made in order to have the Launchpad matrix buttons coordinates informations to be translated into single numbers... perfect for midi note number. I can insert this patcher into a m4L audio device and have midi control.
You won't be able to do something with if you don't have a launchpad, but maybe it could be handy to look at it (the top half part of it).
... And I just realise that this will probably work only if you have a "Live-supported" controller; i.e the controllers that can be selected in Live's preferences, midi sync tab, in the control surfaces part, not the "midi ports" one. But there's a little chance you controller's not, except if you bought it 20 years ago, or if you DIY it.
Thanks, all. That looks like an interesting work-around, Crampe, but I don't have a controller. I haven't had time to look at Stefan's suggestion, but I think that might be the nearest thing to what I need. I've read here that using send and receive between tracks can be a bit sluggish, so I'm not sure how it'll work out in practice.
What you have to do is, put into a miditrack a Midi device, basically a [midiin]->[send MyWonderfullAudioEffect] and in the Audio device you place instead of a [midiin] a [receive MyWonderfullAudioEffect]. Now you can use the Midi track to route Midi to your Audio effect.
If you want it more universal, have a look at my MidiSend device
Hello Stefan. That is a very useful m4l device, does something very similar to what I want. I would like to modify it to send note on/off as well, but for some reason I cannot edit it in Max - "unlock patch" button is disabled.
Surely I am missing something basic, but is there a reason I cannot edit this device?
The device is prepared to receive Midi via the MidiSend device. To send Midi doesn't make too much sense, I'd look at the two keyboards just for displaying purposes. Within MidiSend, you could add a keyboard as well...
Anyway, modify it at your will, it comes with a cc sa-nc-by license...
A smile or a donation in an unspecified amount to my moneybookers account will give you also a commercial license...;-)
(But you can only pass on your changes with the sa-nc-by license. (I still need some cash to finally buy a Live license, after the beta phase I had been cut off from further device development for the lack of monetary resources...))