Jump to content


Member Since 1 Dec 2011
Offline Last Active 20 Jan 2013 13:49

Topics I've Started

Extended Event Descriptor

20 January 2012 - 10:50

The extended event descriptor is not read correctly in event.cpp
It works most of the time, however the dvb spec allows for the extended event descriptor to be segmented into multiple extended event descriptors, which is not handled here.
enigma2 is storing all extended event descriptors it finds but only using 1 of them.

Content descriptors

16 January 2012 - 19:40

Here is a patch for enigma2 to enable caching of the content descriptor and allow the data to be retrieved with lookupEvent and search.

The function declaration in event.h may need to be moved so that we can request the information from the event in python.

Currently this will allow listing event categories such as (Movie/Sport/etc...), to specific highlight when we show the information.

For a future release I will look into adding a search option for the content descriptor, so we can perform searches like, show all movies or show all sporting events.

Content descriptors are typically 2 bytes for the descriptor header, and 2 bytes for the classification. However since the descriptors do allow for multiple classifications you could potentially have 2 bytes descriptor and n*2bytes classifications. This should therefore have a minimal impact on memory usage.

eepgcache and title searching

7 January 2012 - 10:33

I am searching for title string in eepgcache and it seems that it does not work correctly with special or accented characters.
Could anyone confirm if there is something special I need to do for this to work?

service number

5 January 2012 - 08:01

Would it be possible to change eServiceReference to store the service number and eServiceReferenceDVB to take a service number as a parameter to the constructor?
Currently in db.h we in loadServicelist we read service_number from lamedb but we never store or use it other than to check if it is set to -1 to skip the service in lamedb.

If we store it then we can let people set service numbers for the whole list, but it would also allows us to add something like #NUMBER to the user bouquets to allow for individual service numbering in bouquets.
Of course this requires a change to InfoBarNumberZap and ChannelNumber renderer, but I think this would allow us to be more flexible with channel numbering and also keep old behaviour and compatibility with userbouquets from other enigma2 releases.

How does channel numbering work?

4 January 2012 - 08:48

Can anyone explain how channel numbering works in the current images?