mountaintop

Johan, I just tested again on a fresh container and after making sure my OBS was open on my gaming PC it shows up on the drop down list as a source as it should. Did you give the docker container an IP as thought its another device on your network? (IE: i uses 192.168.1.x and my docker container has an IP of 192.168.1.250) or does it have a docker assigned IP like 172.16.x.x? If its the docker assigned IP, change to using your bridge device (br0 most likely) for networking and give it a normal IP on your network and the problem should be resolved. The NDI plugin uses avahi / mdns to broadcast service availability, make sure that nothing is blocking communication. (firewall, having docker container on a different LAN segment, using docker internal IP instead of bridged networking will all cause avahi not to work.)

Instructions above in the post linked for a fixed container image: https://forums.unraid.net/topic/114911-support-obs-ndi/?do=findComment&comment=1242303

The web interface is on port 5901, the latest template says 6901, if you try http://ip:5901 it should give you the novnc interface. you can also connect directly with your own vnc client on port 5900 To delete a post click the ... on the post header and click delete.

Hi gents, Waited a bit to work on fixing this myself and ended up revamping a bit of it back to the old system to get it to work. The new accetto/ubuntu vnc based image does not play well with avahi so NDI is unable to locate sources. I've posted the changes to: https://github.com/mountaintopsolutions/docker-obs-ndi-ng The summary is: Went back to the old container format for now. based on the old images when this was first published. Updated to ubuntu 22.04 Updated OBS to 29.0.2 Updated NDI plugin Fixed startup scripts. The images are available for the unraid OBS-NDI plugin at https://hub.docker.com/r/mountaintopsolutions/docker-obs-ndi-ng they can be imported by changing the repository URL for the OBS-NDI image to: mountaintopsolutions/docker-obs-ndi-ng:legacy-latest or if you want to stay safe and not get any updates mountaintopsolutions/docker-obs-ndi-ng:legacy-1.0 This container uses port 5900 for direct VNC connections and 5901 for novnc connections. Please let me know if you have any problems or suggestions. for the "NG" part of docker-obs-ndi-ng I have rebuilt the accetto based image, fixed the issues, and have it running manually but it needs some startup script changes that will require rebuilding the entire accetto base image to fix, as avahi and dbus need to start with xvnc. When i have time to fix that I will publish those images, but this should get everyone back streaming for now. -- DC Screenshot attached showing we are cooking with gas again!