OK so just need to add in start and end margins to settings and do my magic trick of automatically working out server offset.
Xstreamity is lot more complex code than Jedi. So it will take a few days to focus and work on that. Been a while since I looked at this Jedi code. EEK!
Add in the option of adding an alias name to playlists.txt lines (that was requested).
And then I can forget about Jedi again, as it just works... no need to break it or fix it any further. ;)
Posts by KiddaC
-
-
-
I rarely use jedi nowadays. (I even forgot how to view the catchup :) ). So I don't want to start changing things and upsetting people that use it often.
So feel free to speak up if you have a preference.
But I think if the day list remains (less faff for me if it stays), it is probably best to reverse the order on that to. -
For those who use catchup in jedi... should i just make it very similar to xstreamity.
Should I get rid of the day choice.
6bccef2875.png
Should i then reverse the list like xstreamity. So latest is at top
b24aac4b85.png -
Catchup in jedi is old and a pain. It was written a long time before the newer xstreamity one. Xstreamity is much simpler for catchup.
One rainy day. I will amend Jedi to function the same as XStreamity. But for now, there is no catchup start and end margins.
-
all the epgshare01 sources were updated in the last update.
your crash log mentions this
/etc/enigma2/jediepgxtream/sources/RIPEER-INDIA.xml
that isn't one of my files. So this is user error. -
Converting a modern dreambox skin to other builds is not straight forward and not a quick job.
1) Not all screens names are the same
2) Some of the skin elements differ.
3) This skin has been designed with vector SVG graphics. SVGs cannot be used on any other enigma2 box (yet). All the graphics would have to be converted to PNGs. And all references changed.
4) The author of this skin might not want it converting to other images. You would have to seek the authors permission ideally. Dreambox crew are a closed knit community. They don't share their wares. But its users want to use everyone elses plugins.
5) It has 5500 lines of code that would need checking and converting.
6) is it do-able... yes you can get something close but not exact, is it worth another skinners effort... probably not. -
main settings ... group bouquets into its own folder. yes/no
I can see how you missed it as its not that obvious :redface:
-
plenty of plugins to aid in the watching of IPTV.
Here are 3 of mine.
Jedimakerxtream - iptv bouquet creator - watch iptv channels like normal tv channels
Jedi Maker Xtream (IPTV Bouquet Creator) - Main thread
JediEPGxstream - Assign 3rd party EPG channels to your IPTV created bouquets. Perfect for replacing your russian language one you mention. You need to use JediMaker above to use this plugin though.
Jedi EPG Xtream
Xstreamity - IPTV player - wont help with replacing your Russian language EPG though.X-Streamity - Xtream Codes IPTV Player
and plenty other iptv plugins available on this forum.
Enigma2 IPTV Plugins -
the response they got was this...
Firstly to use https urls you need to use the epgimporter hack that is on the first post of jedi.
Universal epgimport.py file attached (python 3 / python 2.7 / dreamboxes) to allow https urls to be used. Copy over to /usr/lib/enigma2/python/Plugins/Extensions/EPGImport
Back up your original epgimport.pyo in case you need to reload it.
Secondly, if your domain, username and password are still the same, the saved data in my plugin may need deleting.
So delete all jedi created bouquets via the plugin and create them all again.
Are you sure you have no port number. https usually do. If no port is provided my plugin will default it to 80.
you can check your user info which will show you your port numbers, by changing your get.php in your url to player_api.php
i.e
https://domain.xyz:port/player_api.php?username=blah&password=blah
or
https://domain.xyz/player_api.php?username=blah&password=blah
type that in a browser window and see what it says.
-
...and coincidentally someone has just asked the exact same question in private message. About their provider changing to https and no port.
Whether it is the same provider as yours I do not know.
-
Jedi maker can use either various formats of iptv... xtream codes urls, old and new panels, local m3u8 playlists, external m3u8 playlists.
Xstreamity is strictly for xtream codes urls only (the newer xtream code panels are called XUI ONE panels - they can also be used in my plugins)
-
The plugin is designed to be used hand in hand with other iptv bouquet makers.
I.e my own jedimakerxtream and I assume it works with suls bouquet maker.
Once you have created iptv bouquets via one of those plugins.
You then open up this plugin which will read those bouquets and allow you to re-assign any missing epgs from alternative epg list provided.That is all this plugin does. Nothing else.
-
nizwa that error shouldn't happen.
What are you using to create IPTV bouquets?
Have you got any IPTV bouquets?Have you got an empty bouquet?
Try this file and see if it eliminates your crash
/usr/lib/enigma2/python/Plugins/Extensions/JediEPGXtream/
-
The plugin doesn't require fuzzywuzzy to run. Although it is better if you have that package as it finds better channel matches.
There is fallback code for images that don't have fuzzywuzzy package. ie. Dreamboxes.
Does the plugin install ok, but you just get this dependancies message every time it runs.
If the IPK has installed OK, you can just remove the dependancies check. Then it wont prompt you every time it runs.
in
/usr/lib/enigma2/python/Plugins/Extensions/JediEPGXtream/main.py
look for this line (around line 116)
self.onFirstExecBegin.append(self.check_dependencies)
and replace it with
self.onFirstExecBegin.append(self.start) -
What image are you having issues with for fuzzywuzzy?
ignore me... just seen it says openpli 8 all over that log :) -
:shocking:
-
Github (feeds) was updated with the latest on 11th April.
And yes I just forgot to change the version number in the about us page. It is only text.
I am not to familiar with the version numbers currently in feeds. As I am aware Captain for openatv was trying to recommend version numbers be changed for my jediEPGXtream plugin. Hopefully they haven't been faffing with Jedi or Xstreamity to, as that when we end up with version conflicts
If your OCD is getting the better of you, here is the amended about.py file\usr\lib\enigma2\python\Plugins\Extensions\JediMakerXtream\about.py
-
in which case you need to amend your keymap.xml
or the main.py file to add in your reference.
Code
Display Moreself["actions"] = ActionMap(["SetupActions", "DirectionActions", "WizardActions", "ColorActions", "MenuActions", "MoviePlayerActions"], { "ok": self.ok, "back": self.exit, "cancel": self.exit, "red": self.exit, "green": self.keygreen, "yellow": self.keyyellow, "blue": self.keyblue, "left": self.goLeft, "right": self.goRight, "up": self.goUp, "down": self.goDown, "channelUp": self.pageUp, "channelDown": self.pageDown, "0": self.reset, "2": self.prevLetter, "8": self.nextLetter }, -1)
The actionmap list at the top is the sections it is looking for in the keymap.xml file
In oe-alliance keymap.xml we would have something like this
a948782982c3f14707c999.png
So in any of the listed sections
["SetupActions", "DirectionActions", "WizardActions", "ColorActions", "MenuActions", "MoviePlayerActions"]
add in<key id="KEY_CHANNELUP" mapto="channelUp" flags="m" />
<key id="KEY_CHANNELDOWN" mapto="channelDown" flags="m" />
or alternatively edit the main.py and add in your button namesCode
Display Moreself["actions"] = ActionMap(["SetupActions", "DirectionActions", "WizardActions", "ColorActions", "MenuActions", "MoviePlayerActions"], { "ok": self.ok, "back": self.exit, ... ... "channelUp": self.pageUp, "channelDown": self.pageDown, "nextBouquet": self.pageUp, "prevBouquet": self.pageDown, }, -1) -
and what does bouquet up and down do.
