Bug Report Some bugs I've discovered (output-streaming)

[Barabba]

Hi! Here is my little contribution it it may help:
1) If I specify an address on live stream which can't be used (in my case I've tried to stream to local multicast 239.0.0.1), I can't change it more. I mean, if I put back the local one, which is correct and works previously, I can't start more live.. it gives the same error. I need to close and open OBS, and without change nothing it will stream to live again (it remembers the correct address).

2) If I'm using the ?mode=listerner it waits for host to connect, and I can't stop the live until someone will connect, it keeps "waiting". I should be able to stop it even if noone will connect.

3) it happened that running external ffmpeg as recording the program still run in memory even if I close it, I've to manually kill it by task manager. You maybe need to assure to kill all OBS istances when close the GUI.

I've Win7-64 SP1, 6 core AMD and 4GB of RAM

May I please ask you to introduce the multicast streaming? It will be really useful, thank you.
I would also ask to introduce a third output, it can be used to stream the same to Facebook or in my case to a remote monitor which is placed on the scene, far from the server. Thank you a lot!

 

[Barabba]

Probably caused by the srt output with listener parameter, the sudio is able to close its GUI but it still running in background, need to be killed by task manager

 

[vapeahoy]

using obs version of ffmpeg? I just found a 6-8 second lag introduced in ffmpeg 4.2.2 by Zeranoe if using some new x264 settings. I had to revert back to a previous version from last year. Currently compiling my own ffmpeg but probably going to take some attempts to find the right minimum of libs needed. This is great news because there means there's crap we need to fix that will make things better.

 

[Barabba]

Hi, thanks for your answer. I've also noticed a huge lag but I can't compare it with the past. I would ask, OBS is using the ffmpeg file I downloaded and I put in path folder? The same for live output and for record output to ffmpeg?
If you can figure out how to reduce the lag, may you post it here please? Thank you!

 

[vapeahoy]

It turned out for my use case, while newer zeranoe ffmpeg 4.2.2 is indeed about 1.5-2 seconds slower - and i repeat for my usecase- it wasn't that bad. The main problem was that the syntax has changed and that i didn't know i wasn't using the latest version because file synchronization across my network hadn't copied the file for some reason. And i've sort of now waiting to get up with a new build so, long story. Anyhoo..
My usecase in this is sending uncompressed video+audio192 with a 10gigabit direct connection. So bandwidth isnt limited. 4.1.3 i know is very good for this and 4.1.4. From ffmpeg 4.1.5. and onwards the syntax is changed but it's also a bit slower. I dont know why, but what i do know is that x264 release build is up +7MB since july 2019 till today to a total of 26mb. But codec itself i dont believe has changed that much.

OBS will in general use locally placed .dll files at least if running in portable mode, that i know for sure. I have not tested with .exe files but you can check what is running by using task manager or an alternative task manager like process hacker. Which is awesome btw.