On Sunday 04 Jan 2004 10:07 am, John Richard Smith wrote:
Richard Urwin wrote:
You have tried the -idx flag to mencoder?Oh gosh yes, always include it without fail,
Not quite: On Saturday 03 Jan 2004 6:44 pm, John Richard Smith wrote: > Core was generated by `mencoder dvd://1 -ovc lavc -lavcopts > vcodec=mpeg4:vhq:vbitrate=1024 -oac mp3lam'.
No, Actually I did, it's gdb that omits it, don't know why. Here is the full line I used,
mencoder dvd://1 -ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=1024 -oac mp3lame -lameopts br=96:cbr -alang en -idx -o toystory1.avi
mencoder dvd://1 merely sets up which film to encode,
-ovc lavc -lavcopts vcodec=mpeg4:vhq:vbitrate=1024 says what codec to encode into and what bitrate to use
-oac mp3lame -lameopts br=96:cbr says encode the audio with lame at bitrate 96, and to maintain constant bit rate(cbr) as against vbr which means variable bit rate.
-alang en says use english sound track
-idx means make sure to do an index scan of the finished result.
and the rest gives a name to the film
This may help other to construct their own CL's.
But I always use -idx option because they are so important to replaying the result.
OK so I have to recompile with the debug options and then gdb the make file in directory sources.
On Sunday 04 Jan 2004 12:25 am, John Richard Smith wrote:When you say search the code, do you mean the installed binaries or the
Anyhow , how do you look up the address on the code ?You already have the function where the fault occurs so a simple search of
the source code will find that function.
unpacked tar ball ? or what ?
The source code, of course.
For a more precise answer build the application as given on the How ToYou mean recompile the unpacked tar ball with instrutions on debugging
Produce a Bug Report page.
in the readme ?
Or possibly you are refering to mplayer website instructions ?
Extract the source code from the tar ball. Recompile the source code with the flag on the ./configure command as given on the mplayer website documentation under how to submit a bug report.
http://www.mplayerhq.hu/DOCS/HTML/en/bugreports_what.html#bugreports_crash
Then when you run it under gdb,Or are you saying after the ./confure , and make, but before make
install, run gdb on the install file which lies somewhere in the source
directory ?
Not the install file, the application. The make command creates the application, make install just moves it into the right place. The documentation recommends running it before the make install, but probably only so the command is simpler: "gdb ./mplayer" rather than "gdb ./usr/local/bin/mplayer" or some such. It also avoids replacing your currently installed version. In your case I would imagine it will be "gdb ./mencoder" of course.
That will take me a little while , so I will have to come back on the rsult later.
John
--
John Richard Smith
[EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
