![]() That said, I had interpreted his post to primarily be about Matroska. x264 is one specific implementation of the H.264 standard -) You can specify to use TONS of b-frames, which will bring even the best computers to their knees.Īctually, it is. You can see how that might require more RAM and more CPU to decode while saving disk space. B-frames, for example, describe the content of the current frame in terms of the differences between the last frame and the next frame. Hell, the standard defines things like "Predictive lossless coding", and 10 bit color depths, neither of which is likely supported by your playback program of choice. Basically, profiles like "baseline", "main", "extended", etc define which techniques will be used and to what degree when compressing the video, then it's up to the encoder to limit its self to those and decide how to go about things. I would go so for as to call x264 a suite of video compression techniques with defined standard implementations. (While kind of dickish,) TM was talking about x264 having lots of tweakable parameters, many of which increase decoding power needed. You may even be able to improve playback by remuxing troublesome videos. ![]() The de facto standard for muxing into the Matroska container is mkvtoolnix. The problem is likely some very immature software available for Windows to allow for DirectShow output being used by people who don't know any better. There isn't much to "tweak" in the container if you're using standard tools for working with it. There we go! While MKV is an open standard and the x264 videos typically included within this container are also based on an open standard, people who produce MKV x264 videos frequently tweak the living hell out of the standard and stretch it out as far as it can go from a technical standpoint.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |