Cobra_Fast
New Member
A few friends and me set up our private custom streaming server that receives and streams Matroska/MKV via HTTP. This used to work pretty well for a long while until some update to OBS a couple months ago.
We use the Output -> (Advanced) Recording tab to set up the stream; see attached screenshot.
The problem now is, that either the bufsize= or maxrate= or both options are ignored. It usually works initially, but once it hasn't been outputting much for a little while (e.g. in a games menu screen) and screen activity resumes, it overshoots the maxrate= setting by god knows how much and jams the uprate (which on our home connections is around 5 Mbit/s). It'll take several minutes of constant lagging until all excess data has been uploaded at which point all viewers will be lagging behind by some considereable time as well.
I've tried bufsize= values of 2x, 1x, 0.5x, and 0.25xbitrate, none of them make any noticeable difference leading me to believe that bufsize= is somehow overriden to a (very) large value by OBS.
Looking at the pinned posts in this forum I've found just out about log files while writing this post, and the log pretty much confirms what I suspected:
22:47:54.684: Settings changed (outputs)
22:47:54.684: ------------------------------------------------
22:47:56.319: Failed to set threads=4
22:47:56.319: Failed to set maxrate=2560k
22:47:56.319: Failed to set bufsize=640k
22:47:56.319: If you're trying to set x264 parameters, use x264-params=name=value:name=value
22:47:56.324: Using muxer settings:
22:47:56.324: live=1
Putting those three options into the Muxer Settings box doesn't work either.
We also occasionally use ffmpeg with similar settings on the server machine itself and don't run into this problem, maxrate and bufsize work as expected then.
We're not using the "Streaming" setup as it doesn't allow selection of the container format (which needs to be matroska).
So, how do I actually use maxrate and bufsize in the recording context?
We use the Output -> (Advanced) Recording tab to set up the stream; see attached screenshot.
The problem now is, that either the bufsize= or maxrate= or both options are ignored. It usually works initially, but once it hasn't been outputting much for a little while (e.g. in a games menu screen) and screen activity resumes, it overshoots the maxrate= setting by god knows how much and jams the uprate (which on our home connections is around 5 Mbit/s). It'll take several minutes of constant lagging until all excess data has been uploaded at which point all viewers will be lagging behind by some considereable time as well.
I've tried bufsize= values of 2x, 1x, 0.5x, and 0.25xbitrate, none of them make any noticeable difference leading me to believe that bufsize= is somehow overriden to a (very) large value by OBS.
Looking at the pinned posts in this forum I've found just out about log files while writing this post, and the log pretty much confirms what I suspected:
22:47:54.684: Settings changed (outputs)
22:47:54.684: ------------------------------------------------
22:47:56.319: Failed to set threads=4
22:47:56.319: Failed to set maxrate=2560k
22:47:56.319: Failed to set bufsize=640k
22:47:56.319: If you're trying to set x264 parameters, use x264-params=name=value:name=value
22:47:56.324: Using muxer settings:
22:47:56.324: live=1
Putting those three options into the Muxer Settings box doesn't work either.
We also occasionally use ffmpeg with similar settings on the server machine itself and don't run into this problem, maxrate and bufsize work as expected then.
We're not using the "Streaming" setup as it doesn't allow selection of the container format (which needs to be matroska).
So, how do I actually use maxrate and bufsize in the recording context?
