[mythtv-users] mplayer crashes playing back .ts file

John P Poet jppoet at gmail.com
Wed Sep 16 05:16:39 UTC 2009


On Tue, Sep 15, 2009 at 11:06 PM, Ryan Allen <ryan at the-summit.net> wrote:
> This might be slightly off topic, but I'm trying to set up an D-PVR
> into Mythbuntu right now...
>
> I've successfully installed the drivers into the kernel, with only one
> suspicious message:
> [796805.100015] usb 4-1: new full speed USB device using ohci_hcd and
> address 5
> [796805.280018] usb 4-1: device descriptor read/64, error -62
> [796805.508021] hub 4-0:1.0: unable to enumerate USB device on port 1
> [796806.232016] usb 2-1: new high speed USB device using ehci_hcd and
> address 5
> [796806.391901] usb 2-1: configuration #1 chosen from 1 choice
> [796806.602942] Linux video capture interface: v2.00
> [796806.611691] hdpvr 2-1:1.0: untested firmware version 0xf, the driver
> might not work
> [796806.917674] hdpvr 2-1:1.0: device now attached to /dev/video0
> [796806.917698] usbcore: registered new interface driver hdpvr


That all looks normal.



> It seems to capture a sample .ts file just fine, with the following
> command:
>
> cat /dev/video0 > test.ts
>
> but playback with mplayer crashes and spews a large stack trace::
>
> Starting playback...
> [h264 @ 0x8972330]PAFF interlacing is not implemented
> [h264 @ 0x8972330]concealing 675 DC, 675 AC, 675 MV errors
> VDec: vo config request - 720 x 480 (preferred colorspace: Planar YV12)
>    VDec: using Planar YV12 as output csp (no 0)
>    Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
>    VO: [xv] 720x480 => 720x540 Planar YV12
>    [h264 @ 0x8972330]PAFF interlacing is not implemented??% ??,?% 0 0
>    [h264 @ 0x8972330]left block unavailable for requested intra4x4 mode
>    -1 at 0 2
>    [h264 @ 0x8972330]error while decoding MB 0 2, bytestream (20890)
>    [h264 @ 0x8972330]illegal short term buffer state detected
>    [h264 @ 0x8972330]concealing 1350 DC, 1350 AC, 1350 MV errors
>    *** glibc detected *** mplayer: corrupted double-linked list:
>    0x09996600 ***
>
> ... <stack trace> ...
>
> MPlayer interrupted by signal 6 in module: decode_audio
> - MPlayer crashed. This shouldn't happen.
> It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
> gcc version. If you think it's MPlayer's fault, please read
> DOCS/HTML/en/bugreports.html and follow the instructions there. We
> can't and
> won't help unless you provide this information when reporting a
> possible bug.
>
>
>
> Known issue????
> Known fix or work around??


Just guessing, but I am guessing that version of mplayer is too old.

You will have to ask the mplayer folks, though, for help.  While
mplayer and myth use ffmpeg libs for a lot of the decoding, the two
projects are very different in their implementation.


John
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?


More information about the mythtv-users mailing list