Mr_Jay84

Twitch OBS bandwidth switcher https://github.com/715209/nginx-obs-automatic-low-bitrate-switching I have tis running on a Ubuntu VM however a docker version would be more efficient.

Ah okay thanks for the info.

Thanks for the reply I'm looking for it to be used with an DIY external DAS. Not quite sure what you mean here.

Spied this on ebay https://www.ebay.co.uk/itm/303686605799?hash=item46b521dbe7:g:WacAAOSwofVfXEyc Has anyone had experience with this model?

Is it normal for any of the variables set in the UI to reset when the docker restarts?

The media is stored on my NAS however I did find it was better to copy the item to the OBS VM first. The Owncast end user has a delay of about 8 seconds, owncast is set at medium for the latency buffer. I've had up to 8 users so far in various parts of the world, playback has always been smooth with no issues.

Ah right I see. Yeah you connect to Owncast from OBS via the unRaid IP. You may have to adjust the hardware resources or the stream settings in Owncast itself if you're experiencing buffering the Owncast stream page. My Owncast is set for 3000Kbps but you'll have to tailor yours for your hardware/bandwidth. There's also a buffer/delay setting to be mindful of, too low and your end users might have issues. With regard to OBS. I have the stream set to use the x264 CPU encoder, CBR, 3000Kbps, fast CPU usage. I tried NVENC but the result was a pixelated stream on the Owncast side. Remember Owncast does a transcode of it's own. My setup is OBS on a Win 10 VM hosted on unRaid streaming to Owncast docker on the same machine. I have four cores (8 threads) assigned to both the docker and the VM. I also tested tested it from various bare metal machines ony CAT6 network with no issues either. I wouldn't recommend trying this on WiFi though. Feel free to ask any more questions if needed.

I think you're getting confused here mate. You use RTMP to stream from OBS to Owncast. This is normally done on your internal network i.e. rmtp://YourUnraidIP:1935/live. Port 1935 is what you stream to from OBS. It's not the port users should connect too, which by default is 8080 Then to access the Owncast page via https use (for example) https://Owncast.yourdomain.com No port is required as it's https. Your gateway should be pointing the domain to the internal address i.e. http://YourUnraidIP:8080

You stream from OBS to Owncast via RTMP on the internal address Users access Owncast via the http/https address Could this be the confusion?

Like you I use Cloudflare although I use SWAG as the gateway. Works perfectly for me. Owncast should be used via http or https. My runs via https on my domain name and http internally. Why would you want to use RTMP just out of interest?

To add to this discussion. I'm using Brave Browser and noticed recently that it won't load any Guca based dockers. I need to use FF for that even though there's nothing wrong with the docker

Neither can I! That's what took me so long to find out why it was crashing. Very strange. Thinking back though, at one point I had an issue where I selected "animate on hover" which caused the folder to disappear and the UI to become unresponsive. Eventually I managed to delete the folder and recreate it. Maybe this happened twice. I wonder if it's linked.

I installed the plugin a few weeks back and had issues with the machine becoming completely unresponsive via both Web and SSH that included all the running dockers. This happened almost every day until I uninstalled it a few days back. I assumed it was other dockers that I had installed since then. I don't have any proof of this though as there was never anything in the logs at all. I had discounted the possibility of the crashes were due to this, but everything is back to normal once uninstalled. I'll give it another go in a few weeks again as it's a very good addition to unRaid. I need the server for some vital tasks at present.

Has there been any reports of system instability using this plug-in?

Do you need help with the reverse proxy config?

I'm using a reverse proxy via SWAG for external access.

No rush mate. Thank you looking into this.

It's from the Ghost container. I was advised on the Ghost forum to perform this... https://ghost.org/docs/faq/misconfigured-mysql-database/ However I still have no idea how to turn off the ANSI quotes. All the guides online tell you how to turn it on, not off

