Sending control messages/audio from Ableton to Max standalone instead of using M4L
Hi guys,
I am not sure if this is possible but I was wondering if Ableton can send data to Max standalone with some message protocol (touchosc?), without using M4L.
The reason why I am asking this is because I would like to integrate some Jitter visualization insides my Live set and it is common opinion that M4L is quite unstable with Jitter. So could be a viable approach to keep them separated and sending control messages from Ableton to Max (like midi/automations to control some parameters on the Max patch)? For sending audio I guess is more complicated then sending midi messages?
I am talking about having Ableton and Max running and communicating (Ableton -> Max, no need for the other way around) on the same machine, without using M4L.
What do you think?
Why should m4live device affect jitter performance in Max Standalone
if midi or OSC messages are sent ?
midi from live ... ok there are some latency reports, but OSC ?
If you use automated CC# or note messages from live
to trigger stuff in max, one could measure latency and
compensate if necessary.
It depends what exactly you need to control.
Only triggers or full automated ramps which need to be
composed as midi automation in Live ?
or oscillators which get triggered by tempo - time events ?
OSC is usually used to communicate in network, or when midi has limitations,
like on windows, or when more separated control lanes are needed and so multichannel midi output from live track.
If I remember correctly, you use Mac - Intel max version.
IAC Buss or "to Max " midi pipe works fine for inter-midi
Hi!
I was not referring to latency but to the overall stability of M4L when using Jitter. I heard some people stating that Jitter is better to use with Max standalone that inside M4L, that's why I was asking this. I have just started learning Jitter so I don't have real world experience yet
Use M4l device / devices and send udp messages to control the external jitter patch might be a good solution.
Yeah, udp seems also pretty simple to use. Thank you!
When you jitter inside M4L , isn't it on a lower priority thread? I read that somewhere. I know that should only be a concern if you really need thread management. For most graphic jitter via M4L should be fine. I get frame rates well above 100fps running inside M4L. I am curious though what the difference is say in a raymarching shader. Which one would it run better in?
I'm setting up a project now where the visuals are in Max and control messages are sent as osc/udp from Ableton. I've done this before and it works well. And the only reason for doing it this way for me is the assumption that jitter *might be hindered within M4L.
curious about.. Some years ago my constat was Live cares first of itself, and than jitter in amxd. So : jitter in max standalone and osc commands from Live to be responsive. Maybe better today and Mnn Mac's ?
It could well be that the issue is Jitter overloading the Max4Live UI thread, in which case piping over osc to Max standalone should do the trick.