On Sunday 04 Jan 2004 12:25 am, John Richard Smith wrote:Oh gosh yes, always include it without fail, there is also a -channel option with flags for 2channel,and surround sound, and an -aid 128 option (the number can be varied within limits, not shure why?) to aid detection of AC3 channels, tried them all at various times, spent many hours trying out the permutations, but the problem is within the code, not in user choice of options. Well that is my current assessment, but I'm entirely open to suggestions.
Now I have some
reason to suppose that it is an issue to do with how mencoder rips AC3
sound, which is dolby's surround sound. Sometimes it makes a dogs
breakfast of encoding and creating the all important index file. The
finished result, indeed the example given , the one that created the
core dump in question, finishes, even though it made a core dump, but
there is no index file, at least no index file that mplayer or any
ofther mpeg4 stand alone multiformat dvd player can find. The result is
that the stand alone players cannot play the CD's but mplayer can, as it
has the built in ability to create a temporary index file by means of an
index scan before it goes on to play it. It's annoying, but nothing
morethan that, that mplayer has to do this, but it's absolutely
critical that the stand alone players cannot as a result play the
mencoder ripped CD's created in this way.
You have tried the -idx flag to mencoder?
When you say search the code, do you mean the installed binaries or the unpacked tar ball ? or what ?
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.
For a more precise answer build the application as given on the How To Produce a Bug Report page.You mean recompile the unpacked tar ball with instrutions on debugging in the readme ?
Or possibly you are refering to mplayer website instructions ?
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 ?
or read the core file under gdb as you have been doing, it will probably give you a file name and line number.Sorry if I'm being a bit dense today.
Look at that line in the code and deduce what has gone wrong.
John
--
John Richard Smith
[EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
