<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Justin,<br>
<br>
I think I'm beginning to see what you've done.<br>
<br>
The way I built ffmpeg/ffplay was to "sh checkout.sh"<br>
in the soc/eac3 directory, "cd ffmpeg", configure with<br>
<br>
.... ./configure --enable-gpl --enable-pp --enable-swscaler
--enable-pthreads --enable-liba52 --enable-liba52bin --enable-libfaac
--enable-libfaad --enable-libfaadbin --enable-libmp3lame
--enable-libx264<br>
<br>
and then "make". I've used this method over the past several<br>
months with success.<br>
<br>
Can you tell me how I can successfully compile your most<br>
recent changes in order to play an EAC3 stream?<br>
<br>
Your help on this would be much appreciated.<br>
<br>
Also, do you have any thoughts on the video issue I mentioned<br>
earlier, namely where the stream 0 codec frame rate differs from
container frame rate<br>
resulting in a 90000 fps? It appears I have to somehow employ h264.<br>
<br>
Thanks much.<br>
<br>
Bill.<br>
<br>
<br>
Justin Ruggles wrote:
<blockquote cite="mid:477AB69E.10901@bellsouth.net" type="cite">
<pre wrap="">Bill Crowley wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Justin,
Thanks for the reply.
I realize that liba52 does not support E-AC3. My problem is that
the soc/eac3 changes made over the last day or so do not allow
for recognition of EAC3 streams now, whereas before that it did.
Whatever modifications/changes made just recently (i.e. - today)
seem to not be able to see the EAC3 streams, whereas (at least
through 20071230) the soc/eac3 compiled ffmpeg/ffplay correctly
saw them.
Any thoughts as to what changes made over the last day or so would
have caused the sudden inability to interpret EAC3 streams now?
Thanks,
Bill.
</pre>
</blockquote>
<pre wrap=""><!---->
I'm sorry. I should have been more clear. The way I've decided to
implement E-AC3 is as an extension to AC3, not as a separate codec. So
it does indeed recognize the E-AC3 streams as valid, it's just that the
AC3 decoder you've chosen to configure FFmpeg for does not support that
extension.
I do realize that you want to use liba52 for the plain AC3 and
libavcodec for the E-AC3, but it won't work that way. If you want to
decode E-AC3, do not use liba52.
-Justin
_______________________________________________
FFmpeg-soc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:FFmpeg-soc@mplayerhq.hu">FFmpeg-soc@mplayerhq.hu</a>
<a class="moz-txt-link-freetext" href="http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-soc">http://lists.mplayerhq.hu/mailman/listinfo/ffmpeg-soc</a>
</pre>
</blockquote>
<br>
</body>
</html>