You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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
My input setup is: 4 converters (pointing to 4 differents sats) with 4 outputs each + 4 diseqc switches.
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.
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).
The text was updated successfully, but these errors were encountered: