After restart TV stops playing after first attempt ... (2 Viewers)

[pur_berger]

do you need anything else?

No, that's perfect.

Thank you once again for your assistance and patience. Hopefully the tuner will work nicely for you now.

Hello and a verry goog christmas! As I know the thing you want most are logs logs logs ... well - here is a present for you

TV stops after an undefined amount of time (hours) and picture scrumbles - audio stays good. I have EPG in mind (disabled it meanwhile and will check if that changes anything) but maybe you can check if you can see anything? was around 11:14 today when it started ...

 

[mm1352000]

Merry Christmas to you also!
Do you have the TsReader (client side) and/or TsWriter (server side) log files also? They are of equal or higher importance (compared to the TV service log) for diagnosing such situations...

 

[pur_berger]

Sure - here you go.

 

[mm1352000]

Thanks again.
The TsWriter log is quite full of continuity errors starting from ~11:10 as you said (though there are some throughout the log, even at the start - just not as many). If you search the forum you will probably find hundreds of threads telling you that continuity errors in the TsWriter log file usually are caused by:

1. Poor signal strength or quality.
2. HDD overloaded.

There are other causes (eg. incorrect tuning details, driver DPC latency issues, overheating), but these seem to be much rarer.

If you're convinced that your signal is okay, check the HDD. Task manager -> resource monitor should give a good indication. It can be overloaded when:

• almost full
• highly fragmented
• other programs need to use it heavily (eg. security software - virus/malware scan)
• etc.

 

[pur_berger]

Thx for looking. Seems strange as the config was not changed. The disk the ts file is written to is an ssd and the folder is excluded from any antivirus scan.

Anyway if you say it doesn't come from the tuner side I need to check the performance monitor as suggested as soon it appears again ...

 

[mm1352000]

Anyway if you say it doesn't come from the tuner side...

I'm not saying that. It could be the tuner... or it might not be. Continuity errors are very "generic". They just mean that the stream is missing parts. An investigation always needs to be done to determine exactly what is causing it.

Does the problem still happen now?
If yes, one thing you could check is whether the problem only affects certain channels. If the problem only affects DVB-S2 channels (and not DVB-S channels) then the problem may be something that I changed in the patch.

 

[pur_berger]

Love generic errors

As i know now what data you require and what to loock after I will collect them when the problems appears again and report back ASAP

Thx for supporting me here.

 

[pur_berger]

Ok ... seems as moving the timeshift to the Ramdisk has solved the stopping issue - I know telling that it has worked before is excatly what you want to hear therfopre I dont say it

Still there are pixel errors from time to time - the logs show bad signal (?) but it is for sure always ok - also no special weather conditions which could cause this. Using the patch doesn't show signal strength in the serverconsole and signal quality is always showing 100%.

I attach the logs for you but if there is nothing you can do about this its ok fine - my old man is happy that it runs

 

[mm1352000]

Ok ... seems as moving the timeshift to the Ramdisk has solved the stopping issue

...which tells me that the problem is/was most likely related to the timeshift folder access/IO speed.
Are you certain that the timeshift folder was previously on an SSD, and that the SSD was not loaded?
If yes, maybe consider my answer just given here:
https://forum.team-mediaportal.com/threads/continuity-errors-after-windows-10-update.133175/

 

[pur_berger]

True enough and of course something to look after. Still this doesn't explain the pixel errors. Using a Ramdisk is no problem here but if this is the reason it is somthong to be thought of for future design of tvserver.