From: Antti Palosaari <crope@iki.fi>
To: "Pásztor Szilárd" <don@tricon.hu>
Cc: linux-media@vger.kernel.org, linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Anysee E30 C Plus + MPEG-4?
Date: Wed, 19 Aug 2009 13:28:43 +0300 [thread overview]
Message-ID: <4A8BD3DB.1010704@iki.fi> (raw)
In-Reply-To: <20090819094242.50ae2a03.don@tricon.hu>
On 08/19/2009 10:42 AM, Pásztor Szilárd wrote:
> Thierry Lelegard:
>> Stream type 0x1B precisely means AVC / H.264 video stream (cf. ISO
>> 138181-1:2000/FDAM 3)
>>
>> Try VLC instead of mplayer. VLC does render H.264 HD video, provided you
>> have a (very) good CPU.
>
> Thanks for the info. Anyway, mplayer also does render H.264 of course, it's
> the stream that's not very cleverly muxed, it seems. And with mplayer I have
> vdpau acceleration on my nvidia card that can render 1920x1080@50 fps in real
> time.
Actually I met just similar case some months ago (I have also Anysee
E30C and fi-3ktv cable). Only audio no video. HD-video PIDs were
missing. I zapped to the channel and looked correct PIDs from dvbtraffic
traffic output and added those to the channels.conf. Mplayer and Totem
still resists to show video, but VLC does!
After that I looked transmission parameters by using dvbsnoop and there
was H.262 (MPEG2) set those H.264 (MPEG4-AVC) channels. I think that was
reason for my problems.
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2009-08-19 10:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 15:08 [linux-dvb] Anysee E30 C Plus + MPEG-4? Pásztor Szilárd
2009-08-18 16:20 ` Christophe Thommeret
2009-08-18 18:13 ` BOUWSMA Barry
2009-08-18 19:01 ` Pásztor Szilárd
2009-08-18 19:10 ` Markus Rechberger
2009-08-18 19:30 ` BOUWSMA Barry
2009-08-21 14:03 ` Pásztor Szilárd
2009-08-19 7:17 ` Thierry Lelegard
2009-08-19 7:42 ` Pásztor Szilárd
2009-08-19 10:28 ` Antti Palosaari [this message]
2009-08-18 19:43 ` Luis Silva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A8BD3DB.1010704@iki.fi \
--to=crope@iki.fi \
--cc=don@tricon.hu \
--cc=linux-dvb@linuxtv.org \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox