1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 >BiaMovE documentation
</TITLE
8 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.79"></HEAD
42 >A short guide to video encoding using
<SPAN
86 >Video encoding basics
</A
124 >Chapter
1. Introduction
</H1
129 > (pronounced
"by-a-movie") is a graphical user interface to
<A
130 HREF=
"http://www.mplayerhq.hu/"
136 >, an extremely powerful and versatile cross-platform video encoding command-line utility. The problem with
<SPAN
139 > is that it is very complex and non-trivial to lay users.
142 > Adding to the complexity is the existence/non-existence of video/audio codecs, proprietary technologies and technical terminology related to audio and video. I had a very difficult time poring over the
<SPAN
145 > documentation to find specific options so I decided that while I was learning how to use it, why not create a GUI front-end for it?
165 >? Well, for one,
<SPAN
168 > can wrap around
<SPAN
171 > libraries using
<TT
174 >. Secondly I found using the
<SPAN
177 > command line much easier than
<SPAN
180 > and felt that it would be better to write a GUI around
<SPAN
198 > I wanted to mainly explore the codec-specific options of
<SPAN
201 >. I did so because video/audio codecs are extremely complex creatures. I cannot pretend that I understood everything I read in the
<SPAN
204 > manual pages. With
<SPAN
207 > I've tried to hide a little bit of the complexity, but without restricting the advanced user.
213 > is not a tool for the newbie though. It is just a thin (albeit useful) GUI wrapper to
<SPAN
228 >Check for the sanity of your
<SPAN
231 > configuration, nor does it check for codec availability on your setup.
</P
235 >Does not verify the sanity of your options. It just passes on your choices to the underlying
<SPAN
244 > Along the way, I've been bumbling along, discovering by trial and error, by experimentation and research, the proper way to mix video and audio codecs and produce valid video streams. If you are a newbie to video encoding and want to learn more, I suggest your read the section on
<A
246 >video encoding basics
</A
247 > and also study the
<SPAN
250 > manual pages in depth.
260 >Chapter
2. Video encoding basics
</H1
262 > Before you jump into video encoding, it's useful to understand a few video (and audio) related concepts. This will help you exploit the full power of
<SPAN
268 >. While most of the information here is common knowledge, I've documented some of my thoughts and discoveries in an easily accessible manner. However, before you dive in, I suggest you read the
<A
271 > section for definitions to common terms specific to digital audio/video technologies.
274 > If you are of the
"just want to rip my DVDs to my iPod" type, feel free to skip this section.
285 > For most people simply using a command-line tool like
<SPAN
288 > can be a daunting task. The
<SPAN
291 > manual page alone is scary enough, because it documents both the player
<SPAN
294 > as well as the encoder.
297 > Apart from the command-line itself, video and audio codecs are complex and tricky subjects in themselves. Apart from the variety of standards and formats adopted by different organizations (for instance,
<ABBR
309 > etc.), there exists hundreds of specifications within even these formats. Worse still, many of these standards are not compatible with each other and many video players, particularly hardware players, do not recognize open standards codecs (the
<SPAN
312 >™ is a case in point).
315 > Complicating it is the fact that not all muxers (container formats) work with all codecs and not all video and audio codecs are compatible with each other. Again, certain codecs provide very sane default parameters while other codecs require to be told exactly how to encode the underlying data. Last, but not least, some codecs are plain buggy and broken or don't work very well with
<SPAN
324 > cannot overcome these problems for you for the reasons already mentioned earlier. However reading these notes should help you avoid some of the pitfalls.
344 > Bitrate is the number of bits which encode the information per unit of time. It is usually measured in kilobits per second (kbit/s) or megabits per second (mbit/s). In practical terms, higher the bitrate, higher the quality of the information stored (whether video or audio).
347 > The best bitrate depends on several factors including desired video/audio quality versus size trade-off, the resolution of the video as well as the number of frames per second.
359 > Framerate is the number of frames per unit time. Frames may be audio or video frames. Think of a single frame as a still. Over the years, different video standards (
<ACRONYM
365 > etc.) have evolved and use standard framerates (
24.997 fps,
25 fps,
29.997 fps,
30 fps etc.) but theoritically any video can have any framerate or even variable framerates.
368 > The higher the framerate, smoother the animation. Usually
25 to
30 fps is more than enough for the human eye.