Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 880060" data-attributes="member: 82144">Hi RonD&nbsp;Nice spotting! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />This is normal behavior for TV Server - it is an attempt to save time in the tuning process. If TV Server thinks the tuner was previously tuned to the same frequency/RF channel then it skips tuning and attempts to just start timeshifting. If you look back to &quot;2012-07-04 15:02:56.011758&quot; before the example in lock_prob.txt you'll see that tuner 2 was previously tuned to the same frequency (565250 kHz), so therefore TV Server doesn't think it needs to force the tuner to tune... so it doesn't.&nbsp;This behavior is one reason why the previously reported test results with QuickTV side by side weren't necessarily &quot;fair&quot; for TV Server.&nbsp;mm</blockquote>

[QUOTE="mm1352000, post: 880060, member: 82144"] Hi RonD Nice spotting! :) This is normal behavior for TV Server - it is an attempt to save time in the tuning process. If TV Server thinks the tuner was previously tuned to the same frequency/RF channel then it skips tuning and attempts to just start timeshifting. If you look back to "2012-07-04 15:02:56.011758" before the example in lock_prob.txt you'll see that tuner 2 was previously tuned to the same frequency (565250 kHz), so therefore TV Server doesn't think it needs to force the tuner to tune... so it doesn't. This behavior is one reason why the previously reported test results with QuickTV side by side weren't necessarily "fair" for TV Server. mm [/QUOTE]

Verification