Tvheadend

Alasdair Campbell: Immediate thoughts - you're either not on that transmitter or you've got something wrong with the config of the muxes you entered. Certainly "Auto, 8000kBaud" doesn't look right, although everything else appears normal (you're tuning to a channel, for example, so the tuner seems to be working).

Delete them and add them again: QAM64, 8MHz bandwidth, Auto everything else. See what that does. You can disable the 538 mux if needed, it's not broadcasting yet, but it shouldn't hurt to have it there - disable it only if scanning gets stuck at that point.

Also, @Brad - sorry, missed your message - try the later versions (3.9.x) from the "Builds" menu above. I say again that I know nothing about US broadcasting standards, but I've heard rumo(u)rs that support is better in the newer DVB code.

Hi Prof,

Thanks for that, will update it after I finish work.

I wan't sure if the baud was wrong, from memory, the openelec version requires a value (from the general tab 870000 - 11700000).

I couldn't remember how to calculate baud at the time.

Can you remember how to do this, using the example for C23 (490.0MHz) 64QAM 8K 2/3 24.1Mb/s DVB-T MPEG2.

Many Thanks,
Alasdair.

As I say, no reason to work anything out - I've never had to, anyway! - just add Frequency (490000), Bandwidth (8MHz) and the Constellation (QAM64) and leave everything else on Auto.

I think the baud bit is the symbol rate, but I've never had to set it.

I'm not running 3.4/3.5 any more, and the config has changed in 3.9 so I can't immediately replicate what you're doing here. Let me look into my config backup and see if I can make sense.

Nope - nothing about symbol rate in my DVB-T/T2 setup on the old version either. I have a symbol rate in my DVB-S2 adapters, but that's always set automatically once I've defined the satellite config.

So... is this an artefact of the DVB-C bit? Or are you on a really different version of tvheadend, maybe 2.something?

Will give it a shot tonight and update you to my progress.

Thanks again.

My situation is almost same
one of 3 muxex is ok
rest can't find names of services

Alasdair Campbell - another couple of thoughts...

1. Does this appear as multiple tuners? If so, does the C appear separately from the T/T2? Are you adding the muxes to the right one?

