i
Most likely you changed the interface language of the image and did not reboot ... After reboot everything should work.
im using only eng. language and dont do change it.
but EPG are in foreing language (CS) could be this couse reboot?
i
Most likely you changed the interface language of the image and did not reboot ... After reboot everything should work.
im using only eng. language and dont do change it.
but EPG are in foreing language (CS) could be this couse reboot?
but EPG are in foreing language (CS)
Nothing related
Testing on openatv6.4
OpenATV 6.4 is good for testing ))) But have you thought about having other images like VTI... or any of the OE2.5/2.6 (DeamOS) images? Why do you think skinpatcher.py was added to the code? Are you sure that the changes you suggested in the xml skins will universally work on all images on which this plugin works after my alteration?
Your ExandableSelectionList.py needs some work.
I'm not sure. Believe me, everything is written there exactly as intended, so that it works EVERYWHERE, and not just on OA-based images (OpenAlliance: OpenATV, OpenPli, OpenBH e.t.c.)
the settings file address is incorrect.
SETTINGS_FILE = '/etc/epgimport/epgimport.conf'
should be
SETTINGS_FILE = '/etc/enigma2/epgimport.conf'
Why should? I deliberately changed the storage path to /etc/epgimport/ ... - https://en.wikipedia.org/wiki/…entional_directory_layout
Alternatively, I can replace it with /usr/epgimport/ , which, in my opinion, will also be more correct in terms of file organization for Linux-based systems
EPGConfig.py
subprocess.call for less than python3.5subprocess.run for python3.5+
Yes, it is ... this is deprecated in version 3.5+ ... but ... it works in 3.8 and in 3.9 and in 3.10 ))) If this makes it easier for you, I can change it, taking into account this remark ... But the code will work exactly the same as it works now
root@vuultimo4k:~# python
Python 3.10.4 (main, Mar 23 2022, 20:25:24) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import subprocess
>>> subprocess.call(["ls", "-s",])
total 4
4 logs
0
>>>
>>> subprocess.run(["ls", "-s",])
total 4
4 logs
CompletedProcess(args=['ls', '-s'], returncode=0)
>>>
Display More
Can be rewritten via enigma.eConsoleAppContainer or Components.Console.Console ))) But the result will be the same
Doesn't matter mate, keep plugging along. I will be offering no more testing.
Doesn't matter mate, keep plugging along. I will be offering no more testing.
Tests are a good and very necessary thing. But tests should be with an understanding of the essence. The differences in the appearance of the "windows" indicated by you are not a mistake. This is a compromise for compatibility with all images on which this plugin works. Otherwise, you will have to "cut" skins for each image. Why this is done - I wrote to you in the posts above. Please make the changes you suggested and check how it will work on VTI or DreamOS ;) - and it will be a good test! Moreover, the "beautifulness" of the GUI is secondary. The main emphasis was placed on code optimization ... to work faster and "omnivorously" (any image, any Py version with a same code)... in comparison with the original
Well, with regard to your remark about the run/call in the subprocess method - I gave you a good example on Python 3.10. Do you see a difference there as a result of the execution?
p.s. Why did you delete your posts? You have done some work and tests .. And, it seems to me, that our discussion may be of interest to other users
Many thanks for this plugin. It works really well. I have a custom.channels.xml that I used to use with the original epg import , but doesn’t seem to work with this one. Is there something I need to do to use this file or does this version not allow a custom channel file? Thanks
Is there something I need to do to use this file or does this version not allow a custom channel file?
1) There are no restrictions on the use of custom files. Moreover, if this file works for you with the original version, then it will and should work with this one.
2) If something does not work - THERE IS A LOG ... well, at least you can show the contents of your custom file
Log files attached for each version. Notice the original epg import log mentions about parsing the custom.channels.xml file (ignore the parsing failure error - it does work). Doesn’t mention the custom file or work on your modded version. I can’t upload the custom channels file as it contains personal iptv server details etc for each line.
Doesn’t mention the custom file or work on your modded version.
I understood what it was about ... I "threw out" this piece of code related to castom.channels.xml from the mod as unnecessary .... If you need additional filtering of certain channels, then use their addition via "Menu" - "Ignore services list" ... Unlike the original - this "feature" works in mod
An example of one of my lines (personal details redacted)..
<?xml version="1.0" encoding="UTF-8"?>
<channels>
<channel id="SkySpF1.uk">4097:0:1:844:63:27:FFFF0000:0:0:http%3a//######/######/#######/4796</channel><!-- SKY SPORTS F1 -->
</channels>
An example of one of my lines (personal details redacted)..
I have modified the previous post. Read it again
0:http%3a//######/######/#######/4796</c
Why do you need this plugin for IPTV EPG events? There is also a ready-made solution for generating IPTV bouquets and linking EPG - RE: [Plugin] E2m3u2bouquet
I was playing around with that earlier. Unfortunately my providers epg is not great so using epg import worked better, which is why I had to link my channels to the source names in the file
4097:0:1:844:63:27
And I would strongly recommend you to use serviceapp for IPTV ... and install exteplayer3 and gstplayer for stable and trouble-free viewing of IPTV broadcasts...
The world of IPTV is fairly new to me. I’m still exploring…
which is why I had to link my channels to the source names in the file
Just create your ****_cahnnels.xml and add it to the sources.xml you need or create your own sources.xml ... Get exactly the same functionality as with custom.channels.xml
That makes sense. Thankyou
Greetings for all
The plugin was working with me without any problem on DM920 and deb files until VER 1.6 ( work without any pb )
Starting new versions, the dream start to freeze when I press yellow to start import, the only way with the receive is rebooting it.
I try to trace the reason of the error, I found that the pb with EPGImport.py ( work good until end of ver 1.6 ) start 1.7 and new ver make the receiver freeze.
please find attached working ver 1.6 and the last ver not working.
Br
please find attached working ver 1.6 and the last ver not working.
I don't need my sources, and even more so those that are NOT responsible for importing events into the SQL database in any way ... For everything that does not work, freezes, e.t.c - there is a log.
Don’t have an account yet? Register yourself now and be a part of our community!