Summer of Code 2009
Students please use the template at Summer of Code Applications when applying for a GSoC position.
Mentors please visit Summer of Code Mentoring and help us prepare our application as a mentoring organization.
- OpenMAX IL components for Ogg codecs
- Get skeleton patches upstream so players stop choking on it.
- Portable listening application for codec MOS/MUSHRA comparisons (Win32, MacOS, Linux; FF3.1 web application?).
- Proof of concept liboggplay-based media patch for Google's Chrome browser.
- Metavid improvements
- Firefox extension to record locally and stream to icecast.
- Firefox extension to support RTP for conferencing.
- also consider applying under Mozilla SOC org.
- mod_duration apache module to generate X-Content-Duration headers for Ogg files. (We should get people to use oggz_chop instead ... oggz_chop provides this functionality and more, is already relatively lightweight.) Perhaps this project could be more focused on packaging oggz_chop for other web servers like lightpd and maybe a fastCGI version and or maybe push for an mod_ogg to be adopted upstream in apache to improve distribution.
Detailed Project Descriptions
These ideas were suggested by various members of the developer community as projects that would be beneficial and which we feel we can mentor. Students should feel free to select one of these, develop a variation, or propose their own ideas. Here, ideally.
Proof of Concept liboggplay (html5 video) support in Chromium Browser
This project would focus on integrating support for liboggplay into chrome. This project would only need to be a proof of concept with the end result being some frames decoded in the browser. We have some direct contacts with people on the Chromium project in Google, but would expect the student mostly to work through the Xiph on Chromium online communities.
- Improve transcript import / export system:
- Wiki to SRT
- SRT to Wiki
- CMML to Wiki
- Extend oggz_chop or other tool for exporting transcript encapsulated in the ogg file.
The main focus of the project is on enabling video accessibility for Ogg in Firefox.
Problem / Intro
Captions, subtitles and other categories of time-aligned text are starting to become relevant to HTML5. In Ogg, we currently encapsulate such data in OggKate and can use SRT or Kate as input formats. Display of OggKate is currently supported in VLC and there are patches for various other media players. We now want to enable Web browsers to also deal with these time-aligned text tracks in those Web Browsers that support the HTML5 video tag.
Solution / Task
The project is adaptable to the qualifications of the student - it may consist in simply implementing a tool-chain for handling srt through OggKate, or it may go much further and include richer forms or time-aligned text such as audio annotations, Karaoke, ticker text, clickable text etc.
- Silvia Pfeiffer (nessy / ginger)
OpenMAX IL components for Ogg codecs
OpenMAX is a set of low-level C APIs for media codecs. It is specified by the Khronos Group (who also co-ordinate standards like OpenGL and OpenAL) and is used by many mobile devices, in platforms like Maemo and Android. As we'd like to encourage the use of free codecs on mobile and embedded devices, we want to develop a set of components using our codec libraries.
This project would implement free codec support for the lowest of the three OpenMAX layers, OpenMAX IL (Integration Layer). This is an interface to multimedia codecs implemented in hardware or software. It does not provide any interfaces for synchronized capture or playback of video and audio -- typically this is handled by higher OpenMAX layers, or by a framework like GStreamer.
Developing software OpenMAX IL components will allow application developers to implement Ogg support ahead of hardware support. It would also give hardware manufacturers a set of specific, well-defined goals for implementing Ogg support, with the understanding that the hardware components, when shipped with these software control APIs, will work in a variety of open source applications with minimal modifications.
Your project proposal should cover a reasonable portion of these steps:
- Implement generic Ogg mux/demux components (instead of single Ogg Vorbis component)
- Implement IL components for each codec (Theora, Dirac, Speex, CELT, FLAC)
- Implement GStreamer OpenMAX plugins for each codec
For details, including the motivation for this project and links to related projects, see Is OpenMAX important for Free Software?
- Conrad Parker (kfish)
XSPF import and export for Songbird
- Songbird cannot read XSPF playlists
- Songbird cannot write XSPF playlists
- Extend the development line of Songbird by XSPF read and write support.
- Read support should be able to tolerate most above-XML-level errors so users don't get frustrated with XSPF. That's the short version :-)
- Communication with upstream will be needed
- Sebastian Pipping (sping)
Python library / Online validator refactoring
- The Online XSPF Validator's code (Python >=2.4) is a procedural spaghetti mix of logic and presentation.
- There is no Python XSPF library around.
- Refactor the current validator code and separate it into a OOP XSPF reading library/API
- Adapt the validator to use former library
- Separate presentation and logic in validator code possibly involving a popular light-wight LGPLv3-compatible Python framework of your choice
- Sebastian Pipping (sping)
Conference bridge using CELT
When a conference takes place, the voice from all participants is often decoded, mixed together, and re-encoded. The goal of this project is to do better. We would like to have only partial decoding and re-encoding of CELT and reuse as much as possible from the already-encoded streams. This not only decreases the CPU load but also improves quality. The project is specific to the CELT codec, and during the course of the project, the student will learn the internals of the CELT codec.
Reference SIP client for CELT
The RTP profile for CELT is currently being written and to ensure that SIP clients with CELT support are really compliant, we would need a reference client that is 100% compliant with the RTP profile. This would provide:
- A reference to test for compatibility
- Some reference C code to copy directly