Project

General

Profile

Wrong mux

Added by Kyle Rose almost 13 years ago

I'm sort of at the end of my rope here, and wondering where to go. During the initial scan, tvheadend consistently maps channels incorrectly to muxes, and . In one case, it seems to like putting one of the subchannels of WHDH-HD on 647 MHz, when in actuality WGBX-HD is on that frequency; in another case, it thinks WBZ is on two different frequencies (569 MHz and 509 MHz, when in fact WBZ is on 569 and WCVB is on 509). I'm not really clear on what is going wrong here: is tvheadend reading old data from the tuner after it thinks the frequency has changed, and is applying the scan results to the wrong mux as a consequence? I'm happy to modify the data myself to match reality so I can get this working without pulling more of my hair out, but I don't know quite how to do that: should I just wait for tvheadend to populate the scan info incorrectly, and then just modify the frequency in each of the dvbmuxes files to match where the channel actually is?

Thanks,
Kyle


Replies (9)

RE: Wrong mux - Added by Eric Valette almost 13 years ago

try w_scan to get the transponder and put the transponder manually. default value for Renness in FR is also plain wrong.

RE: Wrong mux - Added by Kyle Rose almost 13 years ago

This would be great, except that tvheadend keeps overwriting my corrections with incorrect info.

FWIW, it appears my initial suspicion is probably correct, because what appears to be happening is that channel information is nearly always associated with the next higher mux, meaning that tvheadend thinks the tuner has changed frequencies before it actually has. w_scan doesn't have this problem and correctly output all the proper muxes on the first try, presumably because it scans more slowly to tolerate sluggish tuners.

RE: Wrong mux - Added by Eric Valette almost 13 years ago

You have an option were tvheadend does not try to discover frequency chnage.

RE: Wrong mux - Added by Kyle Rose almost 13 years ago

Which option is this? I have everything unchecked on the adapter page.

RE: Wrong mux - Added by Eric Valette almost 13 years ago

If you already have autodetect muxes off and idle scan off, I do not understand why you get incorrect values. The channels are wrongly detected when you add a single transponder?

Are you sure its not leftover related to old DVB-T setup? Did you clean up the corresponding .hts/tvheadend file directory before readding the muxes

RE: Wrong mux - Added by Kyle Rose almost 13 years ago

Whenever I restart tvheadend, all the muxes go back to requiring initial scan, which is when this misconfiguration takes place.

I have no old DVB-T setup. I live in the US and always start from an empty .hts/.

RE: Wrong mux - Added by Kyle Rose almost 13 years ago

To be clear, the already-configured muxes are still there: it's just that the data get overwritten by the new "initial" scan.

RE: Wrong mux - Added by Kyle Rose almost 13 years ago

Fundamentally, though, even if disabling autodetect muxes/idle scans worked, it would still be a hack: the real problem is that tvheadend is misidentifying the source of data it's pulling from the tuner. That problem needs to be fixed. Where in the code is the scan taking place? I tried making sense of it earlier today, but a pointer from someone more familiar with the code would greatly reduce the amount of looking I need to do. In particular, where in the code is the data coming in from the tuner used to update the files in the dvbtransports/ subtree?

RE: Wrong mux - Added by Hein Rigolo almost 13 years ago

Tvheadend tries to pull all.information from the data stream. You can find most of that data in the various tables.
Have a look ar src/dvb/dvb_tables.c on how these get parsed. Search for atsc for the atsc table parsing.

Hein

    (1-9/9)