MEncoder Issues (Updated 20 Apr 2011)

[Raptor399]

Thanks for keeping the MPlayer devs informed!

[SubJunk]

BTW Raptor, do you want my patch for your OS X build?

[Raptor399]

BTW Raptor, do you want my patch for your OS X build?

Sure, I'd love to keep the OS X build as close to the Windows build as possible. Where can I find the patch?

Although you mention a SVN revision number for FFmpeg and we compile it from Git based on a date. I'm not entirely sure what to do with that on the OS X side.

[SubJunk]

Attached is the patch I use. I don't build FFmpeg so I don't know about that. I do know that a recent update causes a bug with PMS, at least in Windows, so I'm not updating it until that's fixed.

[Raptor399]

Bah, I can't get mencoder to build any more for some reason - with or without patch.

Code: Select all

Undefined symbols for architecture i386:
  "_VDADecoderDecode", referenced from:
      _ff_vda_decoder_decode in libavcodec.a(vda.o)
  "_VDADecoderCreate", referenced from:
      _ff_vda_create_decoder in libavcodec.a(vda.o)
  "_VDADecoderDestroy", referenced from:
      _ff_vda_destroy_decoder in libavcodec.a(vda.o)
  "_kVDADecoderConfiguration_Width", referenced from:
      _ff_vda_create_decoder in libavcodec.a(vda.o)
  "_kVDADecoderConfiguration_Height", referenced from:
      _ff_vda_create_decoder in libavcodec.a(vda.o)
  "_kVDADecoderConfiguration_SourceFormat", referenced from:
      _ff_vda_create_decoder in libavcodec.a(vda.o)
  "_kVDADecoderConfiguration_avcCData", referenced from:
      _ff_vda_create_decoder in libavcodec.a(vda.o)
ld: symbol(s) not found for architecture i386
collect2: ld returned 1 exit status
make: *** [mplayer] Error 1
Fatal error occurred, aborting build.

[SubJunk]

Sometimes FFmpeg revisions cause MPlayer to break so it can take a few days for MPlayer to catch up. I don't know if that's what happened here but it's my guess

[Raptor399]

Sometimes FFmpeg revisions cause MPlayer to break so it can take a few days for MPlayer to catch up. I don't know if that's what happened here but it's my guess

That is true, but that wasn't the case here. I had to add --disable-vda to the FFmpeg configure line to overcome the problem.

Most problems building arise because I build for the "i386" architecture. Builds tend to go more smoothly if I build for "x86_64".

I'm wondering... Are there still 32 bit i386 Macs out there running OS X 10.6+? Isn't 10.6+ completely 64 bit anyway?
In other words: is compiling for "i386" really worth the hassle? It might even be detrimental for the performance on current Macs, so I would rather compile for "x86_64" if that is better.

Oh, and committed the new binaries (i386) in r984.

[SubJunk]

Ah cool, nice one

[macfixme]

Sometimes FFmpeg revisions cause MPlayer to break so it can take a few days for MPlayer to catch up. I don't know if that's what happened here but it's my guess

That is true, but that wasn't the case here. I had to add --disable-vda to the FFmpeg configure line to overcome the problem.

Most problems building arise because I build for the "i386" architecture. Builds tend to go more smoothly if I build for "x86_64".

I'm wondering... Are there still 32 bit i386 Macs out there running OS X 10.6+?

Sure enough. Quite a lot, anything that didn't qualify for 10.7 Lion is still running 32 bit kernels anyway.

Isn't 10.6+ completely 64 bit anyway?

10.7+ is 64bit only.

In other words: is compiling for "i386" really worth the hassle? It might even be detrimental for the performance on current Macs, so I would rather compile for "x86_64" if that is better.

Why not dual architecture, i.e. i386 + x86_64?

[Raptor399]

In other words: is compiling for "i386" really worth the hassle? It might even be detrimental for the performance on current Macs, so I would rather compile for "x86_64" if that is better.

Why not dual architecture, i.e. i386 + x86_64?

You're welcome to change the build-pms-binaries.sh for that. There's already enough compilation pain for one architecture in there, let alone for unified builds. I'm not going to touch that with a 10 foot pole. But you are welcome to give it a shot and post the result.