From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Konstantin Dimitrov <kosio.dimitrov@gmail.com>
Cc: Antti Palosaari <crope@iki.fi>,
Georgi Chorbadzhiyski <gf@unixsol.org>,
linux-media@vger.kernel.org
Subject: Re: DVB-S2 multistream support
Date: Sun, 25 Dec 2011 09:18:04 -0200 [thread overview]
Message-ID: <4EF7066C.4070806@redhat.com> (raw)
In-Reply-To: <CAF0Ff2kkFJYLUjVdmV9d9aWTsi-2ZHHEEjLrVSTCUnP+VTyxRg@mail.gmail.com>
On 25-12-2011 08:55, Konstantin Dimitrov wrote:
> On Sun, Dec 25, 2011 at 12:17 PM, Mauro Carvalho Chehab
> <mchehab@redhat.com> wrote:
>
>> That's said, the approach there assumes that just one mis can be filtered. I'm wandering
>> if it wouldn't be better to use the same approach taken inside dvb-core for PIP filtering.
>
> i'm not sure that i understand correctly what you mean, but i can't
> see way how to filter more that one mis stream at the same time,
> because their id is stored in the bbheader. so, even if we assume it's
> possible to send two ids for filtering to the hardware and then it
> outputs ts packets from both of them there is still no way to know
> which ts packet to which mis stream belongs, because the bbheader is
> stripped inside the demodulator before the data are outputted. in fact
> if you don't set any id for filtering to mis capable hardware then
> usually it outputs the ts packets from all of the streams and that's
> why the outputted stream looks corrupted, because it contains ts
> packets from all mis streams and that's why you what to set id for
> filtering to the hardware in the first place - to make it output ts
> packets just from one selected stream. however, if dvb-core has
> support for bbframes like the following unfortunately lost work:
>
> http://www.linuxtv.org/pipermail/linux-dvb/2007-December/022217.html
Yes, I'm meaning something like what it was described there. I think
that the code written by Christian were never submitted upstream.
> then instead setting mis filtering in the hardware you can force it to
> output bbframes (at least currently all mis capable hardware is
> supposed to be able to output bbframes) and then filter all streams in
> the software, which would be significantly more flexible, because that
> way all streams can be filtered and used in the same time.
While your hardware supports filtering only one MIS, other hardware may
support more. Anyway, it makes sense to add a software filter, and to
add a way to deliver the mis information to userspace, if more than one
mis is filtered.
Regards,
Mauro
next prev parent reply other threads:[~2011-12-25 11:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 1:06 DVB-S2 multistream support Georgi Chorbadzhiyski
2011-12-25 8:23 ` Antti Palosaari
2011-12-25 10:17 ` Mauro Carvalho Chehab
2011-12-25 10:55 ` Konstantin Dimitrov
2011-12-25 11:18 ` Mauro Carvalho Chehab [this message]
2011-12-25 12:37 ` Konstantin Dimitrov
2011-12-27 10:12 ` Christian Prähauser
2011-12-27 16:08 ` Antti Palosaari
2012-01-19 13:34 ` Marek Ochaba
2012-01-21 10:29 ` Christian Prähauser
2012-01-23 13:58 ` Marek Ochaba
2012-01-22 2:13 ` Mauro Carvalho Chehab
2012-01-22 12:44 ` Christian Prähauser
[not found] ` <CAF0Ff2mf0tYs3UG3M6Cahep+_kMToVaGgPhTqR7zhRG0UXWuig@mail.gmail.com>
[not found] ` <85A7A8FC-150C-4463-B09C-85EED6F851A8@cosy.sbg.ac.at>
[not found] ` <CAF0Ff2ncv0PJWSOOw=7WeGyqX3kKiQitY52uEOztfC8Bwj6LgQ@mail.gmail.com>
2012-01-25 13:12 ` Christian Prähauser
2012-02-01 18:49 ` Konstantin Dimitrov
2012-02-18 19:06 ` Christian Prähauser
2012-02-19 23:12 ` Konstantin Dimitrov
2012-03-07 16:33 ` Bob Winslow
2012-03-13 9:36 ` Marek Ochaba
2012-03-13 12:30 ` Bob W
2012-03-13 15:22 ` Konstantin Dimitrov
2012-03-13 15:47 ` Bob W
2012-03-15 9:40 ` Christian Prähauser
2012-03-19 8:46 ` Christian Prähauser
2012-03-19 15:19 ` Konstantin Dimitrov
2012-04-24 22:18 ` Bob W
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=4EF7066C.4070806@redhat.com \
--to=mchehab@redhat.com \
--cc=crope@iki.fi \
--cc=gf@unixsol.org \
--cc=kosio.dimitrov@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).