File: README

package info (click to toggle)
getstream 20070419-1
  • links: PTS
  • area: main
  • in suites: lenny
  • size: 308 kB
  • ctags: 658
  • sloc: ansic: 4,137; makefile: 58
file content (70 lines) | stat: -rw-r--r-- 1,970 bytes parent folder | download
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
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70

Building:
	- Install libevent and glib
	- Probably adapt paths in Makefile
	- type "make"

Configuration:

  As getstream supports DVB-C, DVB-T and DVB-S and all need different
  parameters for tuning in on the right transponder here is a short
  introduction on how to enter the right parameters.

  DVB-T 
    
    There are 6 possible options to list for a DVB-T transponder:

      frequency		- Frequency of transponder in Hz
      bandwidth		- auto, 6 (6Mhz), 7 (7Mhz), 8 (8Mhz)
      transmission-mode	- auto, 2 (2Khz), 8 (8Khz)
      guard-interval	- auto, 4 (1/4), 8 (1/8), 16 (1/16), 32 (1/32)
      hierarchy		- none, auto, 1, 2, 4
      modulation	- auto, 16, 32, 64, 128, 256

    Example:

        dvb-t {
          frequency 570000000;
          bandwidth 8;
          transmission-mode auto;
          guard-interval auto;
          hierarchy none;
          modulation auto;
        };



  Channel
    
    A Channel is the definition of the program in the input transport stream
    and its output streams. A channel contains at least a name and a single output
    definition like "stream-http" "stream-rtp" or "stream-udp". The channel number after
    the channel keyword is the Program Number as found in the PAT (Program Association Table)
    at pid 0 of the transport stream.

    name	- Channel name referred to in SAP announcements and debugging output
    csa		- Content Scrambling config 

    Example:

      channel 28479 {
        name "WDR 5";
        stream-http {
          url /radio/wdr5;
        };
      };

  CSA
  
    Sometimes it might be necessary license wise to encrypt the content send out. To allow
    encryption you may configure csa on the channel. You need to configure a key which is 
    8 byte hex. You may configure an encryption length depending on your CPU resources. By
    default this is the transport packet size of 188 byte.

    Example:
 
    csa {;
      key 0x1234567812345678;
      length 64;
    }