It seems that there is no global send~ and receive~ from an instance to another (ex.: when I have 2 patches on the tracks).
Is there a way to take the audio of a track and use it in the patch of another track?
Thanks a lot!!
You are right, the send~ is not working within maxforlive.
Stefan Tiedje already suggested a live.out~ multi-channel-object (http://forum.ableton.com/viewtopic.php?f=35&t=129706) , which I think would be a perfect solution for spatialization or multi-channel audio. I could work exactly like the "audio to" function in Live itself and would overcome the limitations of the stereo-out of maxforlive.
send~/receive~ between devices didn’t make it into the first version of Max for Live, but we are definitely looking at a solution for future updates. We know this is something a lot of people want to do, and it is high on our list of features to implement.
If you don’t mind introducing a bunch of latency in the sending, you might be able to hack together a buffer~ based solution.
Thank you Andrew, that is good to know, that you are working on it !
Good thing to know!
[plugsend~] and [plugreceive~] seem to work here.
can you confirm we can use it without problem ?
-- Pasted Max Patch, click to expand. --Copy all of the following text. Then, in Max, select New From Clipboard.----------begin_max5_patcher---------- 393.3ocuTsraBCCD7bxWgkOVQQw4Qg1as+FUnJShAbky5nXGUnHx2dicRfzp DDPQ4xJ4YW6clYs18tN3kxsLEF8B5cjiydWGGKjAvo4rCNktMVPU1xv.6K4x OwSpSoYa0V3LQwZECRJQJIDzlFJRkEZASauqWC5JInU7uYFLh2zV3LpNdCGV +QNKVWSoP+prnmCLw4yLQx7odnEM2fmX6cEedjzsmbnskjNsDno1VheMmSEn 2jhDrI6AWWSXxEZ.qDxpVzuB8aPqgz6xX05vbIpFOAgWRg03iB3JbBqGD4cJ NnS3OVNQJSyxK62IHm2INR7djpenUdD6redsVCFPqj905MHlA9W+PIxap+Up QEeMPE2xX1OxH2YDSL3re3i5U492+o7.FS7tXAqDEF5MxlSf8GwSjyYNA+Wy w9nXAG96xQKsL3+1wTxh73VE1LdPmnVBSo4.UykPmZL6r5TzFdRBC5tnLkmj I4ftgCnE8N9tqThLpTJ3BnTznxHy1yKhRjajRUGN39icppqw -----------end_max5_patcher-----------
-- Pasted Max Patch, click to expand. --Copy all of the following text. Then, in Max, select New From Clipboard.----------begin_max5_patcher---------- 448.3ocyU97aBBCEG+L7WQSOyLTPTb2b2Vhm10EyREpXWJsDnr4lQ+aezBn3 F9yQLd4A7Z88998C0GqLMfyDKIYPvifWAFFqLMLzoTILpd1.FiWFvvY5sAiI RR5FnU4R77XQtjQj5EQUYKSI+JgTVY3bl.KgfoUqmfkAKn7n2RIAxxs32ums EXfN5aqhH2d1a+EzPcyEyd+A+F8lx21ZUt0llpf0YZEN4yhBVWNIYoVKvDVd TgvHzOHa.YBt6EZ1LZDGy1414BtLi9sdYjxZGDB88UF20UEGouG42ND7ZGBM 5HGGq6HbbJEy.OIXgvqfQAh3XBW9GH8R6Po1bySilU5I6dtVpPeUrHfZXnCP FUSBDLQ5oqPKPDY6nIGp7xvigQmqhifmkXFMnKw4j6Vb5Ze9zbvcBMGmGRE. o.Lo3+vcNYQcEYGTNlCom4oinQsS1g2XvdjIiEL7.S+cNw.Qq++nwpigdtG8 XXqvx47mMpKJjQ4+9KiZcoxuO5xD4oA0lsZ5LXmzBIYRJGKoBdi83u2dVPCC I7lGLiogIBJWVIAug87JLtm9SCt02Cl15K2tTmNWlNuQJBckJp3g0l+.JL2C p. -----------end_max5_patcher-----------
I double-checked. Here’s the current skinny:
Gosh, this is a huge wall. Nearly all i figured to do with m4l was send~/receive~ related.
What about send/receive ? Coll ?
send/receive and coll are more or less fine. Let me explain the more or less a bit… It’s likely that the devices are in different threads, so with send/receive you will get an unknown latency, with coll you might try to access some data in one device while you clear the same coll at the same time in another device, and there’s no protection against that.
I have two questions about send/receive:
a) Is it possible to estimate an upper limit of the latency?
b) Could it be that OSC messages provide better timing?
a) it shouldn’t be too much, but it’s unpredictable
So it means, for the time beeing that you cannot build a step sequencer which would send triggers to instruments that are on other tracks.
And you cannot build a big Max device which would have multiple outputs you could route to Live tracks.
And you may not rely on send/receive to make your Max devices talk together.
Are these things on the dev list for further release of m4l ?
One of the cool things I like in Live is the Instruments (Audio / MIDI Effects) Racks. You can use a Step sequencer and still use 4 different synths for instance. Communication between Max for Live devices using send and receive is supported, but there may be some latency involved when sending data between devices. Multithreading is tricky… c’est la vie.
i’m assuming (based on the above, and the fact that the only signal-rate MSP devices are live.remote~ and live.param~) that there is no way to to tap into the audio output of another track *without* having a separate M4L device in that track (i.e. via the API).
is this sort of thing possible in principle (signal-rate audio reading directly through the API)? with a platform like M4L, it would be highly beneficial for the purpose of sharing devices to be able to keep things as self-contained as possible. for instance, i’m working on a patch that would ideally operate globally, within the master track, but be able to read audio from other tracks (for analysis purposes), and not be dependent on the rest of the set being configured any particular way.
any thoughts on this? i don’t consider it critical to my projects, but it would be a big step up in my mind to be able to do this eventually.
Forums > Max For Live