Texas Instruments TMS320 Series User manual

MPEG4/H263 Decoder on HDVICP2 and
Media Controller Based Platform
User’s Guide
Literature Number: SPRUGQ8
May 2018

IMPORTANT NOTICE
Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, enhancements, improvements and
other changes to its semiconductor products and services per JESD46, latest issue, and to discontinue any product or service per
JESD48, latest issue. Buyers should obtain the latest relevant information before placing orders and should verify that such
information is current and complete. All semiconductor products (also referred to herein as “components”) are sold subject to TI’s
terms and conditions of sale supplied at the time of order acknowledgment.
TI warrantsperformanceof its components tothe specifications applicable at the timeof sale, in accordance with thewarrantyin TI’s
terms and conditions of sale of semiconductorproducts.Testingand otherqualitycontroltechniquesare used totheextentTIdeems
necessary to support this warranty. Except where mandated by applicable law, testing of all parameters of each component is not
necessarily performed.
TI assumes no liability for applications assistance or the design of Buyers’ products. Buyers are responsible for their
products and applications using TI components. To minimize the risks associated with Buyers’ products and applications,
Buyers should provide adequate design and operating safeguards.
TI does not warrant or represent that any license, either express or implied, is granted under any patent right, copyright, mask work
right, or otherintellectual propertyright relatingto any combination,machine,or process in whichTI componentsorservicesareused.
Informationpublished by TI regarding third-partyproductsor services does not constitutealicenseto usesuchproductsorservicesor
a warranty or endorsement thereof. Use of such information may require a license from a third party under the patents or other
intellectual property of the third party, or a license from TI under the patents or other intellectual property of TI.
Reproduction of significant portions of TI information in TI data books or data sheets is permissible only if reproduction is without
alteration and is accompanied by all associatedwarranties,conditions,limitations,andnotices.TI is notresponsibleorliableforsuch
altered documentation. Information of third parties may be subject to additional restrictions.
Resale of TI components or services with statements different from or beyond the parameters stated by TI for that component or
service voids all express and any implied warranties for the associated TI component or service and is an unfair and deceptive
business practice. TI is not responsible or liable for any such statements.
Buyeracknowledges and agrees that it is solely responsible for compliance with all legal, regulatoryand safety-relatedrequirements
concerning its products, and any use of TI components in its applications, notwithstanding any applications-related information or
support that may be provided by TI. Buyer represents and agrees that it has all the necessary expertise to create and implement
safeguards which anticipate dangerous consequences of failures, monitor failures and their consequences, lessen the likelihood of
failuresthatmightcauseharm andtake appropriateremedial actions.Buyerwill fullyindemnify TI and itsrepresentativesagainstany
damages arising out of the use of any TI components in safety-critical applications.
Insome cases,TI componentsmay be promotedspecificallytofacilitatesafety-relatedapplications.Withsuchcomponents,TI’s goal
is to help enable customers to design and create their own end-product solutions that meet applicable functional safety standards
and requirements. Nonetheless, such components are subject to these terms.
No TI componentsare authorizedfor use in FDA Class III (or similar life-critical medical equipment)unless authorized officers of the
parties have executed a special agreement specifically governing such use.
Only thoseTI components which TI has specificallydesignatedas militarygrade or “enhanced plastic” are designed and intendedfor
use in military/aerospace applications or environments. Buyer acknowledges and agrees that any military or aerospace use of TI
components which have not been so designatedis solely at the Buyer's risk, and that Buyeris solely responsible for compliance with
all legal and regulatory requirements in connection with such use.
TI has specificallydesignatedcertaincomponentsas meeting ISO/TS16949requirements,mainly for automotiveuse. In any caseof
use of non-designated products, TI will not be responsible for any failure to meet ISO/TS16949.
Products Applications
Audio www.ti.com/audio Automotive and Transportation www.ti.com/automotiveAmplifiers
amplifier.ti.com Communications and Telecom www.ti.com/communicationsData
Converters dataconverter.ti.com Computers and Peripherals www.ti.com/computers
DLP® Products www.dlp.com Consumer Electronics www.ti.com/consumer-apps
DSP dsp.ti.com Energy and Lighting www.ti.com/energyClocks
and Timers www.ti.com/clocks Industrial www.ti.com/industrial
Interface interface.ti.com Medical www.ti.com/medicalLogic
logic.ti.com Security www.ti.com/security
Power Mgmt power.ti.com Space, Avionics and Defense www.ti.com/space-avionics-defense
Microcontrollers microcontroller.ti.com Video and Imaging www.ti.com/video
RFID www.ti-rfid.com
OMAP Applications Processors www.ti.com/omap TI E2E Community e2e.ti.com
Wireless Connectivity www.ti.com/wirelessconnectivity
Mailing Address: Texas Instruments, Post Office Box 655303, Dallas, Texas 75265
Copyright © 2014, Texas Instruments Incorporated

