keijiro / KlakNDI

NDI® plugin for Unity

Home Page:https://ndi.video

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Android NDI Sender not visible on desktop

benkuper opened this issue · comments

Hello,
trying to use Klak NDI on an Android device (Redmi Note 9S, Android 11)
Everything compiles and runs fine but the NDI source is not visible from NDI Studio Monitor (or any other app) on a Windows 11 desktop
Running from the editor actually works and is visible as a NDI source in NDI Studio Monitor, but nothing on Android...
Am I missing something ?

Could you test the NDI connectivity using other NDI Android apps?

Sorry forgot to mention, yes it's working with other NDI app like tricaster (didn't test the paying official one but I guess this would work as well)

Also : using Unity 2022.1.6f1, and I checked "Internet access : require" in the player settings.
Tried with different options, check logs and android logcat, nothing seems to be out of place..

More info :
I tried my OSCQuery plugin which includes Zeroconf/Bonjour, it's not visible as well even though the app is accessible through OSC from the plugin, just not advertised.

I tried again with some different configuration :

  • URP settings, using ndi sender with and texture, renderTexture attached to the camera : on windows it's working, on android the source is not detected in NDI Studio monitor
  • URP settings, using ndi sender with "Camera" directly, not working on either windows or android

I am running into the same issue on my end.
Galaxy S21 running Android version 12. NDI feed works if it comes from the NDI HX Camera app, or if I run the app in editor on my windows 10 pc, but the device is not listed if I am running the built Unity app on the phone.

The NDI Sender is using a render texture that is 1920x960

@benkuper I was able to get it working on my android device by ensuring the resolution is a multiple of 16x8 and that the Scripting Backend was set to IL2CPP instead of Mono

The Android support is improved in the latest update (2.1.1). Please reopen this issue if it still reproduces with the latest version.