HDHomerun Manual Mux Setup

Steve Miller

Hi,

I am trying to setup tvheadend version 3.2 compiled on my Pogoplug. I have the hdhomerun driver built and running. Tvheadend can see the tuner and can control it. My problem is that I am on basic US cable and therefore only have the local unencrypted channels. Regardless of the DVB network that I choose, the scan never finds anything. The hdhomerun tuner does work, as I can control it from Windows. I just verified that it receives a local channel 1521.2 as qam256 just fine.

When I start tvheadend, it reports the version as 3.1.694. However, I built from the 3.2 tar file. I have no idea whether this is expected or not?

When I attempt to add a mux manually, I get a blank light blue window with an ADD button at the very bottom. Other posts state there should be somewhere to enter the frequency, but I have no dialog box for that. When I press the ADD button, then the console used to start tvheadend has the following error message.

"Nov 06 22:17:37 [ERROR]:HTTP: 194.168.1.2: /dvb/addmux/_dev_dvb_adapter0_HDHomeRun_ATSC -- 400" The IP address of 194.168.1.2 is the address of the machine with the web browser. I tried both FireFox and Chrome browsers with the same results.

What am I doing wrong for manual adding of muxes?

Thanks.

---- Steve

Adam Sutton

Ignore the version 3.1.694, it was a mistake in the tarball generation. The latest 3.2 update will fix that.

You should indeed be getting more fields to fill in when adding a mux manually. It sounds like there is something wrong in your browser possibly? (though I note you tried 2 different ones).

Might be worth seeing if Chrome's dev tools indicate some errors with the JS code?

Adam

Steve Miller

I have tried IE, Chrome and Firefox. All three give the blank blue window with just a "add" button at the bottom. Chroms dev tools, assuming that I opened them correctly, do not give any errors when opening the window. The only error occurs when I press the "add" button. However, this could be due to the fact that I did not fill out any of the fields that I cannot see. Below is the error.

POST http://194.168.1.5:9981/dvb/addmux/_dev_dvb_adapter0_HDHomeRun_ATSC 400 (Bad request) ext-base.js:7

I also tried to create my own custom mux list per the wiki article:

https://www.lonelycoder.com/redmine/boards/4/topics/6326

I copied the new file into the /usr/share/dvb/atsc along with the other files already there. I also, checked the permissions on this file and make it similar to the other files. I rebooted and restarted tvheadend. However, when I view the list of available locations, the file that I added is not shown. I followed the same naming convention as the other files. I start with a "us" and then use "-" to separate words. The file format is UNIX and I do not see any differences in the special characters. When I created the file, I just used carriage returns and spaces.

Has the file location of the dvb location files changed? I noticed what the GUI displays has underscores in the names and the actual files that I found has dashes. I cannot figure out what I did wrong.

--- Steve

Steve Miller

Looking at other posts, John Nevill has an excellent detailed writeup entitled, Getting a custom "DVB by Location" from an HDHomeRun Prime. John says "When your file is built, move it to /usr/local/share/tvheadend/data/dvb-scan/atsc." On my system that do not have that directory path. I created all these folders, copied my new file into that location, and restarted tvheadend. However, still no joy.

Can someone check which path these location files are supposed to be stored in?

What creates "/usr/local/share/tvheadend/data/dvb-scan/atsc"? The vast bulk of that tree is not present on my machine. Could this be the root of all my problems? Was I supposed to run something or install some add-on that created this structure?

Thanks.

---- Steve

Adam Sutton

Those directories are normally created by the installation process. What do you have installed? If you're using the deb (rather than "make install", urgh!) then the folder you need will be under /usr/share/tvheadend (NOT /usr/local/share/tvheadend).

Adam

Steve Miller

Well, I freely admit that I am not the smartest guy on the block. All I did was follow along in the README. The README file told me to run configure, then make, and then ./build.linux/tvheadend. Perhaps it would be good to add the make install step to the README.

I ran make install. I rebooted and I again ran ./build.linux/tvheadend. While the folder was created and the location files were copied into that folder, the results for me are the same. The location file that I added is not visible in the list and the manual mux window is still blank.

I see that there is a new tar ball. Later today, I will pull down that version and try it.

----- Steve

Steve Miller

FYI,

I downloaded the new tar ball and rebuilt with the latest source code. The two problems remain. The manual mux box is blank and the custom dvb location file could not be found. After searching through the usr folder, I found that I had four or five sets of these dvb location files in different sub-folders. I appended a unique suffix to each of the Boise files as a flag. When I stopped and restarted tvheadend, I found that Boise still had the correct spelling!!!

Then it dawned on me! Again, I took the README literally and I am executing the binary in the build.linux folder of the source code directory. Apparently, when you do this it uses the different folder for the dvb location folders. I ran the tvheadend that was saved to the /usr/local/bin folder and now it can see my custom location file!

Bob Baird

I have the same problem Steve had. I installed 3.2.18 from Adam Sutton's ppa, and dropped my custom location file in /usr/share/tvheadend/... My file dosen't show up in my list of locations. which tvheadend returns /usr/bin/tvheadend. /usr/local/bin/ is empty. Do I need to delete my install from the ppa and build from source?

Bob Baird

Robert Baird wrote:

