From: Issa Gorissen <flop.m@usa.net>
To: "\"Sébastien RAILLARD (COEXSI)\"" <sr@coexsi.fr>
Cc: 'Ralph Metzler' <rjkm@metzlerbros.de>,
'Linux Media Mailing List' <linux-media@vger.kernel.org>,
'Oliver Endriss' <o.endriss@gmx.de>,
'Martin Vidovic' <xtronom@gmail.com>
Subject: Re: DVB nGene CI : TS Discontinuities issues
Date: Mon, 09 May 2011 22:39:49 +0200 [thread overview]
Message-ID: <4DC85115.6020604@usa.net> (raw)
In-Reply-To: <000901cc0e17$65fc4510$31f4cf30$@coexsi.fr>
On 09/05/11 09:04, Sébastien RAILLARD (COEXSI) wrote:
>> I don't know if CAT needs to be in the stream passed through sec0 as
>> Sebastien mentioned, so I modified gnutv to add it to dvr.
>>
> Yes, the CAT table is mandatory, it must be sent to the CAM, as well as :
> * the EMM PID referenced in the CAT
> * all the private descriptors (binary blobs) in the PMT and, of course
> * the ECM PID referenced in the PMT
>
> Of course, the CAM must be initialized, all the necessary CAM resources must
> be initialized and a CA_PMT object must be sent through the CAM command
> channel to ask for unscrambling of needed channels.
>
> That why it's better to send directly the raw TS output of the demodulator
> directly in the CAM.
> And then doing the demux filtering stuff on the TS stream coming from the
> CAM (once unscrambled).
Thx Sebastien,
Will check this out with gnutv and report.
I think gnutv does all the init stuff you mentioned about the CAM. I
will check for the possibly missing PSI packets gnutv might exclude.
--
Issa
next prev parent reply other threads:[~2011-05-09 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 10:59 DVB nGene CI : TS Discontinuities issues Sébastien RAILLARD (COEXSI)
2011-05-07 15:15 ` Issa Gorissen
[not found] ` <19909.47855.351946.831380@morden.metzler>
2011-05-08 16:44 ` Issa Gorissen
2011-05-09 0:41 ` Issa Gorissen
2011-05-09 7:04 ` Sébastien RAILLARD (COEXSI)
2011-05-09 20:39 ` Issa Gorissen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-11 13:12 Issa Gorissen
2011-05-11 13:35 ` Sébastien RAILLARD (COEXSI)
2011-05-12 20:40 ` Issa Gorissen
2011-05-13 11:54 ` Ralph Metzler
2012-02-26 17:11 ` Anssi Hannula
2012-02-26 22:14 ` Ralph Metzler
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=4DC85115.6020604@usa.net \
--to=flop.m@usa.net \
--cc=linux-media@vger.kernel.org \
--cc=o.endriss@gmx.de \
--cc=rjkm@metzlerbros.de \
--cc=sr@coexsi.fr \
--cc=xtronom@gmail.com \
/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