#Mkv2mp4 forum full#
It's a smaller screen device and I'm encoding specifically for it (whichever it happens to be) so I don't care about it being full bitrate full resolution stuff even if the device makes the claim that it can play the file at full resolution, etc). I actually use 1000 Kbps for my video transcodes for several devices, looks fine to me.
If the G-Tablet chokes a bit or whatever, try the same encode but change the video encoding from Constant Quality to Average Bitrate of 1500 Kbps and leave everything else the same, encode and check the results.
I'd say toss the MKV into HandBrake, adjust the resolution up or down as required to get the 1024 pixel wide (or less, which will scale up a bit just fine), leave the setting for video encoding with x264 and the Constant Quality factor at 20 for a test encode (a single chapter from a DVD, a small video file, or even a chunk of a video clip based on the seconds, like an A-B section), the default AAC audio is 160 Kbps, and then see how that looks. No offense, but that imTOO encoder (and pretty much every single product that company spews out) is a piece of shit, in almost all respects. 1500 Kbps for a transcoded MKV (assuming it's h.264 format video and AAC audio at about 128-192 Kbps) is typical for such results.Īnd obviously, HandBrake is the tool to use, there's nothing else out that can really touch it for quality and usefulness (unless you're a command line wizard and can do all that stuff with the x264 CLI itself).
0 kommentar(er)
