Asparon Posted September 26, 2023 Share Posted September 26, 2023 This is the support page for the updated version of OBS-NDI. Big thanks go to patrickstigler on whom this container is based on. https://hub.docker.com/r/asparon/obs-ndi Docker OBS and NDI (QT6) This container is based on https://hub.docker.com/r/patrickstigler/obs-ndi. Due to some QT-changes in the OBS code the initial version by patrick needed some changes. To start the container: docker run --shm-size=256m -it -e VNC_PASSWD=headless -p 5901:5901 -p 6901:6901 -p 4455:4455 asparon/obs-ndi:latest The shm-size argument is to make sure that the webclient does not run out of shared memory and crash. You have to change the "Network Type" to "Custom: br0" in order to be able to find the NDI-Source of your desktop in the container an vice versa. You can change the default VNC password of 'headless'. You can connect with your own VNC client via 5901 or use the webclient at 6901. To enable GPU Support: Nvidia: add -e NVIDIA_VISIBLE_DEVICES=your_GPU_ID -e NVIDIA_DRIVER_CAPABILITIES=all and also add --runtime=nvidia as extra parameter. Intel: add --device=/dev/dri (not tested yet) 1 Quote Link to comment
letum00 Posted October 2, 2023 Share Posted October 2, 2023 I can verify this docker works while the older one has not worked for some time. Thank you! I added the extra parameter for Intel QuickSync but did not see it as an encoding option with a cursory glance. I have to dig into this more, though. Quote Link to comment
letum00 Posted October 4, 2023 Share Posted October 4, 2023 I was able to get Quicksync (ffmpeg VAAPI h264) working after installing the intel media driver: apt install intel-media-va-driver-non-free Quote Link to comment
Nibbles Posted October 25, 2023 Share Posted October 25, 2023 Hey hey, been slowly migrating a second PC over the unraid, finally got everything moved over and set up. Got OBS-NDI to replace the PC that I took down and been dealing with a weird issue. When an NDI Source isn't running, CPU idles around 3-10%, but the minute I make an NDI source visible (whether I use NDI screen cap, or NDI from my gaming machine) my CPU immediately jumps up to 70-80% and I'm not exactly sure why. I passed through my 2080 Super to handle the encoding, but I'm not sure if it's accurately being used or not. Specs CPU: AMD Ryzen 7 2700X Eight-Core RAM: 16 GiB DDR4 Ballistix something or other GPU: NVIDIA GeForce RTX 2080 SUPER I did a small test stream, it hits around 50FPS but I'm wanting to get 60 and it should be fine. My gaming PC and Unraid are connected via an ethernet hub and I'm not sure what other info might be helpful here. Quote Link to comment
mmwiebe Posted November 21, 2023 Share Posted November 21, 2023 Hello , Thank you for the docker, I probably missed something... I downloaded the docker and started it When vnc into docker I only see a desktop and no obs program.... What am I missing? Than you for any help. Quote Link to comment
Jed05 Posted December 14, 2023 Share Posted December 14, 2023 (edited) I'm trying to use this and for whatever reason its setting the IP as 10.0.0.2 when my server is 10.0.0.200. When I set it manually to say 10.0.0.202 I'm able to connect. Also, is there any way to update the OBS version used in this? We are up to 30.0.0.2 now. Edited December 14, 2023 by Jed05 Quote Link to comment
kripy Posted December 17, 2023 Share Posted December 17, 2023 On 9/26/2023 at 1:42 PM, Asparon said: This is the support page for the updated version of OBS-NDI. Big thanks go to patrickstigler on whom this container is based on. https://hub.docker.com/r/asparon/obs-ndi Docker OBS and NDI (QT6) This container is based on https://hub.docker.com/r/patrickstigler/obs-ndi. Due to some QT-changes in the OBS code the initial version by patrick needed some changes. To start the container: docker run --shm-size=256m -it -e VNC_PASSWD=headless -p 5901:5901 -p 6901:6901 -p 4455:4455 asparon/obs-ndi:latest The shm-size argument is to make sure that the webclient does not run out of shared memory and crash. You have to change the "Network Type" to "Custom: br0" in order to be able to find the NDI-Source of your desktop in the container an vice versa. You can change the default VNC password of 'headless'. You can connect with your own VNC client via 5901 or use the webclient at 6901. To enable GPU Support: Nvidia: add -e NVIDIA_VISIBLE_DEVICES=your_GPU_ID -e NVIDIA_DRIVER_CAPABILITIES=all and also add --runtime=nvidia as extra parameter. Intel: add --device=/dev/dri (not tested yet) Hello could you add 1440p support pls in config regards, Quote Link to comment
Evidenz Posted January 4 Share Posted January 4 (edited) I am able to find my output in the drop down but there is no picture arriving on the container side. Am I missing something? //E: It seems like a firewall thing. As long as the firewall is disabled it works. Does anyone know the port I have to open (because there is no NDI related executables as they are just dlls). //E2: nvm - added the OBS Studio app on the allow list and it is fixed Edited January 4 by Evidenz Quote Link to comment
anti-Semitic-fertilizer6229 Posted January 22 Share Posted January 22 I'm also getting high CPU usage when using this docker container. Adding an NDI source jumps my CPU usage to 80% on a Ryzen 7 3700X. GPU is attached and working when locally recording. Quote Link to comment
firetime Posted January 28 Share Posted January 28 (edited) Thanks for the template! I'm using it as a playout server. I added an auto start so in the event the container is updated/server restarts it will resume the stream on startup. Add a file map to /home/headless/.config/autostart/ and place an app.desktop file in the mapped autostart folder with the following to trigger Xfce to start OBS: [Desktop Entry] Type=Application Name=conky Exec=obs & StartupNotify=false Terminal=false This is coupled with an OBS LUA script I wrote that auto starts streaming and sequences media playback. Edited February 7 by firetime Quote Link to comment
repomanz Posted April 3 Share Posted April 3 (edited) @Asparon Hello - thanks for this container. Couple questions. 1) when I try to authenticate via youtube it displays an error input/output error likely related to the container's web browser. I get the same thing when attempting to use the web browser in the container. 2) I think this is related to 1 but I don't see manage broadcasts Thanks! Edited April 5 by repomanz Quote Link to comment
dpavi Posted July 19 Share Posted July 19 Hello, just got OBS-NDI to try, but it is impossible to use actually. When NDI source is added it eats exactly as for other people that told about this problem - 70-80% of cpu usage, I can't reach 60fps at 1080p, max I can get is ~45fps. I see that my gpu is getting used, but only when streaming, I never thought that it could be so demanding for cpu unfortunately. Specs CPU: AMD Ryzen 5 3600 RAM: 32gb 3200 GPU: NVIDIA GeForce GTX 1060 Quote Link to comment
ZooMass Posted October 17 Share Posted October 17 Is there a way (environment variable or config setting) to change the port which the VNC server uses? Not the NoVNC client, specifically the actual VNC protocol port. 5901 often clashes with Unraid VMs which autostart to 5900 + 1 * however many VMs on VNC there are, which when they are running then prevent this container from starting. I can't just bind mount to another port because this container needs to run on network: host in order to detect NDI outputs on the actual (not internal Docker) network via mDNS. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.