Bug #2699
open
AUTO mode for constellation and bandwith in Muxes setup make my dual tuner Terratec Cinergy DT USB XS Diversity/ T5 fail
Added by Eric Valette about 10 years ago.
Updated about 10 years ago.
Found in version:
3.9.2514~g50016a1
Description
As I wanted to switch to recent tvheadend after holding the migration for ages, I first used hdhomerun networked adapter to configure my muxes and channels on one computer and when satisfied moved it to my real target device.
I thus created a tar ball of the working /home/hts/.hts/tvheadend config and after installation on the target device, untarred it and then started the new version. At first it worked because the two DVB-T usb adapter were still unconfigured, but a soon as I enabled them and put them into the same network, it started failing with error saying that no data was received from tuner.
Just to be sure, I tried to start with an empty config again using the muxes w_scan or hdhomerun_config found and it did fail to correctly retrieve channels also with AUTO mode for constellation and bandwith. So AUTO it not working and is misleading (I was expecting the code to try and find the correct setup for dvb-t1 in france at least) and I'm under the impression nothing is done if default values fails. For me the correct settings are 8Mhz and QAM/64.
- Status changed from New to Invalid
Blame the driver for your DVB hardware. The auto flag is passed to the driver which should be able to auto-detect the correct tuning parameters.
Jaroslav Kysela wrote:
Blame the driver for your DVB hardware. The auto flag is passed to the driver which should be able to auto-detect the correct tuning parameters.
Easy for you however, this was working with previous version of tvheadend. So something has chnaged in tvheaedend that make the auto value fails.
- Status changed from Invalid to New
Eric Valette wrote:
Jaroslav Kysela wrote:
Blame the driver for your DVB hardware. The auto flag is passed to the driver which should be able to auto-detect the correct tuning parameters.
Easy for you however, this was working with previous version of tvheadend. So something has chnaged in tvheaedend that make the auto value fails.
You may compile tvheadend with --enable-trace and use --trace linuxdvb to see which parameters are passed to the linux driver. But tvheadend is not really responsible if AUTO does not work on the driver side.
Which previous version of tvheadend you refer?
Jaroslav Kysela wrote:
You may compile tvheadend with --enable-trace and use --trace linuxdvb to see which parameters are passed to the linux driver. But tvheadend is not really responsible if AUTO does not work on the driver side.
Ok. Will do. But I must do it on the real target so at a time nobody wants to watch tv or record something => expect some delays...
Which previous version of tvheadend you refer?
Something of the 3.5 era...
Also available in: Atom
PDF
Updated by 
Updated by