iii
Preface
Read This First
About This Manual
This document describes how to install and work with Texas Instruments’
(TI) MPEG4 Advanced Simple Profile Decoder implementation on the
HDVICP2 . It also provides a detailed Application Programming Interface
(API) reference and information on the sample application that
accompanies this component.
TI’s codec implementations based on the eXpress-DSP Digital Media
(XDM) standard and IRES interface. XDM is an extension of the
eXpress-DSP Algorithm Interface Standard (XDAIS). IRES are the
universal resource manager to handle different types of resource
requests by algorithms (codec). IRES keep the framework independent
and agnostic of different resource requests by different algorithms
Intended Audience
This document is intended for system engineers who want to integrate
TI’s codecs with other software to build a multimedia system based on
the HDVICP2 and Ducati Functional Simulator.
This document assumes that you are fluent in the C language, have a
good working knowledge of Digital Signal Processing (DSP), digital
signal processors, and DSP applications. Good knowledge of
eXpressDSP Algorithm Interface Standard (XDAIS) and eXpressDSP
Digital Media (XDM) standard will be helpful.
How to Use This Manual
This document includes the following chapters:
Chapter 1 - Introduction, introduces the XDAIS and XDM
standards. It also provides an overview of the codec and lists its
supported features.
Chapter 2 - Installation Overview, Describes how to install, build,
and run the codec.
Chapter 3 - Sample Usage, Describes the sample usage of the
codec.
Chapter 4 - API Reference, Describes the data structures and
interface functions used in the codec.
Chapter 5 –Frequently Asked Questions, Provides answers to
few frequently asked questions related to using this decoder.

Read This First
iv
Chapter 6 - Debug Trace Usage, Provides information on enabling
decoder dump debug trace and collection procedure by application.
Appendix A- Picture Format, Provides information on format of
YUV buffers provide to Decoder.
Appendix B- Meta Data Support, Provides information on writing
the MB info data into application provided buffers.
Appendix C- Error Handling, Provides information on handling the
erroneous conditions while decoding.
Appendix D- Parse Header Support, Provides information on parse
header support for MPEG4 streams.
Appendix E- Support for display delay, Provides information on
configuration of decoder to achieve desired display delay.
Appendix F- Support for padding Type, Provides information on
configuration of decoder to support padding type for non standard
resolution video clips (non multiple of 16 resolution )
Appendix G- Support for Dynamic change of resolution,
Provides information when given test stream is having dynamic
change in resolution
Appendix H- Support for drop of frame , Provides info, when first
frame of stream is missing from the sequence
Related Documentation from Texas Instruments
The following documents describe TI’s DSP algorithm standards such
as, XDAIS and XDM. To obtain a copy of any of these TI documents,
visit the Texas Instruments website at www.ti.com.
TMS320 DSP Algorithm Standard Rules and Guidelines (literature
number SPRU352) defines a set of requirements for DSP algorithms
that, if followed, allow system integrators to quickly assemble
production-quality systems from one or more such algorithms.
TMS320 DSP Algorithm Standard API Reference (literature number
SPRU360) describes all the APIs that are defined by the TMS320
DSP Algorithm Interoperability Standard (also known as XDAIS)
specification.
Technical Overview of eXpressDSP - Compliant Algorithms for DSP
Software Producers (literature number SPRA579) describes how to
make algorithms compliant with the TMS320 DSP Algorithm
Standard which is part of TI’s eXpressDSP technology initiative.
Using the TMS320 DSP Algorithm Standard in a Static DSP System
(literature number SPRA577) describes how an eXpressDSP-
compliant algorithm may be used effectively in a static system with
limited memory.
DMA Guide for eXpressDSP-Compliant Algorithm Producers and
Consumers (literature number SPRA445) describes the DMA
architecture specified by the TMS320 DSP Algorithm Standard

