M4L issues

[joex92]

Hi!
I'm working on a M4L project on Max and I want to add this object in order to send a jit.matrix through [jit.ndi.send~ ---Matrix]...
the problem is that when I finally export it to a M4L device and use it on Live, the [jit.ndi.send~] doesn't work, it ONLY works if I open the M4L device as a patch in max...
I even tried to use a subpatcher to "open" the NDI patch, like this:

but it doesn't work...
it ONLY works if I open it on Max:

is it impossible to make it work seamlessly as a M4L device?

[pixsperdavid]

Could you post a minimal example patch so I can try and replicate?

[randallpacker]

Would be glad to do so, but are you talking about a patch that contains six instances of jit.ndi? Is that something you need me to do?

[pixsperdavid]

@randallpacker Did you post in the wrong issue?

[randallpacker]

I did! I thought you wanted an example of resources used. I didn't pay attention to the forum topic! So sorry!!!

[joex92]

@pixsperdavid this is a very simplified version of what I kinda doing

[joex92]

BTW there is another problem... just adding jit.ndi.send~ to the M4L device makes the Ableton Live CPU usage skyrocket from 2% to 100%...
so there might be another issue there... you can see that happening on the test M4L device I shared in the comment above...

[pixsperdavid]

NDI_test_fixed.zip

The above now works for me both in M4L and in Ableton. The key issue was that jit.graph seems to output an all zero alpha plane. I added a matrix conversion from ARGB to RGB (discarding the alpha) and it works as expected.

Regarding the CPU usage, checking with task manager on Windows, the CPU usage of Live is nowhere near what it's internal meter reports when jit.ndi is sending. Are you actually experiencing any audio dropouts?

[joex92]

ok, I tried it, this is what happens:

• as you can see the ndi connection "005graph" is not appearing on the NDI monitor (I oppened the NDI monitor after adding the M4L device)...
• the CPU usage IN LIVE is too high! in this case I'm not having audio issues, but on my main M4L device, the M4L device can't work smoothly, to the point where the audio starts dropping or Live itself starts slowing down... I'm using ASIO4all for the audio driver...

[pixsperdavid]

Can you see if there are any errors in the M4L Max window? (right click on the device title bar and select 'Open Max Window').

Interestingly the CPU usage issue seems to occur even when the object is completely disconnected from any input. I'll look into this.

[joex92]

I cleared the max window, then added the M4L device and there is no errors, nothing on the max window...

I remade my main M4L device without the ndi objects and was using using it rn when I checked the max window... the instant I added the ndi test device, Live started to slow down and it seemed like it was about to crash but it didn't, it just took a lot of time to respond to any interaction... My main device uses jit.world, jit.catch~ and jit.gl.mesh... but even after having all that my main device just makes Live use 4% more of CPU...