[solved] tv tuner Stopped getting signal (2 Viewers)

[wogboy112]

hi, ive been using mediaportal for years now and have had my share of issues, this one has me stumped.

out of nowhere, i could not watch live tv, i tried checking the tv directly using the cable and it works fine,i installed the hauppauge software wibtv8 and it works fine. so i went out amd bought another hauppauge tuner card.. same issue with tuning in mediaportal, works fine in wintv.

i have attached the logs from after trying to tune in. any help would be appreciated.

 

[mm1352000]

Hello

Can you please use the supplied Watchdog tool with option 1 ("report a bug...") to reproduce the problem (ie. try to start viewing live TV), then attach the zip file that it produces.

 

[wogboy112]

I would, but since uninstalling and installing from scratch I cant even find them in a scan this is what happens when Im trying to scan, I get signal quality but no signal level then it doesnt find anything

 

[mm1352000]

I get signal quality but no signal level

That's not necessarily a problem. Some tuners don't report signal level.

then it doesnt find anything

There are a huge variety of potential causes for this:

• insufficient signal strength/quality
• tuning details are incorrect/out-of-date
• other software using the tuner

...and the list goes on.
If the tuner works fine in WinTV8, you should be able to confirm whether MP's TV Server is scanning the right frequencies. I note there are several "Perth..." options to select from. Maybe you simply haven't chosen the right one?

Keep in mind that only one program can use the tuner at any given time. If you want to use the tuner in WinTV you should first stop MP's TV Server (ie. open TV Server Config, go to the "manual control" section, and click "stop service"; after you're done with WinTV you click "start service"). Likewise if you want to use the tuner with MediaPortal you should ensure WinTV is closed.

Finally, I wonder how you installed MP 1.16. Did you update, or did you do a clean installation? Incorrect selection for some of the TV Server tuner options - particularly the "preferred network provider" and "when card enters idle state..." settings - can cause similar behaviour. Your current selection for the 2 aforementioned settings is "generic" and "stop card". I suggest you try "DVBT" and "stop card".

 

[wogboy112]

I did orignally do an upgrade but since done a clean install... I did the scan in Wintv8 and its showing different frequencies 177625 7 in mediaportal and 177500 in wintv8?

How would I try to add that into Mediaportal?

 

[mm1352000]

I did orignally do an upgrade but since done a clean install...

...in which case you should definitely try changing the "preferred network provider" setting to "DVBT" as previously described.

I did the scan in Wintv8 and its showing different frequencies 177625 7 in mediaportal and 177500 in wintv8?

Actually they're the same.
In your example MP's frequency is 177500 kHz, same as WinTV. Reason you see 177625 is: if MP doesn't find signal at the original frequency, it also scans +/- 125 kHz (ie. 177375 and 177625).
In short: this is unlikely to be the problem.

 

[wogboy112]

Ok ive tried that... it still has the full signal quality but then finds nothing...... do you think it could have been a windows update that may have caused this? nothings changed and its been working for about 7 years now.

 

[mm1352000]

I don't have enough information to share an informed opinion about whether a Windows update caused your problem. What I can say is that problems don't start for no reason. Something has changed to cause this.

 

[pwh123]

Exactly the same problem for me, running MP V1.16 on Win 10 with a Hauppauge 2205 tv-card.
Started a week ago on MP V1.13, tried to upgrade to V1.16 to solve problem, with no luck.

I have tried to update Hauppauge drivers and installed WinTv8, that dident solve the problem either.
Watching tv and recording via WinTv8 works perfect, my guess is that it is a Win10 update that MP tv-engine doesn't like.

So basically the same problem as Wogboy112.

 

[mm1352000]

@pwh123

So basically the same problem as Wogboy112.

Maybe same symptoms, but the cause could be different.
Please provide log files if you'd like assistance. Use the Watchdog tool.