Read This First
v
(XDAIS). It also describes two sets of APIs used for accessing DMA
resources: the IDMA2 abstract interface and the ACPY2 library.
eXpressDSP Digital Media (XDM) Standard API Reference (literature
number SPRUEC8)
The following documents describe TMS320 devices and related support
tools:
Design and Implementation of an eXpressDSP-Compliant DMA
Manager for C6X1X (literature number SPRA789) describes a
C6x1x-optimized (C6211, C6711) ACPY2 library implementation and
DMA Resource Manager.
TMS320c64x+ Megamodule (literature number SPRAA68) describes
the enhancements made to the internal memory and describes the
new features have been added to support the internal memory
architecture's performance and protection.
TMS320C64x+ DSP Megamodule Reference Guide (literature
number SPRU871) describes the C64x+ megamodule peripherals.
TMS320C64x to TMS320C64x+ CPU Migration Guide (literature
number SPRAA84) describes migration from the Texas Instruments
TMS320C64x™ digital signal processor (DSP) to the
TMS320C64x+™ DSP.
TMS320C6000 Optimizing Compiler v 6.0 Beta User's Guide
(literature number SPRU187N) explains how to use compiler tools
such as compiler, assembly optimizer, standalone simulator, library-
build utility, and C++ name demangler.
TMS320C64x/C64x+ DSP CPU and Instruction Set Reference Guide
(literature number SPRU732) describes the CPU architecture,
pipeline, instruction set, and interrupts of the C64x and C64x+ DSPs.
The Future of Digital Video White Paper (literature number
SPRY066)
Related Documentation
You can use the following documents to supplement this user guide:
ISO/IEC 14496-10:2005 (E) Rec.- Information technology –Coding
of audio-visual objects –H.264 (E) ITU-T Recommendation
Abbreviations
The following abbreviations used in this document.
Table 1-1. List of Abbreviations
Abbreviation
Description
BIOS
TI’s simple RTOS for DSPs
CPB
Coded Picture Buffer

Read This First
vi
Abbreviation
Description
CSL
Chip Support Library
D1
720x576 resolutions in progressive scan
DCT
Discrete Cosine Transform
DMA
Direct Memory Access
DMAN
DMA Manager
DPB
Decoded Picture Buffer
EVM
Evaluation Module
GMC
Global Motion Compensation
HDTV
High Definition Television
IPCM
Intra-frame Pulse Code Modulation
IRES
Interface standard to request and receive
handles to resources
IVA
Image Video Accelerator
IEC
ISO
International Electro technical Commission
International standard organization
MB
Macro Block
MMCO
Memory Management Control Operation
MPEG
Moving Pictures Experts Group
MV
Motion Vector
NTSC
National Television Standards Committee
RMAN
Resource Manager
RTOS
Real Time Operating System
UUID
Unregistered Unique Identifier
VGA
Video Graphics Array (640 x 480
resolution)
VOP
Video Object Plane
XDAIS
eXpressDSP Algorithm Interface Standard
XDM
eXpressDSP Digital Media
YUV
Color space in luminance and
chrominance form

