Log in
Register
Menu
Log in
Register
Home
What's new
Latest activity
Authors
Forums
New posts
Search forums
What's new
New posts
Latest activity
Members
Current visitors
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
What's On, Transponder and channel support
Daily Transponder News and Updates
Multi-stream update @ 5 west
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="deeptho" data-source="post: 1119235" data-attributes="member: 215446"><p>The information comes from the drivers, and agrees typically with what is on kingofsat.net,</p><p>so I do not have reasons to doubt it (there is more doubt on other reported parameters. Eg. the </p><p>PLS code reported in the figure may be a bug). Of course for 5.0W that website is a bit out of date right now. </p><p></p><p>One thing to be careful of: some programs (also mine) make an initial estimate for symbolrate</p><p>to help the driver. In blindscan the driver then finds the correct symbolrate. One possible bug is</p><p>that the driver just reports back what you put as the initial value and not the real value locked on to. </p><p>This then affects all programs.</p><p></p><p>Such bugs really depend on the driver and not the end user program. Windows drivers are by crazycat,</p><p>but in the end it is likely that they come from the same source as the linux drivers.</p><p></p><p>I am curious: which card did you use under linux and which drivers?</p><p></p><p>About tvheadend: </p><p>1. the standard drivers impose a minimum symbolrate of 1000 KSamples/second. So unless you change to my drivers or edit the tbs sources, tvheadend (and no other program) will never be able to lock them.</p><p></p><p>2 Even then it will be a matter of luck: if the transponder takes a long time to lock, tvheadend will timeout and try to retune. tvheadend also has nasty bugs which render some muxes impossible to tune (they </p><p>stop working and work again after restarting tvheadend)</p><p></p><p>Locking or not locking depends on a lot of factors. I have tried a lot to improve locking in the drivers, but when going to extremes there are always compromises (+documentation is unclear), and some </p><p>transponders with low symbolrates take a while to lock. </p><p></p><p>There is also the issues of frequency offsets of the LNB. Some LNBs</p><p>have errors up to 2 Mhz (I have one of thise). So if you just enter the frequency, it will be 2Mhz wrong, which is much more than the transponder bandwidth, and this makes it a lot harder to catch a narrow band signal (even though the TBS drivers have some tolerances built in)</p></blockquote><p></p>
[QUOTE="deeptho, post: 1119235, member: 215446"] The information comes from the drivers, and agrees typically with what is on kingofsat.net, so I do not have reasons to doubt it (there is more doubt on other reported parameters. Eg. the PLS code reported in the figure may be a bug). Of course for 5.0W that website is a bit out of date right now. One thing to be careful of: some programs (also mine) make an initial estimate for symbolrate to help the driver. In blindscan the driver then finds the correct symbolrate. One possible bug is that the driver just reports back what you put as the initial value and not the real value locked on to. This then affects all programs. Such bugs really depend on the driver and not the end user program. Windows drivers are by crazycat, but in the end it is likely that they come from the same source as the linux drivers. I am curious: which card did you use under linux and which drivers? About tvheadend: 1. the standard drivers impose a minimum symbolrate of 1000 KSamples/second. So unless you change to my drivers or edit the tbs sources, tvheadend (and no other program) will never be able to lock them. 2 Even then it will be a matter of luck: if the transponder takes a long time to lock, tvheadend will timeout and try to retune. tvheadend also has nasty bugs which render some muxes impossible to tune (they stop working and work again after restarting tvheadend) Locking or not locking depends on a lot of factors. I have tried a lot to improve locking in the drivers, but when going to extremes there are always compromises (+documentation is unclear), and some transponders with low symbolrates take a while to lock. There is also the issues of frequency offsets of the LNB. Some LNBs have errors up to 2 Mhz (I have one of thise). So if you just enter the frequency, it will be 2Mhz wrong, which is much more than the transponder bandwidth, and this makes it a lot harder to catch a narrow band signal (even though the TBS drivers have some tolerances built in) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
What's On, Transponder and channel support
Daily Transponder News and Updates
Multi-stream update @ 5 west
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top