A few months back I ran into an issue with Ghost and Maria due to a Ghost update. I was advised on the ghost forum to do this... https://ghost.org/docs/faq/misconfigured-mysql-database/ Does anyone know what the actual commands are to turn off ANSI_QUOTES?

Unfortunately it doesn't. These are ES Xeons with no iGPU.

I have a variety of Nvidia cars installed but the one used for the dockers is a GTX 1060 G6B M/B: ASRockRack EP2C612 WS Version - s/n: 157265490000126 BIOS: American Megatrends Inc. Version P2.50. Dated: 03/22/2018 CPU: Genuine Intel® CPU @ 2.00GHz HVM: Enabled IOMMU: Enabled Cache: 768 KiB, 3 MB, 30 MB, 768 KiB, 3 MB, 30 MB Memory: 128 GiB DDR4 Multi-bit ECC (max. installable capacity 512 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mbps, full duplex, mtu 1500 eth1: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 5.10.28-Unraid x86_64

Dind't work on this occasion... ---Checking if UID: 99 matches user--- ---Checking if GID: 100 matches user--- ---Setting umask to 0000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Starting...--- ---Version Check--- ---Owncast v0.0.7 up-to-date--- ---Preparing Server--- ---Starting Server--- time="2021-07-02T03:18:53+01:00" level=info msg="Owncast v0.0.7-linux-64bit (3810ce4f63ecf7fb7a35c564af68f081c7e8b537)" time="2021-07-02T03:18:53+01:00" level=info msg="Video transcoder started using VA-API with 1 stream variants." time="2021-07-02T03:18:54+01:00" level=error msg="[AVHWDeviceContext @ 0x560bcc2f4980] libva: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)" time="2021-07-02T03:18:54+01:00" level=error msg="[AVHWDeviceContext @ 0x560bcc2f4980] Failed to initialise VAAPI connection: -1 (unknown libva error)." time="2021-07-02T03:18:54+01:00" level=error msg="Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Input/output error" time="2021-07-02T03:18:54+01:00" level=error msg="transcoding error. look at transcoder.log to help debug. your copy of ffmpeg may not support your selected codec of h264_vaapi https://owncast.online/docs/troubleshooting/#codecs" time="2021-07-02T03:18:54+01:00" level=info msg="RTMP is accepting inbound streams on port 1935." time="2021-07-02T03:18:54+01:00" level=info msg="Web server is listening on port 8080." time="2021-07-02T03:18:54+01:00" level=info msg="The web admin interface is available at /admin."

Excellent news! Looking forward to it! 😁

I assumed just adding the variables from the Nvidia plugin would suffice. Its does mention something about FFMPEG may need to be compiled with nvenc.

I'm using the new Owncast plugin and discovered it now supports VA-API Hardware encoding. I added my GPU via the NVIDIA_VISIBLE_DEVICES key (all the same details I use for emby/handbrake) however I get this error in the Owncast log. ---Owncast v0.0.7 up-to-date--- ---Preparing Server--- ---Starting Server--- time="2021-06-29T12:26:19+01:00" level=info msg="Owncast v0.0.7-linux-64bit (3810ce4f63ecf7fb7a35c564af68f081c7e8b537)" time="2021-06-29T12:26:19+01:00" level=info msg="Video transcoder started using VA-API with 1 stream variants." time="2021-06-29T12:26:19+01:00" level=error msg="vaapi not enabled. either your copy of ffmpeg does not support it, your hardware does not support it, or you need to install additional drivers for your hardware." time="2021-06-29T12:26:19+01:00" level=error msg="failed to set va-api device to /dev/dri/renderD128. your system is likely not properly configured for va-api" time="2021-06-29T12:26:19+01:00" level=error msg="transcoding error. look at transcoder.log to help debug. your copy of ffmpeg may not support your selected codec of h264_vaapi https://owncast.online/docs/troubleshooting/#codecs" Any one got this working with VA-API and the Nvidia plugin?