Difference between revisions of "FFmpeg Summer Of Code 2007"

From MultimediaWiki
Jump to navigation Jump to search
(missed an equal)
Line 117: Line 117:
Do you think some code in ffmpeg could run faster? We would love to get some faster decoders or encoders.
Do you think some code in ffmpeg could run faster? We would love to get some faster decoders or encoders.


This requires some ASM skills and using timer code to benchmark.
Speedups needed in:
h264 decoder


=== Review/fix some FFmpeg patches ===
=== Review/fix some FFmpeg patches ===
insert FFmpeg patch list here.
insert FFmpeg patch list here.

Revision as of 13:23, 7 March 2007

Google is sponsoring their third annual Summer of Code for the summer of 2007. This entails sponsoring students to work on assorted open source projects as well as sponsoring mentors in those same projects. Everyone wins.

FFmpeg was a Summer of Code participant in the summer of 2006 (here is the corresponding Wiki page) and hopes to be accepted again this year.

Mike Melanson (mike -at- multimedia.cx) is the administrator and main point of contact for matters relating to the FFmpeg Summer of Code.

How to apply

Before you can apply make sure you are qualified enough to apply. Last year 50% of the applicants weren't qualified for the task they applied for.

  • You have to know how to program in C fairly well.
  • You have to submit a patch that fixes a bug or adds a feature to FFmpeg. By doing that we will know that you are qualified for the task or not. On this page there is a list of Small Tasks that can be done.

Current Status

  • March 5-12, 2007: Application period for mentoring organizations.
  • March 6, 2007: Mike Melanson submitted FFmpeg mentoring application.

Waiting for acceptance...


Project Proposals

Overview

Qualifications for a good Summer of Code proposal:

  • discrete, well-defined, modular
  • comprised of a series of measurable sub-goals
  • based on open specs that are available free of charge
  • based on complete specs

An example of a good proposal is the implementation of a decoder or demuxer for an as yet unsupported multimedia format, or an encoder or muxer for a format that can already be demuxed/decoded by FFmpeg.

An example of a less desirable proposal is one that's not as measurable, such as refactoring APIs. Bad proposals tend to be ones that would require touching a lot of core code.

To re-iterate:

  • Localized/isolated code projects = good
  • Global code refactoring = bad

JPEG2000

Monkey's Audio Decoder

QCELP Decoder

Mentor: Benjamin Larsson

E-AC3 Decoder

GSM Decoder

Dirac Decoder

Dirac Encoder

i263 Decoder

VP6 Encoder

NUT Muxer

Matroska Muxer

MPEG TS/DVB Muxer

PAFF decoding for H.264/AVC

MXF Muxer

Finish AAC decoder and land it in FFmpeg

RV30/RV40 decoders

(contingent on near-term reverse engineering efforts)

Small tasks

TGA encoder

TIFF encoder

Bethsoft VID demuxer

Vivo demuxer


IFF/8SVX 8-bit audio demuxer

Optimize some code

Do you think some code in ffmpeg could run faster? We would love to get some faster decoders or encoders.

This requires some ASM skills and using timer code to benchmark.

Speedups needed in: h264 decoder

Review/fix some FFmpeg patches

insert FFmpeg patch list here.