Happauge DVBS+ wont play first channel after suspend (1 Viewer)

[ColinT]

TV-Server Version:
MediaPortal Version: 1.0
MediaPortal Skin: Blue
Windows Version: Vista Home Premium SP1
CPU Type: Athalon 2.6
HDD: WD 250 (SATA)
Memory: 1G
Motherboard: NVidia HDMI
Video Card: Nvidia 7600
Video Card Driver:
Sound Card:
Sound Card AC3:
Sound Card Driver:
1. TV Card: Hauppauge NOVA S+
1. TV Card Type:
1. TV Card Driver:
2. TV Card: Hauppauge Nova T PCI
2. TV Card Type:
2. TV Card Driver:
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:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote: MCE
TV:
TV - HTPC Connection:

This might be a driver problem, but has onluy occurred since RC4 I believe.

Basically when tuning to the first channel on the Nova S+ card after a suspend wont tune.
Obviuosly this causes a problem for rcordings as they dont work.

Second and subsequent tunes work perfectly.

Have tried reseting driver but to no avail.
Where the wake up is after a short suspend there doesnt apear to be a problem

Log attached. in this log the problem o ccerrured at 18:28:40
Any help is much appreciated

Colin

 

[ColinT]

I wonder if it is connected with fix 0001712.

Gibman - could you help?

The log shows that the server thinks that a graph is already running then skips the wait for pmt then fails to sync and gives up.
Fix 1712 changed the logic arround waiting for pmt and was introduced at RC4 which is when I think I started having a problem

Colin

 

[gibman]

Maybe ur graph isn't properly stopped before entering sleep mode.

Can u try this;
exit MP.exe (no need for MP GUI for this test.)
disable PS server plugin.

Tune some channel in setuptv.
Stop the channel.
wait a few seconds-

Now enter either standby or hibernation manually, using task manager etc.

now Resume PC.

in setuptv, try and tune any channel again.

maybe this will shed some more light on the issue at hand.

/gibman

 

[ColinT]

Thanks for your help

Will try when I get home tonight. btw this shows some similarities with

https://forum.team-mediaportal.com/get-support-90/not-recording-once-woken-51549/

Getting the same error messages, but not if I shut it down and start it up manually

Regards Colin

 

[ColinT]

tried as you suggested and no problems, but then wht I thought of as systematic seems to be more random.
With about 15 suspends and resumes of various kinds it has only failed once.

I have put a delay in starting the card after sleep, and will see if that helps.

Thanks for the suggestion anyway.

Colin

 

[ColinT]

Still having problems with this. (Log attached)

I tried with no Powershceduler but the same thing occured

I have investigated further and it apears that if the tuner is initialised after a sleep event then it fails when attempting to get a graph. The log file is confusing in that it says "Graph already running - skip WaitForPMT" when there is no graph.
The relevent code is
public override void OnGraphStart()
{
Log.Log.WriteFile("subch:{0} OnGraphStart", _subChannelId);

if (GraphRunning())
{
WaitForPMT();
}
else
{
Log.Log.WriteFile("subch:{0} Graph already running - skip WaitForPMT", _subChannelId);
if (_teletextDecoder != null)
_teletextDecoder.ClearBuffer();

_pmtPid = -1;
_pmtVersion = -1;
}
}

After this it tries to start a graph and gives up after 2 seconds, as the tuner hasnt locked (not too surprising as no Wait for PMT ocurred.

Subsequent tunes work, even after a sleep, provided that the tuner is not reinitialised.


When I tick the re-initialise tuners box, it happens every time without fail.
Occasionally it Never tunes. A stop and restart of TV server can clear this. This makes me think it may well be an initialisation problem.


Help very much appreciated

ColinT

 

[ColinT]

Following one of Gibman's links I have just found this on the Hauppauge site (Nova-S-Plus: DiSEqC specs in BDA drivers needed [Archive] - Hauppauge UK Forum)


"Tuning Order

Some of the tuning parameters have to be set in a specific order. Performing these tuning calls out of order can cause general tuning problems or unexpected driver behavior.

The driver can ignore specific property calls if the filter is STOPPED, ensure your filter is in the PAUSE or RUN state before attempting a tune request.

The following order is suggested:

1. Submit any pre-tuning demodulator or tuner related properties including, SetPilot, SetRollOn, PutModulation.

2. Now submit your traditional BDA tunerequest to the driver

3. Submit any DiSEqC requirements

If the filter or graph is subsequently stopped, you have to resubmit again to guarantee the correct settings are re-applied."

What appears to happen in my log is Diseqc first, then Tune then Start Run the graph.
Isuspect this may be the problem.

ColinT