after standby (S3): unable to start timeshift, unable to start graph (no TV possible) (1 Viewer)

[Rudi99]

My two "skystars" are now recognized by WinXP and MP. (driver etc see MySystem on the left side)

After reboot or first start i can look tv etc. without any problems. Even recording one channel and looking another is working (as expected, wow).

But after standby (into S3, yes, that's working here by remote or by button on htpc-case) there always occurs: "timeshift could not be started, unable to start graph". No tv possible. See also these threads:
https://forum.team-mediaportal.com/...nable-start-graph-obwohl-es-davor-ging-40255/
https://forum.team-mediaportal.com/get-support-90/please-help-cannot-get-2-x-skystar2-work-40401/

Because I couldn't find a solution yet and didn't find any other bug-post for this issue, i post it as official bug now.

What i tried:
- RC1 and all svn's including 19228 (clean installs, with erasing database before :-( )
- timeshift-folder on drive c or e (another internal hdd)
- dvbfix installed
- MP waiting fo tv-server-start
- tv-server delay 3-12sec
- MP start-delay 3 - 15 sec
- restart MP on resume after S3
- issue occurs also with only one tv-card installed

Logs are attached. Can anyone help please, please? So, i can't schedule recordings or have a comfortable quick system-start...

 

[ronilse]

Hi,
So when you restart TVService card works again(if not this it's a driver problem)?

Regards
Roy

 

[Paranoid Delusion]

tv-server delay 3-12sec

For my hauppauge it needs 20 secs, so maybe a setting of 20-30 secs might be worth trying.

MP start-delay 3 - 15 sec

Mines just set at wait for TVServer to start.

 

[Rudi99]

So when you restart TVService card works again(if not this it's a driver problem)?

No

For my hauppauge it needs 20 secs, so maybe a setting of 20-30 secs might be worth trying.

I'll try and soon be back...

EDIT: ok, now i have set tv-service to wait 30 sec to detect card and MP -start-delay to 30 sec: no solution. It seems, that after resume from S3 the 30 sec (wait tv-server to detect card) is not working, only at first start after reboot! After resume from S3 only MP waits the 30 sec start-delay! (tv-server reinitialize is checked, see screenshots...)

Any other solution than newer drivers? (i 'm afraid, with the newer SP3-drivers (only beta!) i will have no 2 cards detected and the problem still exists...)

 

[rtv]

Any other solution than newer drivers? (i 'm afraid, with the newer SP3-drivers (only beta!) i will have no 2 cards detected and the problem still exists...)

Definately a driver issue.

 

[Rudi99]

Definately a driver issue.

... nooooo, aargh... sh§&%$"&$

so which driver should i prefer: normal (with only 1 card detected by MP) oder BDA (with resume from S3-problem)?

And why does tv-server not wait the 30 sec before detecting tv-card after resuming from S3?

 

[ronilse]

Hi,
What does the log say about detecting/wait after S3(Detecting Cards in 30 seconds)?

Btw your first log has that correct, but if it doesn't help with restarting TV Server this it's a driver bug which we can't do much about.....

Regards
Roy

 

[Paranoid Delusion]

This also could be a BIOS issue, make sure you have latest for your motherboard.

 

[Rudi99]

Latest BIOS is installed, newer are only betas and do not involve any board-issuesthat are needed, like newest cpu-id's etc.. (if you can trust the gigabyte-statements).

 

[Paranoid Delusion]

Btw your first log has that correct, but if it doesn't help with restarting TV Server this it's a driver bug which we can't do much about...

As Roy said if stopping and then restarting TVServer, and the driver has not loaded correctly, then there is no way TVServer can connect to the card\s.

Just to put your mind at ease even further to prove this, if you stop TVServer and close config. manually put pc into standby and then resume and restart tvserver, try and see if channels are then associated and can be previewed.

Make sure before restarting TVServer that both sql browser, sqlserver and sql writer services are running in taskmanager processes.

After that its back to bum drivers, sorry.