Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 808439" data-attributes="member: 82144">Hi againDarn. Like you say, at least you know it is very unlikely to be hardware now though.TV Server's resilience to stream corruption has been beefed up by miroslav22 in MP 1.2.x. However I don't think the client was touched. The idea is that the server should never crash (else you miss recordings) but the client crash is not so bad (if that can ever be said about a crash! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />).My advice would be that if this is truly a signal problem then invest in fixing it at the source. Anything that we attempt to do in the code is going to be time consuming and ultimately not crash-proof. The last set of logs aren't 100% conclusive - just more circumstantial evidence of the same thing I think. Continuity errors in the TsWriter log -&gt; stream corruption =&gt; bad signal, HDD stress etc. etc. etc. I can say that the tuning parameters for that transponder appear to be correct so at least that is one thing you can cross off the list.I think that's a really sensible idea. Definitely let me know how you get on with that.mm</blockquote>

[QUOTE="mm1352000, post: 808439, member: 82144"] Hi again Darn. Like you say, at least you know it is very unlikely to be hardware now though. TV Server's resilience to stream corruption has been beefed up by miroslav22 in MP 1.2.x. However I don't think the client was touched. The idea is that the server should never crash (else you miss recordings) but the client crash is not so bad (if that can ever be said about a crash! :)). My advice would be that if this is truly a signal problem then invest in fixing it at the source. Anything that we attempt to do in the code is going to be time consuming and ultimately not crash-proof. The last set of logs aren't 100% conclusive - just more circumstantial evidence of the same thing I think. Continuity errors in the TsWriter log -> stream corruption => bad signal, HDD stress etc. etc. etc. I can say that the tuning parameters for that transponder appear to be correct so at least that is one thing you can cross off the list. I think that's a really sensible idea. Definitely let me know how you get on with that. mm [/QUOTE]

Verification