Yahoo Go TV to XMLTV (via API)

[-Oz-]

got your PM I'll be replying soon.

Let me know about the IDs because I'm kinda sick of this channel issue too. They're not even in order because mine is supposed to catch all of them that are next to each other.

[whurlston]

It didn't work. It would be fine for channels received on digital tuners but not analog.

[-Oz-]

It didn't work. It would be fine for channels received on digital tuners but not analog.

I think I'll have to load all the channels into an array and then just add a -1 or -2 to the channels. How would that affect analog listings versus digital, any idea?

For the working version I have right now which I'll probably release in a little bit I've added more advanced downloading (retries and all) so hopefully that'll get rid of the crashes. A few other internal tweaks too.

[whurlston]

For digital channels, we can use pretty much anything we want for the ID. The problem is the analogs. The ID is used for the channel tuning. If the ID is "0013", GBPVR tunes it to channel 13. If we use a non-integer for the ID like "0013.blah" GB-PVR imports it but it assigns all the channels with channel numbers starting with 1 and increments them by one. So if you have channels 0002.blah, 0003.blah, 0004.blah, and 0008.blah, GB-PVR will try to tune them on channels 2, 3, 4 and 5. Once you skip a number, the tuning is all messed up.

Digitals don't matter because they get remapped anyway.

[whurlston]

Ran another test. Your idea to add the -1, -2 was genius.

I used dotted notation instead of dashed but if you have two channel 15s and you put the ID for the first one as "0015" and the second as "0015.1", the first one gets added with the proper tuning. The second gets appended to the end of your channel list when gbpvr imports it.

Code:

<channel id="0003">
  <display-name>3 WAVE</display-name>
</channel>
<channel id="0004">
  <display-name>4 WKKQ</display-name>
</channel>
<channel id="0015">
  <display-name>15 WHAS</display-name>
</channel>
<channel id="0015.1">
  <display-name>15 WKPC</display-name>
</channel>
<channel id="0027">
  <display-name>27 WTTY</display-name>
</channel>

would end up being added as:

3 WAVE - tune channel: 3
4 WKQQ - tune channel: 4
15 WHAS - tune channel: 15
27 WTTY - tune channel: 27
15 WKPC - tune channel: 28

So only the duplicates would have the wrong tuning and they can be edited in GB-PVR Config.

[-Oz-]

I'll have to implement the dashes or something. What i did for the version I just released a minute ago is make sure all duplicate channels were unselected (i think) by tracking them with a string file rather than just checking the channel above.


Also added logging so everyone please attach your logs.

From 1.1.1 to 1.1.4

* Added logging in the yapi2xml folder called “yapi2xml_log.txt”
* Advanced file handling so you can have text files in the yapi2xml directory now (just not any of the schedules)
* More error trapping (ref)
* Added 5 second delay and then 5 tries to download the schedule file to prevent bad downloads and nasty errors
* Added more duplicate channels support, currently all duplicates unchecked; listed in the log

[whurlston]

I think that rather than run a bunch of cyclic checks for .1, .2, etc, I'm just going to do a simple if Channelumber already exists, ID = ChannelNumber.CallSign

[Bondja]

Whurlston and OZ:

Great news!!! The latest version works...I now have all my listings and channels. Great Job...Thank you.

[-Oz-]

Whurlston and OZ:

Great news!!! The latest version works...I now have all my listings and channels. Great Job...Thank you.

Excellent, glad to hear its working for you.

[dennit]

Schedules Direct has some info relating to differences between SD data and DD data. The two items mentioned were a repeat flag and a schedules program id field expanded to 14 characters from 12. Any thoughts on whether YApi2XML be trying to match the original DD data format or the SD format?