Nico Sabbi wrote:
Ralph Metzler wrote:
In the HVR3000 case, do both frontends then use the same demux0?
So, if one can open only one at the same time, both should use
demux0?
please, NO!
it will be a hell to support in applications.
Please, do it simple and bind frontendN to demuxN
Ralph Metzler wrote:
In the HVR3000 case, do both frontends then use the same demux0?
So, if one can open only one at the same time, both should use
demux0?
please, NO!
it will be a hell to support in applications.
Please, do it simple and bind frontendN to demuxN and dvrN (and netN)
If
On 1/15/07, Ralph Metzler [EMAIL PROTECTED] wrote:
Klaus Schmidinger writes:
I'm wondering how an application is supposed to handle
devices with multiple frontends.
Let's assume a device that provides
dvb/adapter0/frontend0DVB-S
dvb/adapter0/frontend1DVB-T
so that
Manu Abraham wrote:
...
There are 2 different cases
(1) multiple frontends sharing the same TS interface
(2) multiple frontends, each having it's own TS interface.
Maybe those should be handled like one multi-protocol frontend?
Not sure if Manu's multi-proto stuff would also
On 1/15/07, Klaus Schmidinger [EMAIL PROTECTED] wrote:
Manu Abraham wrote:
...
There are 2 different cases
(1) multiple frontends sharing the same TS interface
(2) multiple frontends, each having it's own TS interface.
Maybe those should be handled like one multi-protocol frontend?
I'm wondering how an application is supposed to handle
devices with multiple frontends.
Let's assume a device that provides
dvb/adapter0/frontend0DVB-S
dvb/adapter0/frontend1DVB-T
so that it can receive both DVB-S and DVB-T. Does this
mean that it can simultaneously receive
Klaus Schmidinger writes:
I'm wondering how an application is supposed to handle
devices with multiple frontends.
Let's assume a device that provides
dvb/adapter0/frontend0DVB-S
dvb/adapter0/frontend1DVB-T
so that it can receive both DVB-S and DVB-T. Does
