Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
В сообщении от 30 September 2008 22:38:50 Jörn Reder написал(а): > What's the sense of this quoting garbage? > You said it to me? -- Igor M. Liplianin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
What's the sense of this quoting garbage? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
В сообщении от 30 September 2008 19:03:19 Darron Broad написал(а): > In message <[EMAIL PROTECTED]>, "Igor M. Liplianin" > wrote: > > LO > > >> >> > Hi, > >> >> > > >> >> > I'm on Astra 19.2 and tested the following HD transponders : > >> >> > Anixe HD > >> >> > Arte HD > >> >> > Astra HD+ > >> >> > > >> >> > first test results : > >> >> > > >> >> > Arte HD tunes ok and plays fine. > >> >> > >> >> Same here. Arte HD is a DVB-S2 transponder using the 8PSK modulation. > >> >> Locking goes without any problems at all. > >> >> > >> >> > On Astra HD+ and Anixe HD im getting an error : > >> >> > >> >> Astra HD+ en Anixe HD is on a DVB-S2 transponder which is using a > >> >> QPSK modulation. > >> >> > >> >> > -- SNIP -- > >> >> > > >> >> > If you need further informations let me know. > >> >> > >> >> I tested other DVB-S2 transponders which have a QPSK modulation. All > >> >> these didn't want to lock and gave a timeout. DVB-S2 Transponders > >> >> with= > > > > a > > > >> >> 8PSK modulation did gave a lock (Hotbird has a couple, while I don't > >> >> have subscriptions to chose channels, I'm able to lock those). > >> >> > >> >> So my first impression was, it's a missing parameter in the Frontend > >> >> struct. So I made some changes and check if the transponder is DVB-S2 > >> >> and added parameters for DTV_PILOT (with data PILOT_AUTO) and when > >> >> QPSK is used with DVB-S2, to use the NBC_QPSK modulation (which is > >> >> needed f= > > > >or > > > >> >> DVB-S2 if I'm not mistaken) instead of regular QPSK. > >> >> > >> >> However, didn't bring me the sollution I hoped for. I now have a > >> >> timeout, lost lock and regain lock, etc, etc, etc. But it's more then > >> >> = > > > >it > > > >> >> was before. > >> >> > >> >> So I'm close. Currently I do have a small problem where I put in > >> >> parameters which shouldn't been given (oops!) and now my DVB-card > >> >> doesn't lock any more, I need to reboot first. > > If you make an error in the params it can trip the property dump debug > output routine. > > use this patch to catch invalid commands, there may be others to catch tho: > http://dev.kewl.org/v4l-dvb/patches/s2-mfe-debug-dump-9036.diff > > >> >> I hope to start to work on it this further when I'm done with work. > >> >> I'= > > > >ll > > > >> >> keep you all posted :) > >> >> > >> >> BTW, I did manage to get DVB-T working. At least it locks on on the > >> >> encrypted channels, but I didn't had time to check for image. Mainly > >> >> since DVB-T is my backup for channel-viewing and I wanted to focus on > >> >> the DVB-S2 problem. > >> >> > >> >> > cu > >> >> > > >> >> > Edgar (gimli) Hucek > >> >> > >> >> Regards, > >> >> > >> >> Niels Wagenaar > >> > > >> >May I ask you, Niels or Edgar, would you try szap-s2 with parameter > >> > -M3, wh=3D ich=3D20 > >> >means NBC_QPSK modulation. It is interesting for me, whether it works. > >> > i'm=3D =3D20 > >> >not able to receive Astra HD+ and Anixe HD. > >> > >> I will test it. > >> > >> For your information, when I fixed up Manu's szap hack renaming it szap2 > >> i had to add a whole bunch of options which were originally known as > >> `team' then they eventually became known later as `meow' > >> > >> These are all necessary for the hvr-4000 with the cx24116 which is a > >> dumb part. > >> > >> These params were: > >> > >> -m : modulation 0=3DQPSK (DVB-S) 1=3DNBC-QPSK (DVB-S2) 2=3DNBC-8PSK > >> (DV= > > > >B-S2) > > > >> -e : fec 0=3DNONE 1=3D1/2 2=3D2/3 3=3D3/4 4=3D4/5 5=3D5/6 6=3D6/7 > >> 8=3D8= > > > >/9 9=3D9/10 10=3D3/5 > > > >> 11=3DAUTO -o : rolloff 0=3D0.20 1=3D0.25 2=3D0.35 > >> -w : pilot 0=3DOFF 1=3DON 2=3DAUTO > >> > >> The cx24116 can't do auto-detect from what we know for any DVB-S2 > >> paramet= > > > >er > > > >> not only modulation. I had to emulate auto-pilot in the demod. rolloff > >> seems superfluous in most cases but even then you must have an option to > >> allow it. > >> > >> I will check your szap but raise the point above if not all these > >> options are catered for. If they are catered for and not named MEOW then > >> I will be disappointed, but will survive ;-) > > > >Suddenly, pilot not implemented :-(=20 > >I get parameters from VDR(with part of source code, with perspective put > > it= =20 > >back modified), think it is familiar for VDR users > > -S: delivery system type DVB-S=3D0, DVB-S2=3D1 > > -M: modulation 1=3DBPSK 2=3DQPSK 3=3DNBC-QPSK(for DVB-S2) > > 5=3D= 8PSK > > -C: fec 0=3DNONE 12=3D1/2 23=3D2/3 34=3D3/4 35=3D3/5 45=3D4/5 > > = 56=3D5/6 67=3D6/7=20 > >89=3D8/9 910=3D9/10 999=3DAUTO > > -O: rolloff 35=3D0.35 25=3D0.25 20=3D0.20 0=3DUNKNOWN > >So, szap-s2 can handle channels.conf line like this(though not compatible > > w= ith=20 > >VDR, but similar): > >poverkhnost:12111:lC34M5O0S1:0:27500:1201:1301:3201 > > > >It is not like I'm pretend on copyright here, I can easily remove my name > > f= rom=20 > >sources. I pretend to be useful. > >Welcome any other c
Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
В сообщении от 30 September 2008 16:17:22 Darron Broad написал(а):
> In message <[EMAIL PROTECTED]>, "Igor M. Liplianin"
> wrote:
>
> Lo.
>
> >=F7 =D3=CF=CF=C2=DD=C5=CE=C9=C9 =CF=D4 30 September 2008 09:08:59 Niels
> > Wag=
> >
> >enaar =CE=C1=D0=C9=D3=C1=CC(=C1):
> >> Op Zo, 28 september, 2008 23:29, schreef gimli:
> >> > Hi,
> >> >
> >> > I'm on Astra 19.2 and tested the following HD transponders :
> >> > Anixe HD
> >> > Arte HD
> >> > Astra HD+
> >> >
> >> > first test results :
> >> >
> >> > Arte HD tunes ok and plays fine.
> >>
> >> Same here. Arte HD is a DVB-S2 transponder using the 8PSK modulation.
> >> Locking goes without any problems at all.
> >>
> >> > On Astra HD+ and Anixe HD im getting an error :
> >>
> >> Astra HD+ en Anixe HD is on a DVB-S2 transponder which is using a QPSK
> >> modulation.
> >>
> >> > -- SNIP --
> >> >
> >> > If you need further informations let me know.
> >>
> >> I tested other DVB-S2 transponders which have a QPSK modulation. All
> >> these didn't want to lock and gave a timeout. DVB-S2 Transponders with a
> >> 8PSK modulation did gave a lock (Hotbird has a couple, while I don't
> >> have subscriptions to chose channels, I'm able to lock those).
> >>
> >> So my first impression was, it's a missing parameter in the Frontend
> >> struct. So I made some changes and check if the transponder is DVB-S2
> >> and added parameters for DTV_PILOT (with data PILOT_AUTO) and when QPSK
> >> is used with DVB-S2, to use the NBC_QPSK modulation (which is needed for
> >> DVB-S2 if I'm not mistaken) instead of regular QPSK.
> >>
> >> However, didn't bring me the sollution I hoped for. I now have a
> >> timeout, lost lock and regain lock, etc, etc, etc. But it's more then it
> >> was before.
> >>
> >> So I'm close. Currently I do have a small problem where I put in
> >> parameters which shouldn't been given (oops!) and now my DVB-card
> >> doesn't lock any more, I need to reboot first.
> >>
> >> I hope to start to work on it this further when I'm done with work. I'll
> >> keep you all posted :)
> >>
> >> BTW, I did manage to get DVB-T working. At least it locks on on the
> >> encrypted channels, but I didn't had time to check for image. Mainly
> >> since DVB-T is my backup for channel-viewing and I wanted to focus on
> >> the DVB-S2 problem.
> >>
> >> > cu
> >> >
> >> > Edgar (gimli) Hucek
> >>
> >> Regards,
> >>
> >> Niels Wagenaar
> >
> >May I ask you, Niels or Edgar, would you try szap-s2 with parameter -M3,
> > wh= ich=20
> >means NBC_QPSK modulation. It is interesting for me, whether it works.
> > i'm= =20
> >not able to receive Astra HD+ and Anixe HD.
>
> I will test it.
>
> For your information, when I fixed up Manu's szap hack renaming it szap2 i
> had to add a whole bunch of options which were originally known as `team'
> then they eventually became known later as `meow'
>
> These are all necessary for the hvr-4000 with the cx24116 which is a dumb
> part.
>
> These params were:
>
> -m : modulation 0=QPSK (DVB-S) 1=NBC-QPSK (DVB-S2) 2=NBC-8PSK (DVB-S2)
> -e : fec 0=NONE 1=1/2 2=2/3 3=3/4 4=4/5 5=5/6 6=6/7 8=8/9 9=9/10 10=3/5
> 11=AUTO -o : rolloff 0=0.20 1=0.25 2=0.35
> -w : pilot 0=OFF 1=ON 2=AUTO
>
> The cx24116 can't do auto-detect from what we know for any DVB-S2 parameter
> not only modulation. I had to emulate auto-pilot in the demod. rolloff
> seems superfluous in most cases but even then you must have an option to
> allow it.
>
> I will check your szap but raise the point above if not all these options
> are catered for. If they are catered for and not named MEOW then I will be
> disappointed, but will survive ;-)
Suddenly, pilot not implemented :-(
I get parameters from VDR(with part of source code, with perspective put it
back modified), think it is familiar for VDR users
-S: delivery system type DVB-S=0, DVB-S2=1
-M: modulation 1=BPSK 2=QPSK 3=NBC-QPSK(for DVB-S2) 5=8PSK
-C: fec 0=NONE 12=1/2 23=2/3 34=3/4 35=3/5 45=4/5 56=5/6 67=6/7
89=8/9 910=9/10 999=AUTO
-O: rolloff 35=0.35 25=0.25 20=0.20 0=UNKNOWN
So, szap-s2 can handle channels.conf line like this(though not compatible with
VDR, but similar):
poverkhnost:12111:lC34M5O0S1:0:27500:1201:1301:3201
It is not like I'm pretend on copyright here, I can easily remove my name from
sources. I pretend to be useful.
Welcome any other comments. Now it is valuable like gold.
>
> l8r!
>
> --
>
> // /
> {:)==={ Darron Broad <[EMAIL PROTECTED]>
> \\ \
--
Igor M. Liplianin
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
В сообщении от 28 September 2008 22:33:56 Igor M. Liplianin написал(а):
> В сообщении от 28 September 2008 17:12:14 Niels Wagenaar написал(а):
> > Hi Igor,
> >
> > Small question. I tried your patch, but it fails a hunk in dvbdevice.c. I
> > added this hunk manually but I think something is missing:
> >
> > Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,251): Operation not
> > supported Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,252):
> > Operation not supported Sep 28 13:56:15 htpc vdr: [19486] ERROR: frontend
> > 0: Invalid argument
> >
> > Those both lines has the following code:
> >
> > CHECK(ioctl(fd_frontend, FE_SET_VOLTAGE, volt)); CHECK(ioctl(fd_frontend,
> > FE_SET_TONE, tone));
> >
> > The result is, no tuning and no picture.
> >
> > And to be honest, I don't really understand why it shouldn't work.
> > Mainly, since the same code is used with the Kaffeine patch (I'm
> > comparing that also).
> >
> > Any help is appreciated :) If you need a quick chat, I'm currently in
> > #linuxtv on irc.freenode.net :)
> >
> > Regards,
> >
> > Niels Wagenaar
> >
> > > -Oorspronkelijk bericht-
> > > Van: Igor M. Liplianin [mailto:[EMAIL PROTECTED]
> > > Verzonden: zondag 28 september 2008 12:49
> > > Aan: vdr@linuxtv.org; Niels Wagenaar
> > > CC: Gregoire Favre; [EMAIL PROTECTED]
> > > Onderwerp: [vdr][PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
> > >
> > > ? ? ?? 24 September 2008 18:34:01 Niels Wagenaar ???(?):
> > > > Hello all (and especially Klaus):
> > > >
> > > > It's official, the people from V4L have voted for the usage of the
> > > > S2API proposal to be the future for new DVB API improvements (see
> > > > the official announcement at the bottom) within the V4L tree.
> > > > Currently S2API is in a real speed-train and new devices are added
> > > > very
> > >
> > > rapidly.
> > >
> > > > Only the devices currently in Multiproto and written by Manu Abraham
> > >
> > > are not yet ported.
> > >
> > > > Also people are allready busy with patches for Kaffeine (allready
> > > > done) and MythTV (not seen yet, but it's WIP according to a post on
> > > > the linux-dvb mailinglist).
> > > >
> > > > So, this should mean that VDR 1.7.x should focus on S2API because of
> > > > the obvious reasons. Has anybody started on a patch of somekind to
> > > > include S2API in VDR 1.7.0 or 1.7.1? Mainly I was thinking of doing
> > >
> > > it
> > >
> > > > myself (I have a Hauppauge WinTV-NOVA-HD-S2 which is allready
> > > > supported in S2API) in the hope to have it working in the next
> > > > weekend. But if it's allready done or in progress, then I would like
> > > > to use my time for something else ;)
> > > >
> > > > Regards,
> > > >
> > > > Niels Wagenaar
> > >
> > > Hi Niels
> > >
> > > S2API for vdr-1.7.0(1.7.1) quick hack
> > > Patch is ugly and only supported DVB-S. But it is useful to begin.
> > > You may modify it like you wish.
> > >
> > > Igor
> >
> > ___
> > vdr mailing list
> > vdr@linuxtv.org
> > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>
> V.2
> Only satellite, as I have not any cable or terrestrial, but it is easy to
> modify :-)
> I test it with cx24116 based card (though without ISL chip) and didn't find
> any troubles.
>
> Igor
Next version: vdr-1.7.0-s2-30092008.patch
--
Igor M. Liplianin
diff -Naur vdr-1.7.0/channels.c vdr-1.7.0-s2-clean/channels.c
--- vdr-1.7.0/channels.c 2008-04-12 16:49:12.0 +0300
+++ vdr-1.7.0-s2-clean/channels.c 2008-09-30 13:39:22.0 +0300
@@ -21,114 +21,116 @@
// --- Channel Parameter Maps
const tChannelParameterMap InversionValues[] = {
- { 0, DVBFE_INVERSION_OFF, trNOOP("off") },
- { 1, DVBFE_INVERSION_ON, trNOOP("on") },
- { 999, DVBFE_INVERSION_AUTO },
+ { 0, INVERSION_OFF, trNOOP("off") },
+ { 1, INVERSION_ON, trNOOP("on") },
+ { 999, INVERSION_AUTO },
{ -1 }
};
const tChannelParameterMap BandwidthValues[] = {
- { 5, DVBFE_BANDWIDTH_5_MHZ, "5 MHz" },
- { 6, DVBFE_BANDWIDTH_6_MHZ, "6 MHz" },
- { 7, DVBFE_BANDWIDTH_7_MHZ, "7 MHz" },
- { 8, DVBFE_BANDWIDTH_8
Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
В сообщении от 30 September 2008 09:08:59 Niels Wagenaar написал(а): > Op Zo, 28 september, 2008 23:29, schreef gimli: > > Hi, > > > > I'm on Astra 19.2 and tested the following HD transponders : > > Anixe HD > > Arte HD > > Astra HD+ > > > > first test results : > > > > Arte HD tunes ok and plays fine. > > Same here. Arte HD is a DVB-S2 transponder using the 8PSK modulation. > Locking goes without any problems at all. > > > On Astra HD+ and Anixe HD im getting an error : > > Astra HD+ en Anixe HD is on a DVB-S2 transponder which is using a QPSK > modulation. > > > -- SNIP -- > > > > If you need further informations let me know. > > I tested other DVB-S2 transponders which have a QPSK modulation. All these > didn't want to lock and gave a timeout. DVB-S2 Transponders with a 8PSK > modulation did gave a lock (Hotbird has a couple, while I don't have > subscriptions to chose channels, I'm able to lock those). > > So my first impression was, it's a missing parameter in the Frontend > struct. So I made some changes and check if the transponder is DVB-S2 and > added parameters for DTV_PILOT (with data PILOT_AUTO) and when QPSK is > used with DVB-S2, to use the NBC_QPSK modulation (which is needed for > DVB-S2 if I'm not mistaken) instead of regular QPSK. > > However, didn't bring me the sollution I hoped for. I now have a timeout, > lost lock and regain lock, etc, etc, etc. But it's more then it was > before. > > So I'm close. Currently I do have a small problem where I put in > parameters which shouldn't been given (oops!) and now my DVB-card doesn't > lock any more, I need to reboot first. > > I hope to start to work on it this further when I'm done with work. I'll > keep you all posted :) > > BTW, I did manage to get DVB-T working. At least it locks on on the > encrypted channels, but I didn't had time to check for image. Mainly since > DVB-T is my backup for channel-viewing and I wanted to focus on the DVB-S2 > problem. > > > cu > > > > Edgar (gimli) Hucek > > Regards, > > Niels Wagenaar May I ask you, Niels or Edgar, would you try szap-s2 with parameter -M3, which means NBC_QPSK modulation. It is interesting for me, whether it works. i'm not able to receive Astra HD+ and Anixe HD. Best Regards Igor M. Liplianin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
Op Zo, 28 september, 2008 23:29, schreef gimli: > Hi, > > I'm on Astra 19.2 and tested the following HD transponders : > Anixe HD > Arte HD > Astra HD+ > > first test results : > > Arte HD tunes ok and plays fine. > Same here. Arte HD is a DVB-S2 transponder using the 8PSK modulation. Locking goes without any problems at all. > On Astra HD+ and Anixe HD im getting an error : > Astra HD+ en Anixe HD is on a DVB-S2 transponder which is using a QPSK modulation. > -- SNIP -- > > If you need further informations let me know. > I tested other DVB-S2 transponders which have a QPSK modulation. All these didn't want to lock and gave a timeout. DVB-S2 Transponders with a 8PSK modulation did gave a lock (Hotbird has a couple, while I don't have subscriptions to chose channels, I'm able to lock those). So my first impression was, it's a missing parameter in the Frontend struct. So I made some changes and check if the transponder is DVB-S2 and added parameters for DTV_PILOT (with data PILOT_AUTO) and when QPSK is used with DVB-S2, to use the NBC_QPSK modulation (which is needed for DVB-S2 if I'm not mistaken) instead of regular QPSK. However, didn't bring me the sollution I hoped for. I now have a timeout, lost lock and regain lock, etc, etc, etc. But it's more then it was before. So I'm close. Currently I do have a small problem where I put in parameters which shouldn't been given (oops!) and now my DVB-card doesn't lock any more, I need to reboot first. I hope to start to work on it this further when I'm done with work. I'll keep you all posted :) BTW, I did manage to get DVB-T working. At least it locks on on the encrypted channels, but I didn't had time to check for image. Mainly since DVB-T is my backup for channel-viewing and I wanted to focus on the DVB-S2 problem. > cu > > Edgar (gimli) Hucek > Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
> ÷ ÓÏÏÂÝÅÎÉÉ ÏÔ 29 September 2008 00:29:17 gimli ÎÁÐÉÓÁÌ(Á): >> Hi, >> >> I'm on Astra 19.2 and tested the following HD transponders : >> Anixe HD >> Arte HD >> Astra HD+ >> >> first test results : >> >> Arte HD tunes ok and plays fine. >> >> On Astra HD+ and Anixe HD im getting an error : >> >> Sep 28 23:27:28 archvdr dvb_frontend_ioctl_properties() FE_SET_PROPERTY >> Sep 28 23:27:28 archvdr dvb_frontend_ioctl_properties() properties.num = >> 8 >> Sep 28 23:27:28 archvdr dvb_frontend_ioctl_properties() properties.props >> = >> 41b31dc0 >> Sep 28 23:27:28 archvdr dtv_property_process_set() >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0011 >> (DTV_DELIVERY_SYSTEM) >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x0005 >> Sep 28 23:27:28 archvdr dtv_property_process_set() >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0003 >> (DTV_FREQUENCY) >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x00140cd0 >> Sep 28 23:27:28 archvdr dtv_property_process_set() >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0004 >> (DTV_MODULATION) >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x >> Sep 28 23:27:28 archvdr dtv_property_process_set() >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0008 >> (DTV_SYMBOL_RATE) >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x01a39de0 >> Sep 28 23:27:28 archvdr dtv_property_process_set() >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0009 >> (DTV_INNER_FEC) >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x000b >> Sep 28 23:27:28 archvdr dtv_property_process_set() >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0006 >> (DTV_INVERSION) >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x0002 >> Sep 28 23:27:28 archvdr dtv_property_process_set() >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x000d >> (DTV_ROLLOFF) >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x0002 >> Sep 28 23:27:28 archvdr dtv_property_process_set() >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0001 >> (DTV_TUNE) >> Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x >> Sep 28 23:27:28 archvdr dtv_property_process_set() Finalised property >> cache >> Sep 28 23:27:28 archvdr dtv_property_cache_submit() >> Sep 28 23:27:28 archvdr dtv_property_cache_submit() adv, modulation = 0 >> Sep 28 23:27:28 archvdr dtv_property_adv_params_sync() >> Sep 28 23:27:28 archvdr dvb_frontend_ioctl_properties() Property cache >> is >> full, tuning >> >> If you need further informations let me know. >> >> cu >> >> Edgar (gimli) Hucek >> >> > ÷ ÓÏÏÂÝÅÎÉÉ ÏÔ 28 September 2008 17:12:14 Niels Wagenaar ÎÁÐÉÓÁÌ(Á): >> >> Hi Igor, >> >> >> >> Small question. I tried your patch, but it fails a hunk in >> dvbdevice.c. >> >> I >> >> added this hunk manually but I think something is missing: >> >> >> >> Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,251): Operation >> not >> >> supported Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,252): >> >> Operation not supported Sep 28 13:56:15 htpc vdr: [19486] ERROR: >> >> frontend >> >> 0: Invalid argument >> >> >> >> Those both lines has the following code: >> >> >> >> CHECK(ioctl(fd_frontend, FE_SET_VOLTAGE, volt)); >> >> CHECK(ioctl(fd_frontend, >> >> FE_SET_TONE, tone)); >> >> >> >> The result is, no tuning and no picture. >> >> >> >> And to be honest, I don't really understand why it shouldn't work. >> >> Mainly, >> >> since the same code is used with the Kaffeine patch (I'm comparing >> that >> >> also). >> >> >> >> Any help is appreciated :) If you need a quick chat, I'm currently in >> >> #linuxtv on irc.freenode.net :) >> >> >> >> Regards, >> >> >> >> Niels Wagenaar >> >> >> >> > -Oorspronkelijk bericht- >> >> > Van: Igor M. Liplianin [mailto:[EMAIL PROTECTED] >> >> > Verzonden: zondag 28 september 2008 12:49 >> >> > Aan: vdr@linuxtv.org; Niels Wagenaar >> >> > CC: Gregoire Favre; [EMAIL PROTECTED] >>
Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
В сообщении от 29 September 2008 00:29:17 gimli написал(а): > Hi, > > I'm on Astra 19.2 and tested the following HD transponders : > Anixe HD > Arte HD > Astra HD+ > > first test results : > > Arte HD tunes ok and plays fine. > > On Astra HD+ and Anixe HD im getting an error : > > Sep 28 23:27:28 archvdr dvb_frontend_ioctl_properties() FE_SET_PROPERTY > Sep 28 23:27:28 archvdr dvb_frontend_ioctl_properties() properties.num = 8 > Sep 28 23:27:28 archvdr dvb_frontend_ioctl_properties() properties.props = > 41b31dc0 > Sep 28 23:27:28 archvdr dtv_property_process_set() > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0011 > (DTV_DELIVERY_SYSTEM) > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x0005 > Sep 28 23:27:28 archvdr dtv_property_process_set() > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0003 > (DTV_FREQUENCY) > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x00140cd0 > Sep 28 23:27:28 archvdr dtv_property_process_set() > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0004 > (DTV_MODULATION) > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x > Sep 28 23:27:28 archvdr dtv_property_process_set() > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0008 > (DTV_SYMBOL_RATE) > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x01a39de0 > Sep 28 23:27:28 archvdr dtv_property_process_set() > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0009 > (DTV_INNER_FEC) > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x000b > Sep 28 23:27:28 archvdr dtv_property_process_set() > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0006 > (DTV_INVERSION) > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x0002 > Sep 28 23:27:28 archvdr dtv_property_process_set() > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x000d > (DTV_ROLLOFF) > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x0002 > Sep 28 23:27:28 archvdr dtv_property_process_set() > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0001 > (DTV_TUNE) > Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x > Sep 28 23:27:28 archvdr dtv_property_process_set() Finalised property cache > Sep 28 23:27:28 archvdr dtv_property_cache_submit() > Sep 28 23:27:28 archvdr dtv_property_cache_submit() adv, modulation = 0 > Sep 28 23:27:28 archvdr dtv_property_adv_params_sync() > Sep 28 23:27:28 archvdr dvb_frontend_ioctl_properties() Property cache is > full, tuning > > If you need further informations let me know. > > cu > > Edgar (gimli) Hucek > > > В сообщении от 28 September 2008 17:12:14 Niels Wagenaar написал(а): > >> Hi Igor, > >> > >> Small question. I tried your patch, but it fails a hunk in dvbdevice.c. > >> I > >> added this hunk manually but I think something is missing: > >> > >> Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,251): Operation not > >> supported Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,252): > >> Operation not supported Sep 28 13:56:15 htpc vdr: [19486] ERROR: > >> frontend > >> 0: Invalid argument > >> > >> Those both lines has the following code: > >> > >> CHECK(ioctl(fd_frontend, FE_SET_VOLTAGE, volt)); > >> CHECK(ioctl(fd_frontend, > >> FE_SET_TONE, tone)); > >> > >> The result is, no tuning and no picture. > >> > >> And to be honest, I don't really understand why it shouldn't work. > >> Mainly, > >> since the same code is used with the Kaffeine patch (I'm comparing that > >> also). > >> > >> Any help is appreciated :) If you need a quick chat, I'm currently in > >> #linuxtv on irc.freenode.net :) > >> > >> Regards, > >> > >> Niels Wagenaar > >> > >> > -Oorspronkelijk bericht- > >> > Van: Igor M. Liplianin [mailto:[EMAIL PROTECTED] > >> > Verzonden: zondag 28 september 2008 12:49 > >> > Aan: vdr@linuxtv.org; Niels Wagenaar > >> > CC: Gregoire Favre; [EMAIL PROTECTED] > >> > Onderwerp: [vdr][PATCH] S2API for vdr-1.7.0(1.7.1) quick hack > >> > > >> > ? ? ?? 24 September 2008 18:34:01 Niels Wagenaar ???(?): > >> > > Hello all (and especially Klaus): > >> > > > >> > > It's official, the people from V4L have voted for the usage of the > >> > > S2API proposal to be the future for new DVB API improvements (see > >> > &g
Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
Hi, I'm on Astra 19.2 and tested the following HD transponders : Anixe HD Arte HD Astra HD+ first test results : Arte HD tunes ok and plays fine. On Astra HD+ and Anixe HD im getting an error : Sep 28 23:27:28 archvdr dvb_frontend_ioctl_properties() FE_SET_PROPERTY Sep 28 23:27:28 archvdr dvb_frontend_ioctl_properties() properties.num = 8 Sep 28 23:27:28 archvdr dvb_frontend_ioctl_properties() properties.props = 41b31dc0 Sep 28 23:27:28 archvdr dtv_property_process_set() Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0011 (DTV_DELIVERY_SYSTEM) Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x0005 Sep 28 23:27:28 archvdr dtv_property_process_set() Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0003 (DTV_FREQUENCY) Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x00140cd0 Sep 28 23:27:28 archvdr dtv_property_process_set() Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0004 (DTV_MODULATION) Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x Sep 28 23:27:28 archvdr dtv_property_process_set() Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0008 (DTV_SYMBOL_RATE) Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x01a39de0 Sep 28 23:27:28 archvdr dtv_property_process_set() Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0009 (DTV_INNER_FEC) Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x000b Sep 28 23:27:28 archvdr dtv_property_process_set() Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0006 (DTV_INVERSION) Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x0002 Sep 28 23:27:28 archvdr dtv_property_process_set() Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x000d (DTV_ROLLOFF) Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x0002 Sep 28 23:27:28 archvdr dtv_property_process_set() Sep 28 23:27:28 archvdr dtv_property_dump() tvp.cmd= 0x0001 (DTV_TUNE) Sep 28 23:27:28 archvdr dtv_property_dump() tvp.u.data = 0x Sep 28 23:27:28 archvdr dtv_property_process_set() Finalised property cache Sep 28 23:27:28 archvdr dtv_property_cache_submit() Sep 28 23:27:28 archvdr dtv_property_cache_submit() adv, modulation = 0 Sep 28 23:27:28 archvdr dtv_property_adv_params_sync() Sep 28 23:27:28 archvdr dvb_frontend_ioctl_properties() Property cache is full, tuning If you need further informations let me know. cu Edgar (gimli) Hucek > ÷ ÓÏÏÂÝÅÎÉÉ ÏÔ 28 September 2008 17:12:14 Niels Wagenaar ÎÁÐÉÓÁÌ(Á): >> Hi Igor, >> >> Small question. I tried your patch, but it fails a hunk in dvbdevice.c. >> I >> added this hunk manually but I think something is missing: >> >> Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,251): Operation not >> supported Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,252): >> Operation not supported Sep 28 13:56:15 htpc vdr: [19486] ERROR: >> frontend >> 0: Invalid argument >> >> Those both lines has the following code: >> >> CHECK(ioctl(fd_frontend, FE_SET_VOLTAGE, volt)); >> CHECK(ioctl(fd_frontend, >> FE_SET_TONE, tone)); >> >> The result is, no tuning and no picture. >> >> And to be honest, I don't really understand why it shouldn't work. >> Mainly, >> since the same code is used with the Kaffeine patch (I'm comparing that >> also). >> >> Any help is appreciated :) If you need a quick chat, I'm currently in >> #linuxtv on irc.freenode.net :) >> >> Regards, >> >> Niels Wagenaar >> >> > -Oorspronkelijk bericht----- >> > Van: Igor M. Liplianin [mailto:[EMAIL PROTECTED] >> > Verzonden: zondag 28 september 2008 12:49 >> > Aan: vdr@linuxtv.org; Niels Wagenaar >> > CC: Gregoire Favre; [EMAIL PROTECTED] >> > Onderwerp: [vdr][PATCH] S2API for vdr-1.7.0(1.7.1) quick hack >> > >> > ? ? ?? 24 September 2008 18:34:01 Niels Wagenaar ???(?): >> > > Hello all (and especially Klaus): >> > > >> > > It's official, the people from V4L have voted for the usage of the >> > > S2API proposal to be the future for new DVB API improvements (see >> > > the official announcement at the bottom) within the V4L tree. >> > > Currently S2API is in a real speed-train and new devices are added >> > > very >> > >> > rapidly. >> > >> > > Only the devices currently in Multiproto and written by Manu Abraham >> > >> > are not yet ported. >> > >> > > Also people are allready busy with patches for Kaffeine (allready >> > > done) and MythTV (not seen yet, but it's WIP according to a post on >> > > the linux-dvb mail
Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
В сообщении от 28 September 2008 17:12:14 Niels Wagenaar написал(а):
> Hi Igor,
>
> Small question. I tried your patch, but it fails a hunk in dvbdevice.c. I
> added this hunk manually but I think something is missing:
>
> Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,251): Operation not
> supported Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,252):
> Operation not supported Sep 28 13:56:15 htpc vdr: [19486] ERROR: frontend
> 0: Invalid argument
>
> Those both lines has the following code:
>
> CHECK(ioctl(fd_frontend, FE_SET_VOLTAGE, volt)); CHECK(ioctl(fd_frontend,
> FE_SET_TONE, tone));
>
> The result is, no tuning and no picture.
>
> And to be honest, I don't really understand why it shouldn't work. Mainly,
> since the same code is used with the Kaffeine patch (I'm comparing that
> also).
>
> Any help is appreciated :) If you need a quick chat, I'm currently in
> #linuxtv on irc.freenode.net :)
>
> Regards,
>
> Niels Wagenaar
>
> > -Oorspronkelijk bericht-
> > Van: Igor M. Liplianin [mailto:[EMAIL PROTECTED]
> > Verzonden: zondag 28 september 2008 12:49
> > Aan: vdr@linuxtv.org; Niels Wagenaar
> > CC: Gregoire Favre; [EMAIL PROTECTED]
> > Onderwerp: [vdr][PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
> >
> > ? ? ?? 24 September 2008 18:34:01 Niels Wagenaar ???(?):
> > > Hello all (and especially Klaus):
> > >
> > > It's official, the people from V4L have voted for the usage of the
> > > S2API proposal to be the future for new DVB API improvements (see
> > > the official announcement at the bottom) within the V4L tree.
> > > Currently S2API is in a real speed-train and new devices are added
> > > very
> >
> > rapidly.
> >
> > > Only the devices currently in Multiproto and written by Manu Abraham
> >
> > are not yet ported.
> >
> > > Also people are allready busy with patches for Kaffeine (allready
> > > done) and MythTV (not seen yet, but it's WIP according to a post on
> > > the linux-dvb mailinglist).
> > >
> > > So, this should mean that VDR 1.7.x should focus on S2API because of
> > > the obvious reasons. Has anybody started on a patch of somekind to
> > > include S2API in VDR 1.7.0 or 1.7.1? Mainly I was thinking of doing
> >
> > it
> >
> > > myself (I have a Hauppauge WinTV-NOVA-HD-S2 which is allready
> > > supported in S2API) in the hope to have it working in the next
> > > weekend. But if it's allready done or in progress, then I would like
> > > to use my time for something else ;)
> > >
> > > Regards,
> > >
> > > Niels Wagenaar
> >
> > Hi Niels
> >
> > S2API for vdr-1.7.0(1.7.1) quick hack
> > Patch is ugly and only supported DVB-S. But it is useful to begin.
> > You may modify it like you wish.
> >
> > Igor
>
> ___
> vdr mailing list
> vdr@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
V.2
Only satellite, as I have not any cable or terrestrial, but it is easy to
modify :-)
I test it with cx24116 based card (though without ISL chip) and didn't find
any troubles.
Igor
diff -Naur vdr-1.7.0/channels.c vdr-1.7.0-s2/channels.c
--- vdr-1.7.0/channels.c 2008-04-12 16:49:12.0 +0300
+++ vdr-1.7.0-s2/channels.c 2008-09-28 21:43:04.0 +0300
@@ -21,114 +21,116 @@
// --- Channel Parameter Maps
const tChannelParameterMap InversionValues[] = {
- { 0, DVBFE_INVERSION_OFF, trNOOP("off") },
- { 1, DVBFE_INVERSION_ON, trNOOP("on") },
- { 999, DVBFE_INVERSION_AUTO },
+ { 0, INVERSION_OFF, trNOOP("off") },
+ { 1, INVERSION_ON, trNOOP("on") },
+ { 999, INVERSION_AUTO },
{ -1 }
};
const tChannelParameterMap BandwidthValues[] = {
- { 5, DVBFE_BANDWIDTH_5_MHZ, "5 MHz" },
- { 6, DVBFE_BANDWIDTH_6_MHZ, "6 MHz" },
- { 7, DVBFE_BANDWIDTH_7_MHZ, "7 MHz" },
- { 8, DVBFE_BANDWIDTH_8_MHZ, "8 MHz" },
- { 999, DVBFE_BANDWIDTH_AUTO },
+// { 5, BANDWIDTH_5_MHZ, "5 MHz" },
+ { 6, BANDWIDTH_6_MHZ, "6 MHz" },
+ { 7, BANDWIDTH_7_MHZ, "7 MHz" },
+ { 8, BANDWIDTH_8_MHZ, "8 MHz" },
+ { 999, BANDWIDTH_AUTO },
{ -1 }
};
const tChannelParameterMap CoderateValues[] = {
- { 0, DVBFE_FEC_NONE, trNOOP("none") },
- { 12, DVBFE_FEC_1_2, "1/2" },
- { 13, DVBFE_FEC_1_3, "1/3" },
- { 14, DVBFE_FEC_1_4, "1/4" },
- { 23, DVBFE_FEC_2_3, "2/3" },
- { 2
Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
Hi Igor, Small question. I tried your patch, but it fails a hunk in dvbdevice.c. I added this hunk manually but I think something is missing: Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,251): Operation not supported Sep 28 13:56:15 htpc vdr: [19486] ERROR (dvbdevice.c,252): Operation not supported Sep 28 13:56:15 htpc vdr: [19486] ERROR: frontend 0: Invalid argument Those both lines has the following code: CHECK(ioctl(fd_frontend, FE_SET_VOLTAGE, volt)); CHECK(ioctl(fd_frontend, FE_SET_TONE, tone)); The result is, no tuning and no picture. And to be honest, I don't really understand why it shouldn't work. Mainly, since the same code is used with the Kaffeine patch (I'm comparing that also). Any help is appreciated :) If you need a quick chat, I'm currently in #linuxtv on irc.freenode.net :) Regards, Niels Wagenaar > -Oorspronkelijk bericht- > Van: Igor M. Liplianin [mailto:[EMAIL PROTECTED] > Verzonden: zondag 28 september 2008 12:49 > Aan: vdr@linuxtv.org; Niels Wagenaar > CC: Gregoire Favre; [EMAIL PROTECTED] > Onderwerp: [vdr][PATCH] S2API for vdr-1.7.0(1.7.1) quick hack > > ? ? ?? 24 September 2008 18:34:01 Niels Wagenaar ???(?): > > Hello all (and especially Klaus): > > > > It's official, the people from V4L have voted for the usage of the > > S2API proposal to be the future for new DVB API improvements (see > > the official announcement at the bottom) within the V4L tree. > > Currently S2API is in a real speed-train and new devices are added > > very > rapidly. > > Only the devices currently in Multiproto and written by Manu Abraham > are not yet ported. > > Also people are allready busy with patches for Kaffeine (allready > > done) and MythTV (not seen yet, but it's WIP according to a post on > > the linux-dvb mailinglist). > > > > So, this should mean that VDR 1.7.x should focus on S2API because of > > the obvious reasons. Has anybody started on a patch of somekind to > > include S2API in VDR 1.7.0 or 1.7.1? Mainly I was thinking of doing > it > > myself (I have a Hauppauge WinTV-NOVA-HD-S2 which is allready > > supported in S2API) in the hope to have it working in the next > > weekend. But if it's allready done or in progress, then I would like > > to use my time for something else ;) > > > > Regards, > > > > Niels Wagenaar > > Hi Niels > > S2API for vdr-1.7.0(1.7.1) quick hack > Patch is ugly and only supported DVB-S. But it is useful to begin. > You may modify it like you wish. > > Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
> -Oorspronkelijk bericht- > Van: Igor M. Liplianin [mailto:[EMAIL PROTECTED] > Verzonden: zondag 28 september 2008 12:49 > Aan: vdr@linuxtv.org; Niels Wagenaar > CC: Gregoire Favre; [EMAIL PROTECTED] > Onderwerp: [vdr][PATCH] S2API for vdr-1.7.0(1.7.1) quick hack > > -- SNIP -- > > Hi Niels > > S2API for vdr-1.7.0(1.7.1) quick hack > Patch is ugly and only supported DVB-S. But it is useful to begin. > You may modify it like you wish. > Igor, thanks for the hack/patch! Now I have something to compare and this will speed it up for me very much :) I didn't had time to start with it yet (Family ;). It was my plan to start this evening. So if I have something new, I'll report this asap :) > Igor Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] S2API for vdr-1.7.0(1.7.1) quick hack
В сообщении от 24 September 2008 18:34:01 Niels Wagenaar написал(а):
> Hello all (and especially Klaus):
>
> It's official, the people from V4L have voted for the usage of the S2API
> proposal to be the future for new DVB API improvements (see the official
> announcement at the bottom) within the V4L tree. Currently S2API is in a
> real speed-train and new devices are added very rapidly. Only the devices
> currently in Multiproto and written by Manu Abraham are not yet ported.
> Also people are allready busy with patches for Kaffeine (allready done) and
> MythTV (not seen yet, but it's WIP according to a post on the linux-dvb
> mailinglist).
>
> So, this should mean that VDR 1.7.x should focus on S2API because of the
> obvious reasons. Has anybody started on a patch of somekind to include
> S2API in VDR 1.7.0 or 1.7.1? Mainly I was thinking of doing it myself (I
> have a Hauppauge WinTV-NOVA-HD-S2 which is allready supported in S2API) in
> the hope to have it working in the next weekend. But if it's allready done
> or in progress, then I would like to use my time for something else ;)
>
> Regards,
>
> Niels Wagenaar
Hi Niels
S2API for vdr-1.7.0(1.7.1) quick hack
Patch is ugly and only supported DVB-S. But it is useful to begin.
You may modify it like you wish.
Igor
diff -Naur 1/channels.c 2/channels.c
--- 1/channels.c 2008-04-12 16:49:12.0 +0300
+++ 2/channels.c 2008-09-28 13:02:01.0 +0300
@@ -21,114 +21,116 @@
// --- Channel Parameter Maps
const tChannelParameterMap InversionValues[] = {
- { 0, DVBFE_INVERSION_OFF, trNOOP("off") },
- { 1, DVBFE_INVERSION_ON, trNOOP("on") },
- { 999, DVBFE_INVERSION_AUTO },
+ { 0, INVERSION_OFF, trNOOP("off") },
+ { 1, INVERSION_ON, trNOOP("on") },
+ { 999, INVERSION_AUTO },
{ -1 }
};
const tChannelParameterMap BandwidthValues[] = {
- { 5, DVBFE_BANDWIDTH_5_MHZ, "5 MHz" },
- { 6, DVBFE_BANDWIDTH_6_MHZ, "6 MHz" },
- { 7, DVBFE_BANDWIDTH_7_MHZ, "7 MHz" },
- { 8, DVBFE_BANDWIDTH_8_MHZ, "8 MHz" },
- { 999, DVBFE_BANDWIDTH_AUTO },
+// { 5, BANDWIDTH_5_MHZ, "5 MHz" },
+ { 6, BANDWIDTH_6_MHZ, "6 MHz" },
+ { 7, BANDWIDTH_7_MHZ, "7 MHz" },
+ { 8, BANDWIDTH_8_MHZ, "8 MHz" },
+ { 999, BANDWIDTH_AUTO },
{ -1 }
};
const tChannelParameterMap CoderateValues[] = {
- { 0, DVBFE_FEC_NONE, trNOOP("none") },
- { 12, DVBFE_FEC_1_2, "1/2" },
- { 13, DVBFE_FEC_1_3, "1/3" },
- { 14, DVBFE_FEC_1_4, "1/4" },
- { 23, DVBFE_FEC_2_3, "2/3" },
- { 25, DVBFE_FEC_2_5, "2/5" },
- { 34, DVBFE_FEC_3_4, "3/4" },
- { 35, DVBFE_FEC_3_5, "3/5" },
- { 45, DVBFE_FEC_4_5, "4/5" },
- { 56, DVBFE_FEC_5_6, "5/6" },
- { 67, DVBFE_FEC_6_7, "6/7" },
- { 78, DVBFE_FEC_7_8, "7/8" },
- { 89, DVBFE_FEC_8_9, "8/9" },
- { 910, DVBFE_FEC_9_10, "9/10" },
- { 999, DVBFE_FEC_AUTO },
+ { 0, FEC_NONE, trNOOP("none") },
+ { 12, FEC_1_2, "1/2" },
+// { 13, FEC_1_3, "1/3" },
+// { 14, FEC_1_4, "1/4" },
+ { 23, FEC_2_3, "2/3" },
+// { 25, FEC_2_5, "2/5" },
+ { 34, FEC_3_4, "3/4" },
+ { 35, FEC_3_5, "3/5" },
+ { 45, FEC_4_5, "4/5" },
+ { 56, FEC_5_6, "5/6" },
+ { 67, FEC_6_7, "6/7" },
+ { 78, FEC_7_8, "7/8" },
+ { 89, FEC_8_9, "8/9" },
+ { 910, FEC_9_10, "9/10" },
+ { 999, FEC_AUTO },
{ -1 }
};
const tChannelParameterMap ModulationValues[] = {
- { 0, DVBFE_MOD_NONE,trNOOP("none") },
- { 4, DVBFE_MOD_QAM4,"QAM4" },
- { 16, DVBFE_MOD_QAM16, "QAM16" },
- { 32, DVBFE_MOD_QAM32, "QAM32" },
- { 64, DVBFE_MOD_QAM64, "QAM64" },
- { 128, DVBFE_MOD_QAM128, "QAM128" },
- { 256, DVBFE_MOD_QAM256, "QAM256" },
- { 512, DVBFE_MOD_QAM512, "QAM512" },
- {1024, DVBFE_MOD_QAM1024, "QAM1024" },
- { 1, DVBFE_MOD_BPSK,"BPSK" },
- { 2, DVBFE_MOD_QPSK,"QPSK" },
- { 3, DVBFE_MOD_OQPSK, "OQPSK" },
- { 5, DVBFE_MOD_8PSK,"8PSK" },
- { 6, DVBFE_MOD_16APSK, "16APSK" },
- { 7, DVBFE_MOD_32APSK, "32APSK" },
- { 8, DVBFE_MOD_OFDM,"OFDM" },
- { 9, DVBFE_MOD_COFDM, "COFDM" },
- { 10, DVBFE_MOD_VSB8,"VSB8" },
- { 11, DVBFE_MOD_VSB16, "VSB16" },
- { 998, DVBFE_MOD_QAMAUTO, "QAMAUTO" },
- { 999, DVBFE_MOD_AUTO },
+// { 0, MOD_NONE,trNOOP("none") },
+// { 4, MOD_QAM4,"QAM4" },
+ { 16, QAM_16, "QAM16" },
+ { 32, QAM_32, "QAM32" },
+ { 64, QAM_64, "QAM64" },
+ { 128, QAM_128, "QAM128" },
+ { 256, QAM_256, "QAM256" },
+// { 512, MOD_QAM512, "QAM512" },
+// {1024, MOD_QAM1024, "QAM1024" },
+// { 1, MOD_BPSK,"BPSK" },
+ { 2, QPSK,"QPSK" },
+// { 3, MOD_OQPSK, "OQPSK" },
+ { 5, _8PSK,"8PSK" },
+ { 6, _16APSK, "16APSK" },
+// { 7, MOD_32APSK, "32APSK" },
+// { 8, DVBFE_MOD_OFDM,"OFDM" },
+// { 9, MOD_COFDM, "COFDM" },
+ { 10, VSB_8,"VSB8" },
+ { 11, VSB_16, "VSB16" },
+ { 998, QAM_AUTO, "QAMAUTO" },
+// { 999, MOD_AUTO },
{ -1 }
};
const tChannelParameterMap SystemValues[] =