Read This First
vii
Text Conventions
The following conventions used in this document:
Text inside back-quotes (‘‘) represents pseudo-code.
Program source code, function and macro names, parameters, and
command line commands shown in a mono-spaced font.

Read This First
viii
Product Support
When contacting TI for support on this codec, quote the product name
(MPEG4 Advanced Simple Profile Decoder on HDVICP2 ) and version
number. The version number of the codec is included in the Title of the
Release Notes that accompanies this codec.
Trademarks
Code Composer Studio, DSP/BIOS, eXpressDSP, TMS320,
TMS320C64x, TMS320C6000, TMS320DM644x, and TMS320C64x+ are
trademarks of Texas Instruments.
All trademarks are the property of their respective owners.

ix
Contents
Read This First................................................................................................................iii
About This Manual..................................................................................................... iii
Intended Audience..................................................................................................... iii
How to Use This Manual............................................................................................ iii
Related Documentation from Texas Instruments.......................................................iv
Related Documentation..............................................................................................v
Text Conventions...................................................................................................... vii
Product Support........................................................................................................viii
Trademarks..............................................................................................................viii
Contents ..........................................................................................................................ix
Figures.............................................................................................................................xi
Tables.............................................................................................................................xiii
Introduction...................................................................................................................1-1
1.1 Overview of XDAIS, XDM and IRES ................................................................1-2
1.1.1 XDAIS Overview ................................................................................................1-2
1.1.2 XDM Overview ...................................................................................................1-2
1.1.3 IRES Overview...................................................................................................1-3
1.2 Overview of MPEG4 Advanced Simple Profile Decoder...................................1-5
1.3 Supported Services and Features....................................................................1-7
Installation Overview ....................................................................................................2-9
2.1 System Requirements....................................................................................2-10
2.1.1 Hardware..........................................................................................................2-10
2.1.2 Software...........................................................................................................2-10
2.2 Installing the Component ...............................................................................2-10
2.3 Before Building the Sample Test Application .................................................2-15
2.3.1 Installing Framework Component (FC)............................................................2-15
Also, ensure that the environment variable XDCROOT is set to the XDC installation
directory............................................................................................................2-16
2.3.3 Installing HDVICP2 and CSP library................................................................2-16
2.4 Building and Running the Sample Test Application........................................2-16
2.4.1 Building the Sample Test Application ..............................................................2-16
2.4.2 Running the Sample Test Application on OMAP4 ES1.0 ................................2-17
2.4.3 Running the Sample Test Application on DM816x DDR2 EVM REV-B...........2-18
2.5 Configuration Files.........................................................................................2-19
2.5.1 Generic Configuration File ...............................................................................2-19
2.5.2 Decoder Configuration File ..............................................................................2-19
2.6 Standards Conformance and User-Defined Inputs.........................................2-21
2.7 Uninstalling the Component...........................................................................2-21
Sample Usage................................................................................................................3-1
3.1 Overview of the Test Application......................................................................3-2
3.1.1 Parameter Setup................................................................................................3-3
3.1.2 Algorithm Instance Creation and Initialization....................................................3-3
3.1.3 Process Call.......................................................................................................3-4
3.1.4 Algorithm Instance Deletion...............................................................................3-6

