Tvheadend

When you say HDHR3 are you referring to the cable card prime model?

No, the HDHomerun 3 US. Not the prime (http://www.silicondust.com/products/models/hdhr3-us/)

I don't think this is strictly a Synology issue. I'm running TVH on arch linux with HDHR Prime, and both git and 3.2 have the same problem - no service names.

Eric L wrote:

Well, I just started over again last night.
Repackaged my HDHomerun spk.
uninstalled TVheadend
uninstalled HDHR3.
Rebooted the NAS
installed Tvheadend without starting it.
installed my HDHR3 spk
choose ATSC while installing it.
All the logs looked good after the install
dmesg
[...]

dvbhdhomerun.log
[...]

Restarted the NAS (hdhr3 and tvheadend are started on startup)
Go to tvheadend and launch a scan with us_ATSC_center_frequencies_8VSB
68Muxes awaiting initial scan
When it was down to 0, 27 services were found once again without any name :(

Click Map DVB services to channels (it is still clickable after, I can click it 3829 times.. always just print "Service probe started" that is.
Tvhead console
[...]

Now, obviously still does not work.
Any ideas where I could debug this and why my services does not have names??
Is it normal I can't even start the channel when I click "Play" on the service tab?
It prints
[...]
And start vlc in the browser but nothing else happen.

Thanks for anyone who could help me. I'm willing to test anything you're asking me to debug this but I need this to WORK! I've been working on this for a month, without tv lol

Hi,

Can you give me your spk for DS1512+ please?

Thx

I'm having a similar issue with an HDHR3. I get a ton of services (FINALLY!), but I'm unable to map them to channels.

Perhaps if documentation were provided as a fallback on how these could be manually added? I learned that one can add multiplexes manually by adding files in a particular location. This proved very useful since I was unable to batch-add multiplexes. The reason this was important is that the normal scanning would not find any services, even though I had scan files (for dvbscan and w_scan) that were indeed able to find services.

I generated multiplex files based on a manually-added one, and lo and behold: services appeared! I see that services also generate files in the filesystem with information (in the dvbtransports directory). As such, logic suggests that the channel mappings happen in a similar fashion. However, I've not been able to find documentation on this and I lack the time to go source-spelunking to figure things out on my own...

Help will be appreciated!

Thanks!

Having said all that, it looks as if the files are in JSON format. What I don't know is the allowed properties, expected structure, etc... I presume the channel mappings will be something along the lines of:

{
"channel_name" : "some-channel-name",
"adapter" : "<adapter-name>",
"frequency" : <service-frequency>,
"service_id" : "the ID of the service in question"
}

This given that the name for each service's file is in the form dvbtransports/${adapter}${service_frequency}/${adapter}${service_frequency}_${service_id}

Perhaps the filename for the channel is the actual channel name (i.e. obviating the need for a channel_name field)?

Cheers...

Looking at my setup... if this is helpful... each channel file in /home/hts/.hts/tvheadend/channels has this kind of entry:

$ more xxx
{
        "name": "<string>",
        "tags": [
                <numeric>,
                <numeric>,
                <numeric>
        ],
        "dvr_extra_time_pre": <numeric>,
        "dvr_extra_time_post": <numeric>,
        "channel_number": <numeric>
}

I think the filename of each of these is simply the logical sequence (e.g. how the channels are passed to XBMC); the key is the channel_number field, which will tie this channel to something that then maps it to services, I suspect.

The tags then map to entries in /home/.hts/tvheadend/channeltags files:

$ more 1
{
        "enabled": 1,
        "internal": 0,
        "titledIcon": 0,
        "name": "TV channels",
        "comment": "",
        "icon": "",
        "id": 1
}

I'll see if I can see the mapping to mux/services at all (no HDHR here, though, so this could be futile).

Nope, not sure that the channel number is that relevant - it could just be a sequence. If I look at a specific channel (randomly, it's channel file number 120, internally identified as channel_number 834 and named CH NINE UK) and try and trace that, neither of those channel numbers seem to appear elsewhere. However, I can find the channel name:

$ find . | xargs grep NINE
./channels/120: "name": "CH NINE UK",
./dvbtransports/_dev_dvb_adapter1_NXP_TDA1007112560000_H/_dev_dvb_adapter1_NXP_TDA1007112560000_H_d335: "servicename": "CH NINE UK",
./dvbtransports/_dev_dvb_adapter1_NXP_TDA1007112560000_H/_dev_dvb_adapter1_NXP_TDA1007112560000_H_d335: "channelname": "CH NINE UK",

... and those are the only references.

$ more ./dvbtransports/_dev_dvb_adapter1_NXP_TDA1007112560000_H/_dev_dvb_adapter1_NXP_TDA1007112560000_H_d335
{
        "service_id": 54069,
        "pmt": 259,
        "stype": 1,
        "scrambled": 0,
        "channel": 0,
        "provider": "BSkyB",
        "servicename": "CH NINE UK",
        "channelname": "CH NINE UK",
        "mapped": 1,
        "dvb_eit_enable": 1,
        "pcr": 2352,
        "disabled": 0,
        "stream": {
                "pid": 2352,
                "type": "MPEG2VIDEO",
                "position": 0
        },
        "stream": {
                "pid": 2353,
                "type": "MPEG2AUDIO",
                "position": 1,
                "language": "eng" 
        }
}

So it looks like service is mapped to channel based on the string value of the name. However, how you'd go about generating all the numeric values here is anyone's guess - but you may have all of those because you said that you were now discovering services.

This is helpful, thanks!

However, it seems that naming the channels manually by clicking on "unmapped" also works

I'm able to watch TV via OpenELEC (albeit no channel logos, no programming list, etc). My problem is I live outside the US/Canada, and it will be next to impossible to get meaningful XMLTV feeds for the service(s) I have available to me.

TVGuide does keep a detailed listing of the programming in my local service, but there's no way that I've found to extract that data in XMLTV format somehow (let alone the fact that the extraction would require some massaging due to the nuances of my setup...long story...).

Still - I got it working, but I'd like to figure out what the expectations are in terms of relating to what an XMLTV's output would be. For instance, the XMLTV <channel> element has an "id" attribute. Does that have to match the manually-selected channel name exactly? Or is it enough for that manually-selected name to match one of the channel's <display-name> elements? Can the icon be referenced using smb:// URLs (i.e. are they fetched through XBMC's file access service?)?

These are things I can live without at the moment. However, it would be nice to eventually have them working.

Cheers!

On a side note, I have no idea why all of a sudden it started locating services. It happened on my PC, actually, when I installed TVHeadend on Ubuntu so I'd be able to fiddle with it more freely. The Ubuntu installation began finding services, so I just copied the services and mux lists over to the OpenELEC installation and that took care of that.

Then I took the time to filter out the cruft, and voila! Things are "working as intended".

The reason they're not working fully is because my cable service is analog-ish with only some digital channels. This is by design from the cable company to demo HD channels on TVs with QAM-capable tuners (like mine). However, the #$!#$@!# REQUIRE me to buy a cable box from them regardless of the fact that I have all the equipment I need to receive their clear QAM transmissions (yes, it's clear QAM - they control access by MAC address...).

Anyhoo... I wanted to see how the "internet tv" thing worked through OpenELEC/XBMC, to see if it was worth pursuing digital service (i.e. if I liked the experience, etc). I.e. if it didn't take too long to switch channels, image quality, etc.

So far I'm happy, but I'll take a few days to observe more closely and make my decision from that.

Thanks for the quick replies! That channel mapping info will certainly come in handy!

Unless you can find very specifically from someone in the same country on the same provider what the channel names should be - including spaces, case sensitivity, etc.?

If OTA doesn't work, perhaps that would be good enough for XMLTV. Failing that, it'd be a case of running the relevant XMLTV grabber and taking the output apart to see what tallies between channel lists and EPG data.

Logos, you can add locally if needed based on the channel name that's being passed to XBMC.

Ok...I figured as much. I wasn't very hopeful - this is rather specialized stuff and if it's not readily available, it's likely nobody's done it yet.

On a side note, do you know why there is no "bulk mux import" option for TVHeadend? This seems to me like rather basic functionality to support areas which aren't covered under the standard, burned-in locations. In my case, it would have facilitated matters considerably.

Also, importing channels.conf (or similar) files to define services based on known information can be both a time saver, and help resolve issues like I was having when the scanning wasn't having any luck.

Food for future thought...

Cheers!

I have to pass on those... maybe worth raising a feature request for the import functionality?

I am using the Raspbery Pi B OpenElec 4.1.2 and I think I have version 3.4.1.2 TVHeadEnd with a HDHomeRun Dual US ATSC and I have the same issue. The Mux will not map channel names to the service.
Any ideas or help would be great