Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TBS6985 continuity errors when switching channels #47

Closed
kvaster opened this issue Nov 13, 2014 · 3 comments
Closed

TBS6985 continuity errors when switching channels #47

kvaster opened this issue Nov 13, 2014 · 3 comments
Labels

Comments

@kvaster
Copy link

kvaster commented Nov 13, 2014

Latest update is really good for tbs6985. There is no more continuity errors while using all 4 tuners when there is no channel switch. Maybe there is a way to get rid of all issues on 'software level'...

Watch one channel on first tuner, then launch second channel (on another transponder) on second tuner. I can watch both channels without errors for long time, but continuity errors appears immediatelly on first (or second) tuner in case I'm switching to another channel on second (or first).

@ljalves
Copy link
Owner

ljalves commented Nov 15, 2014

Sometimes the issues on channel switch are caused by a poor quality quad LNB and not to the card/driver itself - one of the LNB inputs gets noise/interference by the another input.
It is usually caused by the lnb switching polarization
If you have the chance make the test (change channels) using 2 separate lnb's.
If in that situation switching channels doesn't affect the stream then you should buy a better LNB or use a multiswitch

@kvaster
Copy link
Author

kvaster commented Nov 15, 2014

It's not the case, case:

  1. My input setup is: 4 converters (pointing to 4 differents sats) with 4 outputs each + 4 diseqc switches.
  2. 1x TBS6985, 2x 6925, 1x 5925
    Problem occurs only on TBS6985 tuners when switchin only other tbs6985 tuner (even if tuners are user different converters). And It is always all OK with 6925 and 5925.

@ljalves
Copy link
Owner

ljalves commented May 2, 2015

From user reports, this issue was proven exist on some motherboard chipsets.
Closing this issue as I don't plan to fix it.

@ljalves ljalves closed this as completed May 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants