> Date: Thu, 8 Nov 2007 11:12:49 +0900 > From: "Thomas Zander" <[EMAIL PROTECTED]> > > On 07/11/2007, Kevin Oberman <[EMAIL PROTECTED]> wrote: > > > 'acodec=aac' worked in the version now in ports, although that version > > failed to write the header with a floating point error. :-( > > Does this mean it has never been in a really useful state? > > Riggs >
The problem prior to rc2 turned out to be a bad faac port. Now that I have rolled it back to 1.25, the current rc1 port works again. Unfortunately, rc2 still says that 'aac' is not a valid lavcodec option. I can encode with '-oac faac' which really should use the same code under the hood, but it still seems like something is broken in rc2. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
pgpkuQ4r2hzos.pgp
Description: PGP signature
