58 replies to this topic

[littlesat]

Do we get it with a VU box

Well it happens on the Vu Duo

... with an ET box I do not see this... so in fact we suggest now that incorrect values are forwarded from the frontend (via the drivers)...

I did intent to return the values from the frontend in the first place.... Because usually these are the real values....

Hard to solve this without asking VU to upgrade it in their drivers..........????

Edited by littlesat, 9 March 2012 - 13:56.

[Huevos]

Do we get it with a VU box

Well it happens on the Vu Duo

... with an ET box I do not see this... so in fact we suggest now that incorrect values are forwarded from the frontend (via the drivers)...

I did intent to return the values from the frontend in the first place.... Because usually these are the real values....

Hard to solve this without asking VU to upgrade it in their drivers..........????

Et9200 displays fec ok but not modulation and system. Why is manual scan screen finding the current transponder ok if is a driver problem?

[littlesat]

Why is manual scan screen finding the current transponder

Due to smart tuners can adjust these parameters.... even when you entered incorrect ones.

[pieterg]

It's not necessarily tuning with the wrong parameters, it's just reporting the wrong parameters. (the issue is merely cosmetic)

[razorback]

so, here my results:

VU+Duo and ET-9100
Both OpenPli 2.1 from March 5 2012

Display is correct on both:
DVB-S2 8PSK 11361 MHz H 2/3 22000

Both with Skin HD-GLASS-16 !!!

....whatever you may make of this.....

R

[Huevos]

Yes, it is merely cosmetic, but it is still wrong where ever the fault lies. So here is my question: How can I access the correct info that is available to manual scan? What variable contains that info and how could I call it?

[Huevos]

Display is correct on both:
DVB-S2 8PSK 11361 MHz H 2/3 22000

Both with Skin HD-GLASS-16 !!!

....whatever you may make of this.....

Ok, but we all know that HD-GLASS-16 modifies certain system files, so although your post is helpful it doesn't tell us where that data is coming from.

Pieterg, apart from false what other options does fedata have?

[pieterg]

apart from false what other options does fedata have?

True, which will give the 'original' data, i.e. the transponder parameters from the lamedb.

[Huevos]

Ok, thanks. I'm going to try that and see what I come up with. Thank for your help.

[littlesat]

Display is correct on both:
DVB-S2 8PSK 11361 MHz H 2/3 22000

Both with Skin HD-GLASS-16 !!!

And without Glass skin...when it is 100% completely removed??? (not only disselected)...? May I suggest that glass makes something corrupt here????

True, which will give the 'original' data, i.e. the transponder parameters from the lamedb.

This was not intended to do.... as some tuners may correct faulty stuff in lamedb automatically and then you can go wrong again....

Edited by littlesat, 9 March 2012 - 17:51.

[Huevos]

Pieterg, thanks for pointing me in the right direction.

Littlesat, you've got a choice (as this is only cosmetic), either use data that you are in control of (lamedb) and display the correct parameters, or use the data you are not in control of and when it doesn't work properly just tell everyone it is down to the manfacturer of the receiver and it is up to them to correct it. Just one more question: why should the data in lamedb be wrong anyway? What is the cause?

True {'inversion': 'Auto', 'tuner_signal_quality': 65535, 'modulation': '8PSK', 'tuner_type': 'Satellite',
False {'inversion': 'On', 'tuner_signal_quality': 65535, 'modulation': 'QPSK', 'tuner_type': 'Satellite',
'symbol_rate': 22000000, 'system': 'DVB-S2', 'polarization_abbreviation': 'H', 'tuner_signal_power': 51760,
'symbol_rate': 22000000, 'system': 'DVB-S', 'polarization_abbreviation': 'H', 'tuner_signal_power': 51760,
'polarization': 'Horizontal', 'tuner_bit_error_rate': 0, 'fec_inner': '2/3', 'orbital_position': 'Astra 1H/1KR/1L/1M/2C(19.2E Ku-band)',
'polarization': 'Horizontal', 'tuner_bit_error_rate': 0, 'fec_inner': 'Auto', 'orbital_position': 'Astra 1H/1KR/1L/1M/2C(19.2E Ku-band)',
'frequency': 11361000, 'tuner_signal_quality_db': None, 'tuner_locked': 1, 'tuner_number': 0, 'tuner_synced': 1, 'tuner_state': 'LOCKED',
'frequency': 11361000, 'tuner_signal_quality_db': None, 'tuner_locked': 1, 'tuner_number': 0, 'tuner_synced': 1, 'tuner_state': 'LOCKED'}
'pilot': 'Auto', 'rolloff': '0.35'}

