What I guess is happening is the values in terrestrial.xml don't correspond with your mast. In Signalfinder if you switch to user defined transponder and then to T2 it should show signal.
Last edited:
Yes - changing to T2 works.What I guess is happening is the values in terrestrial.xml don't correspond with your mast. In Signalfinder if you switch to user defined transponder and then to T2 it should show signal.

If I start at ch 22, and move slowly thru to 60, only the valid sd mux's give any values.
Am I using incorrect parameters, there's only one that needs changing?
If I'm tuned to ch 28, bbc1 hd, signalfinder fires up on ch 28, with nothing showing.
I don't want to accept fixes for broken drivers. But I do appreciate your contribution. :thumbsup:
No, that is not correct. T2 should only select T2 muxes. T should only select T muxes. Auto should select either. Any diversion from this behaviour means the drivers are faulty.If you are performing this manually as part of a test and have left Menu-> tuner config -> manual scan -> Sytem =DVB-T then you will only pick up SD MUxs when you slowly select each transmitter channel. If you change that setting to Auto or DVB-T2 you should pick up both SD and HD MUXs with a test manual scan.
0xFFFF just means the tuner is maxed out. Why does that deserve a warning message for a box with broken drivers? That message is going to pop up on everyone's box that is working correctly with a maxed out tuner.If you really are adamant not to include my fixes to get better data, I suggest the user advice along the lines of my warning message when data is missing, and a log of the tuner type in use, would be useful additions.
You're welcome to send a pull request for that. I don't have the STB so I can't test.Who is likely to sort out what is wrong and fix it, and what sort of timescale is that going to take?
TSID is unique on a network. So in theory if you find 2 muxes with the same TSID on 2 different frequencies they should be identical in every way. And that means for certain the SI tables will be wrong on at least one of them.So when the DVB-T frequency finder claims to find unique muxes, it means unique in terms of TsId and rather than unique in terms of services carried?

TSID is unique on a network. So in theory if you find 2 muxes with the same TSID on 2 different frequencies they should be identical in every way. And that means for certain the SI tables will be wrong on at least one of them.
That is what a repeater is. It receives on one frequency and retransmits on another. Nothing is processed. That means the SI tables correspond to the master mast, not the repeater. In such a case if ABM reads the SI tables all the frequency data corresponds to the main mast so the channels are saved with the wrong frequency data. Custom transponder is to correct this problem, or any other situation where the frequency data might be wrong or missing.Is that true with relay transmitters? The relay may just copy all the information from the main transmitter from which it gets its data and then re-transmits on a different frequency.
0xFFFF just means the tuner is maxed out.
You keep referring to broken drivers, but as at least one other parameter generated by frontend.cpp from the driver info is changing it appears to me that frontend.cpp is a possible source of the problem. Have you investigated to locate the source of the problems?Why does that deserve a warning message for a box with broken drivers?
TSID is unique on a network. So in theory if you find 2 muxes with the same TSID on 2 different frequencies they should be identical in every way.
You're welcome to send a pull request for that. I don't have the STB so I can't test.

. Also if 2 muxes with the same TSID are maxed out it doesn't matter which is selected as the content will be the same on both, so also no need for an error message.
That is the problem. You only test for signal quality if lock is achieved. To achieve lock you need a SNR > ~20dB, so a return value of zero indicates an error. There is a very high probability (and a certainty in the cases found so far) that the same value will be returned for every mux however good, so one can reliably predict that some minutes after the first occurrence the user will receive a message saying no muxes found irrespective of how many are in fact OK.@EMJB,
4) A zero value means we don't save the transponder.
The user is almost certainly going to get one a few minutes later that gives him no help whatsoever in determining the source of the problem. My message identifies the source of the problem, a possible work-round of an alternative tuner, and the possibility of proceeding if duplicated muxes are not expected.No need for an error message.
Apologies - I did not make it clear that there is a different problem with maxed-out signals - too strong signals can affect reception just as effectively as too weak ones. Without detailed knowledge of individual tuners it is difficult to say how close to that point is to the point where maximum SNR is reported, but maxed-out signals should be considered as a warning that other muxes may have even stronger signals causing failure to lock, and therefore being ignored. (To be pedantic the overloading is a function of signal strength, not SNR but a high SNR must imply a strong signal, even if the reverse is not true.Also if 2 muxes with the same TSID are maxed out it doesn't matter which is selected as the content will be the same on both, so also no need for an error message.
So now the plugin is supposed to second guess on a crap tuner that gets flooded when signal is strong?