You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi keijiro, currently, I use NDI Receiver to get textures. I have multiple Windows/Android apps running in real time, and I want to do it through multicast. I have two questions about this:
There is no option to configure the multicast address in Klak NDI, which should be a very important step to join the IGMP multicast group, otherwise the application cannot correctly obtain the NDI multicast stream. Like this setting in NDI Access Manager.
Currently, AndroidHelper.cs only targets Wifi networks, and does not handle Ethernet. Is there a plan to implement it in the future? One way I can think of is to get the Ethernet manager, and if it does not exist, use the Wifi Managerer.
The text was updated successfully, but these errors were encountered:
I finally built my application for Quest 3 with KlakNDI. I use a Realtek 8153 Ethernet adapter, which does not require additional driver installation. Unicast and multicast both work when the network is properly configured.
Hi @keijiro , I'm trying to figure out if Multicast can be enabled programly with ndi sdk other than relying on NDI tools/NDI Access Manager on sender side of a PC, with no luck, do you have any clue?
Hi keijiro, currently, I use NDI Receiver to get textures. I have multiple Windows/Android apps running in real time, and I want to do it through multicast. I have two questions about this:
There is no option to configure the multicast address in Klak NDI, which should be a very important step to join the IGMP multicast group, otherwise the application cannot correctly obtain the NDI multicast stream. Like this setting in NDI Access Manager.
Currently,
AndroidHelper.cs
only targets Wifi networks, and does not handle Ethernet. Is there a plan to implement it in the future? One way I can think of is to get the Ethernet manager, and if it does not exist, use the Wifi Managerer.The text was updated successfully, but these errors were encountered: