From 64e88c0501c955985255c38f253e235108acc644 Mon Sep 17 00:00:00 2001 From: diego Date: Thu, 5 May 2005 13:26:59 +0000 Subject: bandaid build fix git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@15352 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/xml/ru/codecs.xml | 143 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 143 insertions(+) (limited to 'DOCS/xml/ru') diff --git a/DOCS/xml/ru/codecs.xml b/DOCS/xml/ru/codecs.xml index 4cf0db9cae..4f3d435936 100644 --- a/DOCS/xml/ru/codecs.xml +++ b/DOCS/xml/ru/codecs.xml @@ -547,6 +547,149 @@ Apple, скомпилируйте MPlayer + + + +x264 + + +What is x264? + + x264 is a library for + creating H.264 video streams. + It is not 100% complete, but currently it has at least some kind + of support for most of the H.264 features which impact quality. + There are also many advanced features in the H.264 specification + which have nothing to do with video quality per se; many of these + are not yet implemented in + x264. + + + +Encoder features + CAVLC/CABAC + Multi-references + Intra: all macroblock types (16x16 and 4x4 with + all predictions) + Inter P: all partitions (from 16x16 down to + 4x4) + Inter B: partitions from 16x16 down to 8x8 + (including SKIP/DIRECT) + Ratecontrol: constant quantizer, constant bitrate, + or multipass ABR + Scene cut detection + Adaptive B-frame placement + B-frames as references / arbitrary frame + order + + + +Encoder limitations + No real RD + + + + + + +What is H.264? + + H.264 is one name for a new digital video codec jointly developed + by the ITU and MPEG. + It can also be correctly referred to by the cumbersome names of + "ISO/IEC 14496-10" or "MPEG-4 Part 10". + More frequently, it is referred to as "MPEG-4 AVC" or just "AVC". + + + Whatever you call it, H.264 may be worth trying because it can + typically match the quality of MPEG-4 ASP with 5%-30% less + bitrate. + Actual results will depend on both the source material and the + encoder. + The gains from using H.264 do not come for free: decoding H.264 + streams seems to have steep CPU and memory requirements. + For instance, on a 1733 MHz Athlon, a 1500kbps H.264 video uses + around 50% CPU to decode. + By comparison, decoding a 1500kbps MPEG4-ASP stream requires + around 10% CPU. + This means that decoding high-definition streams is almost out of + the question for most users. + It also means that even a decent DVD rip may sometimes stutter on + processors slower than 2.0 GHz or so. + + + At least with x264, + encoding requirements are not much worse than what you are used to + with MPEG4-ASP. + For instance, on a 1733 MHz Athlon a typical DVD encode would run + at 5-15fps. + + + This document is not intended to explain the details of H.264, + but if you are interested in a brief overview, you may want to read + The H.264/AVC Advanced Video Coding Standard: Overview and Introduction to the Fidelity Range Extensions. + + + + +How can I play H.264 videos with <application>MPlayer</application>? + + MPlayer uses + libavcodec's H.264 + decoder. + libavcodec has had at + least minimally usable H.264 decoding since around July 2004, + however major changes and improvements have been implemented since + that time, both in terms of more functionalities supported and in + terms of improved CPU usage. + Just to be certain, it is always a good idea to use a recent CVS + checkout. + + + If you want a quick and easy way to know whether there have been + recent changes to libavcodec's + H.264 decoding, you might keep an eye on + FFmpeg CVS repository's web interface. + + + + +How can I encode videos using <application>MEncoder</application> and <systemitem class="library">x264</systemitem>? + + If you have the subversion client installed, the latest x264 + sources can be gotten with this command: + + svn co svn://svn.videolan.org/x264/trunk x264 + + MPlayer sources are updated whenever + an x264 API change + occurs, so it is always suggested to use CVS + MPlayer as well. + Perhaps this situation will change when and if an + x264 "release" occurs. + Meanwhile, x264 should + be considered very unstable, in the sense that its programming + interface is subject to change. + + + x264 is built and + installed in the standard way: + + ./configure && make && sudo make install + + This installs libx264.a in /usr/local/lib and x264.h is placed in + /usr/local/include. + + With the x264 library + and header placed in the standard locations, building + MPlayer with + x264 support is easy. + Just run the standard: + ./configure && make && sudo make install + The configure script will autodetect that you have satisfied the + requirements for x264. + + -- cgit v1.2.3