Tvheadend

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

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.

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

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

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

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/.

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

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?

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