That’s just complicating things, and while it’s all fine and good for someone who isn’t “wet behind their ears” it’s not what I would personally recommend to someone just getting started. A GUI user wanting to use nightly builds (that includes unstable and undocumented code) also has to download the WindowsCLI. To quote their website in regards to nightly builds " They are only recommended for experienced users and developers". And on that note, someone who is new to encoding is going to want something fairly easy and stable. Once you get comfortable with this process you’ll know a lot more about how audio and video tracks are constructed in containers, and it will seem very straightforward.ĪCTUALLY, their last “official” release was in November (), and it only uses the x264 build r1347 (versus r1471 that the last official version of ripbot uses). You’ll note in mkvmerge the option to convert HD tracks to “normal” DTS or AC3 – choose this (because the Live can’t play the HD tracks). Then use mkvmerge to load in the Handbrake MKV file along with whatever audio tracks you stripped. Use txMuxer to strip out (demux) the audio tracks you want. So what you can do is to “get” the audio tracks and then remux them with the Handbraked MKV file (much, MUCH quicker than re-encoding – a matter of a few minutes). If for some reason you fail to do so (like you do, or perhaps you choose the wrong track by mistake, or later decide to have another track passed through) all is not lost.Īt that point you’d have a working MKV file (with some sort of audio track) but you’d still have your original tracks on the original blu-ray file (let’s say it’s one m2ts file to make it simpler). In the case of blu-rays we’re simply passing through the audio tracks (and in actuality, only the core DTS or AC3 of the HD audio). In that particular case you don’t need to re-encode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |