Handbrake also works on the command line.Īnd lastly if you are allergic to the colossal power lurking in terminal.app there are GUIs for ffmpeg, like this or this. This uses the ffmpeg-internal encoder, but under AAC you will find info about more options.įfmpeg -i input -c:v libx265 -preset medium -crf 28 -c:a aac -b:a 128k Veryfast, faster, fast, medium, slow, slower, veryslow and placebo. If you choose ultrafast, the encoding process is going to run fast,īut the file size will be larger when compared to medium. The preset determines how fast the encoding process will be – at the expense of compression efficiency. The CRF of 28 should visually correspond to libx264 video at CRF 23, but result in about half the file size. In this example, we will use the following settings: placebo being so named because the tiny bit of difference it makes at the expense of greatly increased processing time is mostly in your head): Depending on how much time you have you could use anything from ultrafast to placebo to achieve results that vary in file size but with the same quality. I also used the slow preset which gives smaller file sizes. Here's the wiki entry I based my ffmpeg command on, it does a good job of explaining the options used (I'm a bit thingy about lossy compression so I wound up the quality settings somewhat. There are trash command line utilities, but that's beyond the scope of this answer. ![]() This is because if you delete files with the command line they disappear instantly, you don't get a second chance if you change your mind or make a typo. Note that this won't delete the files, it will move them to a new folder called for the trash. movs: cd "/the/path to/your/folder/"įfmpeg -i "$i" -c:v libx265 -preset slow -crf 25 -c:a copy "$" I haven't explored h.265 encoding much yet, but using settings I stole from the ffmpeg wiki here's how you'd encode a folder full of. ![]() Being a command line application it can be easily integrate into any batch process no matter how convoluted, with the benefit that you get to learn about the power of the command line while you're at it (worked for me). I don't consider myself to be very knowledgeable about all of this so I do not know what you mean by MBAFF and using commandline and the nightly build.FFMPEG of course. I really want to get this right, because each time encoding takes 20-26 hours of time to encode and that is with a Windows 7 PC with an Intel 17-4770 3.50 GHz Processor and 16GB of RAM. I am not sure if the Picture settings are important, but I left it alone. Detelecine, Deinterlace, Denoise, and Deblock all OFF. For Filters, the only thing I set was Decomb to Bob. I also set Trellis=2 in the x264 encoder options window at the bottom. = 10:QPRD In All Frames, Motion Est Range = 64, Partition Type = All, Trellis = Always. Method = Uneven Multi-Hexagon, Subpixel Motion Est. Frames and Max B-frames: 8, Adaptive B-frames = Optimal, Adaptive Direct Mode = Spatial, Motion Est. The settings I had were: Video Constant quality RF 20, Ref. What am I doing wrong and what settings should I have? I checked the file with Mediainfo and here is some information: I believe it is interlaced because Mediainfo is showing scan type: Interlaced. I have attempted to do this twice with handbrake where both times the video comes out choppy and doesn't "flow" with smooth motion. I want to convert it to mkv and preserve the quality as much to lossless as possible. ![]() Here is what I am attempting to do with a 4 hour 51 min.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |