Project

General

Profile

Bug #1429

problem with empty service names

Added by Chico Zola about 12 years ago. Updated over 11 years ago.

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

0%

Estimated time:
Found in version:
3.3.163~ge16707b
Affected Versions:

Description

Upgraded from 2.12 to 3.3.163~ge16707b. It worked great until I deleted all muxes and made a new scan. I realized that service names was missing on many channels. To make sure it had nothing to do with my setup i deleted .hts and installed 2.12 again and made a new scan. 2.12 sets "almost" all service names correct but Build: 3.3.163~ge16707b does not. Found this old closed bug #1326 smells like the same?? Great job guys!

History

#1

Updated by Adam Sutton about 12 years ago

Yeah I think my believe was that bug related specifically to some stuff that was added (naively) to the 3.2 release tree.

It may still be an issue in master, so I'll keep this open till I can investigate. It might be worth checking whether things work in 3.2 as that's latest stable release.

3.3 will get a heavy influx of dev changes in the coming weeks, so don't expect it to be stable until we reach the 3.4 release cycle.

Adam

#2

Updated by Per-Inge Hallin about 12 years ago

I have 3 installation, 2 is working fine, but on 1 the .hts directory isn't updated correctly and there are no service names with Tvheadend 3.3.183~g5d2197c.
I compiled the release/3.2 branch and this one worked better. The .hts directory was build OK, but service names was missing on one mux. Actually the first mux tuned by tvheadend. A stranged thing was that tvheadend showed that it had found 8 services even before any mux was scanned.
After started tvheadend again without .hts, .hts was build OK, this time I choosed another location to start with and then the wanted location. At this time all service names was OK.
I think something is going too fast.

System data
Hardware
Device path:
/dev/dvb/adapter0
Device name:
FireDTV T/CI
Host connection:
PCI
Frequency range:
49000 kHz - 861000 kHz, in steps of 62 kHz
Status
Currently tuned to:
Teracom_Mux_1: 490,000 kHz
Services:
46
Muxes:
7
Muxes awaiting initial scan:
0

System
Release 12.10 (quantal) 64-bit
Kernel Linux 3.5.0-19-generic
GNOME 3.6.0
Memory: 3.9 GIB
Processor: Pentium Dual-Core CPU E5200

#3

Updated by Yon Belew about 12 years ago

Same issue with empty service names. Tried both 3.2 and git on HDHR Prime. Any updates on this one? Thanks.

#4

Updated by m 321liftoff almost 12 years ago

I had this issue using master git 5d2197c30f (~Nov 29, 2012) and ATSC in the US.

#5

Updated by Yon Belew almost 12 years ago

m 321liftoff wrote:

I had this issue using master git 5d2197c30f (~Nov 29, 2012) and ATSC in the US.

And now it's fixed?

#6

Updated by Adam Sutton almost 12 years ago

  • Category changed from General to DVB
  • Status changed from New to Accepted

I think there are lots of related errors about empty service names, mostly they relate to use of HDHR in US.

Adam

#7

Updated by Adam Sutton almost 12 years ago

  • Status changed from Accepted to Need feedback

Can you please check if this is still happening?

Adam

#8

Updated by m 321liftoff almost 12 years ago

Starting with what version? (I assume there was a patch)

#9

Updated by Adam Sutton almost 12 years ago

Just pick up latest master. I've been working on some changes to the scanning, its still not perfect but this particular issue "might" have been fixed. Though no promises.

Adam

#10

Updated by Per-Inge Hallin almost 12 years ago

