Feature #3153
IPTV mux creation from service scan
0%
Description
Perexg I know you basically see sending data back and forth only as the second best choice and do favour a plugin solution. As it is always a good idea to have a native interface, this is the right way to go. On the other hand a streaming interface is not bound to any specific software like e.g. tvheadend, mumudvb or whatever, so it also has it's pros.
With the recent enhancements to raw service partial ts streaming, the later is already useable with the small drawback that there is a lot of manual configuration involved, as for every service there needs to be a seperate iptv mux. I know that dynamic mux URLs are not fitting in the concept of tvh, so I would suggest a different approache - still with a seperate iptv mux for every service - like an option on the source to generate an iptv mux automatically for every service.
Since the "streming plugin" needs some way to request the right service from tvh, the generated mux should include the uuid of the service in the URL, so if an option to auto generate muxes while scanning would make it in to tvh, this would need on the one hand the IPTV network it should creates muxes for and on the other hand an URL with a place holder for the uuid.
As always, keep up the good work
History
Updated by Jaroslav Kysela about 9 years ago
Basically, I don't like to put any special logic such this to the code. I just commited 'IPTV automatic network' (m3u at the momment) to git master, so you may just gather the services you need using HTTP API calls and create this m3u file. TVH will manage muxes in the automatic network itself. I plan to join this network to the bouquets, so the channels might be created automatically, too.
Updated by B C about 9 years ago
oh the m3u import is working fully automatically, so no need anymore for this feature :-)
just one sample line of an #EXTINF entry would be nice, it doesn't import the URL 4 me
Updated by B C about 9 years ago
and just another idea, could tvh execute a script with the mux uuid appended as parameter each time it has processed a whole mux scan, be it because it was just scanned or a service on it was tuned? That way we could automatically recreate the m3u file and start rescanning it, or could log changes to some database etc.....
Updated by Jaroslav Kysela about 9 years ago
You can write a HTTP comet client. TVH notifies the GUI about changes already. Just create a new box, use special GET /comet/poll with the boxid and voalla - you can watch for changes for all classes.
Updated by Jaroslav Kysela almost 9 years ago
- Status changed from New to Fixed
I'm closing this. The user app can already grab all information to work with.