Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 761632" data-attributes="member: 82144">Understood.It isn't bizzare - it is exactly the point I've been trying to make! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />Australia uses 125 kHz frequency offsets. That means when a channel is &quot;advertised&quot; as being at 191500 kHz, the frequency is actually located at 191625 kHz. Some tuners handle that automatically... ie. when you tell them to tune 191500 kHz they actually check 191333, 191375, 191500, 191625 and 191667 (to handle Aus's 125 kHz offsets and other countries like the UK that use 167 kHz offsets). Your Asus tuner seems to do that. Your Winfast one *does not* seem to do that. With tuners like the Winfast you have to scan the correct frequency - scanning 191667 seems to be &quot;close enough&quot;, but you'd do *much* better if you scanned 191625.So, with that understood, both TV Server and FTR have the capability to handle tuners like your Winfast that don't automatically check the offset frequencies. FTR only seems to check 167 kHz; TV Server checks either [none], 125 or 167 kHz offsets depending on the tuning detail files (which are correct in your case). When TV Server finds channels on an offset (such as 191625 kHz), it saves the frequency in the database as 191625 kHz as expected. FTR does not seem to do that. It seems to save the base frequency (191500) instead of the offset frequency. Your Asus tuner can handle that, but it is screwing up your Winfast tuner.My guess is that rescanning in TV Server fixed the tuning details. Simple as that.mm</blockquote>

[QUOTE="mm1352000, post: 761632, member: 82144"] Understood. It isn't bizzare - it is exactly the point I've been trying to make! ;) Australia uses 125 kHz frequency offsets. That means when a channel is "advertised" as being at 191500 kHz, the frequency is actually located at 191625 kHz. Some tuners handle that automatically... ie. when you tell them to tune 191500 kHz they actually check 191333, 191375, 191500, 191625 and 191667 (to handle Aus's 125 kHz offsets and other countries like the UK that use 167 kHz offsets). Your Asus tuner seems to do that. Your Winfast one *does not* seem to do that. With tuners like the Winfast you have to scan the correct frequency - scanning 191667 seems to be "close enough", but you'd do *much* better if you scanned 191625. So, with that understood, both TV Server and FTR have the capability to handle tuners like your Winfast that don't automatically check the offset frequencies. FTR only seems to check 167 kHz; TV Server checks either [none], 125 or 167 kHz offsets depending on the tuning detail files (which are correct in your case). When TV Server finds channels on an offset (such as 191625 kHz), it saves the frequency in the database as 191625 kHz as expected. FTR does not seem to do that. It seems to save the base frequency (191500) instead of the offset frequency. Your Asus tuner can handle that, but it is screwing up your Winfast tuner. My guess is that rescanning in TV Server fixed the tuning details. Simple as that. mm [/QUOTE]

Verification