On Thu, 09 Jul 2009 10:45:11 -0400, Stephan Assmus <[email protected]>
wrote:
Forgot to mention, this is the output from ffplay -stats:
Input #0, mpegts, from '/Code/home/media/clips/00011.MTS':
Duration: 00:00:46.82, start: 1.000067, bitrate: 16190 kb/s
Program 1
Stream #0.0[0x1011]: Video: h264, yuv420p, 1440x1080 [PAR 4:3 DAR
16:9], 50 tbr, 90k tbn, 50 tbc
Stream #0.1[0x1100]: Audio: 0x0000, 48000 Hz, 5.1, s16, 448 kb/s
And this is the dump_format() output from my demuxer for the same stream:
Input #0, mpegts, from '':
Duration: 00:00:46.78, start: 1.040000, bitrate: 16204 kb/s
Program 1
Stream #0.0[0x1011]: Video: h264, yuv420p, 1440x1080 [PAR 4:3 DAR
16:9], 25 tbr, 90k tbn, 50 tbc
Stream #0.1[0x1100]: Audio: ac3, 0 channels, s16
Interesting that they are a little different. Couldn't figure out why
until now.
Doesn't sound like you've started on audio yet, but older libav used an
external GPL'd library for ac3 content. Version 0.5 has its own ac3
decoder, but it won't detect properly in a Mpeg-TS stream until it was
fixed about a month ago. You'll need the latest svn if you want to play
ac3 from an mpeg-ts stream.
No clue on the packet sizes... other than that mpegTS uses small packets
like that, and other containers don't. Check the versions of libav that
you link against- is ffplay using the same version as your player?
--
Michael Conrad
IntelliTree Solutions llc.
513-552-6362
[email protected]
_______________________________________________
libav-user mailing list
[email protected]
https://lists.mplayerhq.hu/mailman/listinfo/libav-user
