Want more features on Pastebin? Sign Up, it's FREE!
Guest

root

By: a guest on Dec 25th, 2010  |  syntax: None  |  size: 42.49 KB  |  views: 112  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. MuMuDVB - README
  2. ================
  3. Brice Dubost <mumudvb@braice.net>
  4. Version 1.6.1
  5.  
  6. [NOTE]
  7. An HTML version of this file is availaible on http://mumudvb.braice.net[MuMuDVB's website].
  8.  
  9. image::http://mumudvb.braice.net/mumudvb/logo_mumu_wiki.png[caption="logo MuMuDVB"]
  10.  
  11. Presentation
  12. ------------
  13.  
  14. Description
  15. ~~~~~~~~~~~
  16.  
  17. MuMuDVB (Multi Multicast DVB) is originally a modification of dvbstream that http://www.crans.org[cr@ns] made. We have decided to redistribute it.
  18.  
  19. Now, it's a standalone project.
  20.  
  21. MuMuDVB is a program that redistributes streams from DVB (Digital Television) on a network (also called IPTV) using
  22. multicasting or HTTP unicast. It can multicast a whole DVB transponder by assigning
  23. each channel a different multicast IP.
  24.  
  25. Website
  26. ~~~~~~~
  27.  
  28. http://mumudvb.braice.net[Mumudvb main site]
  29.  
  30.  
  31. Authors and contacts
  32. --------------------
  33.  
  34. .Upstream author
  35. - mailto:mumudvb@braice.net[Brice Dubost]
  36.  
  37. .Contributions
  38. - mailto:manu@REMOVEMEcrans.ens-cachan.fr[Manuel Sabban] (getopt)
  39. - mailto:glondu@REMOVEMEcrans.ens-cachan.fr[Stéphane Glondu] (man page, debian package)
  40. - Special thanks to Dave Chapman (dvbstream author)
  41. - Pierre Gronlier, Sébastien Raillard, Ludovic Boué, Romolo Manfredini
  42. - Utelisys Communications B.V. for the transcoding code
  43.  
  44. .Mailing list:
  45. - mailto:mumudvb-dev@REMOVEMElists.crans.org[MuMuDVB dev]
  46. - https://lists.crans.org/listinfo/mumudvb-dev[MuMuDVB dev list information and subscription]
  47.  
  48. [NOTE]
  49. When contacting about an issue, please join the config file used and the output of MuMuDVB in verbose mode ( -vvv on the command line) and any other information that could be useful.
  50.  
  51.  
  52. Contents and features
  53. ---------------------
  54.  
  55. Features overview
  56. ~~~~~~~~~~~~~~~~~
  57.  
  58. - Stream channels from a transponder on different multicast IPs
  59. - Support for scrambled channels (if you don't have a CAM you can use sasc-ng, but check if it's allowed in you country/by your broadcaster)
  60. - Support for automatic configuration i.e channels discovery, see <<autoconfiguration,Autoconfiguration>> section
  61. - Generation of SAP announces, see <<sap,SAP>> section
  62. - Support of DVB-S2, DVB-S, DVB-C, DVB-T and ATSC
  63. - Possibility to partially rewrite the stream for better compatibility with set-top boxes and some clients. See <<pat_rewrite,PAT Rewrite>> and <<sdt_rewrite,SDT Rewrite>> sections.
  64. - Support for HTTP unicast see <<unicast,http unicast>> section
  65. - Support for RTP headers (only for multicast)
  66. - Ability to transcode the stream (only for multicast for the moment) see the <<transcoding,Transcoding>> section
  67. - CAM menu access while streaming (using a web/AJAX interface - see WEBSERVICES.txt and CAM_menu_interface.png for screenshot)
  68.  
  69. Detailled feature list
  70. ~~~~~~~~~~~~~~~~~~~~~~
  71.  
  72. - Can show reception level when streaming
  73. - Show if channels are successfully descrambled by the CAM
  74. - Makes a list of streamed and down channels in real time
  75. - Can deamonize and write his own process id in a file
  76. - Supports standard and universals LNBs
  77. - Can stop himself if it receives no data from the card after a defined timeout
  78. - Stops trying tuning after a configurable timeout
  79. - The mandatory pids are always sent with all channels :
  80.   * PAT (0): Program Association Table
  81.   * CAT (1): Conditionnal Access Table
  82.   * NIT (16): Network Information Table: intended to provide information about the physical network.
  83.   * SDT (17): Service Description Table: data describing the services in the system e.g. names of services, the service provider, etc.
  84.   * EIT (18): Event Information Table: data concerning events or programmes such as event name, start time, duration, etc.
  85.   * TDT (20): Time and Date Table: information related to the present time and date.This information is given in a separate table due to the frequent updating of this information.
  86. - Can suscribe to all multicast groups (IGMP membership request) in order to avoid some switches to broadcast all channels see <<problems_hp,problems with HP switches>>.
  87. - Supports autoconfiguration, see <<autoconfiguration,Autoconfiguration>> section
  88.   * In autoconfiguration mode, MuMuDVB follow the changes in the PIDs and update itself while running.
  89. - Debian flavor initialisation scripts
  90. - The buffer size can be tuned to reduce CPU usage, see <<reduce_cpu,reduce MuMuDVB CPU usage>> section.
  91. - Can avoid the sending of scrambled packets
  92. - Automatically detect the scrambling status of a channel
  93. - Can reset the CAM module in case of a bad initialisation
  94. - Can sort the EIT PID to send only the ones corresponding to the current channel
  95. - Data reading can be done using a thread, see <<threaded_read, thread reading>> section.
  96. - Playlist generation, see <<playlist, playlist>>
  97. - Templates support
  98. - Simple webservice exposing detailed streaming status (see WEBSERVICES.txt)
  99.  
  100. Installation
  101. ------------
  102.  
  103. From sources
  104. ~~~~~~~~~~~~
  105.  
  106. From a snapshot
  107. ^^^^^^^^^^^^^^^
  108.  
  109. If you downloaded a snapshot, you will have to generate the auto(conf make etc ...) files. In order to do this you will need the autotools, automake, gettext and libtool and, type in the folder of MuMuDVB
  110.  
  111. ----------------
  112. autoreconf -i -f
  113. ----------------
  114.  
  115. Then you have a source which can be installed as a release package.
  116.  
  117. From a release package
  118. ^^^^^^^^^^^^^^^^^^^^^^
  119.  
  120. In order to install MuMuDVB type:
  121.  
  122. ---------------------------------
  123. $ ./configure [configure options]
  124. $ make
  125. # make install
  126. ---------------------------------
  127.  
  128. The `[configure options]` specific to MuMuDVB are:
  129.  
  130. ---------------------------------------------------------------------
  131.   --enable-cam-support    CAM support (default enabled)
  132.   --enable-coverage       build for test coverage (default disabled)
  133.   --enable-duma           Debbuging DUMA library (default disabled)
  134. ---------------------------------------------------------------------
  135.  
  136. You can have a list of all the configure options by typing
  137.  
  138. --------------------
  139. $ ./configure --help
  140. --------------------
  141.  
  142. [NOTE]
  143. The CAM support depends on libdvben50221, libucsi (from linuxtv's dvb-apps). The configure script will detect automatically the presence of these libraries and desactivate the CAM support if one of them is not present.
  144.  
  145. [NOTE]
  146. The decoding of long channel names for autoconfiguration in ATSC depends on libucsi (from linuxtv's dvb-apps). The configure script will detect automatically the presence of this library and desactivate the long channel name support if it is not present. The full autoconfiguration will still work with ATSC but the channel names will be the short channels names (7 characters maximum)
  147.  
  148. [NOTE]
  149. If you want to compile the doc i.e. generate HTML files using asciidoc, type `make doc`. The rendering for the tables will work with asciidoc 8.4.4 (can work with lower version but not tested).
  150.  
  151. In order to install starting scripts (debian flavor) type:
  152.  
  153. ------------------------------------------------------------
  154. # cp scripts/debian/etc/default/mumudvb /etc/default/mumudvb
  155. # cp scripts/debian/etc/init.d/mumudvb /etc/init.d/mumudvb
  156. ------------------------------------------------------------
  157.  
  158. [NOTE]
  159. It is advised to create a system user for MuMuDVB, e.g. : `_mumudvb`, you have to add this user to the video group and make the directory `/var/run/mumudvb` RW by this user. By doing this, you'll be able to get all the features of MuMuDVB.
  160.  
  161.  
  162. From Debian package
  163. ~~~~~~~~~~~~~~~~~~~
  164.  
  165. If you want to install a version which is not in your repositories, you can install it by hand by typing:
  166.  
  167. ----------------------
  168. # dpkg -i mumudvb*.deb
  169. ----------------------
  170.  
  171. Otherwise you can use aptitude/synaptic as usual
  172.  
  173. Usage
  174. -----
  175.  
  176. The documentation for configuration file syntax is in `doc/README_CONF.txt` (link:README_CONF.html[HTML version]).
  177.  
  178. Usage:
  179.  
  180. --------------------------------------
  181. mumudvb [options] -c config_file
  182. mumudvb [options] --config config_file
  183. --------------------------------------
  184.  
  185. Possible options are:
  186.  
  187. ------------------------------------------------------------------
  188. -d, --debug
  189.         Don't deamonize and print messages on the standard output.
  190.  
  191. -s, --signal
  192.         Print signal strenght every 5 seconds
  193.  
  194. -t, --traffic
  195.         Print the traffic of the channels every 10 seconds
  196.  
  197. -l, --list-cards
  198.         List the DVB cards and exit
  199.  
  200. --card
  201.         The DVB card to use (overrided by the configuration file)
  202.  
  203. --server_id
  204.         The server id (for autoconfiguration, overrided by the configuration file)
  205.  
  206. -h, --help
  207.         Show help
  208.  
  209. -v
  210.         More verbose (add for more)
  211.  
  212. -q
  213.         More quiet (add for less)
  214.  
  215. --dumpfile
  216.         Debug option : Dump the stream into the file specified
  217. ------------------------------------------------------------------
  218.  
  219. Signal: (see kill(1))
  220. ------------------------------------------------------------------
  221.     SIGUSR1: switch the signal strenght printing
  222.     SIGUSR2: switch the traffic printing
  223.     SIGHUP: flush the log files
  224. ------------------------------------------------------------------
  225.  
  226. [[autoconfiguration]]
  227. Autoconfiguration
  228. -----------------
  229.  
  230. MuMuDVB is able to find the channels in the transponder and their PIDs (Program IDentifiers).
  231.  
  232. Without autoconfiguration, you have to set the transponder parameters, and for each channel, the multicast ip, the name and the PIDs (PMT, audio, video, teletext etc...)
  233.  
  234. At the end of autoconfiguration, MuMuDVB generates a config file with the discovered parameters. This file is: `/var/run/mumudvb/mumudvb_generated_conf_card%d_tuner%d`
  235.  
  236. If the PIDs are changed, MuMuDVB will automatically update the channels except if you put `autoconf_pid_update=0` in your configuration file.
  237.  
  238. MuMuDVB is able to do two kinds of autoconfiguration:
  239.  
  240. Full autoconfiguration
  241. ~~~~~~~~~~~~~~~~~~~~~~
  242.  
  243. This is the easiest way to use MuMuDVB.
  244.  
  245. Use this when you want to stream a full transponder or a subset of a transponder (using autoconf_sid_list).
  246.  
  247. [NOTE]
  248. You don't have to specify any channel using this mode
  249.  
  250. In this mode, MuMuDVB will find for you the different channels, their name and their PIDs (PMT, PCR, Audio, Video, Subtitle, Teletext and AC3).
  251.  
  252. In order to use this mode you have to:
  253. - Set the tuning parameters to your config file
  254. - Add `autoconfiguration=full` to your config file
  255. - You don't have to set any channels
  256. - For a first use don't forget to put the `-d` parameter when you launch MuMuDVB:
  257.    e.g. `mumudvb -d -c your_config_file`
  258.  
  259. .Example config file for satellite at frequency 11.296GHz with horizontal polarization
  260. ----------------------
  261. freq=11296
  262. pol=h
  263. srate=27500
  264. autoconfiguration=full
  265. ----------------------
  266.  
  267. The channels will be streamed over the multicasts ip adresses 239.100.c.n where c is the card number (0 by default) and n is the channel number.
  268.  
  269. If you don't use the common_port directive, MuMuDVB will use the port 1234.
  270.  
  271. [NOTE]
  272. By default, SAP announces are activated if you use this autoconfiguration mode. To desactivate them put `sap=0` in your config file.
  273. By default, SDT rewriting is activated if you use this autoconfiguration mode. To desactivate it put `rewrite_sdt=0` in your config file.
  274. By default, PAT rewriting is activated if you use this autoconfiguration mode. To desactivate it put `rewrite_pat=0` in your config file.
  275. By default, EIT sorting activated if you use this autoconfiguration mode. To desactivate it put `sort_eit=0` in your config file.
  276.  
  277. [NOTE]
  278. A detailled, documented example configuration file can be found in `doc/configuration_examples/autoconf_full.conf`
  279.  
  280. Name templates and autoconfiguration
  281. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  282.  
  283. By default the name of the channel will be the name of the service defined by the provider. If you want more flexibility you can use a template.
  284.  
  285. For example, if you use `autoconf_name_template=%number-%name` The channels name will be in the form :
  286.  
  287. - `1-CNN`
  288. - `2-Euronews`
  289.  
  290.  
  291. There is different keywords available:
  292.  
  293. [width="80%",cols="2,8",options="header"]
  294. |==================================================================================================================
  295. |Keyword |Description
  296. |%name | The name given by the provider
  297. |%number | The MuMuDVB channel number
  298. |%card | The DVB card number
  299. |%tuner | The tuner number
  300. |%server| The server number specified by server_id or the command line
  301. |%lcn | The logical channel number (channel number given by the provider). You have to put `autoconf_lcn=1` in your configuration file and your provider have to stream LCN. The LCN will be displayed with three digits including 0. Ex "002". If the LCN is not detected, %lcn will be replaced by an empty string.
  302. |%2lcn | Same as above but with a two digits format
  303. |==================================================================================================================
  304.  
  305. Please refer to README_CONF to see which options accept which templates
  306.  
  307. Other keywords can be easily added if necessary.
  308.  
  309.  
  310.  
  311. [[autoconfiguration_simple]]
  312. Simple autoconfiguration
  313. ~~~~~~~~~~~~~~~~~~~~~~~~
  314.  
  315. [NOTE]
  316. This autoconfiguration mode will soon disapear. If you absolutely need it except for setting the channel names and their IP adresses, please contact.
  317.  
  318. Use this when you want to control the name of the channels, and their IPs better than using the templates.
  319.  
  320.  
  321. - You have to add 'autoconfiguration=partial' in the head of your config file.
  322. - For each channel, you have to set:
  323.  * the Ip adress (except if you use unicast)
  324.  * the name
  325.  * the PMT PID
  326.  
  327.  
  328. MuMuDVB will find the audio, video, PCR, teletext, subtitling and AC3 PIDs for you before streaming.
  329.  
  330. [NOTE]
  331. If you put more than one PID for a channel, MuMuDVB will desactivate autoconfiguration for this channel.
  332.  
  333. [NOTE]
  334. A detailled, documented example configuration file can be found in `doc/configuration_examples/autoconf1.conf`
  335.  
  336. [NOTE]
  337. Simple autoconfiguration can fail finding the good pids if a PMT pid is shared within multiples channels. In this case you have to add the `service_id` option to the channel to specify the service id.
  338.  
  339. [[sap]]
  340. SAP announces
  341. -------------
  342.  
  343. SAP (Session Announcement Protocol) announces are made for the client to know which channels are streamed and what is their name and adress. It avoids to give to the client the list of the multicast ip adresses.
  344.  
  345. VLC and most of set-top boxes are known to support them.
  346.  
  347. MuMuDVB will automatically generate and send SAP announces if asked to in the config file or if you are in full autoconfiguration mode.
  348.  
  349. The SAP announces will be only sent for alive channels. When a channel goes down, MuMuDVB will stop sending announces for this channel, until it goes back.
  350.  
  351.  
  352. Asking MuMuDVB to generate SAP announces
  353. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  354.  
  355. For sending SAP announces you have to add `sap=1` to your config file. The other parameters concerning the sap announces are documented in the `doc/README_CONF.txt` file (link:README_CONF.html[HTML version]).
  356.  
  357. SAP announces and full autoconfiguration
  358. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  359.  
  360. If you use full autoconfiguration, you can use the keyword '%type' in the sap_default_group option. This keyword will be replaced by the type of the channel: Television or Radio.
  361.  
  362. .Example
  363. If you put `sap_default_group=%type`, you will get two sap groups: Television and Radio, each containing the corresponding services.
  364.  
  365.  
  366. Configuring the client to get the SAP announces
  367. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  368.  
  369. VLC > 0.8.2
  370. ^^^^^^^^^^^
  371. You have to enter the settings, choose advanced settings. The SAP announces are in playlist->service discovery.
  372.  
  373. Don't forget to save the settings.
  374.  
  375. You should have now a SAP section in your playlist.
  376.  
  377. VLC < 0.8.2
  378. ^^^^^^^^^^^
  379.  
  380. Click on the "Settings" menu, then on "add interface" and choose SAP playlist. Then open you playlist, the SAP announces should appear automatically.
  381.  
  382.  
  383.  
  384. [[unicast]]
  385. HTTP Unicast
  386. ------------
  387.  
  388. In addition to multicast, MuMuDVB also supports HTTP unicast. This make you able to use MuMuDVB on networks wich doesn't support multicast.
  389.  
  390. There is one listening connection, the channel is selected via the HTTP path, see further.
  391.  
  392. And you can have listening sockets per channel, in this case the client will always get the same channel independantly of the path.
  393.  
  394. [NOTE]
  395. Be careful with unicast, it can eat a lot of bandwith. Think about limitting the number of clients.
  396.  
  397. [NOTE]
  398. If you don't want the (always here) multicast traffic to go on your network set `multicast=0`
  399.  
  400. Activate HTTP unicast
  401. ~~~~~~~~~~~~~~~~~~~~~
  402.  
  403. To enable HTTP unicast you have to set the option `unicast`. By default MuMuDVB will listen on all your interfaces for incoming connections.
  404.  
  405. You can also define the listening port using `port_http`. If the port is not defined, the default port will be 4242.
  406.  
  407. Activate "per channel" listening socket
  408. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  409.  
  410. You can create listening connections only for a channel. In this case, when a client connect to this socket he will alway get the same channel independantly of the HTTP path.
  411.  
  412. If you use full autoconfiguration
  413. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  414.  
  415. You need to set the option `autoconf_unicast_start_port` which define what is the output port for the first discovered channel (for the following channels the port will be incremented).
  416.  
  417.  
  418. If you don't use full autoconfiguration
  419. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  420.  
  421. For the channels for which you want to have a listening unicast socket you have to set the option `unicast_port` which define the listening port of the socket
  422.  
  423.  
  424.  
  425. Client side, the different methods to get channels
  426. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  427.  
  428. [[playlist]]
  429. Using a playlist
  430. ^^^^^^^^^^^^^^^^
  431.  
  432. MuMuDVB generates m3u playlists.
  433.  
  434. If you server is listening on the ip 10.0.0.1 and the port 4242,
  435.  
  436. -------------------------------------
  437. vlc http://10.0.0.1:4242/playlist.m3u
  438. -------------------------------------
  439.  
  440. [NOTE]
  441. In this playlist the channels will be announced with URLs type `/bynumber/` (see below), if you want a playlist for single channel sockets, use the URL `/playlist_port.m3u`.
  442.  
  443. [NOTE]
  444. Playlists for multicast are also generated, they are accessible using the following names: "playlist_multicast.m3u" and "playlist_multicast_vlc.m3u"
  445.  
  446.  
  447. Single channel socket
  448. ^^^^^^^^^^^^^^^^^^^^^
  449.  
  450. If the client connect to a single client socket he will get the associated channel independantly of the path.
  451.  
  452. If you server is listening on the ip 10.0.0.1 and the port for the channel is 5000,
  453.  
  454. -------------------------
  455. vlc http://10.0.0.1:5000/
  456. -------------------------
  457.  
  458. Get the channel by number
  459. ^^^^^^^^^^^^^^^^^^^^^^^^^
  460.  
  461. You can ask the channel by the channel number (starting at 1).
  462.  
  463. If you server is listening on the ip 10.0.0.1 and the port 4242,
  464.  
  465. ------------------------------------
  466. vlc http://10.0.0.1:4242/bynumber/3
  467. ------------------------------------
  468.  
  469. will give you the channel number 3. This works also with xine and mplayer.
  470.  
  471. Get the channel by service id
  472. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  473.  
  474. You can ask the channel by the service id.
  475.  
  476. If you server is listening on the ip 10.0.0.1 and the port 4242,
  477.  
  478. ----------------------------------
  479. vlc http://10.0.0.1:4242/bysid/100
  480. ----------------------------------
  481.  
  482. will give you the channel with the service id 100, or a 404 error if there is no channel with this service id. This works also with xine and mplayer.
  483.  
  484. Get the channel by name
  485. ^^^^^^^^^^^^^^^^^^^^^^^
  486.  
  487. [NOTE]
  488. This is not implemented for the moment, it will be implemented in a future release
  489.  
  490. Get the channels list
  491. ^^^^^^^^^^^^^^^^^^^^^
  492.  
  493. If you server is listening on the ip 10.0.1 and the port 4242,
  494.  
  495. To get the channel list (in basic html) just enter the adress `http://10.0.0.1:4242/channels_list.html` in your web browser.
  496.  
  497. To get the channel list (in JSON) just enter the adress `http://10.0.0.1:4242/channels_list.json` in your web browser.
  498.  
  499. HTTP unicast and monitoring
  500. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  501.  
  502. This HTTP connection can be used to monitor MuMuDVB.
  503.  
  504. Monitoring information is avalaible in JSON format (http://en.wikipedia.org/wiki/JSON) vis the following urls `/monitor/signal_power.json` and `/monitor/channels_traffic.json`
  505.  
  506. It's quite easy to add new informations to these files if needed.
  507.  
  508. Monitoring
  509. ----------
  510.  
  511. You can use http://mmonit.com/monit/[Monit] to monitor MuMuDVB an restart it when it experiences problems (MuMuDVB kill himself when big issues appear).
  512.  
  513. You have to install the init scripts (automatic if you used the Debian package) and add the following lines to your `/etc/monit/services` file:
  514.  
  515. ----------------------------------------------------------------------
  516. check process mumudvb with pidfile /var/run/mumudvb/mumudvb_adapter0_tuner0.pid
  517.     start program = "/etc/init.d/mumudvb start"
  518.     stop program = "/etc/init.d/mumudvb stop"
  519. ----------------------------------------------------------------------
  520.  
  521. [NOTE]
  522. The 0 have to be replaced by the DVB card number if you have multiples cards.
  523.  
  524. For more detailled information, refer to the http://mmonit.com/monit/[Monit Website].
  525.  
  526. MuMuDVB usually run for many days without problems, but with monit you are safe. Monit is also able to send e-mails in case of problems.
  527.  
  528.  
  529. Scrambled channels support
  530. --------------------------
  531.  
  532. Important note : check the contract with your broadcaster to see if you are allowed to stream the scrambled channels you're subscribed to.
  533.  
  534. Hardware descrambling
  535. ~~~~~~~~~~~~~~~~~~~~~
  536.  
  537. MuMuDVB supports scrambled channels via hardware descrambling i.e. a CAM (Conditionnal Access Module). It can ask the CAM to descramble multiple channels if the CAM supports it (Aston Pro, or PowerCam Pro are known to work with multiple channels).
  538.  
  539. If you are limited by the number of PIDs the can can decrypt simultaneously, it is possible to ask the CAM to decrypt only the audio and video. This feature is not implemented, please ask if you need it.
  540.  
  541. [NOTE]
  542. The hardware descramblig uses almost no CPU, all the descrambling is made by the CAM.
  543.  
  544. [NOTE]
  545. MuMuDVB doesn't query the CAM before asking for descrambling. The query is not reliable. Most of CAMs answer a menu when the descrambling is not possible and MuMuDVB will display it on the standard error.
  546.  
  547. The information concerning the CAM is stored in '''/var/run/mumudvb/caminfo_adapter%d_tuner%d''' where %d is the DVB card number.
  548.  
  549. .Example contents of '''/var/run/mumudvb/caminfo_carte%d'''
  550. ----------------------------------------------------
  551. CAM_Application_Type=01
  552. CAM_Application_Manufacturer=02ca
  553. CAM_Manufacturer_Code=3000
  554. CAM_Menu_String=PowerCam_HD V2.0
  555. ID_CA_Supported=0100
  556. ID_CA_Supported=0500
  557. ----------------------------------------------------
  558.  
  559.  
  560. How to ask MuMuDVB for descrambling?
  561. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  562.  
  563. .You are using full autoconfiguration :
  564.  
  565. Just add `cam_support=1` to your config file
  566.  
  567. .You are using partial autoconfiguration or no autoconfiguration
  568.  * Add `cam_support=1` to your config file (before the channels)
  569.  * For each scrambled channel add the `cam_pmt_pid` option. This option is made for MuMuDVB to know wich PID is the PMT PID wich will be used to ask for descrambling
  570.  
  571. [NOTE]
  572. You have an example of CAM support in doc/configuration_examples/autoconf1.conf
  573.  
  574.  
  575.  
  576. Software descrambling
  577. ~~~~~~~~~~~~~~~~~~~~~
  578.  
  579. Important note : this solution is not allowed by some provider contracts.
  580.  
  581. MuMuDVB has been reported to work with software descrambling solutions like sascng + newcs + dvbloopback.
  582.  
  583. In this case  you don't need to set the `cam_support` option. Just ajust the `card` option to fit with your virtual dvbloopback card.
  584.  
  585. If you use these solutions, see <<reduce_cpu,reduce MuMuDVB CPU usage>> section.
  586.  
  587. Scrambling status
  588. ~~~~~~~~~~~~~~~~~
  589.  
  590. The scrambling status is stored together with the streamed channel list.
  591.  
  592. .Example
  593. ----------------------------------------------
  594. 239.100.0.7:1234:ESCALES:PartiallyUnscrambled
  595. 239.100.0.8:1234:Fit/Toute l'Histoire:PartiallyUnscrambled
  596. 239.100.0.9:1234:NT1:PartiallyUnscrambled
  597. 239.100.0.10:1234:ACTION:PartiallyUnscrambled
  598. 239.100.0.11:1234:MANGAS:PartiallyUnscrambled
  599. 239.100.0.12:1234:ENCYCLOPEDIA:PartiallyUnscrambled
  600. 239.100.0.13:1234:XXL PL:PartiallyUnscrambled
  601. 239.100.0.14:1234:France 5:HighlyScrambled
  602. 239.100.0.16:1234:LCP:FullyUnscrambled
  603. 239.100.0.17:1234:VIDEOCLICK:FullyUnscrambled
  604. ----------------------------------------------
  605.  
  606.  * FullyUnscrambled : less than 5% of scrambled packets
  607.  * PartiallyUnscrambled : between 5% and 95% of scrambled packets
  608.  * HighlyScrambled : more than 95% of scrambled packets
  609.  
  610. [[pat_rewrite]]
  611. PAT (Program Allocation Table) Rewriting
  612. -----------------------------------------
  613.  
  614. This feature is mainly intended for set-top boxes. This option will announce only the streamed channel in the Program Allocation Table instead of all transponder channels. Computer clients parse this table and decode the first working program. Set-top boxes usually try only the first one which give usually a blank screen in most of the channels.
  615.  
  616. To enable PAT rewriting, add `rewrite_pat=1` to your config file. This feature consumes few CPU, since the rewritten PAT is stored in memory and computed only once per channel.
  617.  
  618. [NOTE]
  619. PAT rewrite can fail (i.e. doesn't solve the previous symptoms) for some channels if their PMT pid is shared. In this case you have to add the `service_id` option to the channel to specify the service id.
  620.  
  621. [[sdt_rewrite]]
  622. SDT (Service Description Table) Rewriting
  623. -----------------------------------------
  624.  
  625. This option will announce only the streamed channel in the Service Description Table instead of all transponder channels. Some clients parse this table and can show/select ghost programs if it is not rewritten (even if the PAT is). This can rise to a random black screen.
  626.  
  627. To enable SDT rewriting, add `rewrite_sdt=1` to your config file. This feature consumes few CPU, since the rewritten SDT is stored in memory and computed only once per channel.
  628.  
  629. [NOTE]
  630. If you don't use full autoconfiguration, SDT rewrite needs the `service_id` option for each channel to specify the service id.
  631.  
  632.  
  633.  
  634. EIT PID (Event Information Table) Sorting
  635. -----------------------------------------
  636.  
  637. This option will make MuMuDVB stream only the EIT packets corresponding to the streamed channel instead of all transponder channels. Some clients parse this table and can show/select ghost programs  (even if the PAT and the SDT are rewritten).
  638.  
  639. To enable EIT sorting, add `sort_eit=1` to your config file.
  640.  
  641. [NOTE]
  642. If you don't use full autoconfiguration, EIT sorting needs the `service_id` option for each channel to specify the service id.
  643.  
  644. [[reduce_cpu]]
  645. Reduce MuMuDVB CPU usage
  646. ------------------------
  647.  
  648. Normally MuMuDVB reads the packets from the card one by one and ask the card if there is data avalaible between each packets (poll). But often the cards have an internal buffer. Because of this buffer, some pollings are useless. These pollings eat some CPU time.
  649.  
  650. To reduce CPU usage, one solution is to try to read several packets at the same time. To do this use the option `dvr_buffer_size`.
  651.  
  652. .Example
  653. ------------------
  654. dvr_buffer_size=40
  655. ------------------
  656.  
  657. To see if the value you put is too big or to low, run MuMuDVB in verbose mode, the average number of packets received at the same time will be shown every 2 minutes. If this number if below your buffer size, it is useless to increase it.
  658.  
  659. The CPU usage reduction can be between 20% and 50%.
  660.  
  661. [[threaded_read]]
  662. Data reading using a thread
  663. ---------------------------
  664.  
  665. In order to make MuMuDVB more robust (at the cost of a slight CPU consumption increase), MuMuDVB can read the data from the card using a thread. This make the data reading "independant" of the rest of the program.
  666.  
  667. In order to enable this feature, use the option `dvr_thread`.
  668.  
  669. This reading uses two buffers: one for the data just received from the card, one for the data treated by the main program. You can adjust the size of this buffers using the option `dvr_thread_buffer_size`. The default value  (5000 packets of 188 bytes) should be sufficient for most of the cases.
  670.  
  671. The message "Thread trowing dvb packets" informs you that the thread buffer is full and some packets are dropped. Increase the buffer size will probably solve the problem.
  672.  
  673.  
  674. [[transcoding]]
  675. Transcoding
  676. -----------
  677.  
  678. MuMuDVB supports transcoding to various formats to save bandwidth. The transcoding is made using ffmpeg librairies. This feature is pretty new, so feel free to contact if you have comments/suggestions
  679.  
  680. [NOTE]
  681. Transcoding doesn't work for the moment with unicast
  682.  
  683. To have more details on transcoding, see the dedicated documentation file
  684.  
  685. Technical details (not sorted)
  686. ------------------------------
  687.  
  688.  * CPU consuming: MuMuDVB takes 15% CPU of a celeron 2.6GHz with an Hauppauge card and linux version 2.6.9 when streaming a full transponder (about 30MBit/s)
  689.  
  690.  * Try to avoid old via or nForce chipsets and in general ultra low cost motherboards. They can't deal with a lot of data on the PCI bus.
  691.  
  692.  * When the program starts, he writes the channel list in the file `/var/run/mumudvb/channels_streamed_adapter%d_tuner%d` (where %d are the card number and the tuner number). This file contains streamed channels (updated every 5 seconds) in the form: "name:ip:port:Scramblingstatus"
  693.  
  694.  * MuMuDVB is able to support as many cards as the operating system does. Old versions of udev+glibc were not able to support more than 4 cards but this problem is solved using relatively recent versions (udev > 104 and libc6 > 2.7)
  695.  
  696.  * When daemonized, MuMuDVB writes its process identifier in `/var/run/mumudvb/mumudvb_adapter%d_tuner%d.pid`, where %d is replaced by the card number and the tuner number
  697.  
  698.  * MuMuDVB supports satellite in the Ku band, with universal or standard LNBs. The support of satellites in the S or C band is implemented via the use of the lo_frequency option. See `doc/README_CONF.txt` (link:README_CONF.html[HTML version]).
  699.  
  700. MuMuDVB Logs
  701. ------------
  702.  
  703. MuMuDVB can send it's logs to the console, to a file or via syslog. It can also be several of these channels. The formatting of the logs can also be adjusted.
  704.  
  705. By default, the logs are sent to the console if not daemonized and via syslog otherwise.
  706.  
  707. If the logs are sent to a file, you can ask MuMuDVB to flush the file using the SIGHUP signal.
  708.  
  709. For more detail about these features see `doc/README_CONF.txt` (link:README_CONF.html[HTML version]).
  710.  
  711.  
  712. Known issues
  713. ------------
  714.  
  715. VLC can't read the stream but it is fine with xine or mplayer
  716. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  717.  
  718.  * For VLC, you must specify the PMT PID besides audio and video PIDs.
  719. It's a frequent issue. To solve it you can use the verbose mode of VLC (`vlc -v`) and you'll see a ligne like: `[00000269] ts demuxer debug:   * number=1025 pid=110` you'll have the PMT PID associated with your program number, you can also use dvbsnoop, or see how to get pids in `doc/README_CONF.txt` (link:README_CONF.html[HTML version]). Another solution is to use full autoconfiguration.
  720.  
  721. VLC reads the video but no audio
  722. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  723.  
  724.  * This problem can happend if the PCR (i.e. clock) information is not carried with the video. In this case you have to check if the PCR PID is in the PIDs list.
  725.  
  726. MuMuDVB can't deamonize
  727. ~~~~~~~~~~~~~~~~~~~~~~~
  728.  
  729.  * In order to deamonize, MuMuDVB needs the directory `/var/run/mumudvb/` to be writable, in order to write his process identifier and the channel list.
  730.  
  731. The system crashes or freeze
  732. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  733.  
  734.  * Old via chipset or nForce chipset are not professional chipsets. They can't deal with a lot of data on PCI. But you can try to tune your BIOS.
  735.  
  736. Tuning issues with DVB-T
  737. ~~~~~~~~~~~~~~~~~~~~~~~~
  738.  
  739.  * You must check tuning settings, knowing that auto bandwidth usually does'nt work.
  740.  
  741. The set-top box display a blank screen
  742. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  743.  
  744.  * If the stream is working well when reading it with a computer and not with your set-top box, this is probably because your set-top box needs the PAT PID to be rewritten. To do this add `rewrite_pat=1` to your config file.
  745.  
  746. Simple autoconfiguration fails finding the right pids
  747. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  748.  
  749.  * This can happend if a PMT PIDs is shared among multiple channels, see <<autoconfiguration_simple,simple autoconfiguration>> section for more details.
  750.  
  751. The CAM is complaining about locked channels
  752. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  753.  
  754.  * Some viaccess CAMs can have a lock for "mature" channels. To desactivate this lock go on the CAM menu using "gnutv -cammenu" for example (from linuxtv dvb-apps).
  755.  
  756. You have to set the maturity rating to maximum and unlock Maturity rating in Bolts submenu.
  757.  
  758. VLC doesn't select the good program even with PAT rewriting
  759. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  760.  
  761. You also have to rewrite the SDT PID using the `rewrite_sdt` option
  762.  
  763.  
  764. [[problems_hp]]
  765. HELP ! my multicast traffic is flooded (I have a HP procurve switch)
  766. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  767.  
  768. The best explanation is found in the HP multicast routing guide.
  769.  
  770. On switches that do not support Data-Driven IGMP, unregistered multicast
  771. groups are flooded to the VLAN rather than pruned. In this scenario, Fast-Leave IGMP can actually increase the problem of multicast flooding by removing the IGMP group filter before the Querier has recognized the IGMP leave. The Querier will continue to transmit the multicast group during this short time, and because the group is no longer registered the switch will then flood the multicast group to all ports.
  772.  
  773. On ProCurve switches that do support Data-Driven IGMP (“Smart” IGMP),
  774. when unregistered multicasts are received the switch automatically filters (drops) them. Thus, the sooner the IGMP Leave is processed, the sooner this multicast traffic stops flowing.
  775.  
  776. Switches without problems (supporting data driven igmp):
  777.  
  778.  * Switch 6400cl
  779.  * Switch 6200yl
  780.  * Switch 5400zl
  781.  * Switch 5300xl
  782.  * Switch 4200vl
  783.  * Switch 3500yl
  784.  * Switch 3400cl
  785.  * Switch 2900
  786.  * Switch 2800
  787.  * Switch 2500
  788.  
  789.  
  790. Switches WITH problems (NOT supporting data driven igmp):
  791.  
  792.  * Switch 2600
  793.  * Switch 2600-PWR
  794.  * Switch 4100gl
  795.  * Switch 6108
  796.  
  797. So if you have one of the above switches this is "normal". The workaround is to make MuMuDVB join the multicast group. For this put `multicast_auto_join=1` in your configuration file.
  798.  
  799. MuMuDVB is eating a lot of CPU with sasc-ng !
  800. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  801.  
  802. If you use sasc-ng + dvbloopback, MuMuDVB will eat more CPU than needed.
  803.  
  804. A part of this CPU time is used to descramble the channels, another part is due to the way dvbloopback is implemented and the way MuMuDVB ask the card.
  805.  
  806. To reduce the cpu usage, see <<reduce_cpu,reduce MuMuDVB CPU usage>> section. In the case of using MuMuDVB with sasc-ng this improvement can be quite large.
  807.  
  808.  
  809. The reception is working but all the channels are down
  810. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  811.  
  812. If the signal is good but MuMuDVB tells you that all the channels are down and you are sure about your pids it can be due to your CAM module if you have one. Try after unplugging your CAM module.
  813.  
  814. I want to stream from several cards
  815. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  816.  
  817. The solution is simple: just launch a MuMuDVB process for each card.
  818.  
  819. I want to stream the whole transponder on one "channel"
  820. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  821.  
  822. MuMuDVB can stream all the data received by the card to one "channel" (multicast or unicast). In order to do this you have to use the put the PID 8192 in the channel PID list.
  823.  
  824. I have several network interfaces and I want to choose on which interface the multicast traffic will go
  825. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  826.  
  827. In order to specify the interface, you can specify a route for the multicast traffic like :
  828.  
  829. ---------------------------------------------------
  830. route add -net 224.0.0.0 netmask 240.0.0.0 dev eth2
  831. ---------------------------------------------------
  832.  
  833. What does the MuMuDVB error code means ?
  834. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  835.  
  836. Here's a short description of the error codes
  837.  
  838. ------------------------------
  839.     ERROR_ARGS=1,
  840.     ERROR_CONF_FILE,
  841.     ERROR_CONF,
  842.     ERROR_TOO_CHANNELS,
  843.     ERROR_CREATE_FILE,
  844.     ERROR_DEL_FILE,
  845.     ERROR_TUNE,
  846.     ERROR_NO_DIFF,
  847.     ERROR_MEMORY,
  848.     ERROR_NETWORK,
  849.     ERROR_CAM,
  850.     ERROR_GENERIC,
  851.     ERROR_NO_CAM_INIT,
  852. ------------------------------
  853.  
  854. I get the message "DVR Read Error: Value too large for defined data type" what does it mean ?
  855. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  856.  
  857. This message means that an overflow append in the ard drivers buffer. I.e MuMuDVB was not able to get the packets sufficiently fast. This issue can have various causes, anything which an slow down (a lot) MuMuDVB an create this message.
  858. To avoid it you can try threaded_read see <<threaded_read, thread reading>> section.
  859.  
  860. An explanation can be networking issues :
  861.  
  862. I experienced the "DVR Read Error..." message very often on my  Streaming Server (ia64 Madison 1.3Ghz) (with errors in the video).
  863. I could solve the problem by exchanging the network switch. The old  switch was limiting multicast traffic to 10Mb/s per port. This limit  is not documented.
  864.  
  865. I have tested the limit the programm dd and mnc (Multicast netcat,  http://code.google.com/p/mnc/)
  866.  
  867. dd if=/dev/zero bs=188 count=1000000 | ./mnc-bin 239.10.0.3
  868.  
  869. I looked with "iftop" at the current network statistics and with my  old switch i saw the limit at 10Mb/s with another switch I was able to  transmit 92Mb/s ~ 100% of the avaiable bandwith.
  870.  
  871. Thanks to Jan-Philipp Hülshoff for the report
  872.  
  873.  
  874.  
  875. Using MuMuDVB with "particular" clients
  876. ---------------------------------------
  877.  
  878. People were able to use MuMuDVB with various clients, I will report here the tutorials I received for some of them
  879.  
  880. XBMC (for XBOX originally)
  881. ~~~~~~~~~~~~~~~~~~~~~~~~~~
  882.  
  883. *Description:* XBMC (XBMP really) started as a program for modified XBOX consoles. In the following years, XBMC has grown into a multi-platform, multi-architecture media center that runs on most standard hardware. The hardware and legal limitations of the XBOX were always a concern and the Team has instead focused on running on the hardware that most people already have.
  884.  
  885. *Website:* http://xbmc.org/
  886.  
  887. *Tutorial:*
  888. Here`s what You have to do, open Your favorite text editor and write an ip address with the protocol You are using of the particular program and port save it as something.strm. You have to create .strm files for every program You are streaming. Once you have done that fire up WinSCP and connect to the ip address of Your XBMC box if You are using the live version username and password is xbmc xbmc if You have installed the live version then You have provided the username and password during install process. Now copy theoes .strm files to the XBMC box in lets say home folder. Now in XBMC go to the video menu then click add source then click browse and navigate to the home folder and click ok then u have to give the name of that source use what ever You like and click ok and thats it. Go to the video menu You will see that You have a folder named as You named the source open it and You will see all of Yours .strm files click on it and it will start to play the stream from mumudvb. Works weather You are using multicast or unicast.
  889.  
  890. Thanks to Ivan Cabraja for the tutorial
  891.  
  892. MythTV
  893. ~~~~~~
  894.  
  895. *Description:* MythTV is a Free Open Source software digital video recorder (DVR) project distributed under the terms of the GNU GPL.
  896.  
  897. *Website:* http://www.mythtv.org/
  898.  
  899. *Tutorial:* Configuring Mythtv and mumudvb
  900.  
  901. Mumudvb Configuration:
  902. ^^^^^^^^^^^^^^^^^^^^^^
  903.  
  904. You need to turn pat rewriting on  (i.e. rewrite_pat=1).
  905.  
  906. You can use either multicast or udp streaming to mythtv (udp streaming
  907. is achieved by using a non-multicast ip address in the  configuration
  908. file  i.e. ip=192.168.1.100). Http unicast streaming is not supported in
  909. mythtv, but RTSP should be when this is implemented in mumudvb.
  910.  
  911. The channel name needs to be in the following format "channel number" -
  912. "channel name" (e.g. name=1 - TV One )
  913.  
  914. Mythtv configuration:
  915. ^^^^^^^^^^^^^^^^^^^^^
  916.  
  917. *Single-transponder*
  918.  
  919. In mythtv-setup you need to add a new "network recorder" capture card.
  920. Enter the address of the playlist mumudvb provides in the  "M3U URL"
  921. field. This will be something like
  922. http://192.168.2.2:4242/playlist_multicast.m3u
  923.  
  924. You then create a video source as normal, and associate this with the
  925. "Network recorder" capture card via the "input connections" option.
  926.  
  927. You then need to carry out a channel scan (while you are associating the
  928. video source or via the channel editor).
  929.  
  930. The channel scan appears to hang on 0%, but just select finish after a
  931. couple of seconds. This should have loaded the channels defined in the
  932. M3U file into mythtv.
  933.  
  934. Relying on the EIT information embedded in the stream does not appear to
  935. work, so you need to load this information from an external xmltv
  936. source. You do this by going into the channel editor and adding the
  937. correct xmltv ID for each channel. Once you have done this you exit out
  938. of mythtv-setup and run something like: mythfilldatabase --file 1
  939. freeview.xml  (where in this case the the xmltv file is called
  940. freeview.xml).
  941.  
  942. To allow recording and viewing of multiple channels from the one
  943. transponder, you need to add additional (identically configured)
  944. "network recorder" capture cards. For example if you want to be able to
  945. record two channels and watch a third at the same time you need to have
  946. set up a total of three network recorder cards.
  947.  
  948. *Multiple-Transponders*
  949.  
  950. if you are streaming channels from several transponders (by using
  951. several instances of mumudvb) you have two options:
  952.  
  953. 1) The obvious thing to do is to define a different network recorder for
  954. each transponder (with the appropriate playlist defined), each
  955. transponder has to be associated with a different video source (assuming
  956. each transponder contains different channels). However, this does not
  957. seem to work well, with regular crashes when changing channels, and it
  958. also requires that you first switch between video sources to be able to
  959. change between channels on different transponders [this may be due to my
  960. lack of skill at configuring mythtv]
  961.  
  962. 2) An easier way is to generate a custom m3u file, that contains the
  963. channels of all the transponders. This also allows you to define the
  964. xmltvid of each channel as well - removing the need to do this manually
  965. in the channel editor. In this case when you set up the network
  966. recorders, you can enter a file path for the location of the m3u file,
  967. as opposed to accessing it via a web-server (e.g.
  968. file///home/nick/channels.m3u ). Once again you simply make multiple
  969. copies of the (identical) network recorder capture card if you want to
  970. record/watch multiple channels.
  971.  
  972. An example of a m3u file is as follows (in this case the first four
  973. channels defined are from one mumudvb instance, and the last two from
  974. another - of course care has to be taken in configuring the various
  975. mumudvb instances to make sure none of the channels are assigned the
  976. same port etc):
  977.  
  978.  
  979. --------------------------------------------------
  980. #EXTM3U
  981. #EXTINF:0,1 - TV1
  982. #EXTMYTHTV:xmltvid=tv1.freeviewnz.tv
  983. udp://192.168.2.101:1233
  984. #EXTINF:0,2 - TV2
  985. #EXTMYTHTV:xmltvid=tv2.freeviewnz.tv
  986. udp://192.168.2.101:1235
  987. #EXTINF:0,6 - TVNZ 6
  988. #EXTMYTHTV:xmltvid=tvnz6.freeviewnz.tv
  989. udp://192.168.2.101:1236
  990. #EXTINF:0,7 - TVNZ 7
  991. #EXTMYTHTV:xmltvid=tvnz7.freeviewnz.tv
  992. udp://192.168.2.101:1237
  993. #EXTINF:0,3 - TV3
  994. #EXTMYTHTV:xmltvid=tv3.freeviewnz.tv
  995. udp://192.168.2.101:1238
  996. #EXTINF:0,4 - c4
  997. #EXTMYTHTV:xmltvid=c4.freeviewnz.tv
  998. udp://192.168.2.101:1239
  999. --------------------------------------------------
  1000.  
  1001.  
  1002. Thanks to Nick Graham for the tutorial
clone this paste RAW Paste Data