Posts by edit4ever

Thanks for testing! Let me know if you have any other issues and in the meantime, I will add those lines to the code.

Hopefuly you can grab logs next time you have an error. Thanks!

You can add as many lineups/channels as you need in schedules direct. I created the Kodi addon interface so people didn't have to use the SSH manual setup to do all of that.

You should have no problem running LE on the Pi 3 with the backend and frontend of TVH addons enabled. That being said, make sure you have a fast sd card as that impacts the cache performace. Depending on what you want to use for recording, you'll want to make sure that has a fast transfer rate as well. That way if you're recording and playing back at the same time, you don't have a buffering issue.

I didn't know a thing about python when I started piecing together my addons (zap2xml and sd4tvh) - I just built on others work and looked up whatever I needed to. SD4TVH isn't really a clean build as it is pieced together from two other projects...but it works and makes the schedules direct setup a lot easier for people. Maybe someday I'll have time to build a cleaner version from scratch (or someone else can) but for now - it hopefully get a lot more people to cut the cord!

If you have any trouble running the addon - let me know!

No problem running on different box. I run my tvheadend on a Pi...that system also has my SD addon. That Pi is running LE, so I could also use it as a front end if I want - but I don't. I let it run as the backend and then I have my phones, laptop and Fire TV running Kodi that connect to that. Running LE on the Pi made setup a lot easier.

You could setup a Pi with Linux or Raspian install and manuall setup tvh and a different type of SD grabber...I just find the LE makes it all so simple!

Did adding swap space solve the issue?

One way would be to limit the number of days of data that is downloaded. The next way is to limit the number of channels being downloaded, using the channel filter part. First we should determine if you can get a base amount of data in. Why not start with a few channels on the dish lineup and see if it will download a full two weeks of data.

- did you get a different error from a system log that you can share?

spydah - let's start by using only the Dish network lineup.

Please remove the other two lineups. Then delete the filter.cfg file from your addon_data/script.module.sd4tvh folder. Then you can rerun the sd4tvh addon and see if you can set the channels for the Dish lineup.

Let me know if that works - and we'll go from there. Thanks!

It has to do with escaped vs unescaped characters. I should have time in the next day or so to investigate. This version was pieced together from various work from other people so I just need to go back and see how the data is being processed. Since I'm not currently using Schedules Direct - when I think I have a fix I'll post the update and maybe you can test it. Thanks!

This should be a setting in tvheadend. Check to make sure that you have unchecked "update channel name" on the CONFIGURATION > CHANNEL/EPG > EPG GRABBER tab. Then go to the CONFIGURATION > CHANNEL/EPG > CHANNELS tab and change the name of the channel there. You don't want to change the name in the filter.cfg as that always references the data that is on the downloaded guide. You just want to change what is displayed in the kodi interface - which is read from the tvheadend epg.

Hope that helps - and thanks for the feedback!

Quote from leading_edjge

I am now enjoying having both ATSC tuners working.

What OS install did you use? It doesn't seem like you're running an LE build.

It's an issue with the ñ character -- likely it's an issue with all non-ascii 128 charcters. I had a similar issue with my zap2xml grabber...now I just have to go back and figure out what I did to make it work!

Also - let's move the conversation on the sd4tvh grabber to its thread: thread-3715-post-40315.html#pid40315

Quote from spydah

WOW, sd4tvh is SO much better!!! But, I'm still running into the encoding issue with it as well. None of my 3 lineups work. I can add them and remove them through the kodi interface, but using the sd4tvh.py and listing the lineups or trying to generate the xmltv.xml file throw the error. Maybe something with my LE version? Happy to move this issue over to a sd4tvh specific thread if that makes sense.

Lineups:
1. Claro TV Brasil/Via Embratel - Digital (Brazil)
2. BSkyB - United Kingdom (United Kingdom)
3. DISH Network - Satellite (USA)

Example Error

[code=php]
Traceback (most recent call last):
File "sd4tvh.py", line 407, in <module>
main()
File "sd4tvh.py", line 399, in main
app.manage()
File "sd4tvh.py", line 68, in manage
self._sd.manage()
File "/storage/.kodi/addons/script.module.sd4tvh/libschedulesdirect/schedulesdirect.py", line 310, in manage
self._list_lineup_channels()
File "/storage/.kodi/addons/script.module.sd4tvh/libschedulesdirect/schedulesdirect.py", line 398, in _list_lineup_channels
print(u"{0}\t{1.callsign} '{1.name}'".format(channel.channel, channel.station))
UnicodeEncodeError: 'ascii' codec can't encode character u'\xf1' in position 28: ordinal not in range(128)
[/php]

