[linux-dvb] Re: AW: Re: DVB-S in the US.

To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Re: AW: Re: DVB-S in the US.
From: William E. Mrozinski <wem@dcshome.com>
Date: Thu, 28 Jun 2001 08:34:46 -0400
Gerhard,

    Unfortunately, the only way to register for
WinDVBLive2000 is to bank wire
them the registration fee.  At the moment my bank wants
$40us as the fee to wire
them $15us for registration(g), so I've been holding
that on the back burner.
If they had another way to register and pay ( plastic
would be perfect but I
know there is a merchants fee on their end ) I would
have joined weeks ago.  I'd
be happy to pay a higher registration fee to cover this
just for the 'instant
gratification' but bank wire is about the worst option
they could have chosen (
again, I understand why but its a major hassle and cost
).

    I think the last time I checked DVBControl it
appeared to still be tied to the old API which doesn't
support the new frontend, but I'll look again today. 
Thanks for the
tips!

    Bill

"Gerhard Andreas (RtW1/WIR2)" wrote:

> Hello William,
>
> looking at your situation I was just wondering, whether you already have
> checked out the following software alternatives for the DVB-S in Windoze:
>
> WinDVBLive
> http://www.odsoft.org
> This is a big project, which became sort of shareware some time ago due to
> the amount of work (~USD15).
>
> DVBControl
> Look in WinDVBLive-Forum @alternative software
> Smaller project, working and still freeware
>
> Best,
> Andreas
>
> -----Ursprüngliche Nachricht-----
> Von: William E. Mrozinski [mailto:wem@dcshome.com]
> Gesendet: Mittwoch, 27. Juni 2001 23:34
> An: linux-dvb@linuxtv.org
> Betreff: [linux-dvb] Re: DVB-S in the US.
>
> Chris,
>
>     I have the exact same setup here in the states too and I've been playing
> with
> both the TT software for 'doze 98 and the Linux driver/vdr since about
> March and have yet to have any success under Linux; I've covered much of
> the same ground you have on the linux side and can confirm:
>
> 1) I've never got a lock or video yet with dvb/vdr, using mainly T5 since
> there
> is plenty of fta there for us (USA).
> 2) The video out pre-lock has always been PAL for me too even after changing
> both code references and the driver startup option.
> 3) I haven't even gotten past the 2.1 'channel not sync'd' issue which many
> are
> having now with the current driver on both sides of the pond.
> 4) Under the TT/Win software there is definitely an issue with the current
> drivers/firmware and spectral_inversion settings.  The auto setting which
> all the software ( TT & Haup's ) default to only currently finds SI_OFF
> bouquets.  This may be isolated to the Win firmware; I think dvb loads
> its own version of firmware, not sure on this.
>
> It looks like you are after dish programming; see if the transponders you
> can at least partially decode are all SI_ON per lyngsat and if those that
> won't lock are SI_OFF... ( I'll try this too on E6 in the next day or so
> and report back... )
>
> Do you know if a CA board will work with dish and their access card???
> If it does then I can expand my usefulness of dvb/vdr tremendously!
> ( once its working well! ) and maybe ditch my 301 box
> ( got a 501 pvr too.. not too shabby ) but to be able to record on the pc
> under my dish subscription is the holy grail!!!.
>
> I've finally been able to use this card reasonably since I got ahold of the
> new TT api that supports the 2.1's new frontend; this is how I was able
> to confirm the spectral inversion issue ( at least under all flavors of the
> TT or Haup software to-date )  I also added custom settings for Viterbi
> and, as you have also experienced, changing this seems to not stop locks
> or help locking when there are issues.  Its almost like its always in
> VR_AUTO mode regardless of the forced setting.  If the two platform's
> apis are the same then:
>
>   VR_AUTO  =  0,    // DVB-S: automatic detection of viterbi rate
>   VR_1_2  =  1,    // DVB-S: viterbi rate: 1/2
>   VR_2_3  =  2,    // DVB-S: viterbi rate: 2/3
>   VR_3_4  =  3,    // DVB-S: viterbi rate: 3/4
>   VR_4_5  =  4,    // DVB-S: viterbi rate: 4/5
>   VR_5_6  =  5,    // DVB-S: viterbi rate: 5/6
>   VR_6_7  =  6,    // DVB-S: viterbi rate: 6/7
>   VR_7_8  =  7,    // DVB-S: viterbi rate: 7/8
>   VR_8_9  =  8,    // DVB-S: viterbi rate: 8/9
>
> I'll confirm this too later today and report back.
>
> Have you compared your results under Linux with the Win software?
> ( Just curious... )
>
> You have actually gotten further with dvb/vdr under linux than I have
> to-date but I switched my experimenting to Win after I got the api and
> while the 2.1 driver support is still iffy.
>
> Please let me know about the dishnet CA support; I may need to place another
> order to get me a CA board!
>
>         Bill
>
> Chris Worley wrote:
>
> > I'm using the Hauppauge DVB-S card with the DVB software, in the U.S..
> >
> > My dish is aimed at Echostar 6:
> >
> >         http://www.lyngsat.com/echo6.shtml
> >
> > (watch out for the pop-up adds.)
> >
> > In using the libdvb/stest utility, I setup my TEST file as:
> >
> > LNB ID 0 TYPE 0 DISEQCNR 0
> >    SAT ID 119 NAME "EchoStar 6" LNBID 0 FMIN 974000 FMAX 1411000
> >      TRANSPONDER ID 0002 SATID 0119 TYPE 0 FREQ 989000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 0003 SATID 0119 TYPE 0 FREQ 1003000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 0006 SATID 0119 TYPE 0 FREQ 1047000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 0008 SATID 0119 TYPE 0 FREQ 1076000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 0009 SATID 0119 TYPE 0 FREQ 1091000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 000a SATID 0119 TYPE 0 FREQ 1105000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 000b SATID 0119 TYPE 0 FREQ 1120000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 000c SATID 0119 TYPE 0 FREQ 1134000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 000d SATID 0119 TYPE 0 FREQ 1149000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 000e SATID 0119 TYPE 0 FREQ 1164000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 0011 SATID 0119 TYPE 0 FREQ 1207000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 0012 SATID 0119 TYPE 0 FREQ 1222000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 0014 SATID 0119 TYPE 0 FREQ 1251000 POL H SRATE
> > 20000000 FEC 2
> >      TRANSPONDER ID 0015 SATID 0119 TYPE 0 FREQ 1266000 POL H SRATE
> > 20000000 FEC 2
> >
> > I figure we don't need the dual LNB baselines in the states, so I set
> > all that to zero, and work directly off the LNB frequency.
> >
> > The FEC is reported to be 3/4.  I don't know which dvb code this
> > corresponds to, but FEC code "2" and "3" work; "2" seems to work a
> > little better.  I'm not sure what the "type" field is, it doesn't seem
> > to effect results anyway.
> >
> > Running stest proves somewhiat unpredictable.  Sometimes it finds
> > PAT/PMT data for a frequency, other times it doesn't.  Sometimes the
> > channel ID's are all printed as "FFFFFFFF" for a given frequency,
> > sometimes the printout is fine.
> >
> > I did find one error, where DVB.cc got confused and try to look at
> > cable data.  In "DVB::scan_tp":
> >
> >                 if (!prog->prog_nr) {
> >                         dvb_nit_t *nit = (dvb_nit_t *)calloc (1, sizeof
> (dvb_nit_t));
> >                         if (GetNIT(nit) >= 0) {
> >                                 if (prog->prog.nit)
> >                                         free(prog->prog.nit);
> >                                 prog->prog.nit = nit;
> >                         } else
> >                                 free(nit);
> >
> >                         //if (fdvb >= 0) osd.Text(64, 120, 2, 1, "NIT");
> >
> >                         cerr << "NIT\n";
> >
> >                         // FIXME: fix NIT parsing
> >                         //if (front.type!=FRONT_DVBC)
> >                       tp.freq=(uint32_t) (1000000*nit->freq+0.5);
> >
> > I commented out that last line, and it quit printing the wrong
> > frequency for found PAT/PMT's.
> >
> > The output data from stest looks something like this:
> >
> > LNB ID 0 TYPE 0  DISEQCNR 0
> >    SAT ID 119 NAME "EchoStar 6" LNBID 0 FMIN 974000 FMAX 1411000
> >      TRANSPONDER ID 0002 SATID 0119 TYPE 1 FREQ 989000 POL H SRATE
> > 20000000 FEC 2
> >        CHANNEL ID 0 NAME "BET" SATID 0119 TPID 2 SID 7c TYPE 1 VPID
> > 1022 APID 1023 PCRPID 1022
> >        CHANNEL ID 1 NAME "HBO-E" SATID 0119 TPID 2 SID 12c TYPE 1 VPID
> > 1422 APID 1423 PCRPID 1422
> >        CHANNEL ID 2 NAME "GOLF" SATID 0119 TPID 2 SID 191 TYPE 1 VPID
> > 1822 APID 1823 PCRPID 1822
> >        CHANNEL ID 3 NAME "EVENT" SATID 0119 TPID 2 SID 1c7 TYPE 1 VPID
> > 1022 APID 1023 PCRPID 1022
> >        CHANNEL ID 4 NAME "CNNFN" SATID 0119 TPID 2 SID ce TYPE 1 VPID
> > 1422 APID 1423 PCRPID 1422
> >        CHANNEL ID 5 NAME "GLVSN" SATID 0119 TPID 2 SID 110 TYPE 1 VPID
> > 1822 APID 1823 PCRPID 1822
> >        CHANNEL ID 6 NAME "TECH" SATID 0119 TPID 2 SID bf TYPE 1 VPID
> > 1022 APID 1023 PCRPID 1022
> >        CHANNEL ID 7 NAME "COURT" SATID 0119 TPID 2 SID cc TYPE 1 VPID
> > 1422 APID 1423 PCRPID 1422
> >        CHANNEL ID 8 NAME "BRAVO" SATID 0119 TPID 2 SID 81 TYPE 1 VPID
> > 1022 APID 1023 PCRPID 1022
> >        CHANNEL ID 9 SATID 0119 TPID 2 SID 8f01 TYPE 0 VPID 1422 APID
> > 1423 PCRPID 1422
> >        CHANNEL ID a NAME "AUD01" SATID 0119 TPID 2 SID 39b TYPE 1 VPID
> > 1822 APID 1823 PCRPID 1822
> >        CHANNEL ID b NAME "AUD13" SATID 0119 TPID 2 SID 3a8 TYPE 1 VPID
> > 1022 APID 1023 PCRPID 1022
> >        CHANNEL ID c NAME "AUD16" SATID 0119 TPID 2 SID 3ab TYPE 1 VPID
> > 1422 APID 1423 PCRPID 1422
> >        CHANNEL ID d NAME "METRO" SATID 0119 TPID 2 SID 3a4 TYPE 1 VPID
> > 1822 APID 1823 PCRPID 1822
> >
> > Note how the vpid/apid data keeps repeating (for example, it says the
> > only audio PIDS for these 14 channels are 1022, 1422, and 1822).  The
> > real PIDS can be seen here:
> >
> >         http://www.lyngsat.com/dig/dish119.shtml
> >
> > (Again, sorry for any pop-up adds.)
> >
> > Furthermore, stest doesn't find anything at the frequencies for about
> > half of the transponder ID's.
> >
> > I found two flags pertaining to NTSC/PAL in the driver, but switching
> > them to what should have setup NTSC output didn't work, so I switched
> > them back, and got a PAL-syncing TV.
> >
> > Switching to VDR, I setup my channel.conf file with a clear (no CA)
> > channel:
> >
> >         DISH1:11340:h:0:20000:4386:4387:12:0:101
> >
> > (1134 MHz, 200 M/sym/sec, vpid/apid 4386/4387, transponder 12, no CA,
> > SID 101.)
> >
> > Those PIDS are as reported at the above web site for this channel
> > (rather than what the stest scan found).
> >
> > In playing with this line in channel.conf, there were a few times when
> > I could get VDR to display the channel information data in the stream,
> > but I have not been able to repeat that (it allways comes up with
> > "DISH1" and the time, but a few times it also came up with the channel
> > information data describing the channel).
> >
> > I can't get it to display any video data.
> >
> > Any ideas on what other tests I can do or get it to work?
> >
> > Thanks,
> >
> > Chris
> >
> > --
> > Info:
> > To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe
> linux-dvb" as subject.
>
> --
> Info:
> To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe
> linux-dvb" as subject.



-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.
Prev by Date: [linux-dvb] Re: DVB-S in the US.
Next by Date: [linux-dvb] VIDEO_STILLPICTURE
Prev by thread: [linux-dvb] VIDEO_STILLPICTURE
Next by thread: [linux-dvb] dvdplayer with region 1 dvd, success with new kernel
Index(es):
- Date
- Thread
Home | Main Index | Thread Index