> I have the same problem Steve had. I installed 3.2.18 from Adam Sutton's ppa, and dropped my custom location file in /usr/share/tvheadend/... My file dosen't show up in my list of locations. which tvheadend returns /usr/bin/tvheadend. /usr/local/bin/ is empty. Do I need to delete my install from the ppa and build from source?

Update: I named my file incorrectly (us_KS_Salina instead of us-KS-Salina). Fixed that and now it shows up. Still cant get services to map to the channels, but that is an issue for another thread.

Steve Miller

Robert, I also could not get the services to map to the channels. I assumed it was something that I was doing wrong, so I just did it manually. I only have basic cable, so the total number of channels is low. I assigned each service a bogus number like dd1 thorough dd20 and then viewed these channels in XBMC via Live TV. Once I knew the real channel name, I made a list and then renamed the services and channels. For me, I had to do the rename all at once and then tell XBMC to reset the PVR settings. Otherwise, XBMC and TVH were out of sync and then channels got even further screwed up.

Bob Baird

Steve Miller wrote:

> Robert, I also could not get the services to map to the channels. I assumed it was something that I was doing wrong, so I just did it manually. I only have basic cable, so the total number of channels is low. I assigned each service a bogus number like dd1 thorough dd20 and then viewed these channels in XBMC via Live TV. Once I knew the real channel name, I made a list and then renamed the services and channels. For me, I had to do the rename all at once and then tell XBMC to reset the PVR settings. Otherwise, XBMC and TVH were out of sync and then channels got even further screwed up.

Thanks Steve, your solution pushed me in the right direction. Unfortunately I had 51 muxes and 416 services :( After mucking about for a couple of days and reading every post on this forum I figured out that only four of my muxes had unencrypted channels, that left me with 18 services which was much more manageable. Your tip got me up and running from that point on.

K C

Steve:
Did you ever resolve the issue with manually adding muxes? I get the same blue screen with only an "add" button on the bottom. Thanks...

Steve Miller

I never got the add mux manually to work. I got around it by creating a custom location file that had only the muxes that I was interested in. Because I only have basic cable, this was a fairly short list. Then I chose my custom location file and used that to scan for channels. This proved to be easier than adding a mux to a generic list of frequencies.

In my case, I am running on a Pogoplug. So, I suspected the blue screen was due to the limitations of the HW I was using. If your setup is running on a true PC or something with more power than my Pogoplug, you may want to report your setup so the developers can get an idea of the types of HW this occurs on.

Also, Adam advised me to try different browsers, as this sometimes is the issue. However, I tried Firefox, Chrome,and IExplorer with the same results. Be sure to try another browser.

---- Steve

K C

I am running tvheadend via OpenElec/XBMC installed on a foxconn nta-350 (amd fusion platform). I tried IE, chrome, and FF... same result.

Moving on to the method you used (John Nevill's instructions for custom mux list) I've created the mux list, but I don't know where to find it (same problem you had.)

Can anyone help me figure out where to place this file in an OpenELEC installation of TVHeadend?

Thanks!

Steve Miller

The directory where these are stored appears to have changed in recent software releases. On my system, I had several folders that had location files. The folder that is actually active in my Pogoplug is

/usr/local/share/tvheadend/data/dvb-scan/atsc

Here is how I figured it out by brute force.
1. I searched the entire drive for a known location name like, us-ID-Boise.
2. I when to every folder that contained this location file and renamed each to something unique.

3. I restarted TVH and then looked to see what unique name appeared for us-ID-Boise. This told me what folder to place my edited location file in.

I am sure there is an easier way, but this worked for me.

--- Steve

K C

Thanks Steve,
I like your style.... because i tried almost the same strategy. Only I couldn't find any of the pre-existing location files. Maybe I didn't do the search properly. I used the "find" command from the Linux ssh command line, like this:
>find . -name "*us_ID_Boise*"
And nothing came up. :(

I tried placing my custom file in several TVH related folders, but that didn't work, either.

Steve Miller

I am no Linux guru, or for that matter even a novice level. However, your find command does not work on my Pogoplug. When I use the following command, then I find stuff.

find / -name us-ID-Boise

The quotes and the wild cards did not work for me. Also, note that the separator symbols are dashes not underscores. If you read the above posts by others, it seems that TVH must have dashes as separators, underscores do NOT work.

If you execute make install, then the executable will be in /usr/local/bin . If you run the executable from that folder, then I believe the location files are in the directory that I quoted above. I would strongly suggest running "make install" from the build folder. I think this is critical to getting everything synced up.

---- Steve

K C

Thanks Steve.

Your find command did not turn anything up for me either. Just as a test I put in the name of the file I had placed and it turns up. Nothing named anything like us-ID* or us_ID* or any other variant on existing mux list names.

I did not do a make install, because TVH comes pre-installed with the version of XBMC I'm using (OpenELEC) and I'm not sure if I installed another version if it would work correctly with XBMC.

Bob Baird

KC - Try:

sudo find / -name us-ID-Boise

K C

Steve,
You said underscores don't work... but when I go to add a mux by location all the locations use underscores (see attached image)... do yours show a dash/hyphen? Or is it that the filename has to have a dash, but it shows up in the list with an underscore?