60 replies to this topic

[ims]

Why do you think that could get an incorrect provider? Channel id is unique.

I think, in case, when lamedb is not actual ?

Edited by ims, 22 March 2015 - 17:51.

[littlesat]

Not allone lamedb... in a userbouquet there could be different channels from different providers....

 

I suggest it is better to create a softlink on serviceref... (So to do it really right)

[Taapat]

And what is the probability that lamedb isnt actual?
If the channel is in a bouquet what the user used regularly, then it is likely that this channel is actual in lamedb. If the channel is not used, then which worried that it will not show the correct information?

 

What do you think with the softlink on serviceref? Create a link with the provider name? How it will work if need both the channel and the provider picons? I do't think that someone will do it.

 

Or I can understand correctly, and with this that issue is closed, and no changes can be expected (especially in .cpp)?

[littlesat]

When we change this it should be made good...

But provider icons are skin specific... and I suggest skins that support that feature do have a renderer/converter for it.....

[Taapat]

Yes of course, I am using own renderer PiconProv, but there isn't discussion about it.
I've seen that a lot of skin is used privider pcon. Maybe I'm looking the wrong skins? Maybe this is a bad habit, and needs to be removed from the skins...

[littlesat]

Can you post that renderer here....?

[maigais]

nothing better than for ServiceName2  
 

Attached Files

•  screenshot_2015-03-22_21-38-23.jpg   126.64KB   3 downloads
•  screenshot_2015-03-22_21-39-46.jpg   138.83KB   3 downloads

[ims]

Hey guys, do not thinking about it, that it seems more as skin for inspectors DVB

[littlesat]

Servicename2 is a stupid name here...,you better could call it picongetter or something like that... (Remember the way it is made slows down the performance, but it seems nobody cares)
I would recommend to leave these x-mass tree stuff to the specific skins...

But still with the current method service bane can get the provider name and there are also convertere to get the satposition.... So with changes to a picon renderer all this could be arranged in a quick an structured way.... The renderer searches a picon on providername or satpos.... (Or add a type to e current picon renderer)

Edited by littlesat, 24 March 2015 - 07:59.

[Taapat]

Can you post that renderer here....?

This renderer PiconProv which I have been using is identical standard renderer Picon, just looking for picons in the folder piconProv to easier manage them. But of course for this can also be used standard penderer Picon.

 

nothing better than for ServiceName2

Do you understand something from python, and looked in ServiceName2 code?

 

Remember the way it is made slows down the performance, but it seems nobody cares

I am worried about performance, so I hope that you will find a way how to add this in cpp.

Edited by Taapat, 24 March 2015 - 10:42.

[littlesat]

you can get the provider name from a specific service via service name.... and then simply look at this service name to the specific picon with the same name (and remove special chars and make it lower case)... and not look for references or so... Then no loops are required at all in python.

[Taapat]

1. Service name does not work on channels with such as cyrillic encoding.
2. This I can do for himself, but ask others to do so to use my skin is not realistic.

[littlesat]

1. Also not with the trick from huevos... to seach picon on channel name...?

[Taapat]

If you are talking about Picons by 'Service name':

Very nice option but it works only for users who use latin characters.
First of all, as I wrote in another topic, it will not work if in the name of the channel is, for example, the Cyrillic symbol. Maybe someone has an idea how to use such names. Maybe could be used translit from here: https://github.com/j2a/pytils to replace the symbols, but I think, that replace it one by one, is slowly. If it would be acceptable for one picon, then build the channel list with picons, not seem a good idea. Maybe someone else has a better and faster solution?

[Taapat]

The code is not mine, so I do not understand it 100%, so I added loop count and an additional print, to see how deep is the loop for provider and services in reality.
I walk around my bouquets, in which are channels from different providers.
I found that the provider is found immediately and there is not any loop, but for most services it is from 1 to about 15, the largest 30.
So the reality is not so bad.
Maybe you can add the code from my pach with big TODO?
He should not have any effect on standard provider using.

[maigais]

what's the point,
Viasat Internet provider does not add lamedb
2boom, found a solution ServiceName2.
and can be seen in my screnshoft

[ims]

then would be better using it still as part of skin...

[littlesat]

For streams enigma2 does not have a provider field... This simply does not exists.... So someone make a real uggly work-a-round in a servicename2.py. I suggest use this hack or find a better way, e.g. Add somehow a provider name featur for streams in enigma2...

[maigais]

lamedb not provider Viasat


1st Baltic Ch. Estonia
p:,c:001839,c:031839,c:01183a,C:0000
183f:00320000:000d:0055:128:0

1st Baltic Ch. Lithuania
p:,c:00184d,c:03184d,c:01184e,C:0000
1856:00320000:000d:0055:1:0

REN-TV LIETUVA
p:,c:001861,c:031861,c:011862,C:0000
186a:00320000:000d:0055:1:0


2boom,implemented without the emergence provider lamedb

Edited by maigais, 26 March 2015 - 16:22.

[littlesat]

Then this should be added in lamedb.... ...

 

for streams this is different. Streams are not in lamedb.... So you should add some functionality for this one.... That is the structured way to do it...

 

E.g. what i did today... checking in a channelname on endswith("3D") is easy.... adding a flag to do it in a structured way less easy, but a more stuctured way...