33 replies to this topic

[jpuigs]

I've modified channel list skin's code to include a transponder or frequency information when browsing channel lists.

<widget borderWidth="2" source="ServiceEvent" foregroundColor="foreground" backgroundColor="secondBG" render="Label" position="598,635" size="571,25" transparent="1" noWrap="1" font="prive3; 22" zPosition="1">

      <convert type="ServiceName2">TpansponderInfo</convert>

    </widget>

 

I want the terrestrial freq. to be shown in Mhz format , not Khz.

 

On ServiceName2.py file , line which contains:

elif f == 'F': # %F - frequency (dvb-s/s2/c/t) in KHz

    if type in ('DVB-S','DVB-C','DVB-T'):

     result += '%d'%(self.tpdata.get('frequency', 0) / 1000)

 

 

has been "slipt" to be different between DVB-T and DVB-S

elif f == 'F': # %F - frequency (dvb-s/s2/c/t) in KHz

    if type in ('DVB-S'):

     result += '%d'%(self.tpdata.get('frequency', 0) / 1000)

    if type in ('DVB-T','DVB-C'):

     result += '%.3f'%(((self.tpdata.get('frequency', 0) / 1000) +1) /1000)

 

The "+1" is there because terrestrial freq's. showed 569999 instead 570000

 

But I have a problem:

If I use the last code I've written, I get 184.000 , and the real value I'd have to get is 184.500 Mhz.

If I change code to

result += '%.3f'%((self.tpdata.get('frequency', 0) / 1000) +1)

I get : 184500.000 

 

I want to get 184.500

 

How Could I do it ?

 

[littlesat]

Devide the freq by 1000000

[MiLo]

1/2 delivers an integer result in Python, hence it's "0". If one of the numbers is a floating point, it will use floating point output.

 

>>> 1/2
0
>>> 1.0/2
0.5
>>> 1/2.0
0.5

So use "1000.0" instead of "1000" and it'll probably do as you expect.

[MiLo]

By the way, if you want to "round" the outcome, add half the divider:

 

kHz = (MHz + 500)/ 1000

 

That will work better than the "+1" later on.

[jpuigs]

OK thanks. I'll try.

[jpuigs]

Solved.

if type in ('DVB-C','DVB-T'):

     result += '%.3f'%(((self.tpdata.get('frequency', 0) / 1000) +1) / 1000.0) +" Mhz. "

Attached Files

•  channellist.jpg   109.71KB   6 downloads

[littlesat]

I suggest you only need to adjust the +1... See post #4

[jpuigs]

Done.

result += '%.3f'%(((self.tpdata.get('frequency', 0) +500) / 1000) / 1000.0) + " Mhz. "

Thanks.

[littlesat]

And now the en results of your code please...

[athoik]

result += '%.3f'%(((self.tpdata.get('frequency', 0) +500) / 1000) / 1000.0) + " Mhz. "

 

Better to use Mhz inside formating.

result += '%.3f Mhz. '%(((self.tpdata.get('frequency', 0) +500) / 1000) / 1000.0)


>>> '%.3f Mhz. '%(((350000000 +500) / 1000) / 1000.0)
'350.000 Mhz. '

[jpuigs]

Better to use Mhz inside formating.

result += '%.3f Mhz. '%(((self.tpdata.get('frequency', 0) +500) / 1000) / 1000.0)


>>> '%.3f Mhz. '%(((350000000 +500) / 1000) / 1000.0)
'350.000 Mhz. '

 

Thanks, I didn't know it.

I tried mine's, and as It worked, I thought it was correct.

 

 

And now the en results of your code please...

 

What do you mean ? screenshot ?

[jpuigs]

The final results.

 

Using Pli-HD Skin and some others (f.i. PD1-LOI-FullHD), when I'm browsing into Channel Lists, it may hapopen that you have several services with similar or equal names.

So, a simple way of knowing which service we are browsing is to have it's technical frequency details on screen.

I remember to have seen it on some other skins some time ago.

 

We have to include the python file Servicename2.py on /usr/lib/enigma2/phyton/Components/Converter/

I got it from 2boom and modified it to show some frequencies in a desired way as you've already read before.

 

 ServiceName2.py   22.67KB   11 downloads

 

 

