The proposal describes the goal of the project “to develop a solution for the capture and playback of H264 video on mobile device.” The problem description states that transcoding from MPEG-2 or WMV to H.264 is resource intensive and is not suitable due to resource limitations on mobile devices.
Some of the points that the author should pay attention to while working on this project are:
· What are the advantages .Net provides over Java in speed and optimization. Java is platform independent; therefore it is more portable than .Net. The scope of the project could include any mobile device if Java were used.
· Would there be compatibility problems with devices that run Windows CE but don’t have capability for the .NET framework because they are older versions of Windows CE?
· The mobile device should have capability to playback H264 video. Does that capability exist? If devices playback only MPEG2 or WMV, a decoder on the device will be needed to decode the H264 stream.
Though comprehensive and ambitious, the requirements for this project are extensive. It might be helpful to narrow the scope of the project to simply capturing video through DirectShow transmitting (saved video) it using H264 to a mobile device for the device to play it back.
The project requirements mention transmitting live video to mobile devices as well. Some things to consider when transmitting live video over to mobile devices are:
· The frame rate, resolution and number of mobile devices that are viewing the live video at a given time. Such variable can greatly impact the quality of the live stream.
· There might be a need to decode the live stream at the mobile device end, some “optimal” buffering would be required so enhance the user experience.
· Connection, session management and resumption after failure should be handled as well.
References:
More information on DirectShow:
http://en.wikipedia.org/wiki/DirectShow
A commercially available codec to capture H264 video using DirectShow
http://www.leadcodecs.com/Codecs/LEAD-H264.htm