M3UIPTV plugin for IPTV managment

There are 490 replies in this Thread which was already clicked 118,293 times. The last Post () by DimitarCC.

    • Official Post
    Quote from DimitarCC
    Quote from tbe
    Quote from DimitarCC

    Well you can make only one entry. But you can not have sub bouquets. Only Markers(separators) that will separate groups.

    Sent you another DM as not really understanding your response, so feel free to tell me to go away if I am becoming a nuisance :smiling face:

    I have replied...But that is nost supported by most of the distros out there. I think only ATV and derivatives supports subbouquets.

    Pretty sure ViX also supports sub bouquets unless recently removed.

    • Official Post

    The reason people like sub-bouquets is that it does not clutter the bouquet list. It is very old code in PLi. It should have been included when Andy forked from PLI. ATV (formerly AAF) forked from ViX.


    I am sure somebody posted a screenshot of ViX with sub-bouquets using kiddac's plugin within last 18 months. Maybe you can double check code yourself.

    after installing the M3UIPTV plugin, I have a problem with displaying youtube links in this form in the latest openatv 7.5.1

    #SERVICE 4097:0:1:0:0:0:0:0:0:0:YT-DLP%3a//https%3a//www.youtube.com/@VivaTheKeys/live:Florida Keys Aquarium, USA (YT)

    there is no image before installation, there was an image, only uninstalling helps and the image comes back

    Quote from rappek

    after installing the M3UIPTV plugin, I have a problem with displaying youtube links in this form in the latest openatv 7.5.1

    #SERVICE 4097:0:1:0:0:0:0:0:0:0:YT-DLP%3a//https%3a//www.youtube.com/@VivaTheKeys/live:Florida Keys Aquarium, USA (YT)

    there is no image before installation, there was an image, only uninstalling helps and the image comes back

    OK i have never tried youtube links. Are you using a plugin for that? If yes which is it?

    Since some users complain that using the plugin causes crashes with some skins, I want to explain what the problem actually is.


    Enigma2 was not originally designed for streaming (IPTV). However, IPTV is widely used nowadays (even more than satellites). That's why some extensions/plugins had to be made for Enigma2 to make IPTV work. Most of the plugins created are designed with their own screens, dashboards, EPG importers, so they are a completely separate environment that runs on top of the Enigma2 UI. However, this leads to the need for skin creators to create additional screens, and using them in most cases makes it feel like you are not in Enigma2 at all.


    My plugin works differently, as it integrates deeply into enigma2 and works with most of the standard screens and features. However, the lack of its own info panel prevented it from working smoothly, as Enigma2 was not designed to handle stream connection issues smoothly. So the plugin had to use some tricks to make it work like a normal DVB receiver.

    So the info panel had to be forced to reload (to show the EPG and channel name in the info panel) before connecting to the stream (otherwise you get huge delays on slow connections when switching IPTV channels).

    This change requires converters and renderers to support eServiceReference, not just iPlayableServicePtr (before the plugin was made, converters/renderers only used iPlayableServicePtr).

    So converters/renderers had to add eServiceReference support, or at least add sanity-check (before no one bothered to add sanity-check, because they never thought these shortcomings needed to be fixed).

    So this support was added to OpenViX, OpenPLi, OpenBH and all based on them. However, it was added to the pythons included in the images. Of course, all the third-party converters/renderers were not updated, and so they now hang.


    In general, good practice requires sanity checks to be done wherever a crash could potentially occur. It's just that the old converters/renderers were not designed to prevent potential crashes.


    So all this means is that the plugin cannot fix these crashes, since they are outside the enigma2 standards in third-party Python files.


    So currently the user has the following options:


    1. Convince the module developers to fix their modules and add sanity checks to them. Keep in mind that skin developers usually copy converters/renderers and rename and modify them. So the fixes have to be done in each skin and skin module. Since it is not centralized.

    2. Use skins that don't use external Python modules

    3. Use a different IPTV plugin (if they are ok with this and all the other glitches that enigma2 has)

    So in the latest source there are more Stalker fixes. Including EPG import support for Stalker...

    It will be good if someone can test this with portal that do really have EPG since my test portals have no or very limited epg.

    Quote from DimitarCC

    So in the latest source there are more Stalker fixes. Including EPG import support for Stalker...

    It will be good if someone can test this with portal that do really have EPG since my test portals have no or very limited epg.

    Will keep testing but so far although it creates the EPG Import entry it does not pull any EPG info. Only tested 3 so will keep trying. Also, there is often an issue with setting up blacklists and getting incorrect bouquets on Stalker. I will try and document what I see and do to fix and post later.

Your resource for Enigma2 IPTV plugins

Discover the best Enigma2 IPTV plugins. Access downloads and dedicated support for integrating live TV streams and video-on-demand services. Find downloads, setup guides, and community support for the latest streaming players and playlist managers.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login