24 replies to this topic

[Huevos]

So we can safely assume drivers for these brands (Zgemma and Mut@nt) may well be developed by the same people.

By the way, it is not only the frequency which is incorrect but also SR=0 and FEC=auto.

No, you can't assume that. More likely is the manufacturer of the tuner chip has supplied both with the same (dodgy?) code.

[Robinson]

Huevos, do you experience the wrong frequency/SR/FEC on your HD51?

Do you still use this box? What tuner do you have? S2 or S2X?

[Rob van der Does]

By the way, as the author of this thread pointed out:
"The correct frequency can be spotted for a second while zapping."  It just immediately turns into 9750 or 10600 in the second infobar.

Possibly because the lamedb values are used until lock?
PLi has the option to show just the database values or the tuner feed back. 
 

So we can safely assume drivers for these brands (Zgemma and Mut@nt) may well be developed by the same people.

Possibly; don't forget that Zgemma has a proven track record of counterfeit cloning boxes.

[Huevos]

Huevos, do you experience the wrong frequency/SR/FEC on your HD51?

Do you still use this box? What tuner do you have? S2 or S2X?

I have never owned an HD51.

[Robinson]

 

By the way, as the author of this thread pointed out:
"The correct frequency can be spotted for a second while zapping."  It just immediately turns into 9750 or 10600 in the second infobar.

Possibly because the lamedb values are used until lock?
PLi has the option to show just the database values or the tuner feed back. 
 

 

Makes sense.

Although, if someone can read the code for displaying the values in the second infobar, could you please check if they are indeed taken from lamedb before lock? If so, then that must be driver fault.

Otherwise, it might suggest that something overrrides these values.