[mythtv-users] BBC HD Trial

[Ivan Kowalenko]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On May 17, 2006, at 04.26, Dan Seddon wrote:

> David Watkins wrote:
>> On 15/05/06, Robert Johnston <anaerin at gmail.com> wrote:
>>
>>> On 5/15/06, David Watkins <watkinshome at gmail.com> wrote:
>>>
>>>> G:\movies>mplayer HD1.mpg
>>>> MPlayer dev-CVS-050928-16:38-3.4.2 (C) 2000-2005 MPlayer Team
>>>> CPU: Advanced Micro Devices  (Family: 8, Stepping: 0)
>>>> Detected cache-line size is 64 bytes
>>>> CPUflags:  MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 0 SSE2: 0
>>>> Compiled with runtime CPU detection - WARNING - this is not  
>>>> optimal!
>>>> To get best performance, recompile MPlayer with --disable- 
>>>> runtime-cpudetection.
>>>> Creating config file: G:/movies/mplayer/config
>>>>
>>>> Playing HD1.mpg.
>>>> TS file format detected.
>>>> DEMUX OPEN, AUDIO_ID: -1, VIDEO_ID: -1, SUBTITLE_ID: -1,
>>>> PROBING UP TO 2000000, PROG: 0
>>>> VIDEO MPEG2(pid=1502)AUDIO A52(pid=1505) NO SUBS (yet)!  PROGRAM  
>>>> N. 0
>>>> Opened TS demuxer, audio: 2000(pid 1505), video: 10000002(pid  
>>>> 1502)...POS=13912
>>>>
>>> It looks like the Video's got the wrong PID (Or you requested the
>>> wrong PID), as MPlayer is saying it's got MPEG2 on PID 1502, when it
>>> should report H264/x264.
>>>
>>> Though it looks like it's also a (possible) problem with mplayer  
>>> (And
>>> VLC) according to this:
>>>
>>> http://forum.videolan.org/viewtopic.php?t=20387
>>>
>>> http://article.gmane.org/gmane.comp.video.mplayer.user/43896
>>>
>>> I think the problem is that so far, no codec (on linux) supports  
>>> MBAFF.

 From what I know about MPlayer, isn't it possible to tell it to use  
a certain decoder? Or couldn't you remux it and change the FOURCC to  
"avc1"? I'm pretty sure that MEncoder has the ability to losslessly  
remux (though I don't think MPEG-TS is a supported output container)  
files, and should allow the forced changing of a FOURCC.

>>
>> I've been doing some reading and I think you're right.  I also think
>> that if it does become supported then it still won't run on any
>> hardware that I've going to have access to in the immediate future
>> :-(
>>
> Though if we could get a codec that would support this on linux (the
> past record of new codecs being supported on linux is pretty good
> surely?), then it just means you can't play liveTV as it would be
> possible to transcode the h.264 back in to mpeg2 meaning it would take
> up twice the disk space (or more?) but would be playable?

If you can get a codec that supports interlaced H.264, then sure.  
You'd lose some quality in the transfer, but if you set your bitrate  
high enough, you shouldn't notice. The biggest problem should be  
getting that codec, which doesn't seem to be as easy as you make it  
out to be.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEa33s187keuSyQSQRAjcnAJ4t50ub6xa6SbTh8Q5aL+R7BzaU0gCdHPqw
iQNQecaycoAM0aeX0nO9lD4=
=kmjD
-----END PGP SIGNATURE-----