Then, using skin file ( /usr/share/enigma2/PLi-HD/skin.xml ) I edit it and make channel List a bit smaller, to have enough space to include an info line.

 

I change on line 237 size, 690,510 to 690,450

<widget name="list" position="530,110" size="690,510" itemHeight="30" colorServiceDescription="yellow" transparent="1" serviceNumberFont="Regular;24" scrollbarMode="showOnDemand" serviceInfoFont="Regular;22" serviceNameFont="Regular;24" serviceItemHeight="30" foregroundColorServiceNotAvail="#656565" foregroundColorEventSelected="#ccc040" foregroundColorMarkedSelected="#902020" backgroundColorMarkedSelected="#656565" selectionPixmap="PLi-HD/buttons/sel.png" />

to:

<widget name="list" position="530,110" size="690,450" itemHeight="30" colorServiceDescription="yellow" transparent="1" serviceNumberFont="Regular;24" scrollbarMode="showOnDemand" serviceInfoFont="Regular;22" serviceNameFont="Regular;24" serviceItemHeight="30" foregroundColorServiceNotAvail="#656565" foregroundColorEventSelected="#ccc040" foregroundColorMarkedSelected="#902020" backgroundColorMarkedSelected="#656565" selectionPixmap="PLi-HD/buttons/sel.png" />

and after that I add the following line:

<widget borderWidth="2" source="ServiceEvent" foregroundColor="green" backgroundColor="secondBG" render="Label" position="550,590" size="620,26" transparent="1" noWrap="1" font="Regular; 24" zPosition="1">

      <convert type="ServiceName2">TpansponderInfo</convert>

    </widget>

And finally I get that desired green info line:

 

 PLI-HD-mod1.jpg   86.59KB   2 downloads         PLI-HD-mod2.jpg   84.33KB   3 downloads

 

 

 

 

[dax]

Well done! Is it possible to show more info also for dvb-t channell? I mean

642.000 MHz 8k 64qam 2/3 1/4

instead of

642.000 MHz auto auto auto auto

Thanks

[Robinson]

Could this be implemented in a standard PLi HD skin, please?

[littlesat]

Under the channel selector isn't a good idea.... possibly when a better place could be found it can be considered...

[jpuigs]

Well done! Is it possible to show more info also for dvb-t channell? I mean

642.000 MHz 8k 64qam 2/3 1/4

instead of

642.000 MHz auto auto auto auto

Thanks

 

Well, I think it's not always possible.

It depends on "how" channels have been tuned and stored.

That info green line shows data stored on (db) channel lists, so if you have stored several services using "auto" options (which always work on DTT services) , you'll see "auto" values always.

Correct me if I'm wrong please.

 

 

 

Could this be implemented in a standard PLi HD skin, please?

 

If they want, it'd be a good idea.

 

 

Under the channel selector isn't a good idea.... possibly when a better place could be found it can be considered...

 

Why ?

I've reduced list size to have enough space to place it.

Where would you place it ?

[Robinson]

By the way, is this the same info that is available under Menu - Show transponder info (when in channel list)?

Because my dream would be to somehow see more information (at least SID, and perhaps VPID, APID) without actually having to zap to the channel.

[jpuigs]

Yes, it's the same info. Info stored on database

The info you'd like to see, would be shown if it's stored on lamedb.

I think that PIds are not always stored.

[dax]

 

Well, I think it's not always possible.

It depends on "how" channels have been tuned and stored.

That info green line shows data stored on (db) channel lists, so if you have stored several services using "auto" options (which always work on DTT services) , you'll see "auto" values always.

Correct me if I'm wrong please.

 

 

Thanks for the answer!

Is it possible to remove "auto" mode? From wich files? My utopia

When we go to the main channel list (by typing down arrow) the widget show 0 Mhz. Could you delete?

 

[dax]

Thanks for the answer!

Is it possible to remove "auto" mode? From wich files? My utopia

When we go to the main channel list (by typing down arrow) the widget show 0 Mhz. Could you delete?

 

If i modify the lamebd file

eeee0000:23e5:217c
	t 641999999:0:5:5:3:2:4:4:2:0:0:0

doesn't work...