Mplayer unexpected quit

[thoughton]

Ever since upgrading to 10.3.3 I've had this problem with Mplayer.

I launch ffmpegX, all is well. But when I drag-n-drop (or manually open) one particular file (a 900MB mov file with 3ivx video and mp3 audio), Mplayer will launch and attempt to do it's thing but instead it crashes with the message about notifying Apple.

This only happens with this one mov file. BUT prior to upgrading to 10.3.3 I used ffmpegX to convert this file successfully! (unfortunately I produced 3 mode 1 SVCD images instead of 2 mode 2s which is why I need to redo it).

The mplayer crash log says this: (along with pages of other stuff)

Command: mplayer
Path:    /usr/bin/mplayer
Version: ??? (???)
PID:     1670
Thread:  0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_INVALID_ADDRESS (0x0001) at 0xfffa000c

Thread 0 Crashed:

I have repaired permissions, re-downloaded mplayer (and other binaries) twice, upgraded to ffmpegX 0.0.9b, and I still have this problem with this one mov. It would be nice to solve it, it's my wedding video! (Still have a couple copies on DV tape so all is not lost, but it would be nice to figure out what's going wrong here).

I realise this isn't an mplayer forum, but does anyone have any suggestions??

TIA!

[major]

Enable "Terminal output".

[thoughton]

Do you mean the checkbox in ffmpegX? On 0.0.9b it seems to be called 'Keep Terminal Open' (or something like that, at work at the moment, no mac to check). Or do you mean some command-line switch in mplayer?

I will play with it some more when I get home. Thanks for the advice. I didn't try the ffmpeg checkbox before because mplayer would crash before I got to the point of clicking anything in ffmpegx.

[major]

If it crashes even before then there is some issue in your source file. Try to use Quicktime Player to Re-export it.

[thoughton]

Thanks Major. I was hoping it wouldn't be some prooblem with the file, after all it worked OK just 3 or so weeks ago, and since then it's just be sitting on my HD. However I was expecting the worst so, oh well, just have to reimport from DV and export again I guess.

I will try the QT reexpoort just on the off-chance it does something. Doesn't seem very likely to me

Thanks for your time!

[thoughton]

Just wanted to thank you again for the suggestion. After opening it in QTplayer I discovered the playback is now jerky and after a short while after I press 'play' QTplayer crashes. Oddly enough QT was still able to save it as a new standalone movie (as long as I didn't press play), but even more strangely the new version does exactly the same thing. At least I know it's the file and not my install!

Still a bit concerned that it got corrupted like that though. I'm off to check the rest of my HD!

[Wibbler]

Another way of capturing the program output, upen up a Terminal window, and type:

script

mplayer xxxxx.xxx

and after the crash, do a ctrl-d, and you'll end up with a file called typescript which has the contents of program output. (xxxxxx.xxx) is the movie filename)

paste the contents of typescript into a message..

W.I.Bler

[thoughton]

I never even considered running mplayer from the command line. Thanks for the suggestion! I couldn't find the typescript file at first so I just cut-n-paste from the terminal, but I later found it inside my tintin src folder.

mplayer is basically complaining about my "unknoown audio" (mp3) and saying mplayer crashed due to bad use of CPU/FPU/RAM. Then it suggests I recompile it with debug enabled. I think my movie file is just shot to peices

[Wibbler]

I'm from the Linux world, and the command-line is second nature to me.. ffmpegX is very nice and well done, but I like the extra control the command-line gives..

W.I.Bler