M4L need more inputs.

    Jul 19 2011 | 9:08 pm
    So, I´ve been fiddling with M4l for a couple of weeks. Been using plogue Bidule before which is great but I think that I prefer the Max way of calling up objects by typing in the object box instead of wading thru menus and submenus as you have to do with Bidule.
    But.. there is a big problem with Max for Live. You can only have 2 inputs. This is unfortunate imho, you can´t sidechain stuff. plugsend~and plugrecevie~ does the job but really bad with enormous latency and crackles.
    In Bidule you can have lots of inputs and they will show up as destinations in the "audio to" in other tracks. This is how M4L should behave aswell, in combination with a working plugsend~/plugrecevie~ combo. Then it would be awsome.
    I apologize if I´ve missed some obvious workarounds or functions since I´m pretty new with M4L, but it seems that there is no real sidechain routing in M4L.

    • Jul 19 2011 | 11:21 pm
      There are some other workarounds but not any without latency problems.
      Flexible audio routing is very high on the wishlist, so we can expect improvements in future versions of M4L.
    • Nov 11 2013 | 4:51 pm
      Hi Claesbjo,
      I know this is an old thread, but I wondered if you are still using [plugsend~] [plugreceive~] these days.
      Still now, Max's documentation says: “The use of the plugsend~ and plugreceive~ objects to pass audio between Max for Live devices is not supported.” but it seams to work...
      I am trying them at the moment. With my setup I get a steady 46ms latency (2048 samples) between [plugsend~] and [plugreceive~], and I have not noticed any problem.
      Well, it is not perfect, as I get 1ms latency between [send~] and [receive~].
      Here my latency test devices, if it is any use: http://liveelectronics.musinou.net/devices/latencytest/
      Could you share your experience with [plugsend~] and [plugreceive~]. Any bug, glitches? Excessive or random latency?
      Thank you!