Muxes "auto" unchecked

nunu mp

Hi,

i have an issue with TvHeadend 3.x (used on a NAS). Sometime, when tvheadend service is started, one or 2 muxes are disabled even if i recheck them, it could be unchecked next start (and not same muxes). I addn't this issue with 2.x version.

Which kind on event makes the muxe to be unchecked by tvheadend ?

regards
nunu

Adam Sutton

The only thing that will automatically disable muxes is my code that checks for invalid (un-tunable) ones. Note: un-tunable in this context does not mean an inability to receive the signal etc... It actually means the freq (or other params) are outside of the valid range for the tuner.

Check to see if you're getting any errors such as these in your logs:

Oct 19 07:48:11 [ERROR]:dvb: "/dev/dvb/adapter1" tuning to "99,999,980 kHz Vertical (Default (Port 0, Universal LNB))" -- Front configuration failed -- Invalid argument, frequency: 89399980

This is an invalid mux that gets auto detected on ASTRA-28.2 and so is rejected. If this rejection code is rejecting things it shouldn't then I'll take a look.

Adam

IchBeiTVH

Adam Sutton

Hi Adam

you said: The only thing that will automatically disable muxes is my code that checks for invalid (un-tunable) ones.
Can you share this code ? Or give me a hint where to start ?

Thanks Tobi

Chris Merrett

Hi Adam,

I've found that in the latest official release in the PPA and with a freshly build .deb from the Git repo, the "99,999,980 kHz" mux doesn't get automatically rejected/removed/disabled. I was wondering why I couldn't tune anything despite service scans running fine until I stumbled upon this post. I'll log a bug when I get home from work if you don't get to it first.

Cheers.