Tvheadend

Hi,

I use a similar setup, however, with dvb-c and not with ATSC.

You say you find only 2-5 good channels, but how many muxes do you find?
Are all the muxes present in the muxes-list ? Otherwise you can try to add them manually.
It might be that the file with information about your carrier is not complete in tvheadend, and tvheadend only scans the define muxes.
There is the possibility of auto-discovery, but some providers do not support this.

Also, what is in your /etc/dvbhdhomerun file ?

Alex.

Nate Burr wrote:

I've been playing on and off again with tvheadend for last 1-2 years. Every time i try a new release i generally walk away with the same issue and have finally decided that i should

post to see if others are having the same issue.

I'm using the hdhomerun dvb frontend. it's connected to my cable and i'm located in the USA. so it's configured as ATSC.

When ever I scan for any channels in the tvheadend I usually only get about 2-5 good channels that'll show up as being un-encrypted tv streams. When i do a scan with kaffeine i get about 60.

Both programs use the same dvb driver. so my question is what can I do to get more channels to show up in tvheadend? Is tvheadend doing some sort of filtering on channels that's being to aggressive?

thanks,

-nate

I've used that standard USA cable channel muxes and created my own mux list. I get the same result using both.

Here is the output from my dvb config file:

1. Remember to exchange the XXXXYYYY-Z with the serial number of your HDHomeRun
2. tuner:

1. Auto detect tuner type is not possible in all cases, so you can force it
2. DVB-C
3. DVB-T
4. ATSC

[1012137F-0]
tuner_type=ATSC

[1012137F-1]
tuner_type=ATSC

1. You can use a full name including tuner ID. Meaning the tuner will appear as
2. "HDHomeRun DVB-C 1234EA3D-0" instead of just "HDHomeRun DVB-C" in for example
3. TVHeadend.

[1012137F-0]
use_full_name=true

1. You can disable certain tuners. As default all detected hdhomeruns are used

[1012137F-1]
use_full_name=true