2. Some mutterings (I haven't really dug) about patches to V4L that are necessary for ... well, perhaps for this card, perhaps something similar.

https://tvheadend.org/boards/5/topics/10314

http://www.vdr-portal.de/board18-vdr-hardware/board102-dvb-karten/p1077194-aktuelle-treiber-f%C3%BCr-octopus-ddbridge-cines2-ngene-ddbridge-duoflex-s2-duoflex-ct-cinect-sowie-tt-s2-6400-teil-2/

From your OpenElec posts, though, I suspect you've effectively got the patched tree because you're using the media_build image, so that may be a dead end.

3. There's some ancient discussion on Freeview symbol rates here: http://forums.digitalspy.co.uk/showthread.php?t=668731. If you are stuck entering the baud rate for some reason, this might give some pointers as to what values you'd need, since you can pull the bitrate from the same source as the mux info and recalculate from there.

I'm still not convinced that you should need to enter this, though, but maybe that's just me being hopeful...!

@saen - I'll need more information to even take a guess... okay, you're in Bulgaria, but beyond that...!

Screenshot of your card config, please, and the mux config as well (the General and Multiplexes tabs).

Your transmitter details are well, please - what muxes, frequencies, a link to the configs of those if you have them.

I'll say now that I'm better with UK stuff, but I'll certainly take a look for you.

am walk around and see also other have same problem
in my case
[quote]
Adapter name: DiBcom 7000PC /aka [url=http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500]Hauppauge WinTV Nova-T-500 German edition[/url]/
Enabled: yes
Autodetect muxes: YES
Idle scanning: yes
Monitor signal quality: yes
[/quote]
HTS Tvheadend 3.5.247~g098b7de~precise on Ubuntu 12.04

same situation with AF9033 based AVerTV Volar HD Nano (SKY Italy dongle for PACE receivers)
only at 10 years old "Toshiba USB DVB-T Tuner PX1211E-1TVD" (lite-on-dib3000mc) everything is OK

@Saen ...

Likely to be firmware if your Toshiba stick works and the others don't. Check dmesg to see if the tuners start up properly. Also, make sure you have the firmwares installed (sudo apt-get install linux-firmware-nonfree) and reboot.

The default kernel on Ubuntu 12.04 is getting old, so doesn't have support for newer cards built in. That's probably why the old stick works and newer ones don't.

Worst case, you'll also need to update v4l, which is the subsystem that talks to your card - that brings support for things that aren't in the kernel already.

Hi

Update time. The version of tvheadend on openelec is 3.4.27~gfbda802. In the Add muxes popup the only options are:
Frequency (kHz)
Symbolrate (baud)
Constellation
FEC

Inputting 490000 for the Frequency, setting the constellation to QAM-64, and FEC at auto the form will not submit as Symbolrate is a required field.

It would be soo much easier if the add by location popup was not empty.

Any ideas Prof?

Nope, I'm clueless here. I've never once seen baud rate on any version of tvh from 2.something to date on my DVB-S or DVB-T/T2 tuners. I have to thus conclude that it's forcing you into a DVB-C config, where you have to specify the symbolrate, instead of the DVB-T side, where you don't. But I can't prove that, not having cable within 50 miles of me here, let alone having an equivalent adapter!

All I can otherwise suggest... have you checked the adapter dropdown, does it appear as multiple adapters (e.g. /dev/dvb/adapter0 as well as /dev/dvb/adapter1)? Is there any indication that you're perhaps trying to add T muxes to a C config, and hence the confusion? Is there anything in dmesg about the multiple adapters or frontends that perhaps isn't making it through to tvheadend?

Failing that, I'm not sure what else to suggest. I don't know if there's some way of updating tvheadend in OpenElec, or whether you have a separate system you could boot up (e.g. under a live CD) and see if you can get the stick working on that - just to isolate the problem - driver/firmware/tvh version/kernel/whatever?

Prof Yaffle wrote:

@Saen ...

Likely to be firmware if your Toshiba stick works and the others don't. Check dmesg to see if the tuners start up properly. Also, make sure you have the firmwares installed (sudo apt-get install linux-firmware-nonfree) and reboot.

The default kernel on Ubuntu 12.04 is getting old, so doesn't have support for newer cards built in. That's probably why the old stick works and newer ones don't.

Worst case, you'll also need to update v4l, which is the subsystem that talks to your card - that brings support for things that aren't in the kernel already.

100% working
[ 10.916954] dvb-usb: found a 'Hauppauge Nova-TD-500 (84xxx)' in cold state, will try to load a firmware
[ 10.962082] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
[ 12.188138] dvb-usb: found a 'Hauppauge Nova-TD-500 (84xxx)' in warm state.
[ 12.188195] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 12.634811] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[ 13.525311] dvb-usb: schedule remote query interval to 50 msecs.
[ 13.525315] dvb-usb: Hauppauge Nova-TD-500 (84xxx) successfully initialized and connected.
[ 13.525579] usbcore: registered new interface driver dvb_usb_dib0700

@Saen - you're in Bulgaria by the channels, yes? Where?

Do you have the mux frequencies correct? Have you tried adding them manually? Do you have the right configuration (constellation, bandwidth...)?

https://en.wikipedia.org/wiki/Digital_terrestrial_television_in_Bulgaria

https://en.wikipedia.org/wiki/Television_channel_frequencies#Western_Europe.2C_Greenland.2C_most_countries_in_Asia_and_Africa.2C_and_most_of_Oceania

http://nurts.bg/en/uslugi/%D1%86%D0%B8%D1%84%D1%80%D0%BE%D0%B2%D0%B0-%D0%B5%D1%84%D0%B8%D1%80%D0%BD%D0%B0-%D1%82%D0%B5%D0%BB%D0%B5%D0%B2%D0%B8%D0%B7%D0%B8%D1%8F-dvb-t/

yes freq. is correct test in two different cites same result
am also use Kaffeine and there is no problem
both TVHeadend and Kaffeine use same scanning freq. in dvb-apps
that's why 39E sat position missing in both programs
100% this is not scanning parameters error it is a program error

If you're that certain, I'd suggest you upgrade to the latest (3.9) builds if you can, see if it still occurs; if it does, raise a bug along with logfiles if there's anything specific that the development team can look into. I can't see anything from what you've shared (you may need to upload the contents of .hts, for example).

I don't immediately know why tvheadend would be happy with one mux but not another unless there's a configuration difference.

if explain how to scan with it coz it very strange
post youtube video

Yeah I don't have cable either. Yep there are 2 adapters but the popup for both are the same i.e. only those 4 inputs.

From what you are saying it does seem as though it is trying to force me to use a C config when all I want is T/T2, it didn't occur to me until you suggested it, although other than the popup not sure what indication there would be to confirm this. If this is indeed the case I have no idea how to force it only T/T2 or how to disable C

The Card is PCI-E and know it works under M$, Openelec was the only distro i noticed that already had the drivers, I know xbmcbuntu doesn't.

