TVHeadend


Revision history for TVHeadend


Revision [15878]

Last edited on 2017-06-19 22:24:28 by daveraver
Additions:
From last unstable version 4.3.240 we can get channels on raspberry directly with .m3u file as debian/ubuntu method described at the end of this wiki.
Deletions:
From last unstable version 4.3.240 we can get channels on raspberry directly with .m3u file as debian/ubuntu described method.

Revision [15875]

Edited on 2017-06-19 22:17:55 by daveraver
Additions:
Tested on TVHeadend 4.3 (early versions dont map all services at once on Raspberry).
Edited on june 19th, 2017:
From last unstable version 4.3.240 we can get channels on raspberry directly with .m3u file as debian/ubuntu described method.
Deletions:
Tested on TVHeadend 4.3 (early versions dont map all services at once on Raspberry)

Revision [15866]

Edited on 2017-06-06 08:50:50 by daveraver
Additions:
==RASPBERRY PI==
==UBUNTU/DEBIAN==
Deletions:
==RASPBERRY PI way==
==UBUNTU/DEBIAN way==

Revision [15863]

Edited on 2017-06-06 08:50:14 by daveraver
Additions:
**file:///home/hts/.hts/tvheadend/services.m3u** f.i.
And then we click on create, and if input doesn't start to scan muxes, click on force scan.
Deletions:
**file:///home/hts/.hts/tvheadend** f.i. ; yes, file: followed by 3 bar
And then we click on create, and if input doesnt start to scan, click on force scan.

Revision [15860]

Edited on 2017-06-06 08:40:02 by daveraver
Additions:
Tested on TVHeadend 4.3 (early versions dont map all services at once on Raspberry)
Deletions:
Tested on TVHeadend 4.3 (early versions dont map all service at once on Raspberry)

Revision [15857]

Edited on 2017-06-06 08:30:21 by daveraver
Additions:
Tested on TVHeadend 4.3 (early versions dont map all service at once on Raspberry)

Revision [15854]

Edited on 2017-06-06 08:27:37 by daveraver
Additions:
==RASPBERRY PI way==
**file:///home/hts/.hts/tvheadend** f.i. ; yes, file: followed by 3 bar
Deletions:
==Raspberry Pi way==
**file:///home/hts/.hts/tvheadend** f.i. ; yes, file:///

Revision [15851]

Edited on 2017-06-06 08:25:33 by daveraver
Additions:
**file:///home/hts/.hts/tvheadend** f.i. ; yes, file:///
Deletions:
**file:///home/hts/.hts/tvheadend** f.i. (yes, file:/// )

Revision [15848]

Edited on 2017-06-06 08:24:44 by daveraver
Additions:
==Raspberry Pi way==
**service tvheadend stop**
**/home/hts/.hts/tvheadend/./iptv2hts.py -r -n 0 -i eth0 -c utf-8 services.m3u**
The .py file takes almost all parameters so we can do simply:
**/home/hts/.hts/tvheadend/./iptv2hts.py services.m3u**
==UBUNTU/DEBIAN way==
It's easier with these linux OS. We have to:
- Create an 'Automatic IPTV' input.
- Place 1 on max # input stream.
- Put in the first URL field the file path of .m3u this way:
**file:///home/hts/.hts/tvheadend** f.i. (yes, file:/// )

And then we click on create, and if input doesnt start to scan, click on force scan.
At the end of the scan all muxes, we make DVB input>services>map all services
And that's all. I hope you enjoy it.


Deletions:
**
service tvheadend stop**
**/etc/tvheadend/./iptv2hts.py -r -n 0 -i eth0 -c utf-8 services.m3u**

Revision [15826]

Edited on 2017-05-08 12:03:05 by daveraver
Additions:
We are deleting the channel number before channel name (-r) to generate correlative channel number (-n 0) the interface we are working with (-i eth0, for example) we indicate the m3u code (-c utf-8), and finally the *.m3u file we want to convert.
Deletions:
We are deleting the channel number before channel name (-r) necessary to generate correlative channel number (-n 0) the interface we are working with (-i eth0, for example) we indicate the m3u code (-c utf-8), and finally the *.m3u file we want to convert.

Revision [15823]

Edited on 2017-05-08 12:01:07 by daveraver
Additions:
We are deleting the channel number before channel name (-r) necessary to generate correlative channel number (-n 0) the interface we are working with (-i eth0, for example) we indicate the m3u code (-c utf-8), and finally the *.m3u file we want to convert.
Deletions:
We are deleting the number of the channel (-r) necessary to generate channel number starting with 0 (-n 0) the interface we are working with (-i eth0, for example) we indicate the m3u code (-c utf-8), and finally the *.m3u file we want to convert.

Revision [15820]

Edited on 2017-05-08 11:58:13 by daveraver
Additions:
We are deleting the number of the channel (-r) necessary to generate channel number starting with 0 (-n 0) the interface we are working with (-i eth0, for example) we indicate the m3u code (-c utf-8), and finally the *.m3u file we want to convert.
Deletions:
We are deleting the number of the channel (-r) necessary to generate channel number starting with 0 (-n 0) we indicate the m3u code (-c utf-8) the interface we are working with (-i eth0, for example), and finally the *.m3u file we want to convert.

Revision [15817]

Edited on 2017-05-08 11:54:53 by daveraver
Additions:
If we import a single channel, it doesn't care.
Deletions:
If we import a single channel it doesn't care.

Revision [15814]

Edited on 2017-05-08 11:53:33 by daveraver
Additions:
Now, when we go to configuration>dvb inputs>networks we will find the network we define inside the .py file or the default network name IPTV Movistar.
Deletions:
Now, when we goes to configuration>dvb inputs>networks we will find the network we define inside the .py file or the default network name IPTV Movistar.

Revision [15808]

Edited on 2017-05-07 20:34:30 by daveraver
Additions:
Now select the network and click to force scan. You will see how the total muxes goes to scan queue, and decrease up to 0. When all muxes are scaned with their services, we can go to services, and map all services.
Deletions:
Now select the network and click to force scan. You will see how the total muxes goes to scan queue, and decrease up to 0. When al muxes are scaned with their services, we can go to services, and map all services.

Revision [15805]

Edited on 2017-05-07 20:32:57 by daveraver
Additions:
If we import a single channel it doesn't care.
Deletions:
If we import a single channel it dont care.

Revision [15802]

Edited on 2017-05-07 20:31:59 by daveraver
Additions:
If we import a complete service with several channels, we have to edit the input network and we place 1 on maximun # input stream field.
Deletions:
If we import a complete service with serveral channels, we have to edit the input network and we place 1 on maximun # input stream field.

Revision [15799]

The oldest known version of this page was created on 2017-05-07 19:18:13 by WanWizard
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki