2006-01-20, 06:51 PM
I had a little problem the other day during epg update. It updated some of my capture sources but a couple failed. They are all currently using the exact same zap2it account and lineup. The problem occured when I woke it to watch something and the failed updates started again. I went to the tv guide and it blew up with the width equal zero error.
So I got to thinking about epg updates, at least as far as zap2it is concerned. It seems that is should be possible to download the content from zap2it once, then reuse it for all the identically configured capture sources. It appears that now it redownloads it for each souce, which I can see would be easier, and that is when it usually fails with a timeout error. If the downloaded content could be stored in a file locally with a name relating it to the provider and lineup then the download routine could check first to see if the data already was there and check the date to make sure it was current. At the end of the epg update cycle the data could be deleted so that old data was not reused.
Since many users seem to have multiple tuners and I would bet most have at least 2 of those tuners on the same lineup this could not only speed up the epg update process but lessen the load on zap2its servers significantly. In my case I currently have all six tuners on the same zap2it lineup / account. Once I get around to configuring the MCE remotes ir blaster with hip I will have five on one lineup and one on the other since it will use the cable box and be able to record premium channels.
Just an idea anyway. Keep up the good work and I look forward to the next version.
So I got to thinking about epg updates, at least as far as zap2it is concerned. It seems that is should be possible to download the content from zap2it once, then reuse it for all the identically configured capture sources. It appears that now it redownloads it for each souce, which I can see would be easier, and that is when it usually fails with a timeout error. If the downloaded content could be stored in a file locally with a name relating it to the provider and lineup then the download routine could check first to see if the data already was there and check the date to make sure it was current. At the end of the epg update cycle the data could be deleted so that old data was not reused.
Since many users seem to have multiple tuners and I would bet most have at least 2 of those tuners on the same lineup this could not only speed up the epg update process but lessen the load on zap2its servers significantly. In my case I currently have all six tuners on the same zap2it lineup / account. Once I get around to configuring the MCE remotes ir blaster with hip I will have five on one lineup and one on the other since it will use the cable box and be able to record premium channels.
Just an idea anyway. Keep up the good work and I look forward to the next version.
Pete Borders
My GB-PVR System:
Asus A7N8X Deluxe Rev 2.0 Nforce2 Motherboard
Saphire Radeon 9600 Pro Atlantis
AMD Athlon XP 3200+
1GB Crucial PC3200 DDR400 Dual Channel
20GB PATA IDE System Drive
Raid 5 Array of 4 x 200GB 8MB Cache PATA IDE Drives
LSI MegaRaid I4 Hardware Raid ATA100 Controller
4 x Hauppauge WinTV PVR-500MCE
Windows XP SP2
GB-PVR 0.99.5
My GB-PVR System:
Asus A7N8X Deluxe Rev 2.0 Nforce2 Motherboard
Saphire Radeon 9600 Pro Atlantis
AMD Athlon XP 3200+
1GB Crucial PC3200 DDR400 Dual Channel
20GB PATA IDE System Drive
Raid 5 Array of 4 x 200GB 8MB Cache PATA IDE Drives
LSI MegaRaid I4 Hardware Raid ATA100 Controller
4 x Hauppauge WinTV PVR-500MCE
Windows XP SP2
GB-PVR 0.99.5