<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
Is there any change in the cultiproto disecq code?<br>
MythTV won't tune to channels on disecq port 2 or higher. (Disecq port
1 always works)<br>
However, Kaffeine works. I'm able to watch every BBC channel on Astra
28,2 (which is on my second port)<br>
This made me think it's MythTV. <br>
But a friend of mine now said an older, regular DVB-S card DOES work
I must point out that I'm not using the latest multiproto drivers, the
one with the old_api support (so that I don't have to patch mythtv)<br>
<em>Met vriendelijke groeten,</em>
<strong>Jelle De Loecker</strong>
Kipdola Studios - Tomberg <br>
Manu Abraham schreef:
<blockquote cite="mid:48C58D03.firstname.lastname@example.org" type="cite">
<pre wrap="">barry bouwsma wrote:
<pre wrap="">What I wonder, is two things.
Does DiSEqC 1.1 fit into the existing API, and is it more of
a question of hardware support (generally I've noticed 1.0 and
1.2 listed), and applications being able to handle the additional
switching (I've found an app limit of 4 positions)?
Cascading is not supported by the dvb-apps, i must say. It's more of a
support from the application side.
As far as multiproto goes, the driver used alongwith it supports DiSEqC 2.0
<pre wrap="">I don't know enough about the internals of DiSEqC to have any idea
what I'm talking about; I've got a 1.1 switch on order, and I have
a 1.1-able 8/1+16/1 receiver, where those appear to be incompatible
with my existing 4/1 switch.
Second, how do non-DVB-like technologies like DAB (Eureka-147) fit
into the scope of either multiproto or S2API -- or must they
remain outside of v4l-dvb?
There is already a kernel module called dabusb for ages.
<pre wrap="">The Wiki sez, ``some developers already have hardware using
standards unsupported by multiproto, such as ISDB-T and DMB-T/H.''
And some of us non-developers have such hardware and want to try
it with non-Windows for readily-receiveable DAB.
With some simple definitions ? What applications are used ? With regards
to ISDB-T, there was an idea to integrate the ARIB extension used in the
DVB V4 API, but then it was proven that there wasn't much use for the
same due to:
* lack of available hardware (only some mobile devices using 1 seg or
likewise were available) Of course, there was the demodulator from
Toshiba TCxxxx, the DVB V4 API which it was based on.
* most of the stuff's completely scrambled and the scrambling schemes
are not open like DVB stuff.
But still, if there's need to add support for the same into the
multiproto tree, it is quite trivial.
<pre wrap="">Or is DAB/T-DMB too different from DVB and related technologies,
that a separate development path needs to be taken outside
linux-dvb, but probably within V4L?
DMB resembles quite a bit of DAB. Well, the tables for DMB-T/H is quite
different from standard DVB tables, but still you can use multiproto to
handle DMB-T/H, it's quite trivial.
linux-dvb mailing list
<a class="moz-txt-link-abbreviated" href="mailto:email@example.com">firstname.lastname@example.org</a>
<a class="moz-txt-link-freetext" href="http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb">http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb</a>