Resolume Forum

I needed to use Arena's NDI output feature and capture it in OBS. After a while, it no longer changed scenes (clips), but continued to send the signal.
When I tried to find the signal generated via Studio Monitor, Webcam Input, on the same machine and another on the network, I was unsuccessful.
In short, it remains active where it was captured and disappears.
To get it working again, I can only close Arena and open it again, but with an event running, there is no way.
Does anyone have any idea what could be happening? This is not new, I have had this problem with other versions and it was never fixed.

Running OBS and Resolume on the same machine, Spout or Syphon texture sharing would be a lot better than NDI.

On different machines, check the NDI gotchas here: https://resolume.com/support/en/NDI_inp ... di-gotchas

Zoltán wrote: Thu Apr 17, 2025 19:28 Running OBS and Resolume on the same machine, Spout or Syphon texture sharing would be a lot better than NDI.

On different machines, check the NDI gotchas here: https://resolume.com/support/en/NDI_inp ... di-gotchas

I understand. I believe that using Access Manager will create a sort of tunnel between them, maintaining direct communication without getting lost along the way.

I've used this a few times when I'm on a different VLAN, but I hadn't thought of the same for Resolume itself.

While we're at it... Can this issue solve the problem of the Source NDI coming with a different resolution?
I ask because it often happens that when you insert the NDI into the Timeline, instead of coming in FHD, it comes all wrong.

when you insert the NDI into the Timeline, instead of coming in FHD, it comes all wrong.

In OBS?

What does the NDI monitor app say about the stream resolution?