TV Guide not working

[GreatMilenko]

Hello

I'm trying to get TV guide up and running using a DVB-C card called FloppyDTV from FireDTV, the device is working in its own program and it was able to load EPG in Mediaportal, however in gbpvr it finds all the channels updates and maps the EPG, but when i try to view the TV-Guide it is completely empty.
I'm running "FireDTV DVB-C CI" device as Recording source, "DVB EPG Broadcast" as EPG source and "No channel changer".
The pvrx2.exe.log is a normal startup and pvrx2.exe-1.log/pvrx2.exe-2.log is startup with "pvrx2.exe -updateepgonly" option, in case it had any extra information.

Cheers
uffe

[Sheik Yerbouti]

Hi Uffe, welcome on the forum. Sorry I didn't see your PM earlier and too bad you didn't get an answer on your question yet, it's quite unusual for this forum as you will find out once you get here more often. I really think sub needs to look at this, because it seems you did the setup just fine. I'm using xmltv myself, but I have tried the EPG from DVB-C before and it gave me listings.

Chris

[sub]

Hello

I'm trying to get TV guide up and running using a DVB-C card called FloppyDTV from FireDTV, the device is working in its own program and it was able to load EPG in Mediaportal, however in gbpvr it finds all the channels updates and maps the EPG, but when i try to view the TV-Guide it is completely empty.
I'm running "FireDTV DVB-C CI" device as Recording source, "DVB EPG Broadcast" as EPG source and "No channel changer".
The pvrx2.exe.log is a normal startup and pvrx2.exe-1.log/pvrx2.exe-2.log is startup with "pvrx2.exe -updateepgonly" option, in case it had any extra information.

Cheers
uffe

Sorry, I missed your original post. There is a scenario that can happen occasionally, which I can see in your logs, that results in no listings being loaded from the DVB EPG.

The problem happened at scan time, when it failed to find a specific peice of information, resulting in a zero being used as part of your channel identifer. Later when doing a DVB EPG update, that zero causes it to look like another channel.

Here is what I mean. These are what the application knows your channels as:

2010-03-28 21:21:34.984 VERBOSE [7] Adding DR HD (AC3) as: 3500-1220-0
2010-03-28 21:21:34.984 VERBOSE [7] Adding Nickel as: 6200-1260-0
2010-03-28 21:21:34.984 VERBOSE [7] Adding NatGeo as: 6370-1270-0
...

The later it finds some listings for natgeo, but "6370-1270-65024" does not match "6370-1270-0", so the listings are thrown away.

2010-03-28 21:22:38.437 VERBOSE [7] 6370-1270-65024 now has UID(2): 18E2000045D7
2010-03-28 21:22:38.437 VERBOSE [7] 6370-1270-65024 now has UID(2): 18E2000045D8
2010-03-28 21:22:38.437 VERBOSE [7] 6370-1270-65024 now has UID(2): 18E2000046A4
2010-03-28 21:22:38.437 VERBOSE [7] 6400-1280-65024 now has UID(2): 190000006A50
2010-03-28 21:22:38.437 VERBOSE [7] 6400-1280-65024 now has UID(2): 190000006A51
...

Your best short term option is deleting your capture source and recreating it.

Longer term, the next release doesnt have this problem.

[GreatMilenko]

i deleted the capture source and rebuilt it, but the results are the same as last time:
2010-04-07 00:00:23.484 VERBOSE [7] Adding NatGeo as: 6370-1270-0
2010-04-07 00:01:26.734 VERBOSE [7] 6370-1270-65024 now has UID(2): 18E200004746
2010-04-07 00:01:26.734 VERBOSE [7] 6370-1270-65024 now has UID(2): 18E200004747
2010-04-07 00:01:26.734 VERBOSE [7] 6370-1270-65024 now has UID(2): 18E200004748
2010-04-07 00:01:26.734 VERBOSE [7] 6370-1270-65024 now has UID(2): 18E200004749

[sub]

Sorry, short of you editing your database to correct the numbers, there is nothing I can do about it right now. Its fixed in the next release.

[GreatMilenko]

ok thanks for your support, i will just wait for the next release.