MikeW
24-11-12, 13:40
After going to the new Vix vuduo-3.0.204 I keep getting these "Tuning failed" errors. I can tune into some channels, while other fail.
Sometimes it succeeds tuning the channel, but still display the error, while the picture breaks up (pixelation and freeze)
From the logs (attached), I found numerous "incorrect transponder tuned!!!", which may indicate what could be wrong, but I don't know how to fix this.
My setup is:
VuDuo twin tuner (+ USB DVBT), using Canal Digital (Denmark/Scandinavia), twin Universal LNB, set to 0.8W Thor/Intelsat Ku band. Signal strength is 85-95%, just fine.
I have tried:
Factory reset, full channel search, all imagineable tuner configurations, all updates releases (and betas) from .204 until current (.439)
Checking the Sat search, "manual transponder" is chosen, which result in very bad/faulty signal, and when set to predefined transponder, everything is OK. However this transponder choice can't be set/saved from here.
I have tried the upgrade 4 times during the past 2 months, and every time been forced to give up, starting to believe this to be HW-errors.
Then reverted to the old, trusty v.2.4 image, and EVERYTHING WORKS just fine.
Completely at a loss here.. please help!
Sometimes it succeeds tuning the channel, but still display the error, while the picture breaks up (pixelation and freeze)
From the logs (attached), I found numerous "incorrect transponder tuned!!!", which may indicate what could be wrong, but I don't know how to fix this.
My setup is:
VuDuo twin tuner (+ USB DVBT), using Canal Digital (Denmark/Scandinavia), twin Universal LNB, set to 0.8W Thor/Intelsat Ku band. Signal strength is 85-95%, just fine.
I have tried:
Factory reset, full channel search, all imagineable tuner configurations, all updates releases (and betas) from .204 until current (.439)
Checking the Sat search, "manual transponder" is chosen, which result in very bad/faulty signal, and when set to predefined transponder, everything is OK. However this transponder choice can't be set/saved from here.
I have tried the upgrade 4 times during the past 2 months, and every time been forced to give up, starting to believe this to be HW-errors.
Then reverted to the old, trusty v.2.4 image, and EVERYTHING WORKS just fine.
Completely at a loss here.. please help!