Hi! I'm slowly introducing libavformat support in import_ffmpeg, so future import capabilities will be GREATLY enhanced, almost like import_mplayer.
Implementing the import module itself is quite straightforwarded, but enhancing importing without enhancing probing as well is very little useful since figure out stream parameters is pretty annoying. There are a couple of issues 1) we (will) have two catchall importers, import_mplayer and import_ffmpeg. Same for probing routines. How those two should interact? Please also take in mind that import_ffmpeg can eat quite happily almost all formats/codecs already handled by specifim modules: think to import_dv or import_mp3 (if this isn't true it will be true into near future). 2) same as above for probing routines; I've no a precise plan so far. I've only some thoughts: - mplayer can digest/probe even more (or sometimes more reliably) formats/codecs than ffmpeg, but ffmpeg has a much better integration (no fifos, no external processes, no external dependencies...) So, IMHO ffmpeg should be always preferred on mplayer. Mplayer should be used as very last resort or just ignored unless user selects it explicitely. - it's probable that ffmpeg always does a better job than our code in probing and/or demuxing and/or decoding, but I still like to prefer specific modules (import_mpeg2/mp3 and stuff) - same as above for probing routines Last (but related) topic: better to have a specific identifier for every format/codec handled by ffmpeg or to use just one tag like for mplayer? Comments? Opinions? -- Francesco Romani - Ikitt ['people always complain, no matther what you do'] IM contact : (email first, Antispam default deny!) icq://27-83-87-867 known bugs : http://www.transcoding.org/cgi-bin/transcode?Bug_Showcase tiny homepage : http://fromani.exit1.org (see IDEAS if you want send code!)
