n00b: how to route audio to midi-fx in m4l

I wish to route audio from a chosen (list) audio track to a m4l midi-effect on a midi track.

I am having a hard time figuring out the live.* objects.

So I would be very glad for any help!

Sincerely - Jonas Barsten Johnsen

Sending audio in MFL requires send~ / receive~ or plugsend~ / plugreceive~ object pairs. You can't pick up just any audio signal. So using MFL for this task requires some forethought.

A spare Live audio track can perhaps be used to choose an audio source. In Live you have input selectors to select a track and 3 points in the device chain as audio sources. These choices are part of Live API, so they can be altered on the fly.

If you really need the audio signal in a MIDI-effect you still have to transport it using a send~ / receive~ pair. Expect a variable extra latency of about 12 ms, with no automatic compensation by Live.

Thanks Xanadu, really appreciate it!

Though, I think it would be easier if I rather converted it into an audio-fx, and than find a way to send the MIDI-signals to a MIDI-track.

As far as I have understood, there is no way of routing m4l midi to external devices, such as the IAC-driver?

Is it not possible to program this in java?

-jbj

Hi jbj,

Well, I'm a bit confused about what you want to accomplish.

If you want to do something with a known audio track, an audio-fx is the way to go. If you want a drop down list of available audio signals things get a lot more complicated.

In your reaction to my previous message you mention sending MIDI to an output. Do you want to convert the audio signal to MIDI in some way?

Please make clear what you are up to.

The IAC-driver is on Apple and I'm on Windows XP, but I think there are three equal ways to output MIDI to the outside world for both platforms:

1. Create a MIDI track in Live without a MIDI to audio converter, so don't create a synth plugin. Then choose a MIDI output for the track. You can use a plug / receive pair to transport midi signals to this track in MFL.

2. Get a Max/MSP upgrade licence at the website of C'74. This will allow you to output MIDI using Max.

3. Program a midiout external object. Distributing such an object will spoil the market for C'74, which will eventually shoot ourselves in the foot.

I'm in favor of the first option for using once in a while and option two for power users.

Hello again, thanks for responding!

I have both max/msp/jitter and m4l, but in this case, I´d rather use m4l.

I am making a simple audio-to-midi-device which sends a chosen MIDI-signal when the audio-gain reaches a chosen level.

I reached doing this by placing one "send" instance on an audio track, and one "return" instance on a MIDI-track, communicating trough the send/receive objects.

But I would really like to just have either one audio-device which sends MIDI to an external loopback or to a chosen MIDI-track in Live (umenu), or one MIDI-device with audio from a chosen audio track (umenu).

This is my patch so far, I welcome any comments, as you might see in the send (audio)-device, I am trying to convert db into 0-127 and than send it to it´s corresponding receive (midi)-device, but I have not figured completely how to do that ... well, that´s not the main issue anyways.

send (audio):

reveive (midi):

What kind of "midi signal" do you want to trigger?
If it's for synths, remember that you can use vst~ and audiounit~ objects, directly in your audio device; so you just need one track, one device.

Hi jbj,

Thanks for your demo-devices. Together they achieve what you want to do. It's clear now you are not a noob!

As far as I know your devices are state of the art. A midi-track has no input for audio and once a Live track is using audio it can't output MIDI.

I must agree: it's a bit clumsy. But it works!

I love MFL because it is capable of this kind of 'plumbing' in Live.

In EnergyXT you always have MIDI and (multiple) audio connections in parallel, for input as well as output. Of course there is no integration with Max.

I think the current design of Live without MFL is clever and flexible. Ableton and Cycling '74 are living 4000 km apart and have done a great job of integrating two very different software designs. When using MFL, Live tracks are lacking some flexibility. We must ask Ableton to enhance their tracks to enhance MIDI and audio capabilities of tracks.

Crampe: thanks for your advices, really appreciate them!

Xanadu: thanks for your kind words and for setting things in perspective.

What an excellent community!

Have a nice day.

i am having a similar problem regarding routing midi within Live. and am wondering how to open the earlier patches in Live ??

I have tried saving them as .maxpat then opening in Live but M4L doesnt do anything.

in regard to my own endeavours, i am attempting to create a MIDI LFO (sending controller information) effect which to route to any desirable knob/parameter within Live. My earlier attempts (using SYnthedit) really only worked well using an external host. So I am once again attempting to build an internal device to Live.

i am unable to create (within M4L) a purely midi instrument (or track).. (well that is how it seems as it refuses to coexist with an instrument.)

thanks