Signal Quality changes with 4.9.5/4.9.5.1

[RedDwarf]

I have upgraded from 4.9 to 4.9.5.1, missing 4.9.5 and since doing that the signal quality is now only showing around 58% to 68%, whereas it was showing as 100% all the time previously. Has the quality measurement been changed since 4.9?

 

My satellite card drivers do show any quality over about 70% as being 100% because the makers say above 70% means any errors are correctable so it effectively means 100% quality, so it's not until the quality drops below 70% that the true quality is shown.

 

However, the quality has not changed, it's still the same as it was because I have re-installed 4.9 and that still shows 100% quality and when I go back to 4.9.5 the quality reverts back to around 60%.

 

I have tried this on two different windows installs with the same result.

 

Is this intentional? Why was there no mention of it? I have spent a considerable amount of my time trying to work out whether my dish had moved but it turns out that it has not, it's DVBViewer causing it.

support.zip

Edited March 21, 2012 by RedDwarf

[Griga]

Your reports refers to your Mystique SaTiX-S2, that actually is a relabeled Digital Devices card, right? Signal quality has been replaced by signal strength (in dBµV) for Digital Devices DVB-S2 cards, because getting always 100 % is not really informative. And yes, it has not found its way into the change log...

[Antonio]

Hi Griga, It is possible to replace also a quality signal level in the DVBViewer GE version for Omicom S2 PCI rev.3, as it is made in PRO version.?

Now in DVBViewer GE version the signal of quality is displayed not so informatively. Only five values as 0% 20% 40% 60% 80% and 100%

[RedDwarf]

Your reports refers to your Mystique SaTiX-S2, that actually is a relabeled Digital Devices card, right?

Yes it is, DVBShop Mystique cards are only re-badged cards by other makers. In my cards case, it is a Digital Devices card.

 

Signal quality has been replaced by signal strength (in dBµV) for Digital Devices DVB-S2 cards, because getting always 100 % is not really informative. And yes, it has not found its way into the change log...

Okay thank you. I will have to try testing the dBuV value feeding the card to see how well it matches the value the card reports.