Context Navigation

2014

Timestamp:: Feb 4, 2014, 8:11:40 AM (13 years ago)
Author:: llogan
Comment:: fix subtitles image (refresh your browser cache); trivial nits

Legend:

: Unmodified
: Added
: Removed
: Modified

SponsoringPrograms/GSoC/2014

-              v22
+              v23
 [[Image(animated_PNG_example_bouncing_beach_ball.png, right, nolink)]]
 '''Description:''' FFmpeg currently does not support Animated PNGs, the goal of this project is to change that and add support. The little bouncing ball animation shown to the right is such a APNG file.
+'''Description:''' Add support for Animated PNGs. The little bouncing ball animation shown to the right is such an APNG file.
 Specification: https://wiki.mozilla.org/APNG_Specification
 …
 == Subtitles ==
+[[Image(subtitles_support.jpg, 300, right, nolink)]]
 '''Description:''' FFmpeg has been working on improving its subtitles support recently, notably by adding the support for various text subtitles and various hardsubbing (burning the subtitles onto the video) facilities. While the theme may sound relatively simple compared to audio/video signal processing, the project carries an historical burden not easy to deal with, and introduces various issues very specific to its sparse form.
 …
    - Enhance the rudimentary feature set of the encoder.
 '''Prerequisites:''' C coding skills, familiarity with git/source code control systems. A certain interest in audio coding and/or knowledge about the FFmpeg codebase could be beneficial.
+'''Prerequisites:''' C coding skills, basic familiarity with git. A certain interest in audio coding and/or knowledge about the FFmpeg codebase could be beneficial.
 '''Qualification Task''': Add floating point support to MPEG-4 ALS decoder
 …
            - Add support for VA-API: use the VA/DRM API for headless (no-X display) decoding, use libudev to determine the device to use
 '''Prerequisites:''' C coding skills, familiarity with git/source code control systems, hardware supporting VA-API.
+'''Prerequisites:''' C coding skills, basic familiarity with git, hardware supporting VA-API.
 '''Qualification Task:''' Anything related to the Hardware Acceleration (hwaccel) API, or to its related users. e.g. port VDPAU acceleration to use hwaccel, add JPEG decoding support with VA-API, etc.
 …
        - Add initial support for hardware accelerated encoding to the ffmpeg application
 '''Prerequisites:''' C coding skills, familiarity with git/source code control systems, hardware supporting VA-API for encoding.
+'''Prerequisites:''' C coding skills, basic familiarity with git, hardware supporting VA-API for encoding.
 '''Qualification Task''': Anything related to the Hardware Acceleration (hwaccel) API, or to its related users. e.g. port VDPAU acceleration to use hwaccel, add JPEG decoding support with VA-API, etc.
 …
 '''Qualification Task:''' See the FFmpeg bug tracker for AAC issues, fixing one of them or rebasing the existing incomplete BSAC decoder for current git head or fixing one or more existing bugs are possible qualification tasks.
 '''Prerequisites:''' C coding skills, familiarity with git/source code control systems, knowledge about transform based audio coding would be useful.
+'''Prerequisites:''' C coding skills, basic familiarity with git, knowledge about transform based audio coding would be useful.
 '''Mentor:''' TBA, possibly Baptiste Coudurier (bcoudurier at #ffmpeg-devel IRC)
 …
        - Add support for LBR extension
 '''Prerequisites:''' C coding skills, familiarity with git/source code control systems.
+'''Prerequisites:''' C coding skills, basic familiarity with git.
 '''Mentor:''' TBA, possibly Benjamin Larsson (merbanan at #ffmpeg-devel IRC)
 …
 == MXF Demuxer Improvements ==
 '''Description:''' FFmpeg's MXF demuxer needs a proper, compact way to map EssenceContainer ULs to WrappingKind. See ticket #2776. I wrote stuff in ticket #1916 which is also relevant.
 The gist of this is that essence in MXF is typically stored in one of two ways: as an audio/video interleave or with each stream in one huge chunk (like 1 GiB audio followed by 10 GiB video). Previous ways of telling these apart have been technically wrong, but has worked due to a lack of samples demonstrating the contrary.
 '''Expected results:''' The sample in ticket #2776 demuxes fine and there's a test case in FATE for it. The solution should grow libavformat by no more than 32 KiB.
 '''Prerequisites:''' C coding skills, familiarity with git/source code control systems.
 '''Qualification Task''': Investigate if there may be a compact way of representing the UL -> WrappingKind mapping specified in the official RP224 Excel document. The tables takes up about half a megabyte verbatim, which is unacceptable in a library as large as libavformat.
+'''Description:''' The MXF demuxer needs a proper, compact way to map !EssenceContainer ULs to !WrappingKind. See ticket #2776. Ticket #1916 also has relevant information.
+Essence in MXF is typically stored in one of two ways: as an audio/video interleave, or with each stream in one huge chunk (such as 1 GiB audio followed by 10 GiB video). Previous ways of telling these apart have been technically incorrect, but have worked due to a lack of samples demonstrating the contrary.
+'''Expected results:''' The sample in ticket #2776 should demux correctly, and add a test case in FATE. The solution should increase the size of libavformat by no more than 32 KiB.
+'''Prerequisites:''' C coding skills, basic familiarity with git.
+'''Qualification Task''': Investigate if there may be a compact way of representing the UL -> !WrappingKind mapping specified in the official RP224 Excel document. The tables take up about half a megabyte verbatim, which is unacceptable in a library as large as libavformat.
 '''Mentor:''' TBA, possibly Tomas Härdin (thardin at #ffmpeg-devel IRC)