x
3.2 Frame Buffer Management by Application.......................................................3-6
3.2.1 Frame Buffer Input and Output .........................................................................3-6
3.2.2 Frame Buffer Format..........................................................................................3-7
3.2.3 Frame Buffer Management by Application.........................................................3-7
3.3 Handshaking between Application and Algorithm ............................................3-8
3.4 Address Translations.......................................................................................3-9
3.5 Sample Test Application................................................................................3-10
API Reference................................................................................................................4-1
4.1 Symbolic Constants and Enumerated Data Types...........................................4-2
4.2Data Structures..............................................................................................4-12
4.2.1 Common XDM Data Structures........................................................................4-12
4.2.2 MPEG4 Decoder Data Structures....................................................................4-26
4.3 Interface Functions ........................................................................................4-30
4.3.1 Creation APIs...................................................................................................4-31
4.3.2 Initialization API................................................................................................4-33
4.3.3 Control API.......................................................................................................4-34
4.3.4 Data Processing API........................................................................................4-36
4.3.5 Termination API................................................................................................4-40
Frequently Asked Questions......................................................................................5-41
5.1 Code Build and Execution..............................................................................5-41
5.2 Issues with Tools Version ..............................................................................5-41
5.3 Algorithm Related..........................................................................................5-41
Debug Trace Usage.....................................................................................................5-43
6.1 Introduction....................................................................................................5-43
6.2 Enabling and using debug information...........................................................5-43
6.2.1 debugTracelevel...............................................................................................5-44
6.2.2 lastNFramesToLog...........................................................................................5-44
6.3 Debug Trace Levels.......................................................................................5-45
6.4 Requirements On The Application .................................................................5-45
Picture Format.............................................................................................................5-47
Meta Data Support.......................................................................................................5-55
Error Handling.............................................................................................................5-59
Parse Header Support...................................................................................................5-1
Support for Display Delay.............................................................................................5-1
Support for Padding type .............................................................................................5-3
Support for Dynamic Change in Resolution................................................................5-7
Support for Drop of frame ............................................................................................5-9
Support for Decoding only Intra frames using less memory..................................5-11

xi
Figures
Figure 1-1. IRES Interface Definition and Function Calling Sequence......................1-4
Figure 1-2. Flow diagram of the MPEG4 Advanced Simple Profile Decoder.............1-6
Figure 2- 1.Component Directory Structure..............................................................2-11
Figure 3-1. Test Application Sample Implementation.................................................3-2
Figure 3-2. Process call with Host release. .................................................................3-5
Figure 3-3. Interaction of Frame Buffers Between Application and Framework.......3-7
Figure 3-4. Interaction between Application and Codec.............................................3-8

xii
This page is intentionally left blank

xiii
Tables
Table 1-1. List of Abbreviations ......................................................................................v
Table 2-1. Component Directories .............................................................................2-11
Table 4-1. List of Enumerated Data Types...................................................................4-2
Table 6-2. Error Codes Information............................................................................5-59

xiv
This page is intentionally left blank

1-1
Chapter 1
Introduction
This chapter introduces XDAIS and XDM. It also provides an overview of
TI’s implementation of the MPEG4 Advanced Simple Profile Decoder on
the HDVICP2 and Media Controller Based platform and its supported
features.
Topic Page
1.1 Overview of XDAIS, XDM and IRES
1-2
1.2 Overview of MPEG4 Advanced Simple Profile Decoder
1-5
1.3 Supported Services and Features
1-7

Introduction
1-2
1.1 Overview of XDAIS, XDM and IRES
TI’s multimedia codec implementations are based on the eXpressDSP
Digital Media (XDM) standard. XDM is an extension of the eXpressDSP
Algorithm Interface Standard (XDAIS).
1.1.1 XDAIS Overview
An eXpressDSP-compliant algorithm is a module that implements the
abstract interface IALG. The IALG API takes the memory management
function away from the algorithm and places it in the hosting framework.
Thus, an interaction occurs between the algorithm and the framework. This
interaction allows the client application to allocate memory for the algorithm
and also share memory between algorithms. It also allows the memory to
be moved around while an algorithm is operating in the system. In order to
facilitate these functionalities, the IALG interface defines the following
APIs:
algAlloc()
algInit()
algActivate()
algDeactivate()
algFree()
The algAlloc() API allows the algorithm to communicate its memory
requirements to the client application. The algInit() API allows the
algorithm to initialize the memory allocated by the client application. The
algFree() API allows the algorithm to communicate the memory to be
freed when an instance is no longer required.
Once an algorithm instance object is created, it can be used to process
data in real-time. The algActivate() API provides a notification to the
algorithm instance that one or more algorithm processing methods is about
to be run zero or more times in succession. After the processing methods
have been run, the client application calls the algDeactivate() API prior
to reusing any of the instance’s scratch memory.
The IALG interface also defines three more optional APIs algControl(),
algNumAlloc(), and algMoved(). For more details on these APIs, see
TMS320 DSP Algorithm Standard API Reference (literature number
SPRU360).
1.1.2 XDM Overview
In the multimedia application space, you have the choice of integrating any
codec into your multimedia system. For example, if you are building a
video decoder system, you can use any of the available video decoders
(such as MPEG4, H.263, or H.264) in your system. To enable easy
integration with the client application, it is important that all codec’s with
similar functionality use similar APIs. XDM was primarily defined as an
extension to XDAIS to ensure uniformity across different classes of codec’s

