Changes between Version 8 and Version 9 of SponsoringPrograms/Outreachy/2015-05


Ignore:
Timestamp:
Apr 1, 2015, 1:09:40 AM (4 years ago)
Author:
rogerdpack
Comment:

remove show for now

Legend:

Unmodified
Added
Removed
Modified
  • SponsoringPrograms/Outreachy/2015-05

    v8 v9  
    123123
    124124'''Backup Mentor:'''
    125 
    126 
    127 == directshow digital video capture ==
    128 
    129 '''Description:''' FFmpeg today includes support for windows directshow boxes via creating its own dshow graphs, an internal capture sink, etc.  This had support added recently for things like analog capture devices and analog TV tuners, but lacks support for digital TV tuner capture devices (ATSC etc.) https://msdn.microsoft.com/en-us/library/windows/desktop/dd695354(v=vs.85).aspx
    130 
    131 The first step will be DVB or ATSC, then vice versa, until it encompasses all the various digital capture options and all parameters for the same.
    132 
    133 The next step will be creating a libavfilter that can "pass through" frames to be encoded by a windows directshow encoder (for instance, there are some encoders typically only available in windows as dshow devices, like lagarith).
    134 
    135 Another step would be allowing for "DV capture" (i.e. from a live webcam) viz: https://msdn.microsoft.com/en-us/library/windows/desktop/dd373388(v=vs.85).aspx
    136 
    137 It would also be nice to refactor the directshow code so that it can take multiple inputs instead of just two today.  Input would look like "-i video=name=Webcam:show_input_video_options=true:framerate=25:audio=name=Audio Device:rate=44100:video=name=Webcam 2:show_input_options=false" etc.
    138 
    139 Finally, it would be nice to implement the libav "enumerate devices" API to at least show which devices exist on the system.  Initially return just the devices, then return the devices along with any options they have like "name=Capture device:input_crossbar_device_number=3" (one each for each option) as a follow on.
    140 
    141 '''Expected results:''' It will have the ability to capture video and audio from digital TV tuner devices.  This basically involves setting up the right filter graph and sending it a tuning request, and exposing the output to FFmpeg with the right codecs presented.
    142 
    143 '''Prerequisites:''' C coding skills, basic familiarity with git, desire to learn, access to windows native box, and eventually, a digital capture device.
    144 
    145 '''Qualification Task:''' Study all links on digital video capture graphs: http://stackoverflow.com/questions/14150210/having-trouble-capturing-digital-tv-using-directshow and create some test graphs using MSVC graphedit that capture digital video successfully.  Also add an IPersistStream option to and from file for the dshow code base for video basefilter (basically, you can call this to "serialize" it's setting to a file after setting them, and then read them from a file to get back to what they were set to previously).  This also involves a new command line option.
    146 
    147 '''Mentor:''' Roger Pack (rogerdpack@gmail.com) the dshow module maintainer.
    148 
    149 '''Backup Mentor:''' Ramiro Polla (''ramiro'' in #ffmpeg-devel on Freenode IRC, ramiro DOT polla AT gmail DOT com)
    150125
    151126