Display More

It's an issue with the ñ character -- likely it's an issue with all non-ascii 128 charcters. I had a similar issue with my zap2xml grabber...now I just have to go back and figure out what I did to make it work!

There must be a strange character in your lineup name. I probably need to look at how the encoding is done as that shouldn't cause a problem. I haven't worked on the schedules direct addon in awhile - you may want to check out my last version which included the ability to set lineups and channel filters: thread-3715-post-27764.html#pid27764

If you want to test that version - you can let me know if you have the same error. If your system is working for now - you may not want to be a guinea pig!

The ATV1950A turned out to not be a viable product. Through testing (mine and about 40 other locations) it was determined that the components used in this model were contributing to unreliable signal tuning. Thus, Geniatech has reworked the components into the ATV1960 model. I have not tested one of those unites yet to see if it has better performance.

For now - I am not aware of a unit with working internal dual ATSC tuners. If you want two ATSC tuners, you can get a model like the wetek play 2 and then add an external usb tuner. Or get any 905 based media box and add two external usb tuners.

I am trying to get the Hauppauge dual ATSC usb (955D) working on LE builds - but have not had luck yet. Drivers for that model were written for the DVB version and included in Linux 4.9 - but the ATSC code seems to have errors. And as far as LE goes - we're nowhere near using the 4.9 kernel for the 905 builds - so the drivers would have to be backported (which crazycat has worked on).

I'm hopeful that the Geniatech ATV1960 might be a viable solution - but until I can see a working version with a very updated DTV app - I'm not convinced. Products like the HDhomerun, Tablo and Channelmaster DVR+ are the only real working multi-tuner ATSC DVRs that I am aware of.

Quote from cabbresson

Do you know If I install from zip will it still update from your repo in the future?

I haven't gotten around to setting up my own repo or submitting the addon to LE to add to their repo. So updates are manual for now. This whole coding/addon/github thing is new to me - and just a hobby - so I work on it when I can.

This is the same as the version you're running since you copied the zap2xml.py file over manually. Someone just asked for the version that could be installed from the addon menu. You don't have a need to update. Actually - I prefer if you don't update, in case someone finds an issue with the zipped file. I'm travelling and every now and then I mess up pulling in the updated files! This way your version acts as my control. Thanks!

Someone asked for the zipped addon....I'm travelling - so I haven't been able to run any tests...but since the feedback from my code fixes seems to be fine - you can try this:

script.module.zap2xml-0.6.5.zip

Please let me know if you have issues. Thanks!

Quote from Mick84

I have attached a clear picture of Acemax M8S+ in the my previos post.

Hope, to see Libreelec working on my M8S+ :s :s

Can you confirm that the wifi chip on your board says AP6330? I can't read it due to the reflection on the photo.

I'm running LibreELEC-S802.M8SPlus.arm-7.0-devel-20160923081027-r23240-gafd8f8c.tar build and all works fine.

My board looks like yours. I assume you started from working Acemax firmware?

BTW - before that build, I was running a slightly customized version of Drieschel's original builds - I can't remember if that's when I got the power working from the remote. If you want to try that version, it's here: LibreELEC-S802.M8.arm-7.0.2-2-devel.tar

Since both of these are .tar upgrade files - you will likely need to start from Drieschel's base version - or if you're already LE it should upgrade just fine.
[hr]
One more thing - if you don't have Android firmware running with a working remote - it likely means you have the wrong firmware. That will throw off anything you do in LE. You should be able to run this version: Download latest Android Lollipop 5.1.1 stock firmware for M8S+ TV Box - China Gadgets Reviews as on update to get working again.

There is also a version on the Acemax site - but you need to use the usb burning tool and a male to male usb cable to flash your box. MEGA

Once you have a working remote (and on/off/restart) with the android firmware - you can move to LE.

Thanks again for the update. This is all totally a hobby. I didn't know the first thing about python and other code until I started playing with this and modifying Kodi skins.

As for the different logs - I'm not sure how or why that happens. This project was orginally done by fasteddycurrent - which you can see here: GitHub - FastEddyCurrent/zap2xml: zap2xml in Python 2.7 for use on the RaspberryPI - it was he who converted the the original zap2xml perl script into python.

I basically took what he did and created a kodi addon and then started adding features I wanted to see. And now here we are. I'm just a former tv marketing exec who likes to play. I'm driven by the goal of wanting cheaper/better dvr service and this year I finally cut the cord. If i get around to it, I'll have to look at how the log system is structured.

BTW - the "Skipped:" entry means the code fix worked. That indicates that there was an empty or missing details file that would have previously crashed the grabber. Glad to see it completed!