'No Show Details' in TV Guide if Ch Name includes a '/'

[Granddad]

In the TV Guide I have two channels that show '(no show details)' for all times. The EPG used is XMLTV GUI. Looking at the XML file which is down loaded I find that the offending channels are included with the correct program information.

If I 'Update EPG' in the 'Edit Recording Source' screen of config.exe I can see the channels listed in the config.exe log, without any additional errors, but they are not listed in the 'Programme' table in the database.

The only difference that I can see is that both of these channels are the only ones that include a '/' in the name eg 'Sky Movies Action/Thriller'.

I have this problem on two machines, each running Win 7 and another one, also running Win 7 which does not have the problem.

So is it a bug or do I have to change the channel name somewhere to exclude a '/'.

Any bright ideas?

[dennit]

In the TV Guide I have two channels that show '(no show details)' for all times. The EPG used is XMLTV GUI. Looking at the XML file which is down loaded I find that the offending channels are included with the correct program information.

If I 'Update EPG' in the 'Edit Recording Source' screen of config.exe I can see the channels listed in the config.exe log, without any additional errors, but they are not listed in the 'Programme' table in the database.

The only difference that I can see is that both of these channels are the only ones that include a '/' in the name eg 'Sky Movies Action/Thriller'.

I have this problem on two machines, each running Win 7 and another one, also running Win 7 which does not have the problem.

So is it a bug or do I have to change the channel name somewhere to exclude a '/'.

Any bright ideas?

Since you've looked at the 'PROGRAMME' table in the database, you should be comfortable looking at the 'CHANNEL' table. Check for the existence and exact "name" field for those two channels. Then check in the EPG XML file for the "<display-name>" tag for that channel (it's near the beginning of the file) and see if they match. (There may be multiple "<display-name>" tags.) Since you say it's working in one install, I'd suspect some sort of mismatch.

Maybe sub or another user will pop up and advise on their experience with slashes in channel names.

[Granddad]

Yes the EPG XML file matches the 'name' field in the CHANNEL Table. I tried changing the display_name, which is then reflected in the TV Guide, but still no show details appear.

[dennit]

Yes the EPG XML file matches the 'name' field in the CHANNEL Table. I tried changing the display_name, which is then reflected in the TV Guide, but still no show details appear.

The display_name field in gbpvr.db3 has no effect, other than to change what appears on the Guide Screen. To populate the Guide and PROGRAMME table, GBPVR matches the 'name' field in the CHANNEL table to the '<display-name>' tag in the EPG XML. Since yours already match, it looks like it's a slash-in-the-channel-name issue (although I don't know why it would work on another machine).

You can try changing the 'name' field to remove the slash, and processing the EPG XML file (prior to import by GBPVR) so that the <display-name> tag also has no slash. To accomplish the latter I've used two methods. If you use mc2xml, then use the rename option -r (I think that's it). I've done that, and I've also used SED to do it directly to the EPG XML file - your choice.

[Granddad]

I wrote a filter to remove the '/' character, but that still did not fix the problem. On further examination I looked at the XMLTV GUI program and by refreshing the channel list I found that channels with a '/' in the name have be changed to include a '&' character instead. It now all works!!!!

Thanks for your help.

[dennit]

I wrote a filter to remove the '/' character, but that still did not fix the problem. On further examination I looked at the XMLTV GUI program and by refreshing the channel list I found that channels with a '/' in the name have be changed to include a '&' character instead. It now all works!!!!

Thanks for your help.

Great- I'm glad it's fixed. Thanks for posting your solution - it may help someone else down the road.