Can't start HD channels directly (1 Viewer)

[Spooky]

Tried 1.1.0 Beta 1 today. Still the same error.

2009-08-30 13:48:13.593750 [6]: WaitForPMT: Waiting for PMT 107
2009-08-30 13:48:23.593750 [6]: WaitForPMT: Timed out waiting for PMT after 10 seconds. Increase the PMT timeout value?
...
2009-08-30 19:03:14.046875 [19]: start subch:0 No PMT received. Timeshifting failed

 

[Spragleknas]

Hi!
Could you perhaps try the beta again?

I think you might have used the "old" beta with broken TV for HD-channels.

UPDATE 2009-08-30

The inital Beta 1 release sadly contained one showstopper bug. Because of this we were forced to create a new BETA 1 release.
Those of you who installed the initial release will have to uninstall it and then reinstall the new version linked below.

Sorry for the inconvenience.

MEDIAPORTAL - free media center - MediaPortal 1.1.0 BETA 1 - Released! - UPDATE 2009-08-30

 

[Spooky]

Hi!
Could you perhaps try the beta again?

I think you might have used the "old" beta with broken TV for HD-channels.

UPDATE 2009-08-30

The inital Beta 1 release sadly contained one showstopper bug. Because of this we were forced to create a new BETA 1 release.
Those of you who installed the initial release will have to uninstall it and then reinstall the new version linked below.

Sorry for the inconvenience.

MEDIAPORTAL - free media center - MediaPortal 1.1.0 BETA 1 - Released! - UPDATE 2009-08-30

No no, I used the new beta (I waited until the new release went up). Also the problem in the old beta was a problem with the TsReader, where timeshifting of the channel was already running. In my case timeshift can't even start (I can't tune to the channel...) because of the PMT timeout, when trying to tune to the HD channel without being already tuned to another channel.

 

[infinite.loop]

The issue in the first beta release was client-side (TsReader), but Spooky's problem is severside.
"Sadly" i am still unable to reproduce the problem.

 

[ronilse]

Hi,
Spooky, is the cable to tuner straight from sat(not used to any other tuner first - see in your other post that signal & quality is somewhat low(40))?

Regards
Roy

 

[Spooky]

Hi,
Spooky, is the cable to tuner straight from sat(not used to any other tuner first - see in your other post that signal & quality is somewhat low(40))?

Regards
Roy

Hello . Well, not straight from the Sat, but straight from the Multiswitch which is connected to the LNB. The cable is pretty long though, that's why the signal is rather low, probably. But that shouldn't be the problem. As posted before, I set up a completely new HTPC for a friend, on a completely different location, with almost identical hardware and software and the exact same issue happens there too. The signal level for this HTPC is around or over 90%.

 

[Spooky]

Forgot to add the complete logs before. This is for the test with 1.1.0 Beta 1 #23491.

 

[infinite.loop]

Hi,
Spooky, is the cable to tuner straight from sat(not used to any other tuner first - see in your other post that signal & quality is somewhat low(40))?

Regards
Roy

Hello . Well, not straight from the Sat, but straight from the Multiswitch which is connected to the LNB. The cable is pretty long though, that's why the signal is rather low, probably. But that shouldn't be the problem. As posted before, I set up a completely new HTPC for a friend, on a completely different location, with almost identical hardware and software and the exact same issue happens there too. The signal level for this HTPC is around or over 90%.

This is just confusing.
I have quite some friends and family members with HTPC's using floppy/and firedtv s(2) cards, tuning to Astra 19.2°E, using AlphaCrypt/Cryptoworks/EasyTV Cam's + ORF Smartcard and none of them has a issue.

 

[Spooky]

This is just confusing.

Indeed. From my point of view these may be the vague causes:

• Some software setting, other than in MediaPortal. Since it happens on 2 almost identical systems and since I installed and set up those sysems myself and therefore possibly installed the same things and made the same settings... "some" setting or software is causing the issue. Of course I have no idea what that could be.
• Some hardware issue. We know that the FloppyDTV S2 is working or should work flawlessly with MediaPortal. Therefore, if it is a hardware issue, the MA78GM motherboard could be the cause, since both systems have one. However, I can't imagine why or how the motherboard or its drivers could possibly create such a specific issue.
• Some issue with MediaPortal in combination of either the hardware or the software. Essentially a combination of MediaPortal with the two previous points. Maybe some software or setting is causing this specific issue in MediaPortal 1.x. Or maybe something in MediaPortal is creating this specific issue in combination with the MA78GM motherboard. I had no such problem before MediaPortal 1.x. Maybe it still worked in 1.0.0, but I can't remember.

Again, this is pretty vague. So I still need pointers to what I could try to solve or debug this problem, even if it's just simple ones (because maybe I did something horribly simple and stupid on all those systems that creates this issue ).

The only thing I can think of currently is trying to install Windows Vista or Windows 7 (FloppyDTV should be compatible with Windows 7 since August '09) in order to try to rule out an OS specific issue/setting.

 

[infinite.loop]

I am running floppy and firedtv's on WinXp SP3, Vista and Windows 7 without issues (on W7 RTSP streaming is not fully working yet), so i doubt that this is the cause.
Do both systems also use the "same" CAM? It could be that the issue is there.

Since both systems have nearly the same hardware, testing the floppydtv + MP on an other hardware would be great!