Checked dmesg only relevant messages I could find are:
[ 5.265712] Digital Devices PCIE bridge driver 0.9.9, Copyright (C) 2010-13 Digital Devices GmbH
[ 5.269175] ACPI: PCI Interrupt Link [LN4A] enabled at IRQ 19
[ 5.269309] DDBridge driver detected: Digital Devices Octopus V3 DVB adapter
[ 5.269354] HW 00010000 REGMAP 00010004
[ 5.403530] Port 0 (TAB 1): DUAL DVB-C/T/T2
[ 5.408068] Port 1 (TAB 2): NO MODULE
[ 5.409102] Port 2 (TAB 3): NO MODULE
[ 5.410091] Port 3 (TAB 4): NO MODULE
[ 5.412726] DVB: registering new adapter (DDBridge)
[ 5.412741] DVB: registering new adapter (DDBridge)
...
[ 1238.995851] irq 22: nobody cared (try booting with the "irqpoll" option)
[ 1238.995866] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P C O 3.13.0 #1
[ 1238.995871] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M., BIOS 080015 12/10/2009
[ 1238.995877] 0000000000000000 ffffffff816e939e ffff8800cb6d6700 ffffffff8105a85b
[ 1238.995888] ffff8800cb6d6700 0000000000000000 0000000000000016 ffffffff8105abcc
[ 1238.995896] 0000000000000000 ffff8800cb6d6700 0000000000000016 0000000000000000
[ 1238.995904] Call Trace:
[ 1238.995908] <IRQ> [<ffffffff816e939e>] ? dump_stack+0x41/0x51
[ 1238.995930] [<ffffffff8105a85b>] ? __report_bad_irq+0x2c/0xb4
[ 1238.995939] [<ffffffff8105abcc>] ? note_interrupt+0x140/0x1c0
[ 1238.995947] [<ffffffff810590fc>] ? handle_irq_event_percpu+0xf3/0x101
[ 1238.995955] [<ffffffff81059135>] ? handle_irq_event+0x2b/0x46
[ 1238.995963] [<ffffffff8105b3cc>] ? handle_fasteoi_irq+0x71/0xa1
[ 1238.995971] [<ffffffff810038e1>] ? handle_irq+0x15/0x20
[ 1238.995978] [<ffffffff810035c8>] ? do_IRQ+0x40/0x95
[ 1238.995988] [<ffffffff816ef667>] ? common_interrupt+0x67/0x67
[ 1238.995997] [<ffffffff81030b6a>] ? __do_softirq+0x91/0x1d8
[ 1238.996006] [<ffffffff81030e30>] ? irq_exit+0x51/0xb9
[ 1238.996013] [<ffffffff81003608>] ? do_IRQ+0x80/0x95
[ 1238.996022] [<ffffffff816ef667>] ? common_interrupt+0x67/0x67
[ 1238.996025] <EOI> [<ffffffff81604576>] ? cpuidle_enter_state+0x4d/0x9e
[ 1238.996039] [<ffffffff8160456f>] ? cpuidle_enter_state+0x46/0x9e
[ 1238.996047] [<ffffffff81604689>] ? cpuidle_idle_call+0xc2/0x107
[ 1238.996055] [<ffffffff81008f9b>] ? arch_cpu_idle+0x5/0x14
[ 1238.996063] [<ffffffff81058951>] ? cpu_startup_entry+0xff/0x176
[ 1238.996072] [<ffffffff81ebfc96>] ? start_kernel+0x3bd/0x3c8
[ 1238.996080] [<ffffffff81ebf6fc>] ? repair_env_string+0x54/0x54
[ 1238.996084] handlers:
[ 1238.996091] [<ffffffff815b5ae2>] usb_hcd_irq
[ 1238.996095] Disabling IRQ #22

output from lspci -v suggests irg 22 has nothing to do with the card:
00:04.1 USB controller: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller (rev b1) (prog-if 20 [EHCI])
Subsystem: ZOTAC International (MCO) Ltd. Device a119
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22
Memory at fae7ec00 (32-bit, non-prefetchable) [size=256]
Capabilities: [44] Debug port: BAR=1 offset=00a0
Capabilities: [80] Power Management version 2
Kernel driver in use: ehci-pci

05:00.0 Multimedia controller: Digital Devices GmbH Device 0005
Subsystem: Digital Devices GmbH Device 0004
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at febf0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [50] Power Management version 3
Capabilities: [70] MSI: Enable- Count=1/2 Maskable- 64bit+
Capabilities: [90] Express Endpoint, MSI 00
Capabilities: [100] Vendor Specific Information: ID=0000 Rev=0 Len=00c
Kernel driver in use: ddbridge