Introduction
1-3
(for example audio, video, image, and speech). The XDM standard defines
the following two APIs:
control()
process()
The control() API provides a standard way to control an algorithm
instance and receive status information from the algorithm in real-time. The
control() API replaces the algControl() API defined as part of the
IALG interface. The process() API does the basic processing
(encode/decode) of data.
Apart from defining standardized APIs for multimedia codec’s, XDM also
standardizes the generic parameters that the client application must pass
to these APIs. The client application can define additional implementation
specific parameters using extended data structures.
The following figure depicts the XDM interface to the client application.
As depicted in the figure, XDM is an extension to XDAIS and forms an
interface between the client application and the codec component. XDM
insulates the client application from component-level changes. Since TI’s
multimedia algorithms are XDM compliant, it provides you with the flexibility
to use any TI algorithm without changing the client application code. For
example, if you have developed a client application using an XDM-
compliant MPEG4 video decoder, then you can easily replace MPEG4 with
another XDM-compliant video decoder, say H.263, with minimal changes
to the client application.
For more details, see eXpressDSP Digital Media (XDM) Standard API
Reference (literature number SPRUEC8).
1.1.3 IRES Overview
IRES is a generic, resource-agnostic, extendible resource query,
initialization and activation interface. The application framework defines,
implements, and supports concrete resource interfaces in the form of IRES
extensions. Each algorithm implements the generic IRES interface, to
request one or more concrete IRES resources. IRES define standard
interface functions that the framework uses to query, initialize,
activate/deactivate and reallocate concrete IRES resources. To create an
Client Application
XDAIS Interface (IALG)
TI’s Codec Algorithms
XDM Interface

Introduction
1-4
algorithm instance within an application framework, the algorithm and the
application framework agrees on the concrete IRES resource types that
requested. The framework calls the IRES interface functions, in addition to
the IALG functions, to perform IRES resource initialization, activation, and
deactivation.
The IRES interface introduces support for a new standard protocol for
cooperative preemption, in addition to the IALG-style non-cooperative
sharing of scratch resources. Co-operative preemption allows activated
algorithms to yield to higher priority tasks sharing common scratch
resources. Framework components include the following modules and
interfaces to support algorithms requesting IRES-based resources:
IRES - Standard interface allowing the client application to query and
provide the algorithm with its requested IRES resources.
RMAN - Generic IRES-based resource manager, which manages and
grants concrete IRES resources to algorithms and applications. RMAN
uses a new standard interface, the IRESMAN, to support run-time
registration of concrete IRES resource managers.
Client applications call the algorithm’s IRES interface functions to query its
concrete IRES resource requirements. If the requested IRES resource type
matches a concrete IRES resource interface supported by the application
framework, and if the resource is available, the client grants the algorithm
logical IRES resource handles representing the allotted resources. Each
handle provides the algorithm with access to the resource as defined by
the concrete IRES resource interface.
IRES interface definition and function-calling sequence depicted in the
following figure. For more details, see Using IRES and RMAN Framework
Components for C64x+ (literature number SPRAAI5).
Figure 1-1. IRES Interface Definition and Function Calling Sequence.

