Intel® Integrated Performance Primitives
Deliberate problems developing high-performance vision, signal, security, and storage applications.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
6814 Discussions

H.264 encoder structure and process

tgoh27
Beginner
‎05-29-2008 08:54 PM
442 Views

Hi,

I'm studying to video encoder, especially H.264/AVC.

I read a source code of H.264 encoder in sample code of IPP v5.3.

In, sample code, umc_video_enc_con.exehave many components, such as H264, H263, DV100, MPEG4, and so on...

As I understand, when I execute umc_video_enc_con.exe with any .cif sequence file, this .exe file read .cif file and some arguments.

And then proper component of encoder, like as H264 or MPEG4, loaded and encode .cif file.

Is this right....?

However, I couldn't understand structure and process of .exe file and h264 encoder source code.

Could I get some information of umc_video_enc_con.exe file and H.264 code's structure and process or analysis information?

Please let me get some helps.

Thanks,

TG

0 Kudos

Link Copied

1 Reply
Vladimir_Dudnik
Employee
‎05-30-2008 05:01 AM
442 Views

I thought there is description of command line options in sample's readme.htm file. Anything wrong with this on your side?

Vladimir

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.