I also tested every single setting in the tmpgenc advanced tab to see if i can basically break the output and make it look like ffmpeg but that did not work either. I also exported the quantization matrix from tmpgenc and tested it with x264 and ffmpeg but it didn't help either.īy changing the custom quantization matrix in tmpenc the files still turn out like in the screenshot. I left 'slices' out since it has to do with the image being split up not the GOP's those where: refs 4, subme 9, chroma_qp_offset -4, lookahead_threads 1, bframes 2, b_pyramid 0, weightp 0, nal_hrd vbr I also matched all the ffmpeg x264 settings to the tmpgenc settings. I also tested this with x264 and results are similar to ffmpeg and far away from tmpgenc.įfmpeg x264 settings are the following: preset 'very slow', refs 5, keyint 100, keyintmin 51, bitrate 3500k, maxrate 10000k, bufsize 1120k
the top is ffmpeg and the bottom is tmpgenc. I've attached a screenshot to show the difference. I've been playing around with tmpgenc and i noticed a significant difference between my ffmpeg files and the tmpgenc files in how the GOP's are filled.
After the build completes, you’ll end up with the binaries inside ffmpeg-install folder (provided to the prefix parameter in configure). Obviously you can modify the parameters above as it fits your needs. configure -enable-static -disable-shared -disable-debug -disable-doc -disable-x86asm -enable-gpl -enable-libx264 -prefix=/Users/someuser/ffmpeg-install The last think you need to do, is to configure and build it. Now, download FFmpeg source codes from the following link and extract them somewhere on your computer. Here is what you need to run from Terminal: git clone Start by getting x264 source codes, configuring and then building them. This is why I thought I should gather them up into a single post for easier reference later on. I had to build FFmpeg with x264 support on macO statically, so I had to look around for a bunch of scattered commands.
0 kommentar(er)