LSDVB give more info about tuner
also some devices are hidden behind USB bridge
use LSUSB

Saen, thanks for your suggestions however lsdvb is not available on openelec and as this is a PCI-E tuner lsusb returns nothing relevant:
Bus 003 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
Bus 003 Device 003: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote Controller
Bus 003 Device 004: ID 10f5:0242 Turtle Beach
Bus 004 Device 002: ID 0e8f:0023 GreenAsia Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Alasdair Campbell - another jolly wheeze - or a frig, depending on how you want to look at it ...

If tvheadend is simply getting confused by the adapter type, how about we override it, or maybe even set the configs up manually?

Shut down tvheadend (sudo service tvheadend stop or equivalent) and navigate to /home/hts/.hts/tvheadend/dvbadapters. In here, you should find one entry per adapter - plain text - that you can edit. As a template, here's my DVB-T2 file:

hts@Server:~/.hts/tvheadend.backup.3.5.96~gaa0e5b1/dvbadapters$ more *20R
{
        "enabled": 1,
        "fe_path": "/dev/dvb/adapter3/frontend0",
        "dmx_path": "/dev/dvb/adapter3/demux0",
        "dvr_path": "/dev/dvb/adapter3/dvr0",
        "type": "DVB-T",
        "displayname": "Sony CXD2820R",
        "autodiscovery": 1,
        "idlescan": 1,
        "idleclose": 0,
        "skip_checksubscr": 0,
        "sidtochan": 0,
        "qmon": 0,
        "poweroff": 0,
        "nitoid": 0,
        "diseqc_version": 0,
        "diseqc_repeats": 0,
        "extrapriority": 300,
        "skip_initialscan": 0,
        "disable_pmt_monitor": 0,
        "full_mux_rx": -1,
        "grace_period": 0
}

With that and what you have defined already, (a) you can see if tvheadend thinks the two existing adapters are genuinely different, or (b) you can modify one of them to be more like the above. It may just be a case of specifying DVB-T, for example, especially if it's labelled as DVB-C or similar now.

Worth a punt: sudo service tvheadend start when you're done (or, again, equivalent on your distro).

If that works, great. If it sort-of-works but we still get problems, the next step would be to do the same for the muxes, and see if we can bypass that config step as well.

Same routine - shut down tvheadend, navigate to /home/hts/.hts/tvheadend/dvbmuxes/_dev_dvb_adapter<the_adapter_you_altered_above>. Again, here's my mux list - you can see that they're named after the adapter and the relevant frequencies:

_dev_dvb_adapter1_Sony_CXD2820R474167000
_dev_dvb_adapter1_Sony_CXD2820R482200000
_dev_dvb_adapter1_Sony_CXD2820R498000000
_dev_dvb_adapter1_Sony_CXD2820R506000000
_dev_dvb_adapter1_Sony_CXD2820R522000000
_dev_dvb_adapter1_Sony_CXD2820R530000000
_dev_dvb_adapter1_Sony_CXD2820R538000000

And, in each one, the config:

$ more _dev_dvb_adapter1_Sony_CXD2820R474167000
{
        "quality": 100,
        "enabled": 1,
        "status": "OK",
        "transportstreamid": 12294,
        "originalnetworkid": 9018,
        "network": "Gloucestershire",
        "frequency": 474167000,
        "initialscan": 0,
        "bandwidth": "8MHz",
        "constellation": "QAM64",
        "transmission_mode": "8k",
        "guard_interval": "1/32",
        "hierarchy": "NONE",
        "fec_hi": "3/4",
        "fec_lo": "1/2" 
}

What might screw you here is whether the transport ID and network ID are the same everywhere in the UK. Might need some Googling.

Back to you...

@Saen - I think you should be able to do something similar. Navigate to the muxes directory as above, and check that the config of the non-working muxes is the same as the working one. If it's not, stop tvheadend, edit them and restart. You can also play with the config values if there's anything on the Internet that suggests that any parameter might be different.

@prof - Had a quick look before I had to leave for work and noticed the type set is indeed DVB-C. Will work on it tonight/this weekend and should be able to give you good news soon.

As both tuners are DVB-C/T/T2, is the type in the config file mutually exclusive, i.e. I can only specify one or other? If so maybe a developer could look into this.

You truly are worthy of the name prof, if you're ever in West London let me buy you a beer

Thanks again and I will update you later.

I do frequency offset and some of transponders, work but on non-standard freq???