Forums

Hi guys,

I have a question regarding the structure of lamedb file.
It looks like it consists of 2 sections:
- transponders
- services

Transponder section looks like that:

001f0000:0001:002a
	s 12640000:15000000:1:3:31:2:0:1:2:0:2
/

Service section looks like that:

d048:011a0000:090a:0002:1:0
True Movies 1
p:BSkyB

My question is how does the service "know" which transponder it is for?

Transponder & services entries both contain a namespace (to identify sat) & TransponderID (to specify TP). If your example contained a service from the example tp you'd probably have seen it yourself...

--
hemi

Thanks alot.

I think I got it:

Transponder section:
011a0000:07d2:0002
s 11739000:29500000:1:3:282:2:0:1:1:0:2
/

Service section:
0fa1:011a0000:07d2:0002:25:0
Sky Sports 1 HD
p:BSkyB,c:050001

I'm not sure if the 0002 following Transponder ID is also part of the identification between transpoder and service in lamedb..

yes it is, it's the onid (original network id)
Together (namespace:tsid:onid) they form the unique identification of a transponder.

Thanks a lot, guys.

I would like to ask about some parameters in lamedb.

 

I have noticed the following:

c:00ABCD = PID video

c:01ABCD = PID audio

c:02ABCD = PID TXT

c:03ABCD = PID PCR

c:04ABCD = PID AC3

 

However, there are some extra parameters:

c:05ABCD = ???

c:09ABCDEFG = ???

Does anybody know what they are used for? Are there any others? Such as c:06, c:10 or c:1f ?

 

Also, how is parameter C:ABCD = used? For example, C:2600, C:0963, C:0100. I know it is a CAID but how does the presence of this parameter change the behaviour of our boxes?

0 VPID

1 APID

2 TPID

3 PCRPID

4 AC3PID

5 VTYPE       // looks like video type

6 ACHANNEL // don't know what that is

7 AC3DELAY

8 PCMDELAY
9 SUBTITLE

 

So you are correct with 0-4.

Edited by betacentauri, 26 September 2013 - 19:30.

c:09ABCDEFG = ???

9 SUBTITLE

 

Let's take an example of ITV2 HD:

c:092418800

241 is TXT PID in hex but what is 8800?

And what if TXT PID is longer than 3 characters?

Does anyone know?

lamedb is managed  in lib/dvb/db.cpp in the enigma2 repository. Maybe you find follow the leads in there to figure this out...

Transponder section:
011a0000:07d2:0002
s 11739000:29500000:1:3:282:2:0:1:1:0:2
/

Service section:
0fa1:011a0000:07d2:0002:25:0
Sky Sports 1 HD
p:BSkyB,c:050001
 

 

Hi,

 

I would like to manually add a transponder and a service which is not broadcasting at the moment (maybe only occasional feeds) to lamedb.

I know this seems not to make sense at all but I need that for some testing purposes.

Basically, I need any Ku band channel from 27.5W other than those at 11495 V. Of course, I have not seen any ready-made channel list with such a channel, which is understandable.

An example would be 11609 V, DVB-S, QPSK, 5632, 3/4, NID=0, TID=0 as listed by Kingofsat.

Does anyone know how to arrange those transponder and channel sections in lamedb to accommodate this particular or any other dummy channel from 27.5W?

 

Perhaps something like this:

 

Transponder section:
0cfdace7:0000:0000
s 11609000:5632000:1:3:-275:2:0
/

Service section:
0001:0cfdace7:0000:0000:1:0
Dummy Channel at 27.5W
p:Dummy provider

Edited by Robinson, 3 August 2014 - 21:02.

I would just like to confirm the above example works.

Can someone explain how the NAMESPACE value is derived?

Have a look at:

 

This piece of code converts lamedb to VDR format, it contains the info to figure out lamedb

https://bitbucket.or...dr.sh?at=master

 

This is enigma code wich helped/gave the needed info for the above

https://raw.githubus...frontendparms.h

Can't see anything about namespace there.

look at getHash for info? http://sourceforge.n...ontend.cpp#l387

for sat pos part of namespace eg...

<sat name="19.2E Astra 1KR/1L/1M/1N Ku Band" flags="1" position="192">
192 decimal converted to hex gives c0
namespace is 00c00000

<sat name="28.2E Eutelsat 28A..Astra 2A/2E/2F" flags="1" position="282">
282 decimal converted to hex gives 11a
namespace is 011a0000

I think the term "namespace" may be used for at least 2 different things.

The one LraiZer is saying takes into consideration satellite position in hex and so it should be the same for all channels on the same satellite (00820000 for Hot Bird). Right?

However, if you look at OpenWebif, tab "Current", you will see some information regarding the channel that is on now and one of the parameters is NAMESPACE.

For example for Euronews at 13E (SID 8211) we can see namespace 8519680. Why is it therefore different from the one above?

I think the term "namespace" may be used for at least 2 different things.

The one LraiZer is saying takes into consideration satellite position in hex and so it should be the same for all channels on the same satellite (00820000 for Hot Bird). Right?

However, if you look at OpenWebif, tab "Current", you will see some information regarding the channel that is on now and one of the parameters is NAMESPACE.

For example for Euronews at 13E (SID 8211) we can see namespace 8519680. Why is it therefore different from the one above?

It doesn't contain SID. According to LraiZer's link it is position, frequency and polarization, giving each transponder a unique namespace.

c:05xxyy - definition video type

c:09zzzz0101 - SUB pid

c:12zzzz - AAC pid

c:16zzzz - PMT pid

 

not known different f:4 vs f:5

Edited by EnoSat, 22 August 2018 - 21:45.

What about western satellite positions.  What is the difference on the name space hash?  Its not as simple as converting it to hex.. There is some other formula missing?

Got it.... 3600

 

For 127w

 

3600 - 1270 = 2330 Dec = 091a Hex