Project

General

Profile

Bug #1196

channels with low signal not opening at all

Added by hanza hanza about 9 years ago. Updated over 6 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
Category:
DVB
Target version:
Start date:
2012-09-03
Due date:
% Done:

100%

Estimated time:
Found in version:
3.1.632.gebf95.dirty
Affected Versions:

Description

today i upgrade tvheadend to latest version from git
i notice that channels with low signal are not opening at all
with previous version everything is fine, there is some stuttering but channel at least is opening
http://pastebin.com/ZEjNwBUR

adapter settings:
Autodetect muxes: X
Skip initial scan: X
Idle scanning:
Skip service availability check when mapping: X
Monitor signal quality:
Disable PMT monitoring: X
Write full DVB MUX to disk:
NIT-o Network ID:
Extra priority:
DiSEqC version:
Turn off LNB when idle:

Associated revisions

Revision 0999618c (diff)
Added by Adam Sutton about 9 years ago

Ensure that quality monitoring is properly adhered to and also low quality services are not completely ignored. Fixes #1196.

History

#1

Updated by Adam Sutton about 9 years ago

  • Category set to DVB
  • Found in version changed from HTS Tvheadend 3.1.632.gebf95.dirty to 3.1.632.gebf95.dirty

Can you clarify what you mean by previous version?

And what configuration you previously had, since many of the options you've ticked relate to new functionality.

Adam

#2

Updated by hanza hanza about 9 years ago

revision 3db460f4 on 08/31/2012 was working fine

adapter settings:
adapter settings:
Autodetect muxes: X
Skip initial scan: X
Idle scanning:
Skip service availability check when mapping: X
Monitor signal quality:
Write full DVB MUX to disk:
NIT-o Network ID:
Extra priority:
DiSEqC version:
Turn off LNB when idle:

also on previous version if i enable "Monitor signal quality:" then debug says "signal too low" and channel wont open, and if i uncheck it then it opens fine
but on newest git version it doesn't matter enabled or not, it doaesn even show message "low signal" etc.

#3

Updated by Adam Sutton about 9 years ago

ah, now that sounds familiar ;) I think that might be happening on my own system and was something I wanted to look into.

I think its related to the way the whole idle/mux scanner works now. There was some discussion about removing the whole signal monitoring stuff but I wanted to keep the option for this very reason.

However its perfectly possible that I screwed up in the mod and essentially forced the option on unintentionally.

I'll take a look.

Adam

#4

Updated by Adam Sutton about 9 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100
#5

Updated by Adam Sutton about 9 years ago

  • Target version set to 3.2
#6

Updated by Jonathan Turner over 6 years ago

Hi I seem to be having this problem on build 3.4~wheezy. I have multiplexes with quality around 50% but I am unable to watch the channels. I see this in the logs...

May 23 09:03:06 jttv tvheadend[2291]: Service: Subscription "HTTP": Skipping "Afatech AF9033 (DVB-T)/London: 490,000 kHz/BBC ONE Lon" -- not enabled
May 23 09:03:06 jttv tvheadend[2291]: subscription: No transponder available for subscription "HTTP" to channel "BBC ONE Lon" 
May 23 09:03:06 jttv tvheadend[2291]: webui: Couldn't start streaming /stream/channelid/37?ticket=D2A2F1930CA4EE54A3EE704043F804A490D26120, No service enabled
May 23 09:03:06 jttv tvheadend[2291]: subscription: "HTTP" unsubscribing from "BBC ONE Lon" 
May 23 09:03:06 jttv tvheadend[2291]: Service: Subscription "HTTP": Skipping "Afatech AF9033 (DVB-T)/London: 490,000 kHz/BBC ONE Lon" -- not enabled
May 23 09:03:06 jttv tvheadend[2291]: subscription: No transponder available for subscription "HTTP" to channel "BBC ONE Lon" 
May 23 09:03:06 jttv tvheadend[2291]: webui: Couldn't start streaming /stream/channelid/37?ticket=D2A2F1930CA4EE54A3EE704043F804A490D26120, No service enabled

I have these settings for the adapter

{
    "enabled": 1,
    "fe_path": "/dev/dvb/adapter0/frontend0",
    "dmx_path": "/dev/dvb/adapter0/demux0",
    "dvr_path": "/dev/dvb/adapter0/dvr0",
    "type": "DVB-T",
    "displayname": "Afatech AF9033 (DVB-T)",
    "autodiscovery": 1,
    "idlescan": 1,
    "idleclose": 0,
    "skip_checksubscr": 1,
    "sidtochan": 0,
    "qmon": 0,
    "poweroff": 0,
    "nitoid": 0,
    "diseqc_version": 0,
    "diseqc_repeats": 0,
    "extrapriority": 0,
    "skip_initialscan": 0,
    "disable_pmt_monitor": 0,
    "full_mux_rx": -1,
    "grace_period": 0
}

I have checked that I have turned off "Monitor signal quality". Not sure if it is related but I see lines like this in the logs eventhough this is turned of...

May 23 09:05:56 jttv tvheadend[2291]: dvb: "London: 490,000 kHz" on adapter "Afatech AF9033 (DVB-T)", status changed to OK
May 23 09:05:57 jttv tvheadend[2291]: dvb: "London: 490,000 kHz" on adapter "Afatech AF9033 (DVB-T)", status changed to Bad signal

The aerial I'm using is the same as that which I plug my TV into and I have no issues in viewing these channels on the TV.

Thanks.

#7

Updated by B C over 6 years ago

based on your last log it seems the adapter is not as good as your TV and simply can't receive it properly.

May 23 09:03:06 jttv tvheadend2291: Service: Subscription "HTTP": Skipping "Afatech AF9033 (DVB-T)/London: 490,000 kHz/BBC ONE Lon" -- not enabled
not enabled --> got disabled somehow, maybe because of your recepion problems, you can try to rescan, but as long as you get those Bad signal messages it won't help anyway.

Also available in: Atom PDF