aboutsummaryrefslogtreecommitdiffstats
path: root/util/szap/README
blob: a9903575830bc610cd2145f010da39e6ac7f47ee (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
Hi,

this are some trivial zapping applications explaining how to use the frontend
and demux API. They are also pretty useful to test your hardware.

For DVB-S, Astra Channel config file:

$ ./szap -c channels-conf/dvb-s/Astra-19.2E n24

will tune to N24. For DVB-C, Berlin Cable channel config:

$ ./czap -c channels-conf/dvb-c/de-Berlin Arte

For DVB-T, Berlin Config:

$ ./tzap -c channels-conf/dvb-t/de-Berlin phoenix

For ATSC, Raleigh Durham Config:

$ ./azap -c channels-conf/atsc/us-Raleigh-Durham WRAL

will tune to WRAL's Digital Channel 5-1.

By default the MPEG stream is routed to a hardware decoder. If you want to
record the stream to disk you will route it to the DVR device by using the
'-r' option:

$ ./tzap -c channels-conf/dvb-t/de-Berlin phoenix -r
[keep it running in one console]
$ cat /dev/dvb/adapter0/dvr0 > /tmp/recording.ts
[in a second console, will dump the MPEG transport stream to /tmp/recording.ts]

The status messages have the following meaning:

status 0x1f              --- The demodulator status bits.
			      0x1f means all bits set, everything ok.

signal [0x0000...0xffff] --- Signal Strength. Values above 0x8000 should be ok.

snr [0x0000...0xffff]    --- Signal/Noise Ratio. Values above 0x8000 are ok.

ber [0...0xffffffff]     --- Bit Error Rate. The less the better.

unc [0...0xffffffff]     --- Number of Uncorrectable Blocks.
			     Small numbers are Preferable.

If everything is alright and all frontend circuits are working stable
(are locked) you should see a FE_HAS_LOCK in the rightmost line.

Good luck,

Holger