SchedulesDirect problem with channel names, some have channel #

[Wakalaka]

I just signed up for SchedulesDirect and have 2 capture sources. I defined each to use SchedulesDirect, input my userid and password, clicked "Empty EPG", and clicked Remove until all channels were gone. I then clicked "Update EPG" and got the channels I have selected in SchedulesDirect in the list box.

The problem: some of the channels have the channel number before the name, and some don't. It looks like only the broadcast stations have the <fccChannelNumber> tag present, but this doesn't line up with what the config app shows. Config app shows "# name" for the following channelS: 2 KATU, 3 KRCW, 8 KGW, 12 KPTV, 13 KPDX, 35 ESPN, 43 ANIMAL, 57 SPIKEP, 60 COMEDYP, 62 VH1P, 64 TVLANDP.

forum software isn't letting me upload my zap2it.xml file (compressed to zip).

screenshot of my SchedulesDirect lineup for Comcast Tualatin Valley Regional (97124)

[whurlston]

Are you sure those channels were not previously in the database from before Schedules Direct? When you remove channels, the will not be removed if you have recurring recordings for those channels.

[sub]

Yeah, I'm fairly sure whurlston is correct and these are channels hanging around from the past.

[Wakalaka]

Are you saying that I have to remove all Recurring recordings?
Would the proper process be:
1) Delete all Recurring recordings
2) Empty EPG for both capture sources
3) Remove all channels from one of the capture sources
4) Update EPG for one of the capture sources

[sub]

Did you try any other EPG between zap2it any Schedules Direct?

For most people that went straight from Zap2it to Schedules direct it was just a matter of changing the EPG source from the Zapit epg plugin to the Schedules Direct plugin.

[Wakalaka]

I was using zap2xml before hitting another problem with it, and saw that the price of SchedulesDirect was dropped from $60/yr to $20/yr, so signed up.

[sub]

Yeah, I think something must have become broken during these various EPG changes.

What I'd suggest doing is hitting 'export recordings', then rename gbpvr.db3 to gbpvr..db3.backup, then start the config app and set the capture sources up from scratch, then do an 'import recordings'. This should give you a clean database.

[Wakalaka]

Yeah, I think something must have become broken during these various EPG changes.

What I'd suggest doing is hitting 'export recordings', then rename gbpvr.db3 to gbpvr..db3.backup, then start the config app and set the capture sources up from scratch, then do an 'import recordings'. This should give you a clean database.

I did all of that about 2 weeks ago. There was a thread where you and I discussed the problem I was having, and I ended up doing the above. If this cleans it up again, then I'd suggest that some coding be done to improve the sensitivity of GB-PVR. Yes I've donated money, yes I support you wholeheartedly, yes this is some constructive criticism.

[sub]

If this cleans it up again, then I'd suggest that some coding be done to improve the sensitivity of GB-PVR.

I did code it to work smoothly for the zap2it -> schedules direct move, but users of some of these other EPG utilities that popped up post 1.0.16 have not worked as well. I obviously didnt test against these before putting out the 1.0.16.

The problem comes from the fact the utilities generate different channel names, so GB-PVR has no way to know they're the same channel.

[Wakalaka]

Should SchedulesDirect generate channel names that are "# name"?