Please note as of Wednesday, August 15th, 2018 this wiki has been set to read only. If you are a TI Employee and require Edit ability please contact x0211426 from the company directory.

Encoding and decoding DVEVM clips

From Texas Instruments Wiki
Jump to: navigation, search

Encoding and decoding clips for the DM6446 DVEVM on a Windows host

Note! This topic discusses version 1.10 of the DVEVM, as it comes with codecs with a certain feature set. If you are trying to use these instructions with another version of the DVEVM, consult the codec data sheets to see which features are supported in your version and adapt the encoder parameters accordingly. The process described should be the same however.

We will show how to encode clips for use with the DVEVM decode demo, and how to play clips from the DVEVM encode demo on a Windows host. The instructions should work on a Linux host too, as the open source tools used are cross platform. The easiest platform to encode on is actually MacOS X because a very good interface (ffmpegX, see below) is available for the open source command line tools used in this doc.

Playback of DVEVM clips on a Windows host

You cannot use Windows Media Player to play the clips used by the DVEVM demos (unless plugins are available for download somewhere that lets you). This because the DVEVM demos are using elementary streams as opposed to transport streams. A full fledged multimedia application will use transport streams to facilitate (de)muxing of audio and video and other recovery and seek features, but the DVEVM demos only use elementary streams, which are essentially just the encoded frames stored one after the other in a file. An elementary stream can be extracted from a transport stream (like an AVI file) though, and a transport stream can be created around an elementary stream. See the tips and tricks section below for more information.

To play back the MPEG2 and H.264 elementary streams on a Windows (or Linux) host, the VideoLan player (, or VLC as it's often called, is preferred. It has an easy to use GUI. It does not however play back MPEG4 elementary streams.

Another option which plays back all elementary streams supported by the DVEVM is mplayer. Make sure you select the GUI version and download it from It is available for many operating systems, including Linux and Windows.

A shareware alternative for MPEG4 elementary streams is the Elecard MPEG Player available from

Encoding clips for use with the DVEVM demos and codecs

This section describes the process we went through when creating the "davinci effect" clips for the DVEVM. Depending on the nature of your raw content some parts may or may not be applicable.

To manipulate the raw video data we will use the VirtualDub application ( It can be downloaded from SourceForge using We used version 1.6.15.

VirtualDub can be extended through external plugins. Probably the biggest collection is through another project called AviSynth. This is a scripted technology that uses external DLLs that perform various conversions or I/O. Download the AviSynth installer from We used version 2.5.6a. There is a list of available filters at

As our "davinci effect" raw clips were originally in a MOV container we needed a plugin for this format. There is one available from

As the DVEVM 1.10 clips only support Top Field First (TFF) clips, a useful filter to convert to TFF from Bottom Field First (BFF) is available from

Once the raw data is in the correct format, we will use the open source command line tool ffmpeg to encode our clips. This is a command line tool with a lot of options and very little documentation, which can make it a little scary at first. Unfortunately we cannot seem to find a good and stable GUI front end for ffmpeg for Windows, but if you own a Mac you can use ffmpegX ( which is quite easy to use.

The ffmpeg application is a swiss army knife when it comes to video, and it has a lot of advanced options. You should be able to get clips which work with the DVEVM using the information in this document, but for more detailed information the application documentation is available from

Building ffmpeg for Windows is unnecessary as a prebuilt binary is available from (We used rev. 6830). Wherever you download ffmpeg from, execute ffmpeg -formats and make sure that the 'E' flag is set for xvid, mpeg2video and h264 under the Codecs list (signaling that encode is available for those algorithms), and 'E' is set for m4v, m2v and h264 under File Formats (signaling writing to these elementary stream types is available as options). The ffmpeg tool can be compiled with various support form other open source libraries, and the above flags are necessary to be able to encode the formats used in the DVEVM.

In order to get more control of the parameters used to encode our H.264 clips we use the x264 tool directly (as opposed to through ffmpeg). The homepage is and you can download a precompiled version from Make sure your x264 binary is compiled with AviSynth support by executing x264.exe --help. You should see the following:

Infile can be raw YUV 4:2:0 (in which case resolution is required),
  or YUV4MPEG 4:2:0 (*.y4m),
  or AVI or Avisynth if compiled with AVIS support (yes).

For MPEG4 we will use XviD (but invoke it through ffmpeg). It's homepage is If you want to install the codec (for use with VirtualDub for instance) you can download a precompiled binary from

For RPM based Linux you can find ffmpeg, XviD and x264 binary and source from But note that this can be a cumbersome install (unless you point yum at the freshrpms repository which is quite slick) as there are many dependencies. All dependencies should be available from that site though, it's just a little time consuming.

Manipulating the raw clip

VirtualDub prefers to work with AVI files, but can be extended through AviSynth to read and write MOV files (and others), see above for download details. You will want to save an AVI file as ffmpeg works well reading these, but depending on which file your original content is in you might have to apply various filters to VirtualDub or AviSynth (VirtualDub uses AviSynth to gain scripting capabilities).

The decoders shipped with the DVEVM 1.10 only support Top Field First (TFF). You can see if you are trying to play a Bottom Field First (BFF) clip using the demos, as there will be a noticeable studder. This is easier to observe on a CRT screen than on an LCD TV. If so you can apply the "ReverseFieldDominance" script downloaded above. The below AviSynth example loads a MOV file and applies the field switching filter and finally saves this back as a MOV file on the file system:


Load the script file, or the AVI file, into VirtualDub using File->Open Video File. You should now see two display windows in VirtualDub. The left one is showing the frames before the VirtualDub (not AviSynth!) filters are applied, and the right one is showing the frames after the filters have been applied. You can play the clip and preview the effects or filters you have selected by pressing the play button at the bottom of the application.

Now you can apply the VirtualDub filters from Video->Filters. Note that the AviSynth filters in your script file will be applied before the VirtualDub filters. If you are using a progressive codec like MPEG4 SP or H.264 BP you will likely want to deinterlace your content (if it is interlaced to begin with). Do this by selecting the "Add" in the filter window and adding the Deinterlacer filter (accept default parameters).

Some encoders, like x264, are picky about the data format of the raw clip. This can be changed using Video->Color Depth... and setting "Output format to decompressor / display to 4:2:0 planar YCbCr (YV12).

Now do File->Save as AVI... and write the file to disk. The raw video data is now ready to be encoded. If none of these steps were necessary, i.e. you already had the raw data in a file which ffmpeg accepts as input, your raw data was progressive (i.e. non-interlaced) or top field first, you don't need VirtualDub but can go straight to encoding the data below.

MPEG2 Main Profile

As the TI MPEG2 decoder supports most if not all main profile features, this procedure is quite simple:

ffmpeg -i raw.avi -vcodec mpeg2video -b 8000000 encoded.m2v

This example creates an 8Mbps MPEG2 Main Profile encoded elementary stream (encoded.m2v) from the raw.avi file. Note that there is no issue with your raw video file being interlaced, as MPEG2 Main Profile supports interlaced content.

MPEG4 Simple Profile

MPEG4 Simple Profile doesn't support interlaced content, and therefore you get a better quality encoded clip if you deinterlace the clip prior to encoding it (see above).

The open source XviD encoder gives good quality MPEG4 clips, so we will instruct ffmpeg to use XviD using:

ffmpeg -i raw.avi -vcodec xvid -b 4000000 encoded.m4v

This example creates an 4 Mbps MPEG4 Advanced Simple Profile encoded clip (encoded.m4v) from the raw.avi file. The encoded.m4v file will have to be renamed encoded.mpeg4 before being played with the DVEVM demos, as this is the file extension it expects.

Alternatively you can plug in XviD directly into VirtualDub using the instructions available at Note that you have to use Advanced Simple Profile @ Level 5' and h.263 profile when configuring XviD using the GUI to make DVEVM 1.10 compatible clips.

In order to get better control of the XviD encoding parameters you can use the xvid_encraw.exe example application which comes with XviD. For some reason this application is not provided with the precompiled versions of XviD we found, but it's available in the source package so you can compile it yourself. It's a little difficult to use however, so if you need more control the VirtualDub XviD integration is preferred.

H.264 Base Profile

H.264 Base Profile doesn't support interlaced content, and therefore you get a better quality encoded clip if you deinterlace the clip prior to encoding it (see above).

We will use the x264 utility directly in order to get better control of the encoding parameters. This tool is picky about it's input format, and you can set the format to YUV 420 in VirtualDub using the instructions above. Another way of accomplishing this is to use the AviSynth script support (which needs to be selected for inclusion when x264 is compiled):


Put the above code in a file (c:/input.avs) and execute the command below to get a 3Mbps H.264 Baseline Profile encoded clip (encoded.264) from the input file (c:/raw.avi).

x264.exe --level 3 --no-cabac -r 2 -p 2 -B 3000000 --progress --merange 64 -o c:\encoded.264 c:\input.avs

The most important parameters to make DVEVM 1.10 compatible clips are --no-cabac and --level 3. The rest can be tweaked.

Transcoding and other ffmpeg tips and tricks

If you have encoded content, like mpeg2, which you want to show in another format, like h.264, ffmpeg can transcode the data for you. Execute ffmpeg -formats and make sure the input file format and codec is marked with 'D' (decode) and that your destination file format and codec is marked with 'E' (encode).

Note! By transcoding the data you normally lose quality versus the original content and compared to encoding from raw content.

This for example transcodes from MPEG1 encoded content in an ASF file to xvid (mpeg4) for the dvevm demos:

ffmpeg -i mpeg1.asf -vcodec xvid -b 1000000 encoded.m4v

A good GUI front end in Windows for transcoding using ffmpeg is Super. There is some related information here: TI_DirectShow_Filters#Using_Super_to_create_video_clips_for_CEPlayer_on_WinCE

Another useful thing ffmpeg can be used for is to strip elementary streams out of their containers (transport streams). The file ffmpeg file formats m4v, m2v and h264 are elementary streams. This would for instance extract an m4v elementary stream from an AVI file by using the ffmpeg copy codec:

ffmpeg -i tranport.avi -v codec copy elementary.m4v

Now you should have an MPEG4 video elementary stream (note that this conversion will strip the audio) which you can play on the DVEVM using the demos.

Encoding hi-definition (1920x1080) clips for the DM6467 DVEVM

This section we will show how to create HD (1920x1080) H.264 and MPEG2 streams. These elementary streams are tried with DVSDK 1.40 GA decode demo application.

H.264 Base Profile

The original "davinci effect" clip is in a QuickTime container format, the video is encoded with dvh6 codec and two audio streams are in raw PCM format. ffmpeg is used to create base profile clips for DVSDK. ffmpeg ( provides lots of options to try out or manipulate a audio/video stream.

The original clip have initial 10 seconds of blank screen and silence. So we chopped off first 10 second of the clip. For H.264 BP we need to de-interlace the clip and the GOP size is to be set to 30. We also used ffmpeg’s two-pass feature. In the first pass the encoder saves information about each frame in a log file. In the second pass it uses the log file to allocate bits more effectively. This should result in a better quality output at a given bit-rate or a reduction in bit-rate at the same quality.

Following commands used to transcode the clip to a H.264 BP elementary stream.

ffmpeg.exe -deinterlace -i -y -ss 10 -an -pass 1 -r 29.97 -s 1920x1080 -aspect 16:9 -b 20000k -bufsize 25000k -g 30 -keyint_min 30 Spirit_of_Invention_1920x1080_30fps.h264

ffmpeg.exe -deinterlace -i -y -ss 10 -an -pass 2 -r 29.97 -s 1920x1080 -aspect 16:9 -b 20000k -bufsize 25000k -g 30 -keyint_min 30 Spirit_of_Invention_1920x1080_30fps.h264

If you want to run this clip with the decode demo application we need to change the file extension to .264.

MPEG2 Main Profile

For MPEG2 MP streams, you need to change the pixel format to 4:2:0 planar if the stream is not already in this format, so that the clip can be decoded using DVSDK decode demo application with default options. We can ran two pass ffmpeg with interlacing turned on.

Following commands are used to transcode the clip to a MPEG2 elementary stream.

ffmpeg.exe -i -y -ss 10 -an -pass 1 -r 29.97 -s 1920x1080 -aspect 16:9 -b 20000k -g 30 -keyint_min 30 -qmin 1 -qmax 31 -ilme -ildct -flags +ildct+ilme -top 1 -pix_fmt yuv420p davincieffect_1080i_30fps.m2v

ffmpeg.exe -i -y -ss 10 -an -pass 2 -r 29.97 -s 1920x1080 -aspect 16:9 -b 20000k -g 30 -keyint_min 30 -qmin 1 -qmax 31 -ilme -ildct -flags +ildct+ilme -top 1 -pix_fmt yuv420p davincieffect_1080i_30fps.m2v

Conversion from PNG files to H.264 BP stream

The open movie projects Elephants Dream, Big Buck Bunny provide entire movie as a series of PNG files.

Following steps can be followed to obtain an elementary stream out of the PNG files (Note: You need above 100GB of disk space, a fast PC). And this method is specific to Windows OS as we will use VirtualDubMod liner processing tool, which is not supported (currently) for any other OS.

From URL, download all 14315 PNG files and put in a directory say c:\BBB

Download and install VirtualDubMod from URL

Start VirtualDubMod.exe and in the GUI go to File>Open video file

Goto c:\BBB, where the PNG files were downloaded and open first video file. It will automatically load all PNG files.

Goto Video>Frame Rate. In Source rate adjustment change to 24 frames per second

Go to File>Save As then select options to save as uncompressed as AVI file say with name BigBuckBunny.avi

Now use ffmpeg to get the H.264 file: ffmpeg.exe -i BigBuckBunny.avi -y -r 29.97 -s 1920x1080 -aspect 16:9 -b 10000k -bufsize 15000k -g 300 -keyint_min 30 BigBuckBunny_1920x1080_30fps.h264

The simpler method will be to download 1080P clip available from their download link ( and convert it using ffmpeg to required format using methods described above. But the first method should produce relatively better quality stream.

Related Links