I compiled master today.
All multiplexes showed 100%.
Scan didn't start.
This is the terminal print out
p-i@pi-System-xbmc:~/tvheadend$ tvheadend -C
Feb 09 15:58:53 [ INFO]:START: initialising
Feb 09 15:58:53 [WARNING]:access: Created default wide open access controle entry
Feb 09 15:58:53 [ INFO]:charset: 71 entries loaded
Feb 09 15:58:53 [ INFO]:dvb: Found adapter /dev/dvb/adapter0 (FireDTV T/CI) via PCI
Feb 09 15:58:53 [ INFO]:CSA: Using SSE2 128bit parallel descrambling
Feb 09 15:58:53 [ INFO]:epggrab: module eit created
Feb 09 15:58:53 [ INFO]:epggrab: module uk_freesat created
Feb 09 15:58:53 [ INFO]:epggrab: module uk_freeview created
Feb 09 15:58:53 [ INFO]:epggrab: module viasat_baltic created
Feb 09 15:58:53 [ INFO]:epggrab: module opentv-skyit created
Feb 09 15:58:53 [ INFO]:epggrab: module opentv-skyuk created
Feb 09 15:58:53 [ INFO]:epggrab: module opentv-ausat created
Feb 09 15:58:53 [ INFO]:epggrab: module pyepg created
Feb 09 15:58:53 [ INFO]:epggrab: module xmltv created
Feb 09 15:58:53 [ INFO]:epgdb: loaded v2
Feb 09 15:58:53 [ INFO]:epgdb: channels 0
Feb 09 15:58:53 [ INFO]:epgdb: brands 0
Feb 09 15:58:53 [ INFO]:epgdb: seasons 0
Feb 09 15:58:53 [ INFO]:epgdb: episodes 111
Feb 09 15:58:53 [ INFO]:epgdb: broadcasts 0
Feb 09 15:58:53 [ INFO]:dvr: Creating new configuration ''
Feb 09 15:58:53 [WARNING]:dvr: Output directory for video recording is not yet configured for DVR configuration "". Defaulting to to "/home/p-i/Videos". This can be changed from the web user interface.
Feb 09 15:58:53 [ NOTICE]:START: HTS Tvheadend version 3.3.465~g79c134f started, running as PID:20098 UID:1000 GID:1000, settings located in '/home/p-i/.hts/tvheadend'
Feb 09 16:00:54 [ NOTICE]:dvb: New mux "730,000 kHz" created by built-in configuration from "dvb-t_se_Stockholm_Nacka"
Feb 09 16:00:54 [ NOTICE]:dvb: New mux "746,000 kHz" created by built-in configuration from "dvb-t_se_Stockholm_Nacka"
Feb 09 16:00:54 [ NOTICE]:dvb: New mux "706,000 kHz" created by built-in configuration from "dvb-t_se_Stockholm_Nacka"
Feb 09 16:00:54 [ NOTICE]:dvb: New mux "754,000 kHz" created by built-in configuration from "dvb-t_se_Stockholm_Nacka"
Feb 09 16:00:54 [ NOTICE]:dvb: New mux "642,000 kHz" created by built-in configuration from "dvb-t_se_Stockholm_Nacka"
Feb 09 16:00:54 [ NOTICE]:dvb: New mux "490,000 kHz" created by built-in configuration from "dvb-t_se_Stockholm_Nacka"

I also tried to add muxes manually, but it wasn't possible to select any "Constellation"

Compiled the 3.2 version which worked before. Now scan started, but no services was found.

#11

Updated by Adam Sutton almost 12 years ago

Please note that if you're using a completely fresh configuration you must enable the adapters for them to be operational.

Adam

#12

Updated by Chico Zola almost 12 years ago

Just configured a new system and it seems like the scanning now sets the service names in almost every case. some muxes seems to add some services that are without any information when clicking on service details and according to lyngsat it seems like a junk freq. Thanks

#13

Updated by Adam Sutton almost 12 years ago

  • Status changed from Need feedback to Fixed

The extra service listing is because I've been a bit more open in what gets accepted, the main reason is that previous approaches did not allow detection of currently off-air services (which is a PITA when first setting up). Hopefully these additional services shouldn't cause too much trouble (except possibly slowing the UI) and there is a big rewrite of all the DVB code anyway for post 3.4.

Closing.

#14

Updated by Graeme Russ over 11 years ago

I have just built commit e9ce02138e81d0dd94a2b155e57fda282063c008 and have missing service names for all ABC and SBS channels (Newcastle, Australia)

Forum post here: https://tvheadend.org/boards/4/topics/8117

Also available in: Atom PDF