Question / Help An unspecified error occurred while recording
- Thread starter dims
- Start date
koala
Active Member
By using the custom output (ffmpeg) output, you're basically on your own. There are so many combinations of configuration options, nobody can say if the output will be valid or not. Generally, you work out ffmpeg parameters by consulting the ffmpeg documentation first and after that by trial and error.
In your case, I guess ffmpeg refuses to put h.264-encoded frames or aac-encoded audio frames into a mpegts transport stream, or the bitrate is too high. I once was successfully able to broadcast a obs output with mpegts container format by choosing mpeg2video as video encoder and mp2 as audio encoder.
It helps if you uncheck "Show all codecs", because this will remove all codecs from the drop down list that are incompatible with the container format.
In your case, I guess ffmpeg refuses to put h.264-encoded frames or aac-encoded audio frames into a mpegts transport stream, or the bitrate is too high. I once was successfully able to broadcast a obs output with mpegts container format by choosing mpeg2video as video encoder and mp2 as audio encoder.
It helps if you uncheck "Show all codecs", because this will remove all codecs from the drop down list that are incompatible with the container format.
dims
New Member
I don't understand, how to conslult ffmpeg documentation here. What to look there? If OBS calls ffmpeg command line utility and it returns error, why not print this error into error message instead of "Unknown"? Why not to print ffpeg command line so I be able to try it standalone? These combinations of parameters I took from another post here, where it was declared as "working"
koala
Active Member
Probably one of the video properties is beyond the specification of the configured video encoder. Try a lower bitrate, a lower resolution or a lower fps.
Unfortunately, OBS doesn't transport the ffmpeg error codes. It comes with integrated ffmpeg, it doesn't call a command line version.
The parameters still apply, though. You can enter any desired parameters into the "Video Encoder Settings (if any)" line in the format keyword=value.
Documentation for ffmpeg:
https://ffmpeg.org/documentation.html
https://ffmpeg.org/ffmpeg-codecs.html
https://ffmpeg.org/general.html
Unfortunately, the only way to get about all of the options for your platform into one long list is to install a recent command line version of ffmpeg and call "ffmpeg -h full". Have fun with that.
Unfortunately, OBS doesn't transport the ffmpeg error codes. It comes with integrated ffmpeg, it doesn't call a command line version.
The parameters still apply, though. You can enter any desired parameters into the "Video Encoder Settings (if any)" line in the format keyword=value.
Documentation for ffmpeg:
https://ffmpeg.org/documentation.html
https://ffmpeg.org/ffmpeg-codecs.html
https://ffmpeg.org/general.html
Unfortunately, the only way to get about all of the options for your platform into one long list is to install a recent command line version of ffmpeg and call "ffmpeg -h full". Have fun with that.