Tempest EPG Generator

[kvanc]

Oops, I tried to add xml and log.txt but seems like not allowed so;

Any attachments need to be zipped.

Thanks for the golden rule. I think thats why first I shall read forum rules 

[mvallevand]

I dropped the list to 1 day from 7 since 400 seconds is basically going to be too long and now I get this error. Even with 1 day it would be a rare case to use this slow provider.

Note I get with whether or not index-only is off or on.

Code:

[13-02-2022 15:29:52] (18/33) Site: [ENC][EX]tvpassport.com[CA]_0
[13-02-2022 15:29:52] Channel id: 6
[13-02-2022 15:29:52] Xmltv id: [Broadcast - Ottawa, ON] Global (CIII) Ontario (2)
[      Warning      ]
[13-02-2022 15:30:22] No show grabbed in 30.14 seconds
[       Error       ] Request Error(url1): Connection timed out after 5005 milliseconds
[       Error       ] Request Error(url1): Connection timed out after 10012 milliseconds
[                   ]

Martin

[kvanc]

I dropped the list to 1 day from 7 since 400 seconds is basically going to be too long and now I get this error.  Even with 1 day it would be a rare case to use this slow provider.

Note I get with whether or not index-only is off or on.

Code:

[13-02-2022 15:29:52] (18/33) Site: [ENC][EX]tvpassport.com[CA]_0
[13-02-2022 15:29:52] Channel id: 6
[13-02-2022 15:29:52] Xmltv id: [Broadcast - Ottawa, ON] Global (CIII) Ontario (2)
[      Warning      ]
[13-02-2022 15:30:22] No show grabbed in 30.14 seconds
[       Error       ] Request Error(url1): Connection timed out after 5005 milliseconds
[       Error       ] Request Error(url1): Connection timed out after 10012 milliseconds
[                   ]

Martin

Hi Martin. Connection times out means server is not responding your request on given times or your request is not reaching there on given times. Even I am not receiving such error from that distance to Canada. Most probably still you have some dns problem with tvpassport. You enabled the main adress but keep in mind that data communication is in subdomain level. Most probably a vpn or proxy will solve it. There are some free proxies. You can test in config file/proxy setting in 

protocol://ip:port

Format such as https://xxx.xxx.xx.xx:xxxx

[mvallevand]

Yes and that is why you have received comments not to obfusgating the code. However sniffing the network I do so tls errors which could be caused by tvpassport.com having two dns names.

Non-authoritative answer:
Name: www.tvpassport.com
Address: 34.233.109.3
Name: www.tvpassport.com
Address: 52.205.198.6

Anyway it does work and it is a powerful tool, but not convinced you will find many users here. Thanks for your responsive answers.

Martin

[kvanc]

Yes and that is why you have received comments not to obfusgating the code.  However sniffing the network I do so tls errors which could be caused by tvpassport.com having two dns names.

Non-authoritative answer:
Name:  www.tvpassport.com
Address: 34.233.109.3
Name:  www.tvpassport.com
Address: 52.205.198.6

Anyway it does work and it is a powerful tool, but not convinced you will find many users here.  Thanks for your responsive answers.

Martin

Thanks for your cooperation Martin. With your support, I have collected many information and have several fixes now for upcoming v1.3.2 including your firefox issue.

This is a free-mium tool. It is free to use and always will be like this unlike its old, low level and paid rivals around but trust me unchained version Could be much more dangerous than you can imagine. I know nextpvr has several built in tools but I am just trying to show interested people what I have 

[kvanc]

Hi Martin. Hope everything is ok since last talk. I know you alittle disagree with me about this subject but I just wanted to notify you, Tempest has got approval from Schedules Direct for Json API and siteconfig which you can grab upto 20days & line-up manager which you can do several operations such as add/delete lineups to your account, query/list lineups based on country/postal codes, preview available channels (even for non-selected lineups) and list your selected line-ups; is available in my github repo with pictured how-to-use instructions

https://github.com/K-vanc/Tempest-EPG-Generator

So people who want to use their SD accounts on other devices, may be interested

[sub]

Hi Martin. Hope everything is ok since last talk. I know you alittle disagree with me about this subject but I just wanted to notify you, Tempest has got approval from Schedules Direct for Json API and siteconfig which you can grab upto 20days & line-up manager which you can do several operations such as add/delete lineups to your account, query/list lineups based on country/postal codes, preview available channels (even for non-selected lineups) and list your selected line-ups; is available in my github repo with pictured how-to-use instructions

https://github.com/K-vanc/Tempest-EPG-Generator

So people who want to use their SD accounts on other devices, may be interested

Honestly, NextPVR users would be better off using NextPVR's own built in Schedules Direct support, rather than having this. The built in support is much more sophisticated than what the user will get from using an xmltv file.

[kvanc]

Hi sub;

I agree with you since it is always easier and better to use built-in option. Thats why I wrote it may be useful for people who want to use their SD account on their non-NextPVR devices

[mvallevand]

I don't disagree with XMLTV use at all, my issue is users expecting support for using these XMLTV generators when there is often little or no user-to-user or developer support available to them. My experience with Tempest is it will definitely require both time and support but as long as you are here to guide them that is excellent.

In the case of SD JSON, there is a very small group of NextPVR users who subscribe to SD but still would customize their XMLTV files, and feel it is worth losing integrated meta art downloading, faster updates etc. If your application makes it easier for them great.

Martin

[kvanc]

I agree with you as well, about support issue and trying to help my very small but slowly increasing group of users as much as I can. It is also good for me that I am having chance of finding unnoticed problems such as your mentioned Firefox problem. I was totally unaware about it till you mentioned.

SD Json is not the most user friendly  Api especially if you are not using a generator which directly coded to work with it but after couple of trys, I have found a fast and memory friendly way of grabbing. I attached the photo of test result for 20days, 172 random channels from USA,CAN,UK and able to Generate some +70mb file with +75K shows in 21minutes.