Channels out of Order

[taz]

I just upgraded to v. 1.0.16. I aslo started using one of the XML options to replace zap2it. Now my channels are all out of order. I thought it might be related to the XML file so I switched back to zap2it. No change. They are still out of order. There appears to be no rhyme or reason to the order they are now in. Not numerical, not alphabetical... It is the same with PVRX2.exe and GBPVR.exe. I have attached my most recent logs if anyone has any ideas.

Thanks,
Taz

[bgowland]

Channel ordering (in the TV Guide) is decided by the numerical order on the Channels tab in Config.exe.

I'm guessing that if you've changed your EPG source to XML then the XML file doesn't have the channels in the order you're expecting.

Sorry - I'm not in the US so don't know anything about US channel listings etc. but I've had this happen to me when changing EPG sources.

If your XMLTV grabber can be set to order the channels then it may be the easiest way to fix it although you'd probably have to clear the previous channel information.

Cheers,
Brian

[sub]

Yep, what he said.

Some xmltv files dont contain channel numbers, which means they effectively get allocated some random incrementing number and you have set the channel numbers correctly yourself in the config app.

Alternatively, if the channel numbers are specified, but the channel number is already inuse, then it also gets allocated the number and you'll have to correct it yourself in the config app.

[-Oz-]

Yep, what he said.

Some xmltv files dont contain channel numbers, which means they effectively get allocated some random incrementing number and you have set the channel numbers correctly yourself in the config app.

Alternatively, if the channel numbers are specified, but the channel number is already inuse, then it also gets allocated the number and you'll have to correct it yourself in the config app.

Since I think you're using YApi2XML it does get ordered by channel number with leading zeros. If you have channels with 4 digits it may be out of order but thats fixed in the next release (later today).

Clearing all the channel data will probably help.

[taz]

I had the problem using the XML and the zap2it (after switching back from an XML file). This is what I found

• The channels were out of order using XMLTV (via Yahoo API) and zap2it
  
• There were also several duplicate channels
  
• I emptied the EPG adn removed all of the channls in GBPVR config
  
• I still had the same problem (channels out of orrder and duplicates)
  
• The XML file looked OK, the channel IDs matched the channel
  
• I emptied the EPG again and deleted all of the channels
  
• I then looked in the GBPVR.db3 file and found several channels were still there, so I manually deleted them
  
• I updated the EPG and this took care of the duplicates but they were still out of order
  
• I opened GBPVR.db3 again and noticed the channelID column was blank, and the channel_number field did not always match the correct channel.
  
• I manually fixed the channel numbers and did an EPG update and everything seems fine
  

I am not sure where the channel_number comes from since it appeared the 3 digit channel number in the XML file were all correct. Also not sure why channels still showed up the the db3 file and not in the config app. But everything appears correct now.

Thanks for all the help ,

Taz

[whurlston]

Yep, what he said.

Some xmltv files dont contain channel numbers, which means they effectively get allocated some random incrementing number and you have set the channel numbers correctly yourself in the config app.

Alternatively, if the channel numbers are specified, but the channel number is already inuse, then it also gets allocated the number and you'll have to correct it yourself in the config app.

Is there a way to specify the channel number other than the id attribute in the channel element that I'm not aware of? If so, I could have saved about half a bottle of Excedrin.

[-Oz-]

I had the problem using the XML and the zap2it (after switching back from an XML file). This is what I found

• The channels were out of order using XMLTV (via Yahoo API) and zap2it
  
• There were also several duplicate channels
  
• I emptied the EPG adn removed all of the channls in GBPVR config
  
• I still had the same problem (channels out of orrder and duplicates)
  
• The XML file looked OK, the channel IDs matched the channel
  
• I emptied the EPG again and deleted all of the channels
  
• I then looked in the GBPVR.db3 file and found several channels were still there, so I manually deleted them
  
• I updated the EPG and this took care of the duplicates but they were still out of order
  
• I opened GBPVR.db3 again and noticed the channelID column was blank, and the channel_number field did not always match the correct channel.
  
• I manually fixed the channel numbers and did an EPG update and everything seems fine
  

I am not sure where the channel_number comes from since it appeared the 3 digit channel number in the XML file were all correct. Also not sure why channels still showed up the the db3 file and not in the config app. But everything appears correct now.

Thanks for all the help ,

Taz

I was messing around with mine today, here's what I did.

* open the capture source
* manually delete every single channel
* click ok
* remove all the channels from the other tuner
* click ok
* load the yapi2xml xml file for the first tuner
* load the yapi2xml xml file for the second tuner
* go to the channels tab and click remove all unreferenced channels

That fixed all my problems without having to lose all the recordings and such.

[sub]

Is there a way to specify the channel number other than the id attribute in the channel element that I'm not aware of?

From memory you can use a display-name tag also, but dont use the first one, which should be reserved for the name.

[whurlston]

Ah, I thought you only read the first display-name and ignored the others. I've got some playing to do then. It will have to wait till tomorrow though.

As for you sub, go enjoy your vacation. We won't break things TOO badly while you're gone :p

[whurlston]

Thanks sub, that worked well enough for me.

If there is two channel 4s, the second gets added in the 40-49 range. The only issue is if you have channels 40-49, the second channel 4 is inserted at 49 and the real channel 49 gets moved to 50. Everything after that is one channel off.

I was able to fix it by adding 2000 to the channel number if it already exists. This puts the second channel 4 as channel 2004. I add 2000 because some D* channels can be in the 1000 range. Now the only channel numbers that are wrong are the duplicate channels and they can be easily fixed in the Recording Source configuration.

Example output:

Code:

<channel id="11187">
    <display-name>TWC</display-name>
    <display-name>4</display-name>
  </channel>
  <channel id="11497">
    <display-name>WHAS</display-name>
    <display-name>2004</display-name>
  </channel>
  <channel id="11645">
    <display-name>WLKY</display-name>
    <display-name>5</display-name>
  </channel>
  <channel id="10093">
    <display-name>FAM</display-name>
    <display-name>40</display-name>
  </channel>
  <channel id="11163">
    <display-name>SPIKETV</display-name>
    <display-name>41</display-name>
  </channel>