[FFmpeg-devel] MOD support for FFmpeg (My GSoC 2010 task starts tomorrow)
Fri May 28 12:54:46 CEST 2010
Michael Niedermayer a ?crit :
> I dont think the 1. and. 2. are exclusive, it surely should be possible
> to have a seperate lib and at the same time provide "mod" decoding support
> through the existing APIs.
Yes, that would be a very good approach, too.
> And we need to support it through existing apis because anything else would
> be quite inconvenient for applications.
> I am a bit undecided though about seperate lib or no seperate lib
Pure playback should be done this way, anyway.
It's just for people who want to write a tracker then using FFmpeg will
need are much more detailed API.
> about the existing APIs i do think they are sufficient for basic playback
> and transcoding.
For basic playback we won't actually need much, since it simply outputs
raw PCM audio.
> For video transcoding (mpeg2 for example) we support reusing the motion
> vectors from the source if the user wants.
> This works as the decoder returns a AVFrame that contains an array of
> motion vectors and the encoder takes a AVFrame as input
You mean making an union of the motion vectors which points in case of a
video to the mv's as previous and if it's
SAMPLE_FMT_COMPOSER/_SEQUENCER/_MOD it points to a similar structure for
MOD which the encoder can use from the decoder?
> I imagine that for mod something quite similar is possible to transcode
> them to another mod format.
> Its also a long standing feature request to make encode/decode_audio() work
> with AVFrame or a similar structure instead of int16_t*
For MOD, AVFrame could then point to an AVModule/AVSequencer/AVComposer
structure which contains everything else needed.
:-) Basty/CDGS (-:
More information about the ffmpeg-devel