Just thought I'd throw up a quick note to say that I have
successfully compiled, and tested, the last transcode tarball on OSX
10.4.6. I've reviewed the archives and haven't noticed very many Mac
users and those I did find had lots of questions on how to compile this.
Transcode has lots of dependencies, so I used darwinports to install
the necessary libraries. To get a good install that actually worked,
I needed the following ports installed:
ffmpeg @0.4.9-pre1_0+lame+xvid (notice the +lame and +xvid variants)
jpeg @6b_1
lame @3.97b2_0
libdvdread @0.9.4_0+libdvdcss
libiconv @1.10_1+darwin_8
libmpeg2 @0.4.0b_0+darwin_8
XviD @1.1.0_0
By default darwinports installs everything into /opt/local. I should
note that the ffmpeg portfile needs modifications to work since the
CVS repository at mplayerhq.hu crashed a few days ago. I changed it
to go snag the last CVS snapshot and build from there. I also needed
to add the "--enable-shared" to "extra-ldflags" in the portfile so it
would build the shared library. And lastly, the portfile choked when
passing "-d" to the linker so I removed that too and everything
compiled fine.
I used the following options with configure to get a good Makefile:
./configure --prefix=/opt/local/transcode --enable-altivec --with-
libavcodec-prefix=/opt/local --with-libmpeg2-prefix=/opt/local --with-
libdvdread-prefix=/opt/local --with-lame-prefix=/opt/local --with-
libjpeg-prefix=/opt/local
This installed everything into /opt/local/transcode. I added this to
my path and everything is peachy.
Performance is pretty good. I transcoded a VOB to mpeg4/mp3 with
ffmpeg and averaged 38 fps (on a G5 dual 2.0).
Any benefit to compiling transcode from CVS HEAD? Are there specific
branches considered relatively stable outside of the tarball release?
cr
Chuck Remes
[EMAIL PROTECTED]
www.familyvideovault.com (not yet live!)
