On Thursday 08 Jan 2004 11:04 am, John Richard Smith wrote:
Forced video codec: ffmpeg12
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Cannot find codec 'mpegvideo' in libavcodec...
VDecoder init failed :(
Cannot find codec matching selected -vo and video format 0x10000002.
Read DOCS/en/codecs.html!
My etc/codecs.conf contains:
videocodec ffmpeg2 info "FFmpeg MPEG 2" status working format 0x10000002 ; mpeg 2 fourcc mpg2 driver ffmpeg dll "mpeg2video" out YV12,I420,IYUV
Howabout yours? (That's etc in the source directories of course in my case.)
videocodec ffmpeg2 info "FFmpeg MPEG 2" status working format 0x10000002 ; mpeg 2 fourcc mpg2 driver ffmpeg dll "mpeg2video" out YV12,I420,IYUV
the same,
I build with libavcodec with the full package including the important ones.
If yours is missing maybe it's time to upgrade. Or, reading DOCS/en/codecs.html as suggested above, in the section on FFmpeg/libavcodec:
"If you use an MPlayer release you have libavcodec right in the package, just build as usual. If you use MPlayer from CVS you have to extract libavcodec from the FFmpeg CVS tree as FFmpeg releases are very rare. "
Sure but as far as the codecs are concerned they are the same except mine has all the inportant additional feature, if you've got them too then you added them somehow after the main install, I always include them in the build in the first place, but you have to get them seperate and add them to the CVS package.
ISTR, you built from CVS, while I'm looking at a release (1.0pre3)
Oh yes I quite accept that , if there is a way around the problem , lets do it, otherwise,
So, to sum up, yes it does seem to be a "read error confusion" in that mencoder is having problems handling the variable nature of DVD CD's and yes I do think it needs fixing.Needless to say that is beyond my abilities. Still, I can help identify the problem, and that is half the battle.
There's certainly a bug there, and therefore it needs fixing. But if you can work around it then it isn't going to be your problem. Why beat your head against something you've already found to be a wall. OTOH,
if you can't find a workaround then you need to be very careful to jump through all the hoops when you report the problem, including running the latest CVS code, no matter how stupid the hoops are.I quite agree.
Well yes, certainly, see , mplayer/mencoder is by it's very nature the kind of programme that will generate immense "enquiry" or "bug reporting", and I can see perfectly well they just don't have the time to deal with it all. I can understand that, so the way the game is played it is a case of, if you cannot present the problem in a nut shell, preferably with the answer, then don't bother us. So it's a case of can I work around it, or have I to present the problem as it is and prefereably with an answer. Sure, I'd like a work around, that's easier for me, but I don't know how to do even that at this time. However all this has not been bad for me, I'm getting to know some more about tracing bugs and how to look for them. It's pushing the envelope of my experience that bit further, and helping me to understand the developers lot. That cannot be bad , can it, and I thank you for your interest in my problem.
It took me 20 years to learn to welcome bug reports. Most programmers would prefer to dismiss them. (Although generally less so in the open source world.)
So what do we do next ?
John
--
John Richard Smith
[EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
