After Upgrade to MP 1.1.1. freecom DVB-Tuner won't work any more (3 Viewers)

[spaceland74]

MediaPortal Version: 1.1.1
MediaPortal Skin: Blue wide
Windows Version: Windows XP 32bit SP3 with latest patches and dvb hotfix
CPU Type: Athlon 4850e
HDD: WD10EADS
Memory: 2GB
Motherboard: Gigabyte GA-MA78GM-S2H
Video Card: Onboard ATI Radeon HD 3200
Video Card Driver: Catalyst 8.60
Sound Card: Onboard
Sound Card AC3: Onboard
Sound Card Driver: Onboard
1. TV Card: Freecom DVB-T USB
1. TV Card Type: DVB-T
1. TV Card Driver: 2.0.1.7
2. TV Card: TT-Budget C-1501
2. TV Card Type: DVB-C
2. TV Card Driver: 5.0.0.23
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: ffdshow
MPEG2 Audio Codec: ffdshow
h.264 Video Codec: ffdshow
Satelite/CableTV Provider: Netcologne
HTPC Case: Silverstone
Cooling: Arctic Cooling
Power Supply: CoBa
Remote: MCE-Remote
TV: Phillips 37'' LCD
TV - HTPC Connection: HDMI


I have been using MP 1.0.2.0 quite happily for a long time.
After installing MP 1.1.1. my freecom usb dvb-t tuner won’t work any more.

I did a complete uninstall of MP 1.0.2.0. I dropped the MySQL-DB and even uninstalled MySQL.
After that I found a few remaining MP installation files which I also deleted. I rebooted the PC and did a clean install of MP 1.1.1.

The new version will not find any dvb-t-channels on my freecom usb-stick any more. I already tried uninstalling the bda-drivers and reinstalling but with no effect.

Find the tv-server-logs attached.

I rolled back to an image with MP 1.0.2.0 and dvb-t works fine again like it always did.

 

[jameson_uk]

TV logs show it is tuning ok

2010-10-26 08:53:04.015625 [(6)]: card: Tuner locked: True

We need full logs for MP as well and in debug mode.

Thanks

 

[spaceland74]

Sure, I could post MP-Debug-Logs as well but I fail to see the point in that:

The TV-Server found 0 (zero) dvb-t channels so there is nothing that mediaportal could tune.

And without any channel to tune I don't see what additional clarification the MP-logs could bring?

However I am a newby and willing to deliver the requested information if you still think it can help sort things out.

 

[jameson_uk]

Sure, I could post MP-Debug-Logs as well but I fail to see the point in that:

The TV-Server found 0 (zero) dvb-t channels so there is nothing that mediaportal could tune.

Ahh I see you are scanning. The tuner seems to be locking onto channels as above but not picking up any channel details.

Did you upgrade from 1.0.2 straight to 1.1.1? If you are running 1.0.2 now could you try and upgrade to 1.1.0 and see if it works and then if so attempt to upgrade to 1.1.2 (no need to un-install anything)

Have you checked that the right frequencies are being scanned?

 

[spaceland74]

Sure.

As a basis for comparison I am also attaching a log from my current 1.0.2.0 installation where I preview one specific channel in the TV-Server-Setup.
And yes I’m pretty sure as for the frequencies. I even tried scanning one specific frequency which I know is working. In the old dvbt.xml it was…

    <carrier frequency="538000" bandwidth="8"></carrier>

And in the new file it is:

  <DVBTTuning>
    <Frequency>538000</Frequency>
    <BandWidth>8</BandWidth>
    <Offset>125</Offset>
  </DVBTTuning>

So I now did the following to my current 1.0.2.0:
- Stop TVService
- Make an uninstall (Full media portal products cleanup – also dropping the DB)
- Uninstalled MySQL (you never know)
- Deleted some leftover files and rebooted
- Installed 1.1.0., ran TV-Server-Setup and scanned for my DVB-T-card

Unfortunately with the same result: No channels found.

As for your last suggestion: I assume you meant upgrade to 1.1.1? I can’t find a version 1.1.2.
Anyway: As neither the clean 1.1.0 nor the clean 1.1.1 installation worked I guess an update from a non-working 1.1.0 to a 1.1.1 won’t help either…

Thx for your assistance so far. Looking forward to hearing further suggestions.

Cheers

 

[jameson_uk]

was the offset in the old xml file set to 125? it would have looked something like

<country name="Germany - Dresden" offset="125">
	<carrier frequency="538000" bandwidth="8" />
	<carrier frequency="594000" bandwidth="8" />
	<carrier frequency="618000" bandwidth="8" />
</country>

 

[mylle]

Also you could try to change the type from Generic to dvb-t under the properies for your tuner card and see if that makes a difference.

 

[spaceland74]

jameson_uk: Yes the offset was also 125 in the old config-file. Weird, hugh?

mylle: The tuner was already set to DVB-T. See attached screenshot.
I also thought about doing the opposite of your suggestion and change it from DVB-T to generic - but the configuration interface won't allow this.

In some way the tuner is not adressed properly any more in the 1.1.x releases as opposed to my working 1.0.2.

Any further thoughts are more than welcome.

 

[jameson_uk]

I know this is a pain but could you export tuning details from 1.0.2 and then import them to 1.1

This will at least confirm if it is scanning that is the issue

 

[spaceland74]

Yes, that thought had crossed my mind earlier. However the export-function in 1.0.2. is buggy. After 70 minutes of “please be patient…” the popup still asked me for more patience and had not created the export-file yet. (I only have like 30 channels).

So I took it to the next level and inserted the tuningdetails for one affected channel into the tables channel and tuningdetail by hand.

Apart from the channelID most details where identical between the working 1.0.2 and the non-working 1.1.1. Finally the mapping in channelmap needed altering as my dvb-t-card got a different ID in MP 1.1.1.

Still the channels won’t tune. The probably relevant part is:

2010-10-29 12:27:12.656250 [(11)]: WaitForPMT: Waiting for PMT 150
2010-10-29 12:27:22.656250 [(11)]: WaitForPMT: Timed out waiting for PMT after 10 seconds. Increase the PMT timeout value?

This leaves me with my original assumption that somehow the new MP 1.1.1. won’t communicate with my DVB-T-BDA-drivers correctly. May I add that my other card, a DVB-C card tunes fine in MP 1.1.1.

The error that is now produced is an UnableToStartGraph. I added the log from TV-Server which is trying to tune the channel and also a debug-log from mediaportal itself.
Although the mp-log does not report any errors, MP is in fact displaying an unable to start graph message (attached).


Cheers