Posts by jeepcook

    I don't understand why the algorithm has been totally changed. Not only the mask 1010101 mod by dddd0000, but the full serviceref. This broke some functionalities like subservices. Everything has to be rewritten manually.



    As asked before, could you please definitely remove from enigma2-plugin-extensions-e2m3u2bouquet.postinst script this line:


    find . -name "enigma2-plugin-extensions-$PluginName_*.*" -type f -delete


    This has no sense and avoid to automatically install the plugin with automatic Backup Restore process.


    Thanks

    I need tvg-shift only for few channels,

    Is the logic of this tag correctly described by me above in the posts?


    But this logic can only be implemented for channels that are at least somewhat different ... in name or group ... if you have entries in the playlist that differ only in that one has "tvg-shift" tag, and the other does not. then the logic is not implemented

    Yes I read your previous mod posts. I'm ok with you, the logic would be to have the information directly in the xml with correct timestamps. I think I will contact the epg provider to see if he can do something for the different cases I detected.


    And I confirm the channels have different names between the one with "tvg-shift" and the one without. It's the case in my previous example.

    Hello,


    Is the tvg-shift m3u8 parameter supported by the plugin?

    I've tested a case:

    Code
    #EXTINF:-1 tvg-id="canal+cinemaouest" tvg-shift="-1" tvg-logo="http://<picon_url>" group-title="=== Canal+ AF ===",C+ CINEMA CENTRE AF
    http://<stream_url>
    #EXTINF:-1 tvg-id="canal+cinemaouest" tvg-logo="http://<picon_url>" group-title="=== Canal+ AF ===",C+ CINEMA OUEST AF
    http://<stream_url>

    I obtain the same epg for these 2 channels, no shift for the first one. Perhaps a limitation of epgimport, no?

    If you noticed, all the plugins I made work everywhere... and the code in them is ABSOLUTELY THE SAME.... there is no separate code for OA, OE, DreamOS, etc.

    Yes but they are separate from the oe-a branch dev, not in feeds, because you don't want and you want to keep them closed-sources. And OpenPli, DreamOs have their own dev branch. I can't ask to a oe-a dev to make it's dev for other images, the answer will be that he can't commit to these images..

    Who and why forbids me or anyone else NOT to use a similar built-in functionality in any image, but to use a plugin with extended functionality? Do you have such an opportunity to select from your favorites by channel name, regardless of whether they have EPG or not ... in those images where this is implemented?

    Subservices functionality. But for now up to date only in OpenATV images. For information, I've asked years ago to migrate it from images devs to oe-a core. But this has not been taken in account so each oe-a image has its own dev for subservices. I can do nothing anymore for that.

    There would be a desire ... everything can be implemented ... if it corresponds to the ideology and functionality of the plugin

    This has not a place in e2m3u2b which is there to create bouquets and import corresponding epg (the name is clear m3u2b), not to navigate into lists or epg. HistoryZap already exists in e2. so there's no reason to override it, or just a function to enable/disable this. But it has nothing to do with the plugin.

    Previous messages are very too long... but I think there is a total misunderstood. I don't want a new dev, it already exists but currently there are some devs on it to work perfectly with all cases.


    My initial message was just to know if the gstplayer parameters could be removed from the .tv file. The answer was no, never, so I will do with that. I always found a solution, and the subservices current devs will work on my configuration even if I have to do a e2m3u2b plugin post script.

    The solution is still on test and I'm the tester.


    So for my part it's closed. I'm waiting nothing from e2m3u2b plugin dev.


    Thanks.

    Exactly! That's what I explained, and the screenshot show this.

    You're still damn surly... It's difficult to speak with you. You know I help you with bad, good ideas and open issues to optimize your plugin.

    Anyway it does not matter, this discussion have the only merit of waking up this thread :rolling on the floor laughing: