On Wed, July 11, 2007 09:31, David Härdeman wrote:
> Ok, now I'm confused...when I use one filter by calling
> dvbdemux_set_section_filter with filter[0] and mask[0] set to something, I
> get sections.
>
> If I use two filters by calling dvbdemux_set_section_filter with
> filter[0], mask[0], filter
On Tue, July 10, 2007 10:56, Marcel Siegert wrote:
> On Tuesday 10 July 2007, David Härdeman wrote:
>> I'm trying to understand the dvbdemux_set_section_filter function in
>> dvp-apps/lib/libdvbapi/dvbdemux.c (lines 74 - 93).
...
>
> if you filter a section you can filter on e.g. the table id but N
> The "hole" at bytes 2 and 3 seems like a typical implementation detail
> that a library should hide from its users. Wouldn't it be saner to change
> the API so that the function takes 16 filter/mask values and adds the
> unused bytes itself?
That would make sense if linux DVB stuff was written b
On Tue, July 10, 2007 10:56, Marcel Siegert wrote:
> On Tuesday 10 July 2007, David Härdeman wrote:
>> I'm trying to understand the dvbdemux_set_section_filter function in
>> dvp-apps/lib/libdvbapi/dvbdemux.c (lines 74 - 93).
>>
>> It used to take 16 filter and 16 mask parameters, but then it was
>
On Tuesday 10 July 2007, David Härdeman wrote:
> I'm trying to understand the dvbdemux_set_section_filter function in
> dvp-apps/lib/libdvbapi/dvbdemux.c (lines 74 - 93).
>
> It used to take 16 filter and 16 mask parameters, but then it was changed
> 15 months ago to take 18 filter and 18 mask par
I'm trying to understand the dvbdemux_set_section_filter function in
dvp-apps/lib/libdvbapi/dvbdemux.c (lines 74 - 93).
It used to take 16 filter and 16 mask parameters, but then it was changed
15 months ago to take 18 filter and 18 mask parameters, then it throws
away 2 of each:
int dvbdemux_set
