M4L Audio not send~ing to MIDI track

    Jun 07 2010 | 1:25 am
    Another M4L problem I'm having has been with trying to send signal data from an audio track via send~/receive~ to a MIDI track to process there. Hooking up scope~, I see that the signal data is making it to the send~ object just fine. However, looking at the receive~ object's scope~, it shows nothing. How might I better send Audio data to a MIDI track's M4L patch for processing?
    Cheers, Jay

    • Jun 07 2010 | 8:30 am
      Quote from the documentation:
      "The use of the send~ and receive~ objects to pass audio between Max for Live devices is not supported."
      As far as I know there is no alternative.
    • Jun 07 2010 | 4:01 pm
      How about using a VST like wormhole?
      Havent tried this by the way
    • Jun 07 2010 | 4:03 pm
      I've set up a little test sending from an audio track using 'plugsend~ left' and 'plugsend~ right':
      The receiver is a Max Instrument on a MIDI track with 'plugreceive~ left' and 'plugreceive~ right:
      As long as both devices are in edit mode or both are inside Live this works for me.
      I did not test latency.
    • Jun 07 2010 | 4:37 pm
      I did some testing with Wormhole and some other VST devices with the same functionality. I tried Virtual Audio Cable and ReaRoute ASIO (comes with Reaper) as well.
      I got to two conclusions for all setups I've tried: 1. The latency is just not tolerable 2. The setup configurations are clumsy
      With plugsend~' - plugreceive~ the delay seems to be around 12 ms. This might be bearable in some situations.
    • Jun 07 2010 | 6:16 pm
      Please read this.
      PS. Just did a quick test and measured delay of 44ms!
    • Jun 07 2010 | 6:49 pm
      Thanks broc,
      I suppose we can agree that this is really a serious topic. Every attempt to send audio to some other location runs us into serious problems. This is caused by threads not being synchronized. I hope C'74 and Ableton will come up with a solution in the near future or at least with serious improvements.
    • Jun 07 2010 | 8:22 pm
      Well, I think the root of the problem is the conventional inflexible architecture of Live (like most other DAWs), i.e. strict separation of midi vs. audio tracks and limited routing capabilities. The integration of Max would be much smoother if Live had generic tracks for midi and audio with arbitrary routing, as can be found for example in 'Reaper'. So I think the developers should consider some basic redesign in the long term.