problem with send/receive objects in M4L -by design ??

[bencodec]

yeah right
introduce a ton of timing errors, great idea

well, bonus points for being so polite.

I think you are assuming the current bridge between M4L and Max5 somehow doesn't introduce the same issues as OSC?
I'm not saying it's tidy or that i love the solution, but it is the current reality. Any chance we can convince Ableton to let us spit out sysex?

[fisk]

sorry was a bit short there, youre right its slightly better.
i just think theres a better solution, ie implement sysex. its not like its some esoteric alien technology

[3dot...]

If you browse the control surfaces API, you'll see a function called "handle_sysex".
The messages being sent to and from novation/mackie displays is sysex. Messages from devices like the APc and the Launchpad also contain sysex.
Basically, Live's remote control surfaces section already handles sysex. Another point to prove that is the sysex based API hack which started a lot of this.

Live does support sysex, but not on the track input and output which is where we want it.
Which makes me wonder, could we actually pipe in/out pure sysex once we get control over the remote control surfaces stuff in M4L?

wow I really hope so... although I doubt it...
I actually don't mind that it's not in the channel's i/o...
if there's a way to enable and grab it and send it using the API I'll be glad...

[3dot...]

I don't know about you guys...
but what I was hoping for in M4L is to provide better 'customizable' control over Live...
granted... you can do a heck of a lot more than before...
but to completely free up our minds to think about the design and other creative tasks...
..rather than workarounds for transmitting data between Max objects or MIDI ports...
I understand this is no easy task...
all I can say at this point is that this sort of behavior is a big disappointment to me...

thank the heavens for OSC...

which raises the question of how much M4L is beneficial for control over 'other' solutions that support OSC ...and rewire
(aside from the live API..
which I'm guessing could be made to work with 'processing' 'pd' 'vvvv' 'bidule' or other sorts of real-time development environments I'm not aware of...)
when all the while an 'enable sysex' switch on a midi input or an 'external instrument' device ...
is all that is needed to really open up Live...
once again ...
if there's a 'handle sysex' switch for Live's MIDI ports...
then maybe there's hope on that end..
I still would like to see s/r objects behavior to seem more 'natural'...
well...I've already made my patch work using OSC so I'm not complaining...
evolver tweaking using clip envelopes...sweet...

[charles_2]

Yeah, we definitely need to be able to do sysex from Max4Live.

[djod]

+ 1 for sysex!

In and out, cos you would need to update the status if you twist a knob.