Project

General

Profile

Tvheadend dvb config revamp » History » Version 8

Andreas Smas, 2010-07-04 21:24

1 1 Andreas Smas
There are a few problems with how the TV adapter tab is implemented today
2
3 2 Andreas Smas
 * It cannot handle a large amount of services. With DVB-S you can easily hit >1k services. Ticket #100
4
 * It's hard (but possible via sorting) to see which services that is transmitted on which mux.
5
 * The DVB satconf solution is a bit cumbersome
6
 * Updates to the quality meter indicator refreshed the grid in a way that is bad UX. Ticket #108
7 1 Andreas Smas
8 4 Andreas Smas
Therefore the plan is to totally redesign how Tvheadend interacts with hardware.
9
This rewrite will not be configuration compatible and will therefore bump Tvheadend version to 3.x
10 1 Andreas Smas
11 4 Andreas Smas
= Device tree =
12 1 Andreas Smas
13 3 Andreas Smas
This tree will present the available devices to the user
14 2 Andreas Smas
15 1 Andreas Smas
{{{
16 3 Andreas Smas
  + DVB Adapter #1
17
  | + DVB-C Frontend
18
  |
19
  + DVB Adapter #2
20
  | + DVB-T Frontend
21
  | + DVB-C Frontend
22
  |
23
  + DVB Adapter #3
24
  | + DVB-S Frontend
25
  | | + Switchport 1
26
  | | + Switchport 2
27
  | | + Switchport 3
28
  | | + Switchport 4
29
  | | + Switchport n
30
  | + DVB-T Frontend
31
  |
32
  + V4L Adapter #1
33
    + Tuner
34
    + Composite
35
    + S-Video
36 1 Andreas Smas
}}}
37
38 3 Andreas Smas
Pressing on a node will present the user with information about the entry and a few configuration options as follows:
39 1 Andreas Smas
40 3 Andreas Smas
=== DVB / ATSC Adapter ===
41
==== Info ====
42
Various information about the hardware
43
==== Config ====
44
 * Enable/Disable adapter
45 1 Andreas Smas
46
47 3 Andreas Smas
=== DVB-C / DVB-T / ATSC Frontends ===
48
==== Info ====
49
TBD
50
==== Config ====
51
 * Network the frontend is attached to
52
 * If this device may update network configuration
53 1 Andreas Smas
54 3 Andreas Smas
55
=== DVB-S Frontends ===
56
==== Info ====
57
TBD
58
==== Config ====
59
 * Number of Diseqc switchports
60
 or 
61
 * Network the frontend is attached to
62 7 Andreas Smas
 * If this device may update network configuration
63 3 Andreas Smas
 * LnB configuration
64
65
=== Switchport ===
66
==== Info ====
67
TBD
68
==== Config ====
69
 * Network the switchport is attached to
70 7 Andreas Smas
 * If this device may update network configuration
71 3 Andreas Smas
 * LnB configuration
72
 
73
74
=== V4L adpater ===
75
==== Info ====
76
Various information about the hardware
77
==== Config ====
78
 * Enable/Disable adapter
79
 
80
81
=== V4L frontends ===
82
==== Info ====
83
Various information about the hardware
84
==== Config ====
85 1 Andreas Smas
 * TV system type (PAL, NTSC, etc) (for tuners)
86
 * Network the frontend is attached to
87 4 Andreas Smas
88
89
= Device mapper =
90
91
Upon startup Tvheadend will try to map the available hardware to the adapters as good as it can. 
92
In Tvheadend 2.x it was required that the stored configuration about the adapter exactly matched the plugged in hardware.
93
94
Instead Tvheadend 3.x will try to map hardware to configured devices according to the following ruleset:
95
96
 * device type AND device name AND bus-id AND device path 
97
 * device type AND device name AND bus-id
98
 * device type AND device name
99
 * device type AND bus-id
100
 * device type
101
102
||device path||Path in filesystem||/dev/dvb/...||
103
||bus-id||Hardware address||Bus 001 Device 004: ID 0ccd:0038 TerraTec Electronic GmbH Cinergy T2 DVB-T Receiver
104
||device-name||Name of device(vendor) as reported via DVB API||ST STV0297 DVB-C||
105
||device-type||Frontend type(s)||DVB-T, DVB-C, etc||
106
107 5 Andreas Smas
It will start will all devices and try rule 1 then all devices that could not be mapped and rule 2, and so on.
108 4 Andreas Smas
This will mitigate problems when USB controllers probe devices in different order, etc
109 1 Andreas Smas
Also you can swap your DVB hardware to a new one (different vendor) and still have tvheadend map it correctly.
110 8 Andreas Smas
111
If the mapper cannot find a hardware device using the first rule the adapter info/configuration will highlight this
112
and the user will be able to "nail" the configuration to the detected hardware. Ie. to acknowledge to Tvheadend
113
that: "Yes, this is the correct hardware. I've changed/moved it" or whatever
114 6 Andreas Smas
115
= Networks =
116
117
In Tvheadend 2.x a DVB network (ie. a collection of DVB Muxes) are implicitly tied to a DVB adapter. 
118
There are a number of drawbacks with this
119
120
 * Adding another adapter to the same network require all muxes to be rescanned or copied from an already present adapter
121
 * Replacing an adapter will void all configuration so it needs to be reconfigured. 
122
123
Instead Tvheadend 3.x will keep the Network configuration separated from the adapter configuration. 
124
This obviously fixes the two caveats mentioned above. 
125
126
= LNB configuration =
127
128
Tvheadend 2.x have a set of preconfigured LNBs to select from. Tvheadend 3.x will also have those but also make it possible to enter LNB parameters manuallt.