[linux-dvb] re: megasky does it actualy tune then???
On Wed, 2006-10-18 at 22:40 +0100, Andrew Waldram wrote: > As I couldn't find the post thought I'd better link it here ;-) > > http://www.linuxtv.org/pipermail/linux-dvb/2006-October/013572.html > > shows the error I get when trying to tune I get the same errors. I believe they are due to the frequencies in UK and Australian being offset from the centre frequency. The qt1010.h file seems to have been hardcoded that the frequency must be divisible by 200. > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: Megasky on 2.6.18
On Wed, 2006-10-18 at 17:24 +0930, Malcolm Caldwell wrote: > Hello, > > I am trying to work out how to compile the megasky driver under 2.6.18. > I don't know enough about hg to see if there is an easy way to do this. > Can I somehow magically pull in the changes between the megasky tree and > the v4l-dvb tree? Don't worry, as I said I don't know hg: I had somehow created a tarball without the megasky drivers in it. Now things seem to be working. :) > > > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Megasky on 2.6.18
Hello, I am trying to work out how to compile the megasky driver under 2.6.18. I don't know enough about hg to see if there is an easy way to do this. Can I somehow magically pull in the changes between the megasky tree and the v4l-dvb tree? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] afatech af9005
Hello all,
Has anyone had any luck with this device?
Has anyone tried to approach the manufacturer? They seem to have a
website at http://www.afatech.com.tw/e_home.htm
On the page at http://www.afatech.com.tw/product/e_product.htm they show
their dvb-t chips, and state that there a datasheet.
I don't mind asking, but thought I should ask if anyone has tried this
already.
On Tue, 2006-05-02 at 21:16 +0200, Gunther Mayer wrote:
> steve lynch wrote:
>
> > Dear All,
> >
> > I have an unbranded USB DVB stick that works fine with the provided
> > software under windows.
> >
> > I wanted to use it to move my Mythtv box from the analogue into the
> > digital era. Trouble is the device is unrecognised. Surprise surprise.
> >
> > Physically it looks identical to the Yakumo stick but has an unknown
> > USB VID/PID the only reported branding is from lsusb which reports the
> > vendor name as "Afatech" ('lsusb' below)
> >
> > Has anyone seen this device? If not would anyone care to rate my
> > chance of success (panic free device driver) simply by doing an
> > initial rebuild of dtt200 module with my cards VID/PID in it?
> >
> > - steve
> >
> > Bus 001 Device 002: ID 15a4:9020
> > Device Descriptor:
> > bLength18
> > bDescriptorType 1
> > bcdUSB 1.10
> > bDeviceClass 255 Vendor Specific Class
> > bDeviceSubClass 255 Vendor Specific Subclass
> > bDeviceProtocol 255 Vendor Specific Protocol
> > bMaxPacketSize016
> > idVendor 0x15a4
> > idProduct 0x9020
> > bcdDevice1.00
> > iManufacturer 1 Afatech
> > iProduct2 DVBT
> >
>
> This is the only device yet with Afatech 9005 (see www.bttv-gallery.de)
> This is not supported yet.
>
> You can ask the vendor if he releases the required information or will
> procide
> an open source driver
>
> Gunther
>
> ___
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] channels file for scan for Darwin Australia
Here is my apps/scan/dvb-t/au-Darwin file for Darwin Australia. Out of curiosity: In Australia channels can be 125Khz off centre. When I scan the scan picks up from the information on air that there are channels I have specified in my file but without the 125Khz. What is wrong here? Is the information from the channel wrong, or should scan look +-125Khz. I would have though there would be a standard for this so STBs can scan properly. Anyway - someone might like to add this file to the cvs. # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 543625000 7MHz 3/4 NONE QAM64 8k 1/16 NONE T 55050 7MHz 2/3 NONE QAM64 8k 1/8 NONE T 536625000 7MHz 2/3 NONE QAM64 8k 1/8 NONE T 557625000 7MHz 2/3 NONE QAM64 8k 1/8 NONE
[linux-dvb] Re: Difference btw Binary Only Kernel Modules and Firmware
Not that I can add much to this discussion but... On Mon, 2003-12-22 at 23:12, Egon Single wrote: > Just a philisophical question. Most of you will know that binary only kernel > modules are real evil. You just have to listen to Linus who keeps repeating > this. Now I ask myself what is difference between binary only kernel modules > and the binary only firmware in the DVB driver? (This expands on something Ralph said) Remember: almost all hardware these days has firmware - eg. Hard drive controllers, graphics cards etc. Most times that firmware is in rom/flash etc. Some hareware manifacturers have had the good wisdom to make their fireware easily upgradable. Do you expect any hardware device manufactured to come with source to its hardwired firmware? Why should firmware that is downloaded to the device at driver startup be any different? Perhaps we should say that devices that have hardwired firmware can work with a stock kernel, but not devices with downloaded firmware? (Anyway - this is not the place to discuss this stuff - and I doubt I am adding much that has not been said by others before) > The following appear to be contradictions in terms: > Linux developers want to be able to examine every piece of critical code. > Software producers are looking for a way to protect their IP. > > Can the firmware approach help to resolve this conflict? Or is it just > another name for the same old game? I am grateful for your comments. > > Best regards > Egon > > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: Choosing the "best" DVB-S premium card
On Mon, 2003-12-15 at 04:33, Michal Dobrzynski wrote: > Hi, > > Given the apparent reluctance for anyone to answer my question could > someone at least answer whether the rev1.5 card is unconditionally and > absolutely better than the rev1.6 card (it seems that way from the > specifications and descriptions). > > Also what are all the known problems with support for these cards under > linux? Any limitations, bugs, instabilities, etc. None off this seems > to be documented anywhere. Michael, I don't know how long you have been following this mailing list. Recently there was a big long heated discussion with the dvb authors stating that they do not like full featured DVB cards. This may be why you have not received an answer. I am with you on this: at the moment (and I stress at the moment) full featured cards would seem to be the only way to get: 1. Good TV out 2. CAM support Until someone can describe how to do both with a budget card and TV out on a graphics card I believe that a full featured card is the way to go. (Alas, such a card is beyond my budget...) I would suggest you ask the vdr list about 1.5 vs 1.6 - I would have thought that many people there would be able to answer your question. (BTW: I use a dxr3 and get good output. There are stability problems though. Mine is bt865 based) > Regards, > Michal Dobrzynski > > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] DVB-T in Australia problem
Hello, I have been trying to get a DVB-T card working in Darwin Australia. In Australia each of the original analogue channels now have their own multiplex (they need the bandwidth for HDTV). I can tune one of the multiplexes here fine - the other 3 don't work. I have been working on the assumption that it is my antenna that is the problem. I have installed a longer pole and the one multiplex that works now has a lower verror - but I still get nothing for the others. I *think* I am using the correct frequencies and other modulation parameters. Are we sure that there is no driver problem at play here? Below are some logs with tzap and scan. (For scan I 'if 0'ed out the existing dvb-t definitions and added the local multiplexes - for each frequency I tried what is supposed to be the two sets of modulation paremeters used in Australia) Of note I have a working Budget DVB-S card in this system: Working channel: # ./tzap -a 1 NTD using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' tuning to 55050 Hz status 01 | signal 3a3a | snr | ber | unc | status 1f | signal 3a3a | snr d7d7 | ber 00c6 | unc | FE_HAS_LOCK status 1f | signal 3a3a | snr cfcf | ber 00c6 | unc | FE_HAS_LOCK status 1f | signal 3a3a | snr d5d5 | ber 00c5 | unc | FE_HAS_LOCK status 1f | signal 3a3a | snr d3d3 | ber 00bc | unc | FE_HAS_LOCK status 1f | signal 3a3a | snr d5d5 | ber 00b8 | unc | FE_HAS_LOCK status 1f | signal 3a3a | snr d5d5 | ber 00bd | unc | FE_HAS_LOCK status 1f | signal 3a3a | snr d6d6 | ber 00ae | unc | FE_HAS_LOCK status 1f | signal 3a3a | snr d6d6 | ber 00bd | unc | FE_HAS_LOCK status 1f | signal 3a3a | snr d3d3 | ber 00c3 | unc | FE_HAS_LOCK status 1f | signal 3a3a | snr d7d7 | ber 00ab | unc | FE_HAS_LOCK status 1f | signal 3a3a | snr d3d3 | ber 00b0 | unc | FE_HAS_LOCK status 1f | signal 3a3a | snr d4d4 | ber 00cc | unc | FE_HAS_LOCK Non-working channel: #./tzap -a 1 ABC using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' tuning to 54350 Hz status 01 | signal 3a3a | snr | ber 00be | unc | status 01 | signal 3a3a | snr | ber | unc | status 01 | signal 3a3a | snr | ber | unc | status 01 | signal 3a3a | snr | ber | unc | status 01 | signal 3a3a | snr | ber | unc | status 01 | signal 3a3a | snr | ber | unc | status 01 | signal 3a3a | snr | ber | unc | Another: # ./tzap -a 1 SBS using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' tuning to 53650 Hz status 01 | signal 3a3a | snr | ber | unc | status 03 | signal 3a3a | snr | ber | unc | status 03 | signal 3a3a | snr | ber | unc | status 03 | signal 3a3a | snr | ber | unc | status 03 | signal 3a3a | snr | ber | unc | # ./scan -a 1 using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' >>> tune to: >>> 54350:INVERSION_OFF:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: >>> 54350:INVERSION_OFF:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE >>> (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: >>> 54350:INVERSION_OFF:BANDWIDTH_7_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: >>> 54350:INVERSION_OFF:BANDWIDTH_7_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE >>> (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: >>> 53650:INVERSION_OFF:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: >>> 53650:INVERSION_OFF:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE >>> (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: >>> 53650:INVERSION_OFF:BANDWIDTH_7_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: >>> 53650:INVERSION_OFF:BANDWIDTH_7_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE >>> (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: >>> 55050:INVERSION_OFF:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: >>> 55050:INVERSION_OFF:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE >>> (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: >>> 55050
[linux-dvb] Re: DVB-T in Australia
On Mon, 2003-03-24 at 16:24, Holger Waechtler wrote:
> Malcolm Caldwell wrote:
> > Hello,
> >
> > First a quick question: has anyone been able to get a nova-t to work in
> > Australia yet?
> >
> > I have been helping a user via email/phone (he is on the other side of
> > the continent) who is new to linux try to get his nova-t card to work
> > here in Australia. He purchased the card in the UK and has been able to
> > get it to work since. He has tried to do this under windows with no
> > success and so now is trying linux.
> >
> > We have go the system to the point where the drivers
> > (linuxtv-dvb-1.0.0-pre1) are installed, the card is detected etc and
> > dvbtune (from dvbtools on sourceforge) runs.
> >
> > When the card is tuned to the correct frequency with what is apparently
> > the correct parameters for the transmitter. dvbtune reports that there
> > is signal and carrier but fails to get any further. He tried changing
> > various parameters (frequency/bandwidth/transmission etc) and only got
> > the expected result of no carrier and/or no signal.
> >
> >>From this it would seem that perhaps the frontend is not really working
> > with 7Mhz.
>
> I'm not sure if the Grundig frontend (your card has one, right?)
I have asked Mark (its his computer and card) to confirm this.
> is able
> to tune to VHF channels (you try to, right?).
I am sorry - I should have mentioned: We are trying to tune a UHF
channel. I assume that if this card is going to work at all in
Australia then UHF channels should be the simplest to get working. If
they work then we can try VHF as well. There are places in Australia
where DVB will only be broadcast on UHF so a card with non-working VHF
is still useful as long as UHF works.
> Maybe with other PLL
> settings this is possible, maybe it's really a limitation of the analog
> tuner in the frontend.
>
> Is it possible to tune to these channels using the Windows driver?
No.
> Please try to modify the tsa5060_set_tv_freq() function as shown below
> and report if it works for you.
>
> thanks,
>
> Holger
>
>
>
> /**
> * set up the downconverter frequency divisor for a
> * reference clock comparision frequency of 16 Hz.
> * frequency offset is 36125000 Hz.
> */
> static
> int tsa5060_set_tv_freq (struct dvb_i2c_bus *i2c, u32 freq)
> {
> u32 div;
> u8 buf [4];
> u8 cfg, cpump, band_select;
>
>
> div = (36125000 + freq) / 16;
> cfg = 0x88;
>
>
> cpump = div < 175000 ? 2 : div < 39 ? 1 :
> div < 47 ? 2 : div < 75 ? 1 : 3;
>
>
> band_select = div < 175000 ? 0x0e : div < 47 ? 0x05 : 0x03;
>
>
> buf [0] = (div >> 8) & 0x7f;
> buf [1] = div & 0xff;
> buf [2] = ((div >> 10) & 0x60) | cfg;
> buf [3] = cpump | band_select;
>
>
> return tsa5060_write(i2c, buf);
> }
>
>
>
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
[linux-dvb] Re: DVB-T in Australia
A quick correction: On Mon, 2003-03-24 at 10:22, Malcolm Caldwell wrote: > Hello, > > First a quick question: has anyone been able to get a nova-t to work in > Australia yet? > > I have been helping a user via email/phone (he is on the other side of > the continent) who is new to linux try to get his nova-t card to work > here in Australia. He purchased the card in the UK and > has been able to has not been able to > get it to work since. He has tried to do this under windows with no > success and so now is trying linux. > > We have got the system to the point where the drivers > (linuxtv-dvb-1.0.0-pre1) are installed, the card is detected etc and > dvbtune (from dvbtools on sourceforge) runs. > > When the card is tuned to the correct frequency with what is apparently > the correct parameters for the transmitter. dvbtune reports that there > is signal and carrier but fails to get any further. He tried changing > various parameters (frequency/bandwidth/transmission etc) and only got > the expected result of no carrier and/or no signal. > > >From this it would seem that perhaps the frontend is not really working > with 7Mhz. > > > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] DVB-T in Australia
Hello, First a quick question: has anyone been able to get a nova-t to work in Australia yet? I have been helping a user via email/phone (he is on the other side of the continent) who is new to linux try to get his nova-t card to work here in Australia. He purchased the card in the UK and has been able to get it to work since. He has tried to do this under windows with no success and so now is trying linux. We have go the system to the point where the drivers (linuxtv-dvb-1.0.0-pre1) are installed, the card is detected etc and dvbtune (from dvbtools on sourceforge) runs. When the card is tuned to the correct frequency with what is apparently the correct parameters for the transmitter. dvbtune reports that there is signal and carrier but fails to get any further. He tried changing various parameters (frequency/bandwidth/transmission etc) and only got the expected result of no carrier and/or no signal. >From this it would seem that perhaps the frontend is not really working with 7Mhz. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] OT: What is this item from ebay
This is fairly OT - but I thought someone here might know: what is this item that is listed on ebay? http://cgi.ebay.com.au/ws/eBayISAPI.dll?ViewItem&item=3405988879&ssPageName=ADME:B:SS:AU:1 "You are bidding on DVB EVS Broadcast Equipment Digital Video Broadcasting (DVB) Input / Output Signal Converter Selectable ASI vs LVDS Input & Output Dual (2) Selectable, ASI / LVDS Input Sources Triple (3) Output Ports ASI / LVDS Dual (2) (Data A Data B) Wide SCSI III Ports 19" Rack mountable Chassis Units are new in the makers boxes. So feel confident to purchase as many as you want. Items are sold with a 3 day warrany after receipt. MA residents please add 5% sales tax. Buyer pays S/H. Payment must be received within 7 days. I accept paypal, money orders, and checks (held for clearance)." I don't know many of the phrases (ASI, LVDS) etc. Is this a converter that will convert analogue video into some kind of DVB stream? This is obviously broadcast equipment - would this be useful in any kind of home setup? -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: margi driver
Hello, At least now it compiles :) The problem is it does not appear to work. The following is from dmesg when I run ntuxplayer convdvd : -- AudioClose convdvd : -- L64021Init convdvd : L64021 Software reset... convdvd : L64021 Software reset done. convdvd : L64021 Rev. 0x04 reset successfully. convdvd : -- L64021Setup convdvd : -- MargiFreeBuffers convdvd : DRAM Allocate 0x-0x0513 convdvd : DRAM Allocate 0x0520-0x0A1B convdvd : OSD Open 100X101, 4 bit, mem 0x/0x0520 convdvd : DRAM Free 0x convdvd : DRAM Free 0x0520 bug: kernel timer added twice at d08cafea. convdvd : margi_open - already open On Mon, 2003-03-10 at 21:10, Holger Waechtler wrote: > Hi, > > Malcolm Caldwell wrote: > > Hello, > > > > What is the current state of the margi driver? I tried linuxtv cvs - it > > has references to makepatch but makepatch is not there. > > I updated the Margi stuff, it should compile again. I have no PCMCIA > slot here right now, so I can't test if it works. > > Please try this: > > $ cvs -d :pserver:[EMAIL PROTECTED]:/cvs/linuxtv co DVB > $ cd DVB/driver > > now edit the Makefile: > > CARDS = av7110 > CARDS += #margi > > should get: > > CARDS = #av7110 > CARDS += margi > > then compile and load the modules: > > $ make && make insmod > > please report if it works, > thanks, > > Holger > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] margi driver
Hello, What is the current state of the margi driver? I tried linuxtv cvs - it has references to makepatch but makepatch is not there. Metzler drivers do not semm to have the margi code. Any advice? -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: [vdr] Re: dxr3/vdr problem
On Thu, 2003-03-06 at 20:53, Holger Waechtler wrote: > Malcolm Caldwell wrote: > > > >>>It understand it is related > >>>to BER but how? > >> > >>Block Errors - or better Uncorrected Block Error Count - is the number > >>of MPEG packets that have not been corrected by the forward error > >>correction unit. These get visible as real artifacts in video or audio. > > > > > > If I understand correctly my hardware (budget card) can't report the > > Block errors at the same time as the bit error rate. Does this mean > > that the packets in the TS are not maked with the > > transport_error_indicator bit as mentioned by Johannas? Or is this bit > > worked out some other way? (I will try to look at the driver later) > > no, the transport_error_indicator bit should always get set for > uncorrectable packets. > > > >>In some setups the RF emissions or instable power supplies of your PC > >>might cause problems, > > > > > > Do these power supply problems appear any other way? I would I know if > > this was the problem? Are budget cards susceptible to this kind of > > problem? The reason I ask is it would appear that the card can't power > > my lnb - it works when I connect through my stand alone receiver's > > loop-back connector - but if I turn off the receiver or connect directly > > I have problems. > > Try to borrow + install a stronger power supply and see if this helps... OK - I now have a 300W power supply and there is not much change. (Well, now my irman works again and thats a good thing ;) but no change to the dvb behaviour). Now, the errors I am getting could well be due to a mis-aligned dish. It is worth noting that my stand alone receiver is also having problems since I plugged my budget card into its loop-back port. I think that is just a coincidence. I was away when my card arrived and set it up as soon as I could - it could be that my stand alone receiver/dish were in fact not working well since some time when I was away. We did have some storms while I was away. On the fault where without the receiver powered up I get no signal: Could it be that my budget card simply cannot power my LNB? This is a c-band LNB and so perhaps it has a high draw? > Holger > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: [vdr] Re: dxr3/vdr problem
On Thu, 2003-03-06 at 22:02, Johannes Stezenbach wrote: > Malcolm Caldwell wrote: > > Signal=53116, Verror=0, SNR=43860dB, BlockErrors=0, (S|L|C|V|SY|) >^^ > If the documentation still claims that it devlivers the SNR in dB > it's obviuosly wrong. I don't know about the documentation - this is just what dvbtune from sourceforge outputs. > > Johannes > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: [vdr] Re: dxr3/vdr problem
I have a few questions about the dvb drivers/devices that perhaps someone can answer. When receiving from one of the transponders on asiasat2 I have no problems at at all. While running vdr and also running dvbtune -m I see: ... Signal=53116, Verror=0, SNR=43860dB, BlockErrors=0, (S|L|C|V|SY|) Signal=53427, Verror=0, SNR=43815dB, BlockErrors=0, (S|L|C|V|SY|) Signal=52821, Verror=0, SNR=43836dB, BlockErrors=0, (S|L|C|V|SY|) Signal=53090, Verror=0, SNR=43758dB, BlockErrors=0, (S|L|C|V|SY|) On another transponder I see: Signal=41268, Verror=65357, SNR=37605dB, BlockErrors=0, (S|L|C|V|SY|) Signal=41267, Verror=65291, SNR=37608dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40916, Verror=65494, SNR=37554dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40953, Verror=65381, SNR=37479dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40660, Verror=65349, SNR=37548dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40977, Verror=65315, SNR=37539dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40976, Verror=65434, SNR=37560dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40665, Verror=65419, SNR=37575dB, BlockErrors=0, (S|L|C|V|SY|) Signal=40946, Verror=65478, SNR=37641dB, BlockErrors=0, (S|L|C|V|SY|) This second transponder always gives high levels of Verror. For parts of the day the Verror will be around 2 and the service seems to work and my dxr3 won't freeze. At other times it is up around 65000 and things don't work and the dxr3 will eventually freeze (requiring either a vdr restart or sometimes a machine restart) My questions: 1. Whis is this Verror? What is its units? It understand it is related to BER but how? I understand it is a 16bit number so it would seem my values are high. 2. Why the difference between these two services? I thought it may be symbol rate (the first is 20400 while the second is 28125). I have been assuming that my problems are RF related but is this perhaps some kind of problem due to a high load on a low end machine? On Wed, 2003-03-05 at 22:48, Johannes Stezenbach wrote: > On Wed, Mar 05, 2003 at 08:47:26AM +0100, Marcus Metzler wrote: > > Malcolm Caldwell writes: > > > Kai argues that the dvb drivers should not be passing frames with errors > > > through to applications. Given that there is FEC etc in the dvb spec > > > this may be so - I don't know. I also don't know if a budget card is > > > capable of doing this. > > > > All the error correction required and possible for the DVB > > signal is already done by the frontend. Any remaining errors cannot be > > fixed on the transport stream level. > > It would not make sense to check the MPEG stream on the ES level > > inside the driver. It is the task of the MPEG decoder to fix or ignore > > these problems. E.g. the hardware MPEG decoder of the av7110 already does > > these things which are often necessary for MPEG streams received from a > > error prone source. The dxr3 decoder is probably a little more picky > > because it was not developed for decoding a broken stream. > > If a TS packet has errors that cannot be corrected by FEC the > frontends (depending on configuration) force the > transport_error_indicator bit in the TS header to 1. > > VDR could use this information to do "error processing", i.e. try > to fix the PES packet that the TS packet belongs to (provided > the PID field in the TS is still intact or can be guessed), at least > by ensuring consistent "length" fields. > > I don't know if t is practical in software, but hardware specs always talk > about "error concealment" in their feature lists. E.g. the video MPEG decoder > can use data from the previous frame to fill in the gaps. So it would be > better to drop erronous data than to feed crap to the decoder, but > you can't just drop the TS (or even the PES) packet, you would have to > unpack the ES to the slice level and repack it with filled-in data. > > The dxr3 never sees the transport_error_indicator, so it can't do it. > It shouldn't crash, though. > > Regards, > Johannes > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: [vdr] Re: dxr3/vdr problem
(Kai - I home you don't mind - I think this discussion might receive better response on the dvb email list.) This thread started when I wrote that I was having problems trying to run vdr with a budget card using a dxr3 as the output. I don't think I am the only one. The problem is I have a poor quality signal (due to various factors including weather). These errors get through the dvb driver to vdr and on to the the dxr3. The dxr3 device crashes - sometimes requiring a restart of vdr to reopen the device etc, sometimes requiring a reboot. Others have reported having to reload the dxr3 drivers. (although reloading the dxr3 drivers has never worked for me - but thats OT) My system only ever runs a few hours before crashing. Kai argues that the dvb drivers should not be passing frames with errors through to applications. Given that there is FEC etc in the dvb spec this may be so - I don't know. I also don't know if a budget card is capable of doing this. What do people here think? On Mon, 2003-03-03 at 00:38, Kai Moeller wrote: > On Friday 28 February 2003 14:58, Rantanen Teemu wrote: > > > From: Stefan Schluenss [mailto:[EMAIL PROTECTED] > > > > > > Malcom is using DVB-T if i remember correctly and the currently > > > implemented > > > DVB-T systems seems to be more in an experimental state than in > > > production state ;-) > > > > I'd rather say that transport errors are more likely to happen on DVB-T > > then on DVB-C (should 'never' happen) or on DVB-S (can happen on bad > > weather). > > > > > The question is who (driver/vdr/dxr3-plugin) has to take care of corrupt > > > data ?! In Kai's opinion the data has to be checked and rejected inside > > > the > > > driver and such corrcupt data should never reach upper layers (the dxr3- > > > plugin). > > > > Considering that full error checking is somewhat complex operation (correct > > me if I'm wrong), I'd rather see that amount of code and CPU time not in > > kernel, but in user space. > > > > Sorry, but I think you're wrong. The FEC mechanisms are defined in the DVB > standards and hopefully implemented within the hardware/firmware of the DVB > card. The TS packets, VDR receives from the driver, all have a > transport_error_indicator bit which should be set to '1' when there is at > least 1 uncorrectable bit error (see ISO/IEC 13818-1). > > => So actually it should be quite easy to detect defect TS packets. > PES packets (the Dxr3Plugin receives PES) don't have such an error bit (PES is > used for transmissions where bit errors are unlikely). The only errors the > plugin is able to detect are weird entries within the PES header (and we > already added some more checks on request) but these are not the only errors > which may crash your system. > > Regards, > > Kai > > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: dvbtune
On Fri, 2003-02-28 at 16:56, Malcolm Caldwell wrote:
> Hello,
>
> I just checked and this works for me:
> ./dvbtune -p H -s 28125 -i -f 115 -I 1 -m
>
> So your problem is probably the frequency.
>
> The basically code says:
> if (freq > 220) {
> TAKE AWAY THE LOG
That should say TAKE AWAY THE LOF
> } else {
> // this is an L-Band frequency
>
> So L band frequencies need to be there as absolutes.
>
> Also, the lines
> tuning DVB-S to L-Band:1107310752, Pol:H Srate=28125000, 22kHz=off
>
> Are wrong - the is not the real L-Band frequency as the code to
> calculate that is after this printf!
>
> On Fri, 2003-02-28 at 16:16, Sheetal_Pandey wrote:
> > Hi Malcolm
> >
> > I thought first I should get the signal locked and then try vdr.
> >
> > I know you dont use dvbtune but it is a similiar utility to dvbstream.
> > I gave the command ./dvbtune -f 1150 -t 0 -s 28125
> >
> > and get the following output:
> >
> > tuning DVB-S to L-Band:1150, Pol:H Srate=28125000, 22kHz=off
> > SEC BUS MODE: IDLE (0)
> > SEC VOLTAGE: 18 (4)
> > SEC CONT TONE: OFF
> > Getting frontend event
> > Received failure event
> > Getting frontend event
> > Received failure event
> > Getting frontend event
> > Received failure event
> > Not able to lock to the signal on the given frequency
> > Can somebody help in
> > sorting the problem?
> >
> > Malcolm,
> > I will download dvbstream and try with that.Which version are using?
> >
> > Regards,
> > Sheetal Pandey
> >
> >
> > -Original Message-
> > From: Malcolm Caldwell [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, February 27, 2003 8:00 PM
> > To: Sheetal_Pandey
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: [linux-dvb] vdr problem
> >
> >
> > I not sure what your problem is.
> >
> > Perhaps you should try a newer version of vdr. I am using a developer
> > version (1.1.20).
> >
> > vdr questions should be posted to the vdr email list and I have CCed the
> > list and removed the dvb list.
> >
> > Is the channel working with a normal set to box?
> >
> > On Thu, 2003-02-27 at 19:12, Sheetal_Pandey wrote:
> > > Hi,
> > >
> > > I have mapped the keys of PC Keyboard to work with VDR application.I can
> > > enter into the channels menu and change the parameters.I changed the
> > > freq-1150 S/R 28125 POL-H VPID-517 APID-700 and said ok but it doent show
> > > any video.I have changed the channels.conf as follows
> > >
> > > RTPi:1150:h:S100.5E:28125:517:700:0:0:30:0:0:0
> > > DW:1150:h:S100.5E:28125:2305:2306:0:0:1:0:0:0
> > > RAIi:1150:h:S100.5E:28125:513:644:0:0:3:0:0:0
> > >
> > > I also changed the setup.conf to
> > > LnbFrequHi = 0
> > > LnbFrequLo = 0
> > > LnbSLOF = 0
> > >
> > > I am using vdr-1.0.0pre2.
> > >
> > > Regards,
> > > Sheetal Pandey
> > > **
> >
> > > This email (including any attachments) is intended for the sole use of the
> > > intended recipient/s and may contain material that is CONFIDENTIAL AND
> > > PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying
> > or
> > > distribution or forwarding of any or all of the contents in this message
> > is
> > > STRICTLY PROHIBITED. If you are not the intended recipient, please contact
> > > the sender by email and delete all copies; your cooperation in this regard
> > > is appreciated.
> > > **
> > >
> > **
> > This email (including any attachments) is intended for the sole use of the
> > intended recipient/s and may contain material that is CONFIDENTIAL AND
> > PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
> > distribution or forwarding of any or all of the contents in this message is
> > STRICTLY PROHIBITED. If you are not the intended recipient, please contact
> > the sender by email and delete all copies; your cooperation in this regard
> > is appreciated.
> > **
> >
>
>
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
[linux-dvb] Re: dvbtune
Hello,
I just checked and this works for me:
./dvbtune -p H -s 28125 -i -f 115 -I 1 -m
So your problem is probably the frequency.
The basically code says:
if (freq > 220) {
TAKE AWAY THE LOG
} else {
// this is an L-Band frequency
So L band frequencies need to be there as absolutes.
Also, the lines
tuning DVB-S to L-Band:1107310752, Pol:H Srate=28125000, 22kHz=off
Are wrong - the is not the real L-Band frequency as the code to
calculate that is after this printf!
On Fri, 2003-02-28 at 16:16, Sheetal_Pandey wrote:
> Hi Malcolm
>
> I thought first I should get the signal locked and then try vdr.
>
> I know you dont use dvbtune but it is a similiar utility to dvbstream.
> I gave the command ./dvbtune -f 1150 -t 0 -s 28125
>
> and get the following output:
>
> tuning DVB-S to L-Band:1150, Pol:H Srate=28125000, 22kHz=off
> SEC BUS MODE: IDLE (0)
> SEC VOLTAGE: 18 (4)
> SEC CONT TONE: OFF
> Getting frontend event
> Received failure event
> Getting frontend event
> Received failure event
> Getting frontend event
> Received failure event
> Not able to lock to the signal on the given frequency
> Can somebody help in
> sorting the problem?
>
> Malcolm,
> I will download dvbstream and try with that.Which version are using?
>
> Regards,
> Sheetal Pandey
>
>
> -Original Message-
> From: Malcolm Caldwell [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 27, 2003 8:00 PM
> To: Sheetal_Pandey
> Cc: [EMAIL PROTECTED]
> Subject: Re: [linux-dvb] vdr problem
>
>
> I not sure what your problem is.
>
> Perhaps you should try a newer version of vdr. I am using a developer
> version (1.1.20).
>
> vdr questions should be posted to the vdr email list and I have CCed the
> list and removed the dvb list.
>
> Is the channel working with a normal set to box?
>
> On Thu, 2003-02-27 at 19:12, Sheetal_Pandey wrote:
> > Hi,
> >
> > I have mapped the keys of PC Keyboard to work with VDR application.I can
> > enter into the channels menu and change the parameters.I changed the
> > freq-1150 S/R 28125 POL-H VPID-517 APID-700 and said ok but it doent show
> > any video.I have changed the channels.conf as follows
> >
> > RTPi:1150:h:S100.5E:28125:517:700:0:0:30:0:0:0
> > DW:1150:h:S100.5E:28125:2305:2306:0:0:1:0:0:0
> > RAIi:1150:h:S100.5E:28125:513:644:0:0:3:0:0:0
> >
> > I also changed the setup.conf to
> > LnbFrequHi = 0
> > LnbFrequLo = 0
> > LnbSLOF = 0
> >
> > I am using vdr-1.0.0pre2.
> >
> > Regards,
> > Sheetal Pandey
> > **
>
> > This email (including any attachments) is intended for the sole use of the
> > intended recipient/s and may contain material that is CONFIDENTIAL AND
> > PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying
> or
> > distribution or forwarding of any or all of the contents in this message
> is
> > STRICTLY PROHIBITED. If you are not the intended recipient, please contact
> > the sender by email and delete all copies; your cooperation in this regard
> > is appreciated.
> > **
> >
> **
> This email (including any attachments) is intended for the sole use of the
> intended recipient/s and may contain material that is CONFIDENTIAL AND
> PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
> distribution or forwarding of any or all of the contents in this message is
> STRICTLY PROHIBITED. If you are not the intended recipient, please contact
> the sender by email and delete all copies; your cooperation in this regard
> is appreciated.
> **
>
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
[linux-dvb] Re: setting the proper transonder value
On Wed, 2003-02-26 at 22:46, Sheetal_Pandey wrote: > Hi Malcolm, > > I tried the following > dvbstream -o -f 1150 -p H -I 1 -s 28125 517 700. I used dvbtune instead of > dvbstream.It says could not lock to the given frequency.It shows that > freq=1150 S/R=28125 etc. Do I have to change some where else for it to take > these values. I don't know. (I am not even sure I know what you are asking). Perhaps someone more familiar with dvbtools can answer. > > I changed the parameters as above for RTPi in channels.conf and ran ./vdr.I > am not very friendly with the menu on screen so I was not able to enter into > that.Up and down was fine. So is it working? Here is my channels.conf: RTPi:1150:h:S100.5E:28125:517:700:0:0:30:0:0:0 DW:1150:h:S100.5E:28125:2305:2306:0:0:1:0:0:0 RAIi:1150:h:S100.5E:28125:513:644:0:0:3:0:0:0 TVE:1150:h:S100.5E:28125:514:648:0:0:4:0:0:0 TV5 Asie:1150:h:S100.5E:28125:515:625:0:0:5:0:0:0 (RTP is first because that is what I am more interested in!) I have not added the radio yet. For this to work you need the following in your setup.conf LnbFrequHi = 0 LnbFrequLo = 0 LnbSLOF = 0 > > Regards, > Sheetal Pandey > > > -Original Message- > From: Malcolm Caldwell [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 26, 2003 12:18 PM > To: Sheetal_Pandey > Cc: [EMAIL PROTECTED] > Subject: Re: [linux-dvb] setting the proper transonder value > > > On Wed, 2003-02-26 at 14:35, Sheetal_Pandey wrote: > > Hi, > > > > I am using the Hauuppauge WinTV nexus-S card.I have tuned the antenna to > > ASIASAT 2.I am trying to lock the card to European bouque but since I am > > using the card for the first time ,I am not comfortable in giving the > proper > > values. > > > > I have another digital satellite receiver which is locked properly to > > European bouque ,I mean that the signal is proper. > > > > The downlink freq is 4000 MHZ,fec 3/4,Symbol rate 28.125 Mbaud.I am using > a > > C band LNB with local oscillator freq 5150.Can somebody help in filling > the > > proper values. > > I have this working - asiasat2 and European Bouquet. I am fairly sure > the command line for eg. dvbstream is: (for eg for RTP) > dvbstream -o -f 1150 -p H -I 1 -s 28125 517 700 > (I can't confirm this at the moment as vdr is currently running) > > The problem is that the dvb stuff assumes Ku band LNB where you tune to > L = freq - LOF. > > With c-band L = LOF - freq. > > (L is the frequency on the cable from the LNB to the card). > > Luckily most of the tools accept L band frequences directly. So to tune > to the European Bouquet you need to tune to 1150 (ie 5150 - 4000). > > In VDR I have set the LOF to 0 and I put 1150 in the channels.conf. > > I think that VDR could be modified to accept the real frequencies. All > that is needed is to put freq=abs(freq). > > (If freq - LOF = L, then LOF - freq = -L. By putting the abs in we get > the correct frequency) > > I must add that I have not tried this modification yet. (What do other > think? Klus?) > > > > > Regards, > > Sheetal Pandey > > > > > > ** > > > This email (including any attachments) is intended for the sole use of the > > intended recipient/s and may contain material that is CONFIDENTIAL AND > > PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying > or > > distribution or forwarding of any or all of the contents in this message > is > > STRICTLY PROHIBITED. If you are not the intended recipient, please contact > > the sender by email and delete all copies; your cooperation in this regard > > is appreciated. > > ** > > > ** > This email (including any attachments) is intended for the sole use of the > intended recipient/s and may contain material that is CONFIDENTIAL AND > PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or > distribution or forwarding of any or all of the contents in this message is > STRICTLY PROHIBITED. If you are not the intended recipient, please contact > the sender by email and delete all copies; your cooperation in this regard > is appreciated. > ** > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: setting the proper transonder value
On Wed, 2003-02-26 at 14:35, Sheetal_Pandey wrote: > Hi, > > I am using the Hauuppauge WinTV nexus-S card.I have tuned the antenna to > ASIASAT 2.I am trying to lock the card to European bouque but since I am > using the card for the first time ,I am not comfortable in giving the proper > values. > > I have another digital satellite receiver which is locked properly to > European bouque ,I mean that the signal is proper. > > The downlink freq is 4000 MHZ,fec 3/4,Symbol rate 28.125 Mbaud.I am using a > C band LNB with local oscillator freq 5150.Can somebody help in filling the > proper values. I have this working - asiasat2 and European Bouquet. I am fairly sure the command line for eg. dvbstream is: (for eg for RTP) dvbstream -o -f 1150 -p H -I 1 -s 28125 517 700 (I can't confirm this at the moment as vdr is currently running) The problem is that the dvb stuff assumes Ku band LNB where you tune to L = freq - LOF. With c-band L = LOF - freq. (L is the frequency on the cable from the LNB to the card). Luckily most of the tools accept L band frequences directly. So to tune to the European Bouquet you need to tune to 1150 (ie 5150 - 4000). In VDR I have set the LOF to 0 and I put 1150 in the channels.conf. I think that VDR could be modified to accept the real frequencies. All that is needed is to put freq=abs(freq). (If freq - LOF = L, then LOF - freq = -L. By putting the abs in we get the correct frequency) I must add that I have not tried this modification yet. (What do other think? Klus?) > > Regards, > Sheetal Pandey > > > ** > This email (including any attachments) is intended for the sole use of the > intended recipient/s and may contain material that is CONFIDENTIAL AND > PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or > distribution or forwarding of any or all of the contents in this message is > STRICTLY PROHIBITED. If you are not the intended recipient, please contact > the sender by email and delete all copies; your cooperation in this regard > is appreciated. > ** > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: Budget card, c-band and 1.0.0-pre1
On Sat, 2003-02-15 at 03:01, Johannes Stezenbach wrote: > On Sat, Feb 15, 2003 at 01:56:18AM +0930, Malcolm Caldwell wrote: > > As I understand it I must give the utils the L-band frequency. Now the > > LOF for c-band is 5150, and the channel is 4000 giving an L-band > > frequency of 1150Mhz. > > I don't think the LOF can be higher than the transponder's frequency. > Double check your LNB's LOF and the transponder data, and that the > LNB is suitable for the satellite you want to receive. I am fairly sure that this is correct. To get the frequency for c-band you usually subtract the values the other way around. Another way to look at it (perhaps) is that because these are frequencies, a negative frequency is the same thing as the positibe frequency (ie abs(frequency) is what matters). I have thing sort of working now. What I did was to connect the card to the LNB loop on my existing set-top-box. With the polarity set correctly there I am getting my channels! I don't know why it does not work when the set-top-box is turned off etc. Perhaps I have somekind of voltage problem. Things are working although not optimally. VDR is even working. (In vdr I set the lof parameters to 0 and put in the L-band frequency and it just worked.) Anyway it is getting late here so I will go to bed. > > HTH, > Johannes > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Budget card, c-band and 1.0.0-pre1
Hello, I have just received my budget card and am trying to get it to work. I am using 1.0.0-pre1. I am using the dvbtools from sourceforge. I am trying to tune into asiasat. As I understand it I must give the utils the L-band frequency. Now the LOF for c-band is 5150, and the channel is 4000 giving an L-band frequency of 1150Mhz. $ dvbstream -o -f 1150 -p H -s 28125 8192 dvbstream v0.4pre3 - (C) Dave Chapman 2001 Released under the GPL. Latest version available from http://www.linuxstb.org/ Using DVB card "STV0299/TSA5059/SL1935 based" tuning DVB-S to L-Band:-1073744896, Pol:H Srate=28125000, 22kHz=off polling Getting frontend event FE_STATUS: FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC Event: Frequency: 11748146 SymbolRate: 28124000 FEC_inner: 3 Bit error rate: 801 Signal strength: 0 SNR: 34368 FE_STATUS: FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC Output to stdout Streaming 1 stream >From there I see no more output. Does anyone have any advice? -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: [RFC] USB DVB design
I have a question about the frontend: Will it work internationally? In particular will it work here in Australia with VHF as well as UHF and with our non-standard* channel spacings? (*Actually they are standard - standard for us!) On Mon, 2002-12-02 at 23:02, Jean-Claude Repetto wrote: > - Original Message - > From: "Holger Waechtler" <[EMAIL PROTECTED]> > To: "Sven Karlsson" <[EMAIL PROTECTED]> > Cc: "Linux-dvb" <[EMAIL PROTECTED]> > Sent: Friday, November 29, 2002 1:54 PM > Subject: [linux-dvb] Re: [RFC] USB DVB design > > > > Sven Karlsson wrote: > > > And by the way, what front-ends are you going to use? > > > > The Microtune 7072DTF, just for the reason that we can get them easier > > than other ones. > > I looked for the specifications and/or data sheet of this tuner on their web > site (http://www.microtune.com/), but I couldn't find it. > Is the data sheet available on another site ? > > BTW, what do you think about adding an IR receiver on the board ? A timer of > the FX2 could be used to measure the lengths of pulses and spaces, which > would then be transmitted to the PC. > > Jean-Claude > > > > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] WIN DVB-S Xact
Hello, Are the current drivers compatible with the WIN DVB-S Xact sold by http://www.usa-x.org? This card would appear to be similar to a budget card in functionality. I don't know if it is SAA7146 based. They claim it has a LG tuner which I assume is not supported. Is anyone working on this? They claim linux compatibility - does anyone know the details? Should I ask them? -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: New UK DVB-T channels testing
On Wed, 2002-10-09 at 20:36, Klaus Schmidinger wrote: > Lauri Pesonen wrote: > > > > On Wed, Oct 09, 2002 at 11:51:18AM +0200, Holger Waechtler wrote: > > > Klaus Schmidinger wrote: > > > > > > > The NIT reports frequencies like 28300Hz when I'm using 28275Hz > > > > with VDR. So The NIT reports the 'official' freqs without the offset. > > > > Offsets are -250kHz for QAM_128 freqs and -125kHz for QAM_64 freqs. > > > > > > > >Therefore it should be sufficient to store the "center frequency" and > > > >allow for > > > >an offset handling, which in case of DVB-T could be done by an 'O' > > > >parameter > > > >(note that it's the character between 'N' and 'P', not the number 'zero'), > > > >and in case of DVB-C a table of offsets for the various QAM modes should > > > >do the trick. > > > > > > Are you sure that these offsets are related to the used modulation? What > > > makes you sure of that? > > > > > > Holger > > > > I emailed about theo ffset in DVB-C in Finland (the text segment Klaus > > quoted above). > > > > Some guy in Finland (sorry, I can't remember your name) came up with the > > offsets after trial and error. There is no guarantee that they are correct > > or that the offset is related to the modulation. Actually the only QAM_64 > > bouquet in my providers network is on 162MHz and all QAM_128 bouquets > > (that I'm whatching) are above that, e.g. in the range of 283MHz. So the > > offset might also be related to the freq rather than the modulation (which > > would make more sense to me). > > > > All I can say for sure is that I have offset the QAM_64 bouquet by -125kHz > > and all the QAM_128 bouquets by -250kHz and all channels work perfectly. > > Before I applied the offset 80% of my channels switches across bouquets > > failed. > > Well, after all these postings I guess the bottom line is that it will be best > to store both DVB-T _and_ DVB-C frequencies generally in kHz (I believe > going all the way down to Hz would be really unnecessary, because the user would > then have to enter a NINE digit number when defining a channel in VDR's OSD - pretty > sure six of which would be zeroes). I don't want to interfere here as I probably don't understand the problem but: Why not STORE the values as Hz, but allow input via OSD to be in whatever is most sensible? Also - why not let user suffix their values with Mhz, Khz, Ghz or hz? On the OSD you could use up/down to select the units (but default to the most likely units for the source type). This would seem (to me) to be the most flexible. > VDR would then in no way bother with any offsets, these would have to be added to > the frequency in whatever way the person or program that generates the data sees fit. > The only question left is whether the data broadcast in the data stream really >defines > the frequency *precisely*. > > Klaus > -- > ___ > > Klaus Schmidinger Phone: +49-8635-6989-10 > CadSoft Computer GmbH Fax: +49-8635-6989-40 > Hofmark 2 Email: [EMAIL PROTECTED] > D-84568 Pleiskirchen, Germany URL: www.cadsoft.de > ___ > > > -- > Info: > To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as >subject. > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Where to buy DVB-T
Can someone point me to somewhere I can buy a DVB-T card? Preferably somewhere on the net that will ship internationally. (I am in Australia) -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: DVB-T in Australia
On Tue, 2002-04-23 at 16:00, Dave Chapman wrote: > On Tuesday 23 April 2002 05:59, you wrote: > > As far as I know no one has got DVB-T to work in Australia. I know this > > has been talked about before but there has been no definite answer. > > > > There are people here reporting on the aus.tv.digital newsgroup that the > > DVB-T cards that are available do not work here. > > Have they been using the supplied Windows software, or the Linux software? > The Windows software probably doesn't allow you to fine-tune the tuning > parameters. Windows as far as I recall. > > There seems to be a few potential/actual problems: > > 1. In most places in Australia DVB-T is being brodcast on VHF channels > > 2. It would seem that as Australia uses 7Mhz channels (PAL-B) in the UHF > band > >where as most countries use 8Mhz channels in UHF (PAL-G) > > 3 Others I perhaps don't know about. > > > > Now, luckily, I live in a city where all the digital broadcasts are on > > UHF channels, so problem 1 goes away! > > > > So how about 2? > > The L64781 COFDM demodulator used in the Nova-t cards supports 6, 7 and 8 MHz > channels. From looking at the specifications, it seems to support all > conceivable forms of DVB-T broadcasts, so that shouldn't be a problem. The > Linux driver allows applications to set all these paramaters. > > > If I understand correctly the nova and the tecnotrends DVB-T cars are > > essentially the same? > > > > I would guess that the specifications for the tuner chips used on these > > cards would answer these questions. If so can someone (convergence?) > > have a look? Or at least point me at the specs for the cards? > > I don't know about the actual tuner, but the "COFDM Demodulator" in both > cards is the L64781 which was co-developed by LSI Logic and BBC Research and > Development. A search at www.lsilogic.com will give you information on this > chip, but I couldn't find the actual datasheet (but I downloaded it from > there last year). Yes - I found via google but had to resort to the google cache. > Regards, > > Dave > > > -- > Info: > To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as >subject. > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] DVB-T in Australia
As far as I know no one has got DVB-T to work in Australia. I know this has been talked about before but there has been no definite answer. There are people here reporting on the aus.tv.digital newsgroup that the DVB-T cards that are available do not work here. There seems to be a few potential/actual problems: 1. In most places in Australia DVB-T is being brodcast on VHF channels 2. It would seem that as Australia uses 7Mhz channels (PAL-B) in the UHF band where as most countries use 8Mhz channels in UHF (PAL-G) 3 Others I perhaps don't know about. Now, luckily, I live in a city where all the digital broadcasts are on UHF channels, so problem 1 goes away! So how about 2? If I understand correctly the nova and the tecnotrends DVB-T cars are essentially the same? I would guess that the specifications for the tuner chips used on these cards would answer these questions. If so can someone (convergence?) have a look? Or at least point me at the specs for the cards? -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
