x264 Options syntax doesn't working
- Thread starter Tomani
- Start date
-
- Tags
- help x264 x264 options
what ever you try there will never work, OBS is internally 8 bit so there is no advantage to use 10 bit. And for the other stuff set your encoder x264 to very slow preset. But I don't think there is a CPU that will encode what you set there in real time.
Do you actually know what you do or did you just copy that from somewhere?
Do you actually know what you do or did you just copy that from somewhere?
koala
Active Member
Keep in mind you have 3 input fields for options in OBS: Muxer settings, video encoder settings, audio encoder settings. You need to enter your options in the corresponding options field. If an option is neither muxer, nor video, nor audio, they cannot be used. For example ffmpeg filters cannot be used, and global things like -stats or -threads.
If you call "ffmpeg -h full", you get a huge text output. Valid muxer options have to be in the corresponding "<muxer name> muxer AVOptions" section, valid video encoder options have to be in the corresponding "<video encoder> encoder AVOptions" section. Each option not in these sections is invalid for OBS usage.
If you call "ffmpeg -h full", you get a huge text output. Valid muxer options have to be in the corresponding "<muxer name> muxer AVOptions" section, valid video encoder options have to be in the corresponding "<video encoder> encoder AVOptions" section. Each option not in these sections is invalid for OBS usage.
Tomani
New Member
First of all, thanks for your replys. Appreciate your help.
@TryHD I want to start testing "from above" and balancing down. I know enough about x264 encode, but I want to test it because it is my methodology. I've seen many fallacies about x264 encodes, so I like to venture into various spectrums. I know it's a very heavy setup for streaming, but thanks for your worry.
@R1CH Like this?
@koala Hell huge text! So, with ffmpeg -help encoder=libx264 I get a few possibilities to use but just in record section. As I understand, I won't be able to use FFMPEG commands in a x264 streaming. Right? There is a way to go here? I've used x264 --fullhelp to build my example 1) properly, but I can't understand how the OBS interpret this.
@TryHD I want to start testing "from above" and balancing down. I know enough about x264 encode, but I want to test it because it is my methodology. I've seen many fallacies about x264 encodes, so I like to venture into various spectrums. I know it's a very heavy setup for streaming, but thanks for your worry.
@R1CH Like this?
I'm a bit confuse, 'cause the x264 syntax are like my 1) example above. I expected the x264 options would be the same as they are natively used.
@koala Hell huge text! So, with ffmpeg -help encoder=libx264 I get a few possibilities to use but just in record section. As I understand, I won't be able to use FFMPEG commands in a x264 streaming. Right? There is a way to go here? I've used x264 --fullhelp to build my example 1) properly, but I can't understand how the OBS interpret this.
Suslik V
Active Member
Neither syntax nor parameters set are correct for OBS.
Before claiming that something doesn't work, please start with Help section of the forum and use search to get your answers.
Example: https://obsproject.com/forum/threads/x264-keys-syntax.110984/post-420559
Also, it is unknown where you trying to apply these "sets". Usually, people attaching log-files to their posts. Where is yours?
obsproject.com
Before claiming that something doesn't work, please start with Help section of the forum and use search to get your answers.
Example: https://obsproject.com/forum/threads/x264-keys-syntax.110984/post-420559
Also, it is unknown where you trying to apply these "sets". Usually, people attaching log-files to their posts. Where is yours?
Please post a log with your issue! Here's how...
OBS Studio creates a log file each time you run it which contains very useful diagnostic information. Without a log file, it's much harder for any support volunteers to figure out problems and your post may be ignored. To upload a log file, go to the Help menu > Log Files > Upload Last Log...
I somehow doubt that looking at what you try to set there.
But since you have now the syntax
Code:
level=5.1 ref=16 bframes=8Tomani
New Member
@Suslik V Your example reply was the first in Google. Not working. I searched in forum and outside. Many divergent explanations and non-functional solutions. I didn't specify where I tested the x264 options because I thought it was obvious, sorry about that.
Log attached. This log from a quick record test is enough?
Log attached. This log from a quick record test is enough?
Suslik V
Active Member
Try this (now it is for CUSTOM FFmpeg OUTPUT): https://obsproject.com/forum/threads/ffmpeg-video-encoder-setting.77537/#post-329386
No changes in these part of code for a long, if I understand it right. Should work OK.
About your settings
No wonder, the log says x264 param: ... failed.
You mixed rate control methods and x264-params. This syntax will fail for FFmpeg too (OBS uses FFmpeg libs to encode media data).
OBS has special UI entries for Rate Control (obviously it shouldn't be overridden by the user settings), Bitrate, Keyframe etc. These basic controls where given UI in OBS to simplify settings for the users. So, no need to use keys that sets this controls again (crf=... when CBR was set in UI etc.).
And review your testing method - it is better to take small steps rather than make giant leap with short legs. One parameter, if it works - then next one, and so on. I think it is better in this situation.
Something like this (STANDARD recording, should work well, I skipped some controls that already exist in UI or cannot be used, like multi-pass encoding, color planes configuration, color depth etc.):
typed into OBS Output Advanced Settings field named x264 Options (separated by space)
level=5.1 threads=12 deblock=-1:1 bframes=16 b-adapt=2 ref=16 weightp=2 ratetol=0.1 qcomp=0.4 rc_lookahead=250 aq-mode=2 aq-strength=1.2 merange=64 me=umh direct=auto subme=11 partitions=all trellis=2 psy-rd=2.00:1.00 no-fast-pskipshould work for you.
Edit: the statement above is not absolute. Maybe I miss something. They (options) may not work well (or may not work at all). Sorry. I need some rest.
Last edited:
Tomani
New Member
@Suslik V thanks a lot, friend! Yesterday I spent my day working around this, did a huge reduce to settings (obviously). Recording it's okay, but live streaming it's a pretty awful due to plataform's bitrate limitations. Unfortunately, 6000kbps (Twitch) needs a compression that x264 can't delivery in real time. Do you have any recommendations for a balanced bigger compression x quality?
Suslik V
Active Member
On this forum NVENC was known as king of the encoding (1500-2000$ cards of course):
Question / Help - X264 or Nvenc?
I have a GTX 1080 ti and i7-7820x So should i record games with gpu or cpu? And if it's a Cpu intensive game like Destiny 2 or Battlefront 2 what should I record with?