Posts by edit4ever


    Yeah, I swapped between those options just to see what they would do, but it just changed those entries from 0 KGTVDT to KGTVDT 0. I had it setup originally how you suggested.

    I've done a clean test and the code is pulling channel numbers...so something is not quite right up on your setup.

    I would suggest deleting the zap2xml cache folder under userdata and rerunning.

    As a test of the code - you can unzip the current version in windows. Open a command prompt from that folder and run the code by entering:

    Code
    python zap2xml.py -u username -p password

    replacing username and password with your account

    This will run the code with basic options and you should quickly get an xmltv.xml file you can check. That should have the channel numbers in it.


    I think the last little issue is the channel display-name are missing the channel number in the xmltv. Would that be a change in the py script?

    That's another setting in the options page. Make sure that "Channel name first" is not turned on.

    Of course - you will have to enable the "update name" in the epg grabber tvheadend setting if you want them to update from the xmltv file.

    Otherwise - you can just change the name on the channels page in tvh and it will update on reload in kodi.


    I have only tried to integrate driver from Vitaly (VitMod) in the latest kernel, I don't have sources that I can amend. Yes, the driver doesn't work because of updates in kernel.

    Perfect - thank you for the answers. This gives me an idea of where to focus my efforts.

    Looks like I'm going to start digging into kernel building for dvb. :)

    kszaq - could you please confirm the following:

    1) Internal DVB support in your LE 7 and LE 8 builds is not functional.

    2) Work on internal DVB support is not continuing due to issues with newer kernel.

    3) If 1 & 2 are true, is it the same for KI Plus, KII Pro and Wetek boxes? (I believe these are the only boxes with internal tuners - not counting the tightly controlled Geniatech/Mygica boxes)

    Thanks!

    -- Need a little github help here for my releases.

    When I make a release - it adds the version number to the addon folder inside the zip file. This makes the addon install like it's a different version when updating. I know the release zip name should add the version number but the I think the name of the folder inside shouldn't be changed.

    How do I make it keep the folder named script.module.zap2xml when making a release?

    I'm getting ready to setup a new build environment for testing my internal ATSC tuners. Now that I've sorted out my other hardware settings under both kszaq's 7.0.2.xxx builds/fork and afl1's 7.0.2.004.x builds/fork...my question is which should I use for my base for testing?

    From what I can tell, afl1 has DVB tuners working in his builds but kszaq has not been able to get them working in his builds. If I remember correctly from previous posts, something changed in the kernel???

    If this is the case - I assume I would have to use the older base that afl1 is building from? Or since I am patching together from various builds (firmware, drivers, etc) should I exepriment from kszaq's fork??

    Or should I start from something like wrxtsy's wetek play 2 fork? The following patch contains most of the ATSC elements I will need to work in:
    li17-wetek_dvb.patch

    Thanks for the advice on where to start. I don't mind the long road of experimenting, testing, changing, repeat...but it helps if you start down the right path!

    Looks like some changes happening at zap2it.com - so I may wait a bit before releasing to see if they change the way the listings work.

    In the meantime, Schmell added some fixes, so updated release:

    v0.4.5.zip

    **** update - looks like site changes may have broken zap2it listings for now (using a popup for login window) ****

    Switch to TVguide option in the meantime while I look into a fix or while I build out the titan tv listings option (they're more supportive of this type of use)


    edit4ever: if the code in your add-ons is stable you're welcome to submit them to our repo, or if you need some webspace to publish your own repo instead of using dropbox links (and then add your repo installer to our repo) to make updates easier for users; let myself or other staff know.

    chewitt Is there a wiki for submitting the addons to your repo? I think zap2xml is at the point of being ready for a 1.0 release.


    Check open-source mn88436 driver from TBS
    add the demod'mn88436'and tuner 'mxl603'
    added support TBS6704

    Do you think it is possible to work these into an amlogic LE build? Someone posted that I need to deal with the dvb core file.

    I was thinking I could work off the 010-wetek_dvb_code.patch since the tuner/demod should be the same.

    I'm building from kszaq's and afl1's builds and trying to get the driver/firmware added in for my internal ATSC tuners.

    Thanks for your thoughts.

    afl1 before I spend too much time going down a dead end...do you think it is possible to include the additional dvb support files that are in these CVH builds? LibreELEC

    Specifically I'm looking to include the driver crazycat mentions here: LibreELEC

    I'm happy to do the work in trying to build the drivers into your source, but before I do I thought I'd see if you think it's possible.


    Edit: Here's the add-on log part where it says it is running the things needed, but no xmltv.xml file is created and the tv_grab entry isn't in tvheadend, in case that helps.

    Looking at that log - it seems that you have multiple grabbers running. That includes the zap2xml grabber as it is being run by tvheadend in your log.

    That means that you likely have the channels epg source set to the other grabber - so zap2xml will not actually grab any data and create the xmltv.xml file. Try setting a couple of channel epg sources to the zap2xml. Also, for now - you could try turning off the other grabbers, rebooting, and making sure that zap2xml is the only grabber enabled. Then check the channel epg sources are set to zap2xml, run the grabber and see what happens. If it looks like it is not working - post that log.
    [hr]


    edit4ever: Are you missing the logging.ini file in the kodi addon? I get:

    Code
    Traceback (most recent call last):
     File "/storage/.kodi/addons/tools.module.sd2xmltv/sd2xmltv.py", line 375, in <module>
       logging.config.fileConfig(u"logging.ini", disable_existing_loggers=True)
     File "/home/chewitt/LibreELEC.70-official/build.LibreELEC-WeTek_Play.arm-7.0.2/Python-2.7.11/.install_pkg/usr/lib/python2.7/logging/config.py", line 77, in fileConfig
     File "/home/chewitt/LibreELEC.70-official/build.LibreELEC-WeTek_Play.arm-7.0.2/Python-2.7.11/.install_pkg/usr/lib/python2.7/logging/config.py", line 113, in _create_formatters
     File "/home/chewitt/LibreELEC.70-official/build.LibreELEC-WeTek_Play.arm-7.0.2/Python-2.7.11/.install_pkg/usr/lib/python2.7/ConfigParser.py", line 607, in get

    when running the grabber.

    Is there more to this log? I assume that the xmltv file is not being generated for you?

    Astrilchuk has updated the version in the develop branch and changed the name of logging.ini to loggin.cfg - but this shouldn't make a difference in the version I compiled.

    I can compile the develop branch later tonight to try.


    UnboundLocalError: local variable 'cast' referenced before assignment

    The "cast" error has been fixed. I missed pushing that fix but Schmell caught it and submitted the pull request. Just redownload the zip and reinstall.

    I don't know how to keep github from adding the branch to the zip download from github and so until I can get this uploaded to the LE repo, the directory for the addon will have -master added to it. If you download my dropbox version - it has the proper folder name. Dropbox - script.module.zap2xml.zip

    Let me know if that fixes your issue.
    [hr]


    edit4ever: Are you missing the logging.ini file in the kodi addon?

    I'll have to ask atsrilchuk and run a test - I'm no longer using SD, I just posted the current build of his project. He's been making some updates, so maybe something went wrong...it worked very well for me before I got zap2xml up and running.