Julien Bayle

passing data from Processing to Max is easy, but passing A BUNCH and fast can be tricky.

Naturally, I'm thinking about OSC. I could pack this into a one and only message, at each frame and pop this out from P5 to Max. I'm afraid of network stack issues with that, even if on the same computer (loopback localhost I mean).

I'm even thinking about using syphon as I could send that as textures (even if I had to read it back to CPU in Max, it could avoid the network stack)

Anyone as crazy as me for trying anything related to this ?

Hi there,
passing data from Processing to Max is easy, but passing A BUNCH and fast can be tricky.
Naturally, I'm thinking about OSC. I could pack this into a one and only message, at each frame and pop this out from P5 to Max. I'm afraid of network stack issues with that, even if on the same computer (loopback localhost I mean).

I'm even thinking about using syphon as I could send that as textures (even if I had to read it back to CPU in Max, it could avoid the network stack)

Hi there,
passing data from Processing to Max is easy, but passing A BUNCH and fast can be tricky.
Naturally, I'm thinking about OSC. I coul

passing-a-lot-of-data-from-processing-to-max-on-a-very-fast-way

Convert the data to texture(s) and try exchanging them through Syphon or convert the data to sound stream and try exchanging them through virtual audio port.

Syphon / Texture way could do it, probably. I'd prefer this, GPU / CPU wise.

I'm investigating the MXJ running the java code way too, actually.

Triggering / Controlling the code which calculates my visuals from Max is also a requirement.

Just trying to figure out performances in both case:

1/ Processing Running the code, listening to Max through OSC (fast enough in that case), passing data through textures to Max

2/ Max running the code through MXJ, Max controlling directly the MXJ (or even a MXJ~ if some signals feeding are required, MXJ popping out directly what it has to pop out

Syphon / Texture way could do it, probably. I'd prefer this, GPU / CPU wise.
I'm investigating the MXJ running the java code way too, actually.
Triggering / Controlling the code which calculates my visuals from Max is also a requirement.

Just trying to figure out performances in both case:

1/ Processing Running the code, listening to Max through OSC (fast enough in that case), passing data through textures to Max

2/ Max running the code through MXJ, Max controlling directly the MXJ (or even a MXJ~ if some signals feeding are required, MXJ popping out directly what it has to pop out

Passing a lot of data from Processing to Max on a very fast way...?