[linux-dvb] Trouble with tuning on Lifeview FlyDVB-T

[linux-dvb] Trouble with tuning on Lifeview FlyDVB-T

[Lee Jones]

Hello all :) !

I'm really writing this because it's a case of last resort, in an
effort to try to fix a long-standing problem. Namely, the tuning
problem I seem to have with a DVB T PCI card I have in my PC. It's a
lifeview flydvb-t. In fact, it's this one as listed on linuxtv's
website;

http://www.linuxtv.org/wiki/index.php/DVB-T_PCI_Cards#LifeView
http://www.linuxtv.org/wiki/index.php/Image:LR301.jpg

The computer the card is in is a 64-bit system, running slamd64 which
is a slackware port to 64 bit systems. The version is 12.1, running
kernel version 2.6.24.5 .

http://www.slamd64.com/

The firmware for this card is in /lib/firmware, I don't see any errors
in dmesg about missing firmware files for the card.

The problem I am having is regarding tuning. Namely, the card seems to
miss channels while tuning. The ariel input is working ok as another
DVB-T unit (an Artec T1, USB) finds all channels with no problems, as
does a plain old fashioned digital freeview box.

I live in the UK ,and I'm using the rowridge transmitter. I've
successfully downloaded and compiled the dvbapps from linuxtv  (
dvb-apps-60131cfbbb2e )

----
The problems seem to occur with scanning, however. While tuning, I get
several lines which look like this:
>>> tune to: 562166670:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to: 562166670:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed)
----

After completion, some channels are missing (e.g. BBC1 is there, but
ITV or BBC4 aren't; they are there on a normal freeview box for
example) . After a lot of googling, I eventually found a program
called w_scan ( http://www.edafe.org/vdr/wscan.html ) . Its
documentation mentioned using the -x option in w_scan to create an
initial tuning data file, which I tried. I then tried using the
dvbutils' scan command on that initial tuning data file which w_scan
produced.

This still produced some "WARNING:>>>tuning failed!!!" messages but
appears to have found the 'missing 'channels. But then using the
dvbutils' program tzap seemed to tell a different story. Some channels
existed but yet didn't produce *any* data (I could confirm that they
are working and are on-air, again a normal digital freeview box
works).

For example:
$ tzap -r "BBC ONE"
Produces:
tuning to 489833330 Hz
video pid 0x0258, audio pid 0x0259
status 01 | signal 9f9f | snr 0000 | ber 0000bef8 | unc ffffffff |
status 1f | signal 9f9f | snr f3f3 | ber 0000057a | unc ffffffff | FE_HAS_LOCK
status 1f | signal 9f9f | snr fefe | ber 0000002c | unc 00000011 | FE_HAS_LOCK
status 1f | signal 9f9f | snr fefe | ber 00000022 | unc 00000000 | FE_HAS_LOCK

(in another window, at the same time)
$ cat /dev/dvb/adapter/dvr0
Produces lots of different characters, so I can see data coming in.
Saying cat /dev/dvb/adapter/dvr0 > test.mpg produces a watchable mpeg
file.

but

If I try this:
$ tzap -r "BBC FOUR"
Produces:
tuning to 562000000 Hz
video pid 0x0000, audio pid 0x0000
status 00 | signal 0000 | snr ffff | ber 0001fffe | unc 00000000 |
status 1f | signal 9d9d | snr 0000 | ber 00012966 | unc ffffffff | FE_HAS_LOCK
status 1f | signal 9c9c | snr 9f9f | ber 00000794 | unc ffffffff | FE_HAS_LOCK
status 1f | signal 9c9c | snr fefe | ber 00000038 | unc ffffffff | FE_HAS_LOCK
status 1f | signal 9c9c | snr fefe | ber 00000022 | unc 00000000 | FE_HAS_LOCK

(in another window at the same time)

$ cat /dev/dvb/adapter0/dvr0

Produces this ---------------------->

Nothing!

Not a single byte of data, yet apparently the signal has lock;
"FE_HAS_LOCK". Saying cat /dev/dvb/adapter/dvr0 > test.mpg produces a
file of 0 bytes.

