After 1.0.16 and YAPI2XML, Can't Change Channels

[megacoupe]

Long time GBPVR user. After the unfortunate demise of Zap2It, I was forced to upgrade my installation (which was working perfectly). I went with YAPI2XML, which appears to be getting the correct channel info.

After scheduling a recording recently, I found that it had not worked. I went into Live TV and realized that I couldn't change channels. GBPVR displays my input, the IRBlaster blinks, and my cable box pops up the menu showing the channel, but then nothing happens and the current channel remains.

I tried using the Hauppauge IR utility and it turns my box on and off perfectly, and changes channels accurately. In GBPVR Config, I have it pointed to HaupBlast.exe.

I suspect it might have to do with my YAPI2XML setup, but I'm not sure. The only way I can record things on a schedule is to go the cable box and change the channel myself. The recording works, but it sucks that I have to change the channel myself.

I've included a log (this is the first time I've ever done so, so please let me know if I've done something wrong).

[-Oz-]

Open the config utility. See if the channel numbers on the left match what the channel numbers should actually be. Its possible that gbpvr has treated the xml file as a different set of channels and loaded it on top of the others. This is what hints that to me:

2007-10-13 13:17:50.712 VERBOSE [1] Switching to channel: 106 (73 NYCTV73)
2007-10-13 13:17:50.712 VERBOSE [1] Running: C:\Program Files\devnz\gbpvr\HaupBlast.exe 328

It appears to go to channel 106, which may be actually 73 and HaupBlast sents 328. I have no idea which is correct but that is probably the issue.

I would do the following: http://gbpvr.com/pmwiki/pmwiki.php/Utili...2XML#toc11

[kbr37]

Wait, is yapi2xml working now? I thought that Yahoo! somehow blocked the use of this program.

[-Oz-]

Wait, is yapi2xml working now? I thought that Yahoo! somehow blocked the use of this program.

They never "blocked" it. They actually stopped serving content to their own program and thus all of us that were using that data. Early this month their own program (and thus yapi2xml) started working again and hasn't had a problem since.

[sub]

It appears to go to channel 106, which may be actually 73 and HaupBlast sents 328. I have no idea which is correct but that is probably the issue.

Yeah, the channel numbers are incorrect. This would most likely be because either yapi2xml didnt supply the channel numbers (so some were allocated), or because the requested channel numbers were already in use by existing channels (like old zap2it channels).

Your easiest fix might be to delete the gbpvr.db3 database, then run the config app to recreate you capture sources etc. (effectively starting again from scratch without zap2it channels getting in the way)

Alternatively go into the capture source channel list and correct the channel numbers, then go to the main channels tab and correct the channel numbers.