[littlesat]

I think the manufacturer of the boxes should fix it.....

I want to see the current parameters that the tuner found. And when the manufacturer will not fix it then force the true/false elsewhere in the code is prefereble I suggest..... and not a patch in this converter.... so that it might be "corrected" at any place this data is used.

why should the data in lamedb be wrong anyway? What is the cause?

Some more intelligent tuners can correct incorrect settings in an automatic way..... So when you "feed" the tuner with a FEC of 3/4 and the transponder is at 5/6 the tuner will still tune -and- this gives also bad info...

So the choice is always bad, especially when the tuner (or boxdrivers) do not reply with correct values

Edited by littlesat, 9 March 2012 - 18:54.

[Huevos]

I want to see the current parameters that the tuner found. And when the manufacturer will not fix it then force the true/false elsewhere in the code is prefereble I suggest..... and not a patch in this converter.... so that it might be "corrected" at any place this data is used.

Where else would you suggest? And excuse my ignorance but what else uses this converter?

Edited by Huevos, 9 March 2012 - 19:08.

[littlesat]

E.g. menu->information->Stream Information..... and all other stuff....

In the beginning it is the manufacturer of the box that makes the fault!!!

First we need to now if this failure is only valid for all the VU-boxes.... -or- only the DUO....

[Huevos]

First we need to now if this failure is only valid for all the VU-boxes.... -or- only the DUO....

It is the Duo and Ultimo for sure, and maybe the Uno and Solo as well. ET9200 reports the FEC correctly but system and modulation wrong (always QPSK) when set to false.

Edited by Huevos, 9 March 2012 - 19:24.

[littlesat]

I have system, modulation and FEC correct here with ET box????

[Huevos]

I have system, modulation and FEC correct here with ET box????

I haven't got one but I asked a friend and he said:

A quick check on ET9200 on
BBC HD, on 28E. Infobar shows: DVB-S, QPSK 8/9
C4 HD, on 28E. Infobar shows: DVB-S, QPSK 2/3

C4 HD is DVB-S2 and 8PSK, and BBC HD is DVB-S2

Edited by Huevos, 9 March 2012 - 23:16.

[spock]

I have noticed this too, but I dont currently have access to my box to post any better details..

As far as I can remember the problem seemed to come from using blind scan exclusively on my vu+ultimo, I think more or less all the data is stored as "Auto" in the lamedb. And then wrong values are shown. Anyway the correct information can be seen in information "Tuner status".

I have a few DVB-T tuners too, and they show no information at all on the skin (from PliExtraInfo for whatever it's called). Only thing shown is for example: DVB-T 6900000 (i.e. the frequency 690MHz). Not all too important but anyway, would be nice to see some details there too.

[razorback]

well, guys

you all are riding the horse "HD-Glass-Skin" is BAD, BAD, BAD

but obviously the author (shamann) has found a way to put information straight, didn't he ?

on one of the posts in this thread, Glass-Utilities was used to prove things.
Same author as glass skin - what a surprise !!
(btw does Glass-Utilities also "change system files" ?)

however - it seems to me PLi-Team should try to recruit the author of this stuff (shamann) in order to put things right in terms of information of vital system data.

@littlesat
you said:
And without Glass skin...when it is 100% completely removed??? (not only disselected)...? May I suggest that glass makes something corrupt here????
excuse me, but what could glass "make corrupt" by displaying the correct data ??????

@huevos
you said:
Ok, but we all know that HD-GLASS-16 modifies certain system files, so although your post is helpful it doesn't tell us where that data is coming from.

Well, apparently the maker of Glass-16 DOES know .

Again, I would really suggest the Team to contact this shamann-person - it would definitely be an enhancement....

R

[pieterg]

the glass skin is not in any way related to this frontend info issue, so please do not drag it into the discussion.