Introduction
1-5
1.2 Overview of MPEG4 Advanced Simple Profile Decoder
MPEG4 is a popular video coding algorithm enabling high quality
multimedia services on a limited bandwidth network. MPEG4 standard
defines several profiles and levels that specify restrictions on the bit-stream
and hence limits the capabilities needed to decode the bit-streams. Each
profile specifies a subset of algorithmic features that limits all decoders
conforming to that profile may support. Each level specifies a set of limits
on the values that may taken by the syntax elements in that profile. There
are 19 profiles defined for MPEG4 video coding standard.
Some important MPEG4 profiles and their special features:
Simple Profile:
oI-VOP (Intra-coded rectangular VOP, progressive video format)
oP-VOP (Inter-coded rectangular VOP, progressive video format)
oShort header (mode for compatibility with H.263 Codec’s)
oCompression efficiency tools (four motion vectors per macro block,
unrestricted motion vectors, Intra prediction).
oTransmission efficiency tools(video packets, Data Partitioning,
Reversible Variable Length Codes)
Advanced Simple Profile:
oI-VOP (Intra-coded rectangular VOP, progressive video format)
oP-VOP (Inter-coded rectangular VOP, progressive video format)
oB-VOP (bi-directionally predicted Inter-coded VOP)
oQuarter-pixel motion compensation.
oGlobal motion compensation.
oTwo quantization modes
oInterlace (tools for coding interlaced video sequences).
oShort header (mode for compatibility with H.263 Codec’s)
oCompression efficiency tools (four motion vectors per macro block,
unrestricted motion vectors, Intra prediction).
oTransmission efficiency tools(video packets, Data Partitioning,
Reversible Variable Length Codes)
The input to the decoder can be MPEG-4, short header specific encoded
bit-stream in the byte-stream syntax. Each byte-stream contains sequence
of syntax structure like, VOS (Video object sequence), VO (Visual object),
VOL (Video Object layer), VO(Video object),GOV(Group of VOP) and
VOP(Video object plane. All the above syntax structures have their own
length defined by the standard and also some of them may or may not be
present in encoded streams. Each VOP will be containing Intra, Inter, MV
data for decoding and reconstructing the frame.
Intra coded data: - Spatial prediction mode (AC DC Co-efficient
prediction from neighboring intra MB/BLOCKS) and prediction error
data that subjected to DCT and later quantized.

Introduction
1-6
Inter coded data: - Motion information (Motion vector) and residual
error data (differential data between two frames) that is subjected to
DCT and later quantized.
The decoder re-constructs an Intra frame by spatial intra-prediction
specified by the mode and by adding the prediction error. In case of inter
coding, the decoder reconstructs the frame by adding the residual error
data to the previously decoded picture, at the location specified by the
motion information (Motion vector). The output of the decoder is a YUV
sequence, which is of 4:2:0 semi planar format(Y is a single plane and the
Chroma data –Cb and Cr are interleaved to form the other plane).
Figure 1-2. Flow diagram of the MPEG4 Advanced Simple Profile Decoder.
From this point onwards, all references to MPEG4 Decoder means MPEG4
Advanced Simple Profile Decoder only.
Inverse
Quantization
Inverse DC &
AC prediction
Variable
Length
Decoding
Inverse
Scan
Inverse DCT
Coded Data
(Texture)
MPEG4 BIT-STREAM
Coded Data
(Motion)
Motion
Decoding
Motion
Compensation
Used only in P-Block decoding
Used only in I-Block decoding
QFS[n]
PQF[v] [u]
QF[v] [u]
F[v] [u]
F[y] [x]
D[y] [x]
P[y][x]
+
+
MEMORY
(previous VOP)
MEMORY
(neighbor
blocks)