December 22, 20223 yr Hello, I have two questions with this build. 1. When I try to access the webvnc, I get this screen. What's the difference between the Lite and Full client, and what is the -e for? 2. When I try to pick up my NDI source, I don't see any options. Is there something I'm missing? Thank you
December 27, 20223 yr Had to delete and reinstall to get it working. Where's the option to change the vnc password in the setup? I'm unable to access the VNC from a 3rd party client? I'm using TightVNC Viewer just "closes gracefully" when I make the attempt. Couple other things. Might want to consider putting an OBS shortcut on the desktop. You may also want to update the info in the thread's first post. Thanks for your time/effort. Nice to finally be able to use this. Edited December 27, 20223 yr by scooterbaga reworded
December 27, 20223 yr Author 2 hours ago, scooterbaga said: Had to delete and reinstall to get it working. Where's the option to change the vnc password in the setup? I'm unable to access the VNC from a 3rd party client? I'm using TightVNC Viewer just "closes gracefully" when I make the attempt. Couple other things. Might want to consider putting an OBS shortcut on the desktop. You may also want to update the info in the thread's first post. Thanks for your time/effort. Nice to finally be able to use this. I will update the template soon. If you like you can add the variable VNC_PW yourself, with it you can overwrite the password. OBS shortcut is a good point. I will add it in the next version. And also check the external VNC connection.
December 27, 20223 yr Author On 12/22/2022 at 10:15 AM, iForeverNoob said: Hello, I have two questions with this build. 1. When I try to access the webvnc, I get this screen. What's the difference between the Lite and Full client, and what is the -e for? 2. When I try to pick up my NDI source, I don't see any options. Is there something I'm missing? Thank you The -e should be a "bug" from the base image. About the different versions I also haven't found anything usefull. In case I find it, I'll let you know. 2. You have to be in the same subnet. That is also the reason why you have to define a IP for the container.
December 28, 20223 yr I'm having the same issue as iForeverNoob. After updating (and updating all my OBS "endpoints"), my NDI source isn't showing up in the Docker image, but it does show up in a Windows VM that runs from the same Unraid server.
December 28, 20223 yr @patrickstigler would you know the version of NDI that's being used for this docker image? I know that new version of NDI (v. 4.10.0) came out not too long ago which addresses issues with OBS v. 28.0.0+
December 28, 20223 yr 23 minutes ago, iForeverNoob said: @patrickstigler would you know the version of NDI that's being used for this docker image? I know that new version of NDI (v. 4.10.0) came out not too long ago which addresses issues with OBS v. 28.0.0+ It seems like to be this version On 12/27/2022 at 4:23 PM, scooterbaga said: Had to delete and reinstall to get it working. Where's the option to change the vnc password in the setup? I'm unable to access the VNC from a 3rd party client? I'm using TightVNC Viewer just "closes gracefully" when I make the attempt. Couple other things. Might want to consider putting an OBS shortcut on the desktop. You may also want to update the info in the thread's first post. Thanks for your time/effort. Nice to finally be able to use this. TightVNC does work for me. 5 hours ago, tj177mmi said: I'm having the same issue as iForeverNoob. After updating (and updating all my OBS "endpoints"), my NDI source isn't showing up in the Docker image, but it does show up in a Windows VM that runs from the same Unraid server. Also NDI source is not showing up anymore.
December 28, 20223 yr 55 minutes ago, iForeverNoob said: @patrickstigler would you know the version of NDI that's being used for this docker image? I know that new version of NDI (v. 4.10.0) came out not too long ago which addresses issues with OBS v. 28.0.0+ It looks like this is the version
December 28, 20223 yr 27 minutes ago, Evidenz said: TightVNC does work for me. I think I figured this out. The docker settings are ignoring my custom VNC port value. I was able to use TightVNC after changing to the default 5901 value.
December 28, 20223 yr Author @scooterbaga That's interesting. I changed to port to default in the current template. But I am not sure if the template gets updated as well or if you have to remove it and reinstall it to update it. I guess I have to check that. @tj177mmi that's a good point then. I will update that aswell.
December 28, 20223 yr Author ok thanks for the hint 😄 @Evidenz @iForeverNoob The new version is currently building - should be ready in 20min.
December 28, 20223 yr Author @iForeverNoob Btw the full client supports copy paste over the session. The image is build but untestet yet. I might have some time to test it soon.
December 28, 20223 yr Apologies for more issues to the pile... Hadn't occurred to me until I added the VNC_PW key, but this docker is going to reset the OS/OBS settings on a rebuild. Is that going to happen with every update as well? Anyone have any suggestions there? I know you can backup OBS settings. Aside from manually saving off directories, is there an easier way? Should we incorporate Syncthing into the OS, or something so we can "backup" these settings?
December 29, 20223 yr Greetings! I have updated the Docker to the latest version. But unfortunately now I don't have the possibility to select the NDI plugin.
December 29, 20223 yr 4 hours ago, BuTscH said: Greetings! I have updated the Docker to the latest version. But unfortunately now I don't have the possibility to select the NDI plugin. It looks like NDI was removed with the newest build, yes.
December 30, 20223 yr On 12/29/2022 at 7:05 AM, Evidenz said: It looks like NDI was removed with the newest build, yes. @patrickstigler It seems the latest image broke the install of the NDI plugin. Any chance you know why?
December 30, 20223 yr On 12/29/2022 at 7:05 AM, Evidenz said: It looks like NDI was removed with the newest build, yes. Created an issue on GitHub to report this there as well Also, @patrickstigler, thanks a lot for putting this all together. Edited December 31, 20223 yr by iesou added thanks
January 12, 20233 yr On 12/29/2022 at 7:05 AM, Evidenz said: It looks like NDI was removed with the newest build, yes. Having same issue. Is there a way I can just add it myself?
January 18, 20233 yr Seems like a general issue with the missing NDI https://github.com/Palakis/obs-ndi/issues/823
January 19, 20233 yr How do I use Intel Quick Sync with this instead of Nvidia? I'd like to use my 12th gen iGPU for encoding as it actually has better quality then Turing / Ampere NVENC as shown in eposvox video Edit: Can anyone confirm if the way to get Intel iGPU as the encoder is to change extra parameters from --runtime=nvidia to --device=/dev/dri? Edited January 19, 20233 yr by hoeman
February 9, 20233 yr @patrickstigler Appreciate the work you've put in. I can confirm that changing extra parameters to --device=/dev/dri allows for H.264 encoding by Intel QSV, however the latest image does not have NDI Source as an option. Any chance this can be fixed?
February 16, 20233 yr On 1/19/2023 at 10:15 AM, hoeman said: How do I use Intel Quick Sync with this instead of Nvidia? I'd like to use my 12th gen iGPU for encoding as it actually has better quality then Turing / Ampere NVENC as shown in eposvox video Edit: Can anyone confirm if the way to get Intel iGPU as the encoder is to change extra parameters from --runtime=nvidia to --device=/dev/dri? I've been trying to get this to work but no luck
February 23, 20233 yr On 2/17/2023 at 1:28 AM, Dirtyrobot said: I've been trying to get this to work but no luck Actually I got it right, you just have to change extra parameters to --device=/dev/dri and when you spin up the container, open OBS, settings, streaming, advanced, you will see that there's the hardware encoder available for usage. The problem now is that this container seems abandoned by the dev and the latest one has broken NDI implementation where under sources, NDI doesn't even show up. Sigh, it would be nice if @patrickstigler would come back to this.
February 27, 20233 yr On 2/23/2023 at 1:53 AM, hoeman said: Actually I got it right, you just have to change extra parameters to --device=/dev/dri and when you spin up the container, open OBS, settings, streaming, advanced, you will see that there's the hardware encoder available for usage. The problem now is that this container seems abandoned by the dev and the latest one has broken NDI implementation where under sources, NDI doesn't even show up. Sigh, it would be nice if @patrickstigler would come back to this. Bummer!
March 1, 20233 yr Author Hi Sorry for the delay. I will take a look at it, but currently I am quite busy so I had no time to do something on the image. Also my network interface broke (might be a software issue) but now I have to fix the build pipeline first. I will update you guys here.
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.