From: Antti Palosaari <crope@iki.fi>
To: Andre Newman <linux-media@dinkum.org.uk>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: PCTV T292e whole DVBT2 mux/Ultra HD performance question
Date: Wed, 09 Jul 2014 22:18:59 +0300 [thread overview]
Message-ID: <53BD95A3.2050509@iki.fi> (raw)
In-Reply-To: <35906397-E8F4-4229-966F-7ED578441C10@dinkum.org.uk>
Moikka
On 07/09/2014 04:14 PM, Andre Newman wrote:
> I’m using a T290e for whole mux DVBT2 capture, using this to record the current BBC World Cup Ultra HD tests, works well. :-)
>
> It seems impossible to buy more T290e’s, everyone want to sell me a T292e, I understand there is a driver now, thanks Antti. I read on Antti’s blog that there is a limit on raw TS performance with the T292, that it didn’t work well with QAM256 because of this...
>
> I am wondering if this is a hardware limit, or a performance problem that may have been resolved now the driver is a little tiny bit more mature?
>
> I am very happy to get a T292e and make some tests, help debug if there is a hope that it can handle 40Mbps in hardware.If there is a hardware limit I’d rather not be stuck with a limited tuner!
>
> The mux I need to record is QAM256 at ~40Mbps and the UHD video is ~36Mbps of this.
>
> Otherwise what other DVBT2 tuners are there that can capture a raw QAM256 mux at 40Mbps?
You simply confused two different devices. There is no such limit on
PCTV 292e as far as I know. It is another DVB-T2 device having RTL2832P
bridge having problem with stream bandwidth.
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2014-07-09 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 13:14 PCTV T292e whole DVBT2 mux/Ultra HD performance question Andre Newman
2014-07-09 19:18 ` Antti Palosaari [this message]
2014-07-09 19:21 ` Andre Newman
2014-07-13 11:13 ` Andre Newman
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=53BD95A3.2050509@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@dinkum.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.