home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Installation, configuration support
Tuning Data Correct But Displayed Program Is Not
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1173227" data-attributes="member: 82144"><p>Okay, I understand now.</p><p></p><p>TV Server simply tells the tuner to tune with the tuning parameters that you supply. If the tuner ends up locking onto the wrong transponder then that's likely to be due to one or more of the following factors:</p><ol> <li data-xf-list-type="ol">An error in the tuning parameters you've supplied.</li> <li data-xf-list-type="ol">An issue with the tuner driver's tuning algorithm.<br /> </li> <li data-xf-list-type="ol">LNB LOF drift.</li> </ol><p>In any case it's got nothing to do with TV Server, and TV Server will have no idea that the tuner has locked onto the wrong transponder.</p><p></p><p>According to <a href="http://www.lyngsat.com/SES-1-and-DirecTV-4S-8.html" target="_blank">Lyngsat</a> there are three transponders with the same polarisation, symbol rate, FEC etc. within a 10 MHz carrier frequency range (3953, 3957, and 3961 MHz). That's a perfect recipe for a combination of (2) and (3) above to cause the problem you're seeing. Especially if there's a significant difference in the signal strength/quality of the transponders.</p><p></p><p>To resolve this situation, please start by confirming that the parameters that you're using for your scan are correct:</p><ul> <li data-xf-list-type="ul">frequency = 3953000 / 3957000 / 3961000 kHz</li> <li data-xf-list-type="ul">symbol rate = 2734 ks/s</li> <li data-xf-list-type="ul">polarisation = vertical</li> <li data-xf-list-type="ul">modulation = <strong>not set</strong></li> <li data-xf-list-type="ul">inner FEC rate = 5/6</li> <li data-xf-list-type="ul">pilot = not set</li> <li data-xf-list-type="ul">roll-off = not set</li> </ul><p>Note the modulation setting. That is the setting you should use for DVB-S QPSK.</p><p></p><p>If you were already using the correct parameters and/or using the correct parameters doesn't help, try modifying the frequency slightly (3952000,</p><p>3951000, 3950000 etc.). When transponder carrier frequencies are so close, even the slightest error in the LNB LOF can mean that the tuner will lock onto the wrong transponder. For example, if the LNB LOF is actually 5149 MHz instead of 5150 MHz and you attempt to scan 3953 MHz, the tuner will actually scan 3954 MHz (...which makes it that much more likely to lock on the 3957 "Decades" transponder, especially if 3957 is received with stronger signal strength/quality than 3953).</p><p></p><p></p><p>I don't know what you mean by "cards folder", but yes TV Server will be using whatever [BDA] driver you've installed. TV Server couldn't "load something different" even if it wanted to. The way Windows works is that you install one driver, and then all software - TV Server, DVB Dream etc. - must use that driver.</p><p></p><p></p><p>I don't think there have been any significant changes to Windows' tuner support (BDA/PBDA) since Windows 7. So yes it's fine to use the same tuner driver for Windows 10 as for Windows 8/8.1.</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1173227, member: 82144"] Okay, I understand now. TV Server simply tells the tuner to tune with the tuning parameters that you supply. If the tuner ends up locking onto the wrong transponder then that's likely to be due to one or more of the following factors: [LIST=1] [*]An error in the tuning parameters you've supplied. [*]An issue with the tuner driver's tuning algorithm. [*]LNB LOF drift. [/LIST] In any case it's got nothing to do with TV Server, and TV Server will have no idea that the tuner has locked onto the wrong transponder. According to [URL='http://www.lyngsat.com/SES-1-and-DirecTV-4S-8.html']Lyngsat[/URL] there are three transponders with the same polarisation, symbol rate, FEC etc. within a 10 MHz carrier frequency range (3953, 3957, and 3961 MHz). That's a perfect recipe for a combination of (2) and (3) above to cause the problem you're seeing. Especially if there's a significant difference in the signal strength/quality of the transponders. To resolve this situation, please start by confirming that the parameters that you're using for your scan are correct: [LIST] [*]frequency = 3953000 / 3957000 / 3961000 kHz [*]symbol rate = 2734 ks/s [*]polarisation = vertical [*]modulation = [B]not set[/B] [*]inner FEC rate = 5/6 [*]pilot = not set [*]roll-off = not set [/LIST] Note the modulation setting. That is the setting you should use for DVB-S QPSK. If you were already using the correct parameters and/or using the correct parameters doesn't help, try modifying the frequency slightly (3952000, 3951000, 3950000 etc.). When transponder carrier frequencies are so close, even the slightest error in the LNB LOF can mean that the tuner will lock onto the wrong transponder. For example, if the LNB LOF is actually 5149 MHz instead of 5150 MHz and you attempt to scan 3953 MHz, the tuner will actually scan 3954 MHz (...which makes it that much more likely to lock on the 3957 "Decades" transponder, especially if 3957 is received with stronger signal strength/quality than 3953). I don't know what you mean by "cards folder", but yes TV Server will be using whatever [BDA] driver you've installed. TV Server couldn't "load something different" even if it wanted to. The way Windows works is that you install one driver, and then all software - TV Server, DVB Dream etc. - must use that driver. I don't think there have been any significant changes to Windows' tuner support (BDA/PBDA) since Windows 7. So yes it's fine to use the same tuner driver for Windows 10 as for Windows 8/8.1. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Installation, configuration support
Tuning Data Correct But Displayed Program Is Not
Contact us
RSS
Top
Bottom