Tvheadend

MT,
If the program sees your adapter go to the setting for it and use the ATSC center frequencies from the drop down for the frequency list it needs to scan from and let her scan it will take awhile but mine works no problem found all the local channels and plays them in XMBC.
mclapp

Thanks mclapp,
Since yours works fine, it sounds like something it doesn't like with my tuner frontend then.
I create a custom list of freqs for my local area in linuxtv_muxes.h, and compile.
My dvb adapters all show up, I add my custom list to multiplexes to scan, it scans
but the device never obtains a lock. The same tuner works fine in all other linux apps
I've used, including mythtv.

As a further troubleshooting step, I created a custom frequency list, the same way as above, essentially
sweeping UHF channel 14 from 470 - 476 Mhz, in 62 KHz increments (the resolution of my frontend).
I sat there and watched it trying to tune from 470,000 Khz to 476,000 KHz and it never locked once.
Pretty much rules out a 'center freq" issue.
In addition while it's tuning, in another terminal I run 'femon' on that adapter to see if i ever get any quality indication.
It never does. Behaves like fe_set_properties never gets sent to the frontend during the tune process.
I don't know enough about the source code here to troubleshoot any further though, so I guess I'm SOL using it for ATSC.
DVB-S and DVB-S2 work fine.

Regards,
mt

are you using an adapter with multiple frontends? so one frontend supports DVB-S(2) and the other ATSC?
Are you sure the ATSC frontend is selected in tvheadend? currently we only support one frontend (frontend0) on a adapter.

To get additional log details you can either enable debug logging via the webgui (click on the little "cogs" icon in the lower panel) or via the tvheadend startup options -s (to log to syslog) or -d (to log to the console)

All the code around "dvb" adapters can be found under the src/dvb directory. This also includes everything around ATSC.

If i look at the source code then some code was added on 2009 to support ATSC. There some people that posted some questions and success here so it must be possible to get it working.

If you can get it working using the standard dvb-apps tools to tune a station, you can get the required mux information from that also. Using that information you should be able to manually add a mux. The predefined lists of muxes are there as a convenience, but you do not have to use those.

Hein

Hi Hein,
Thanks for the reply. Yes I understand tvheadend must work for ATSC, as I now know mclapp is using it. That's why I started out asking.
No, I use 2 separate USB DVB cards. One for DVB-S is the Prof 7500 USB tuner, and the one ATSC is this
inDtube Tuner I have. Admittedly inDtube is not very popular but it does work with the cmd line tools (dvb-apps, etc).
I can confirm the icon or Cog to add a multiplex manually does not do anything while in the ATSC adapter's multiplexes form.
I can add DVB-S / DVB-S2 multiplexes while under the the DVB-S adapter's form however.
Check out this post from another user a while back who noticed the same issue.
https://www.lonelycoder.com/redmine/boards/4/topics/2424

Okee, so what frequency do you need? Maybe there is an atsc predefined muxes list that has the correct details already in it.

And looking at the webgui code there is no "case" in there when the adapter type is ATSC..... So that might be the reason you cannot manually add the muxes. But I think you should be able to change an already existing mux directly in the grid ... (not sure .. Can you try that?)

Reading your wiki page on your adapter i guess there is no correct predefined list because of this incorrect frequency handling. But you could manually update the frequency of an incorrect mux.

Yes the PC cards I'm using are well supported in linux, tuner 1 is a pchdtv5500 and the other is a dvico fusion5 they work fine with the default ATSC center frequency list just took a long time to scan the list (it's got frequencies that are no longer used for ATSC reception in the US).

I can't create muxes manually using the manual add feature either for the ATSC cards and I'm nowhere close to a linux wiz to figure out why. I did try it to see if I could make just a short list manually of my known channels through the GUI without success.

It's not a big deal in my case since the list provided worked, I just deleted the known unused muxes from the supplied list through the GUI.

I also noticed that there is no update of the program guide by EIT happining.

I think what I'm gonna try next is try compiling some older versions.
Never know possible some regression occurred somewhere along the way?
Mclapp, can you tell what version you have under help about ?

Merry Xmas to all.
MT

Tom,

Add a incorrect list of atsc muxes ... And the update the frequency by double clicking it and then save that grid ... And see if that locks it.

Hein

Hi Hein,

I am unable to modify a Multiplex Frequency from the gui when double clicking on it, doesn't do anything.
I collected some logs from dmesg as the program is starting up. My understanding is that a device should
have it's firmware loaded as it's being used?
A comparison of that dmesg log as Mythtv started and tuned a station.

mythtv:
dmesg starting mythtv, or any other application looks like this:

[123981.928046] xc2028 16-0061: Loading firmware for type=BASE MTS (5), id 0000000000000000.
[123982.861439] xc2028 16-0061: Loading firmware for type=D2633 DTV6 ATSC (10030), id 0000000000000000.
[123982.874061] xc2028 16-0061: Loading SCODE for type=DTV78 DTV8 DIBCOM52 SCODE HAS_IF_5200 (61000300), id 0000000000000000

tvheadend like this:

Dmesg when starting tvheadend, with Autodetect Muxes, and Monitor Signal Quality checked.

[124382.644047] xc2028 16-0061: Loading firmware for type=BASE MTS (5), id 0000000000000000.
[124383.056602] tvp5150 16-005c: tvp5150am1 detected.
[124383.613978] xc2028 16-0061: Loading firmware for type=D2633 DTV6 ATSC (10030), id 0000000000000000.
[124383.626588] xc2028 16-0061: Loading SCODE for type=DTV78 DTV8 DIBCOM52 SCODE HAS_IF_5200 (61000300), id 0000000000000000.
[124384.203247] s5h1409_readreg: readreg error (ret -19)
[124384.203843] s5h1409_readreg: readreg error (ret -19)
[124384.204470] s5h1409_readreg: readreg error (ret == -19)

Not sure why I'm seeing that line with tvp5150am1 detected, as I believe that's related to the North American NTSC Analog Tuner,
which is also part of this device. /dev/video should be the legacy analog v4l tuner right?

Also saw this message from tvheadend as it's starting up...
[WARNING]:v4l: /dev/video0: Device lacks MPEG encoder, device skipped.

I'm guessing it's complaining about not having a HW MPEG encoder for the analog side of this device, would think that should be OK,
since we aren't using analog here in this application. Or are we, and it's confused about the device's capabilities??
Wonder what the 'readreg error' is all about, that looks like it's related to the Samsung s5h1409 frontend this tuner uses.

Attached is the rest of the log info I collected this evening.
When you have a chance, have a look and see if ya spot something?

From the about screen in the web GUI it says build 2.12.

I also can't modify ATSC frequency information or add Muxes through the Multiplexes tab of the GUI on the list provided through the program. Only delete them and enable disable them.
Happy Holidays

Thanks again mclapp.
I just downloaded and compiled the 2.12 release (non git version) with my modified ATSC Frequencies.
So far it seems to behave the same as the git version. I'll let
it run for a while longer though. If I get anywhere will provide details.

Happy New year to all!

i've built tvheadend "HTS Tvheadend git-7910c50" from src,

git log | head -n 3
        commit 7910c50e0fd20f2d0252f4c3dddb237368f27d73
        Author: Andreas Öman <[email protected]>
        Date:   Wed Jan 4 23:53:08 2012 +0100

on

uname -rom
        3.1.0-1.2-xen x86_64 GNU/Linux

with an attached, functional HDHomeRun

./hdhomerun_config discover
        hdhomerun device 101110BA found at 10.10.10.1
    ./hdhomerun_config 101110BA get XXX
        /sys/model     hdhomerun_atsc
        /sys/hwmodel HDHR-US
        /sys/version 20111025
        /sys/features
            channelmap: us-bcast us-cable us-hrc us-irc
            modulation: 8vsb qam256 qam64
            auto-modulation: auto auto6t auto6c qam

after populating Adapters and auto-slecting N.A. muxes @ tvheadend config UI, the system scans, but I get no Services. and, as a result, nothing populated in the EPG.

i similarly " ... can't modify ATSC frequency information or add Muxes through the Multiplexes tab of the GUI on the list provided through the program. Only delete them and enable disable them."

@ tvheadend service restart, syslog ->

Jan 12 09:25:22 pvr tvheadend[32168]: STOP: Exiting HTS Tvheadend
    Jan 12 09:25:23 pvr tvheadend[32517]: dvb: Found adapter /dev/dvb/adapter0 (HDHomeRun ATSC) via PCI
    Jan 12 09:25:23 pvr tvheadend[32517]: dvb: Found adapter /dev/dvb/adapter1 (HDHomeRun ATSC) via PCI
    Jan 12 09:25:23 pvr kernel: [59387.143296] DVB (dvb_dmxdev_filter_start): could not alloc feed
    Jan 12 09:25:23 pvr kernel: [59387.143328] DVB (dvb_dmxdev_filter_start): could not alloc feed
    Jan 12 09:25:23 pvr kernel: [59387.143352] DVB (dvb_dmxdev_filter_start): could not alloc feed
    Jan 12 09:25:23 pvr tvheadend[32517]: dvr: Creating new configuration ''
    Jan 12 09:25:23 pvr tvheadend[32517]: dvr: Output directory for video recording is not yet configured for DVR configuration "". Defaulting to to "/var/lib/tvheadend/". This can be changed from the web user interface.
    Jan 12 09:25:23 pvr tvheadend[32517]: CSA: Using SSE2 128bit parallel descrambling
    Jan 12 09:25:23 pvr tvheadend[32517]: START: HTS Tvheadend version git-7910c50 started, running as PID:32517 UID:107 GID:33, settings located in '/var/lib/tvheadend//.hts/tvheadend'
    Jan 12 09:25:23 pvr kernel: [59387.145136] DVB (dvb_dmxdev_filter_start): could not alloc feed
    Jan 12 09:25:23 pvr kernel: [59387.145161] DVB (dvb_dmxdev_filter_start): could not alloc feed
    Jan 12 09:25:23 pvr kernel: [59387.145184] DVB (dvb_dmxdev_filter_start): could not alloc feed
    Jan 12 09:25:24 pvr tvheadend[32517]: xmltv: Grabbing "North America (Data Direct)" using command "/usr/bin/tv_grab_na_dd" 
    Jan 12 09:25:43 pvr kernel: [59407.152055] DVB (dvb_dmxdev_filter_start): could not alloc feed
    Jan 12 09:25:43 pvr kernel: [59407.152102] DVB (dvb_dmxdev_filter_start): could not alloc feed
    Jan 12 09:25:43 pvr kernel: [59407.152126] DVB (dvb_dmxdev_filter_start): could not alloc feed
    Jan 12 09:25:43 pvr kernel: [59407.152195] DVB (dvb_dmxdev_filter_start): could not alloc feed
    Jan 12 09:25:43 pvr kernel: [59407.152220] DVB (dvb_dmxdev_filter_start): could not alloc feed
    Jan 12 09:25:43 pvr kernel: [59407.152248] DVB (dvb_dmxdev_filter_start): could not alloc feed
    Jan 12 09:25:49 pvr tvheadend[32517]: xmltv: /usr/bin/tv_grab_na_dd: Parsing completed. XML contained 31 channels, 6814 events, 0 new events injected in EPG

anyone seeing any progress/success?

minor progress ...

i had installed built & installed kernel modules & userhdhomerun app from 'latest' tarball,

wget -k -O dvbhdhomerun.tar.gz "http://dvbhdhomerun.cvs.sourceforge.net/viewvc/dvbhdhomerun/?view=tar"

with those inplace, no luck scanning & populating Services, as above.

replacing that tarball source with that from cvs,

cvs -z3 -d:pserver:[email protected]:/cvsroot/dvbhdhomerun co -P dvbhdhomerun

then rebuilding & reinstalling kernel mods & the user app seems to have fixed the problems; initial scans are taking f.o.r.e.v.e.r!, but progress is being made:

Hardware
        Device path: /dev/dvb/adapter1
        Device name: HDHomeRun ATSC
        Host connection: PCI
        Frequency range: 54000 kHz - 858000 kHz, in steps of 62 kHz
        Symbolrate range: 451875 Baud - 7230000 Baud
    Status
        Currently tuned to: 509,028 kHz
-->        Services: 62
        Muxes: 68
        Muxes awaiting initial scan: 10

note the services getting populated.

i still don't see anything in the tvheadend EPG ... yet

An update:
A few weeks ago I received a Hauppauge Aero M. Latest device from Hauppauge with ATSC M/H support.
This device does work with tvheadend. It's busy scanning for channels at the moment.
I'm using NTSC-center-freguencies-8VSB, since I have modified ATSC-center-frequencies-8VSB to
be compatible with the other tuner, which doesn't work (the inDtube tuner with the Samsung frontend has a significantly different center frequency).