I can go straight back to tzap -r "BBC ONE" and data once again is generated.

I can't find any answer for this at all anywhere!

Can anyone help?

Thanks

ljones

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Trouble with tuning on Lifeview FlyDVB-T

[BOUWSMA Barry]

On Tue, 30 Sep 2008, Lee Jones wrote:

> The problems seem to occur with scanning, however. While tuning, I get
> several lines which look like this:
> >>> tune to: 562166670:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
> WARNING: >>> tuning failed!!!
> >>> tune to: 562166670:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed)

Two things:  If you scan with `-v', you should get some
feedback as to how close your receiver is to locking on
the frequency.

Second, it may or may not be a problem, as one of my cards
managed to tune and lock a carrier even when fed totally
wrong tuning data apart from the correct frequency, but
are you sure that FEC_3_4 is correct also for the LP code
rate?  The tuning data I see in recent dvb-apps gives `NONE'
 -- this probably won't affect anything, but in the unlikely 
chance it might...


> After completion, some channels are missing (e.g. BBC1 is there, but
> ITV or BBC4 aren't;

The above frequency is for BBC4; ITV uses 64-QAM unlike the
BBC multiplexes, so I'll assume that is correct in your
initial tuning data (as the above CRLP value doesn't match
that based on the OFCOM data in dvb-apps)...


> This still produced some "WARNING:>>>tuning failed!!!" messages but
> appears to have found the 'missing 'channels. But then using the
> dvbutils' program tzap seemed to tell a different story. Some channels
> existed but yet didn't produce *any* data (I could confirm that they

Can you give the lines with the PIDs of these `missing' channels
which you have found?  Like BBC4 with which you had problems
below...


> $ tzap -r "BBC FOUR"
> tuning to 562000000 Hz
> video pid 0x0000, audio pid 0x0000
              ^^^^              ^^^^
This is wrong -- at least after 19h your-time -- but in case
you did the scan before 19h your-time, you may have gotten
correct PIDs for CBBC+CBeebies -- but not for BBC3+4, as the
correct PIDs are only broadcast during the time those programs
are actually on-air, and `tzap' is not smart enough to take
the Service ID and derive the up-to-date PIDs from that...

So, basically, if you could post what you have for Mux B at
562MHz (ch32), then we can see if you did get correct data
for the radios and the then-active TV services.

Also you said the ITV Mux 2 caused problems in your initial
scan, so if you have problems `tzap'ing those channels, then
posting that data would be useful.


thanks
barry bouwsma

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Trouble with tuning on Lifeview FlyDVB-T

[Darren Salt]

I demand that BOUWSMA Barry may or may not have written...

> On Tue, 30 Sep 2008, Lee Jones wrote:
[snip]
>> $ tzap -r "BBC FOUR"
>> tuning to 562000000 Hz
>> video pid 0x0000, audio pid 0x0000
>              ^^^^              ^^^^
> This is wrong -- at least after 19h your-time -- but in case you did the
> scan before 19h your-time, you may have gotten correct PIDs for
> CBBC+CBeebies -- but not for BBC3+4, as the correct PIDs are only broadcast
> during the time those programs are actually on-air, and `tzap' is not smart
> enough to take the Service ID and derive the up-to-date PIDs from that...

OTOH, each pair (BBC3 and CBBC, BBC4 and CBeebies) use the same PIDs, so a
little careful copying will fix things.

[snip]
-- 
| Darren Salt    | linux or ds at              | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Buy local produce. Try to walk or cycle. TRANSPORT CAUSES GLOBAL WARMING.

The Green Midget Cafe, Bromley. Home to Spam and occasional Viking hordes.

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Trouble with tuning on Lifeview FlyDVB-T

[hermann pitton]

Am Dienstag, den 30.09.2008, 23:57 +0100 schrieb Darren Salt:
> I demand that BOUWSMA Barry may or may not have written...
> 
> > On Tue, 30 Sep 2008, Lee Jones wrote:
> [snip]
> >> $ tzap -r "BBC FOUR"
> >> tuning to 562000000 Hz
> >> video pid 0x0000, audio pid 0x0000
> >              ^^^^              ^^^^
> > This is wrong -- at least after 19h your-time -- but in case you did the
> > scan before 19h your-time, you may have gotten correct PIDs for
> > CBBC+CBeebies -- but not for BBC3+4, as the correct PIDs are only broadcast
> > during the time those programs are actually on-air, and `tzap' is not smart
> > enough to take the Service ID and derive the up-to-date PIDs from that...
> 
> OTOH, each pair (BBC3 and CBBC, BBC4 and CBeebies) use the same PIDs, so a
> little careful copying will fix things.
> 
> [snip]

If also FEC has changed, we often saw that already, it must be corrected
or all except frequency and bandwidth should be set to AUTO in the
initial scanfile for the tda10046.

Also above we see a tuning attempt to 562000000 Hz and previously we saw
already a positive offset added 562166670:INVERSION_AUTO:BANDWIDTH_8_MHZ

IIRC, in the UK, the queen might save you from trolls, spam and vikings,
usually a negative offset like this is reported more regularly?

Cheers,
Hermann



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Trouble with tuning on Lifeview FlyDVB-T

[BOUWSMA Barry]

On Wed, 1 Oct 2008, hermann pitton wrote:

> Also above we see a tuning attempt to 562000000 Hz and previously we saw
> already a positive offset added 562166670:INVERSION_AUTO:BANDWIDTH_8_MHZ

> usually a negative offset like this is reported more regularly?

The original poster was able to quickly obtain lock in both
cases -- plus I would imagine that a tuner able to receive
signals 4MHz either side of the centre frequency can handle
a couple hundred kHz offset automagically -- certainly my
sat set-top-boxen handle typically a ten MHz range with most
full transponders...

In any case, the hg repository copy I have of uk-Rowridge
matches what I find with a quick giggle search:
   Rowridge DVB-T Info
   0 (zero)
   - (minus) 167000 Hz
   + (plus) 167000 Hz
   Mux 1 BBC    channel 23 freq 490000000 - offset = 489833000
   Mux 5 C      channel 26 freq 514000000 - offset = 513833000
   Mux 2 ITV/C4 channel 28 freq 530000000 0 offset = 530000000
   Mux 3 A      channel 30 freq 546000000 - offset = 545833000
   Mux 4 B      channel 32 freq 562000000 + offset = 562167000
   Mux 6 D      channel 33 freq 570000000 + offset = 570167000


However, as the original poster's frequency data shows
two additional significant figures not present in
either of these (in addition to the LP code rate that
differs), it obviously isn't the same source as the hg
repository -- whether obtained by parsing NIT data or
based on user-specified input frequencies or whatever...

Not that either one is guaranteed 100% reliable, though


(hope I make sense, when I should be sleeping)
barry bouwsma

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Trouble with tuning on Lifeview FlyDVB-T

[hermann pitton]

Am Mittwoch, den 01.10.2008, 03:40 +0200 schrieb BOUWSMA Barry:
> On Wed, 1 Oct 2008, hermann pitton wrote:
> 
> > Also above we see a tuning attempt to 562000000 Hz and previously we saw
> > already a positive offset added 562166670:INVERSION_AUTO:BANDWIDTH_8_MHZ
> 
> > usually a negative offset like this is reported more regularly?
> 
> The original poster was able to quickly obtain lock in both
> cases -- plus I would imagine that a tuner able to receive
> signals 4MHz either side of the centre frequency can handle
> a couple hundred kHz offset automagically -- certainly my
> sat set-top-boxen handle typically a ten MHz range with most
> full transponders...

Barry, the tda10046 can not.

Frequency and bandwidth must be correct.

already sleeping ..., but the rest can be AUTO.

Cheers,
Hermann

> In any case, the hg repository copy I have of uk-Rowridge
> matches what I find with a quick giggle search:
>    Rowridge DVB-T Info
>    0 (zero)
>    - (minus) 167000 Hz
>    + (plus) 167000 Hz
>    Mux 1 BBC    channel 23 freq 490000000 - offset = 489833000
>    Mux 5 C      channel 26 freq 514000000 - offset = 513833000
>    Mux 2 ITV/C4 channel 28 freq 530000000 0 offset = 530000000
>    Mux 3 A      channel 30 freq 546000000 - offset = 545833000
>    Mux 4 B      channel 32 freq 562000000 + offset = 562167000
>    Mux 6 D      channel 33 freq 570000000 + offset = 570167000
> 
> 
> However, as the original poster's frequency data shows
> two additional significant figures not present in
> either of these (in addition to the LP code rate that
> differs), it obviously isn't the same source as the hg
> repository -- whether obtained by parsing NIT data or
> based on user-specified input frequencies or whatever...
> 
> Not that either one is guaranteed 100% reliable, though
> 
> 
> (hope I make sense, when I should be sleeping)
> barry bouwsma
> 
> _______________________________________________
> 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

Re: [linux-dvb] Trouble with tuning on Lifeview FlyDVB-T

[Darren Salt]

Will people NOT CC mail to me? Mail-Followup-To is set for a reason...

-- 
| Darren Salt    | linux or ds at              | nr. Ashington, | Toon
| RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army
| + Buy less and make it last longer.         INDUSTRY CAUSES GLOBAL WARMING.

"Bother", said Pooh, as he received his telephone bill.

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Trouble with tuning on Lifeview FlyDVB-T

[hermann pitton]

Hi Darren,

Am Mittwoch, den 01.10.2008, 17:49 +0100 schrieb Darren Salt:
> Will people NOT CC mail to me? Mail-Followup-To is set for a reason...

from my side there was not any intention in that direction.
Barry must have lost it previously and I did just hit the reply to all
button.

Also interesting, unfortunately in German.
http://www.spiegel.de/politik/ausland/0,1518,581790,00.html

Cheers,
Hermann



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Trouble with tuning on Lifeview FlyDVB-T

[hermann pitton]

Am Donnerstag, den 02.10.2008, 07:22 +0200 schrieb hermann pitton:
> Hi Darren,
> 
> Am Mittwoch, den 01.10.2008, 17:49 +0100 schrieb Darren Salt:
> > Will people NOT CC mail to me? Mail-Followup-To is set for a reason...
> 
> from my side there was not any intention in that direction.
> Barry must have lost it previously and I did just hit the reply to all
> button.
> 
> Also interesting, unfortunately in German.
> http://www.spiegel.de/politik/ausland/0,1518,581790,00.html

to stay OT a little more.

I'm following what happens in the prior colonies with interest.

They have driven it against that well known wall for the second time
now.

And what publicly comes over is: the problem is drilling licenses ...

...

Cheers,
Hermann







_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Trouble with tuning on Lifeview FlyDVB-T

[Lee Jones]

Ok apologies if this appears as another thread. I'm looking through
all the responses. FIrst of alll what does "PID" stand for?

btw, first of all here's the tuning details that w_scan originally found;

# file automatically generated by w_scan
# (http://wirbel.htpc-forum.de/w_scan/index2.html)
# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
T 530000000 8MHz AUTO AUTO AUTO AUTO AUTO NONE
T 562000000 8MHz AUTO AUTO AUTO AUTO AUTO NONE
T 570000000 8MHz AUTO AUTO AUTO AUTO AUTO NONE

And a few lines from channels.conf,  generated by scan;

ITV1:530000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE:520:521:8270

BBC FOUR:562000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE:0:0:16832

And I'm guessing this is Mux B (C34); not sure though!

PAT
PMT 0x02c7 for service 0x4c40
PMT 0x02c8 for service 0x4c80
PMT 0x02c9 for service 0x4e00
PMT 0x02be for service 0x41c0
PMT 0x02bf for service 0x4240
PMT 0x02c0 for service 0x4600
PMT 0x02c4 for service 0x4700
PMT 0x02bd for service 0x4180
PMT 0x02cf for service 0x4780
PMT 0x02cb for service 0x4840
PMT 0x02c1 for service 0x4640
PMT 0x02cc for service 0x4880
PMT 0x02cd for service 0x48c0
PMT 0x02c6 for service 0x4c00
PMT 0x02ca for service 0x4280
PMT 0x02c2 for service 0x4680
PMT 0x02c3 for service 0x46c0
PMT 0x02c5 for service 0x4740
PMT 0x02ce for service 0x4900
SDT (actual TS)
0x0000 0x4280: pmt_pid 0x02ca BBC -- BBC Parliament (running)
0x0000 0x41c0: pmt_pid 0x02be BBC -- BBC FOUR (running)
0x0000 0x4240: pmt_pid 0x02bf BBC -- CBeebies (running)
0x0000 0x4600: pmt_pid 0x02c0 BBC -- BBC R5 Live (running)
0x0000 0x4640: pmt_pid 0x02c1 BBC -- BBC 5L SportsX (running)
0x0000 0x4680: pmt_pid 0x02c2 BBC -- BBC 6 Music (running)
0x0000 0x46c0: pmt_pid 0x02c3 BBC -- BBC 7 (running)
0x0000 0x4700: pmt_pid 0x02c4 BBC -- 1Xtra BBC (running)
0x0000 0x4740: pmt_pid 0x02c5 BBC -- BBC Asian Net. (running)
0x0000 0x4c00: pmt_pid 0x02c6 BBC -- 301 (running)
0x0000 0x4c40: pmt_pid 0x02c7 BBC -- 302 (running)
0x0000 0x4c80: pmt_pid 0x02c8 BBC -- 303 (running)
0x0000 0x4180: pmt_pid 0x02bd BBC -- 305 (running)
0x0000 0x4e00: pmt_pid 0x02c9 BBC -- Community (running)
0x0000 0x4840: pmt_pid 0x02cb BBC -- BBC Radio 1 (running)
0x0000 0x4880: pmt_pid 0x02cc BBC -- BBC Radio 2 (running)
0x0000 0x48c0: pmt_pid 0x02cd BBC -- BBC Radio 3 (running)
0x0000 0x4900: pmt_pid 0x02ce BBC -- BBC Radio 4 (running)
0x0000 0x4780: pmt_pid 0x02cf BBC -- BBC World Sv. (running)

----


And also for ITV;

PAT
PMT 0x0102 for service 0x2085
PMT 0x0116 for service 0x20a1
PMT 0x012c for service 0x20c0
PMT 0x0114 for service 0x2240
PMT 0x0104 for service 0x2066
PMT 0x0112 for service 0x21ba
PMT 0x0100 for service 0x204e
PMT 0x011c for service 0x2244
PMT 0x011a for service 0x2243
PMT 0x0110 for service 0x2178
PMT 0x010e for service 0x20fa
PMT 0x0130 for service 0x2100
PMT 0x0131 for service 0x2104
SDT (actual TS)
0x0000 0x204e: pmt_pid 0x0100 ITV -- ITV1 (running)
0x0000 0x20c0: pmt_pid 0x012c Channel 4 TV -- Channel 4 (running)
0x0000 0x2100: pmt_pid 0x0130 Channel 4 TV -- E4 (running)
0x0000 0x2178: pmt_pid 0x0110 Teletext Limited -- Teletext (running)
0x0000 0x2240: pmt_pid 0x0114 Channel 4 TV -- Teletext on 4 (running)
0x0000 0x21ba: pmt_pid 0x0112 Teletext Limited -- Rabbit (running)
0x0000 0x20a1: pmt_pid 0x0116 ITV -- ITV4 (running)
0x0000 0x20fa: pmt_pid 0x010e Channel 4 TV -- More 4 (running)
0x0000 0x2104: pmt_pid 0x0131 Channel 4 TV -- Channel 4+1 (running)
0x0000 0x2085: pmt_pid 0x0102 ITV -- ITV2 (running)
0x0000 0x2066: pmt_pid 0x0104 ITV -- ITV3 (running)
0x0000 0x2244: pmt_pid 0x011c Global Radio -- Heart (running)

I hope that is the correct infos!

Thanks :)

ljones

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Trouble with tuning on Lifeview FlyDVB-T

[BOUWSMA Barry]

On Wed, 1 Oct 2008, Lee Jones wrote:

> all the responses. FIrst of alll what does "PID" stand for?

As I have used it, it is the numbers used to identify the
video and audio streams that can be found highlighted
below.

As for what it means, rather than post bogus information
from the top of my head, you can probably learn more
details than you want, by searching for MPEG Transport
Stream Audio Video PID or something similar.


> btw, first of all here's the tuning details that w_scan originally found;

Thanks.  Now I owe it to everyone to figure out exactly
what w_scan is and how it differs from my hacked `scan'...


> # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
> T 530000000 8MHz AUTO AUTO AUTO AUTO AUTO NONE
> T 562000000 8MHz AUTO AUTO AUTO AUTO AUTO NONE
> T 570000000 8MHz AUTO AUTO AUTO AUTO AUTO NONE

Hmmm, that's it?  You seem to be missing a few of the
frequencies, like half of them, posted in my earlier
reply, sent from this transmitter...

What is interesting to me is that the missing freqs
all have a negative offset (490, 546, & 514MHz nominal)
so perhaps this scan can handle no-offset 530 and the
+1/6MHz offsets of 562 and 570MHz.


You posted earlier some `tzap' signal-strength and bit-
error-rate values.  You also said your other DVB-T card
received all stations without problems.  Do you see similar
error rates, or even better, from this other card?

I can't say anything about the signal strength, as there
is no fixed reference against which all linux drivers are
calibrated, but `9e' is near the middle of the range
between `00' and `ff'.

It's possible there's a sensitivity problem that needs to
be tweaked by the driver (a LNA or something).

(Let me connect a simple short antenna and see how one of
my tuner cards works against two line-of-sight transmitters
within my Faraday-cage-type room.  Hmmm.  Oh yes.  Oh, yes!)

At least for me, `ff' means no useful signal, `9x' has a
few errors, and I do well at `7x'.  My BER rate is zero,
except when I have a horribly weak signal.  Ooh, that one
blasts in compared with the others.  So why did my recent
recording of that frequency with an amplified yagi get all
messed up?  Hmmm...

You didn't say anything about your distance from the
transmitter, the terrain, and so on -- given that the services
I receive all post-DSO and are full-strength, while you are
receiving a lower-power signal until your DSO, I'd like to
see the `tzap' output from each of the six frequencies with
your other card, if possible.

By me, I can get `ffff' for SNR and uncorrected BER of 0
with a simple stub of an antenna, and I would hope you would
see the same.


> And a few lines from channels.conf,  generated by scan;
> ITV1:530000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO
 [snip]:GUARD_INTERVAL_AUTO:HIERARCHY_NONE:520:521:8270
                                           ^^^ ^^^
I've highlighted the video and audio PIDs respectively above
(fixed-width font of course).
  

> BBC FOUR:562000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:
 GUARD_INTERVAL_AUTO:HIERARCHY_NONE:0:0:16832
                                    ^ ^
As this scan was done sometime in the day (before 19h your-
time), you don't get the BBC Four PIDs -- as was noted by
another poster, these are shared with CBeebies, for which
you will (should!) have obtained correct values.


> And I'm guessing this is Mux B (C34); not sure though!

> 0x0000 0x41c0: pmt_pid 0x02be BBC -- BBC FOUR (running)
> 0x0000 0x4240: pmt_pid 0x02bf BBC -- CBeebies (running)

No problems tuning.  Interesting, though -- by satellite,
the status of BBC3/4 CBBC/CBeebies is such that by day,
the first two are tagged as `(not running)', and by night,
the latter two...

In any case, you should be able to ``tune'' into BBC4 by
instead tuning to CBeebies after 19h.  Or you can permanently
fix this by copying the PID values from CBeebies by day to
the 0-values of BBC4 -- repeat for CBBC and BBC3.  Doing so
will give you the correct Service ID (following the video+
audio PIDs).


> I hope that is the correct infos!

Close enough  ;-)

First question:  if you download the latest tuning file from
../HG-src/dvb-apps/util/scan/dvb-t/uk-Rowridge
are you able to receive all six frequencies with both cards?

Second:  How do the `tzap' values for both cards for all
frequencies compare, with the same aerial input -- in particular,
the signal strength, BER, and SNR values?


barry bouwsma

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb