Structure of the "Services"-File

of the Dreambox satellite receiver

Part 1 example: 
eDVB services /2/
transponders
fe3e0468:0000:0000
	s 11601000:6111000:0:3:-450:0:0
/
(...)
end
... and so on, schematically the lines have this appearance:
0xNamespace:0xTSID:0xNID
s freq(khz):symbolrate(hz):pol:fec:pos:y:z
with The y value info is from Harry again: "stands for the Inversion in Polarization. Although, we set this value always to 0 (auto), as stated in the DreamSet changelog (10/06/2007 - ver 2.14 beta). You can take a look at the Enigma format description in German. Settings are for the dbox, but they are much alike to the dreambox settings."

I can watch most European satellites but only on Astra 2 (28 ° E) I found y and z values other than 0. On some Sky transponders I found the combination 2:0 and 2:4. The ONID is 2 but on other satellites y is 0 though Lyngsat mentiones an ONID. The z value only appeared in a services file from my Dreambox 7020S.

Part 2 example: 
f1cc:00c00000:0421:0001:1:23739
Bibel TV
f:1,p:
schematically:
0xSID:0xNAMESPACE:0xTSID:0xNID:type:prognumber
Station Name (customable)
(f:1,p:) or (c:000020,c:010021,c:020031,c:030020,p:Bibel TV)
Harry added this information about the f value, thank you again: 
f: means that flags follow 
the flags 
 
The flags is a bit pattern, expressed in hexademical form. 
  enum 
  { 
  dxNoSDT=1, // don't get SDT 
  dxDontshow=2, 
  dxNoDVB=4, 
  dxHoldName=8, 
  dxNewFound=64 // found in prev scan 
  }; 
 
For example: 
f:40,p means that the bit pattern is 64 (decimal) that corresponds to dxNewFound 
 
dxNoSDT: the servicename will not be automatically updated by the Satellite Data Stream , used to prevent change any parameter of a single service 
dxDontshow: Hidden service 
dxNoDVB: ServicePIDs will be retrieved by the Cache, instead of the current Stream 
dxHoldName: to prevent change service_name 
dxNewFound: Service found in previous scan 
 
3. -------------------Favorites List----------------- 
 
As written in the German site I sent you, here you have the meaning of #SERVICE: 1:0:1:378a:44c:13e:820000:0:0:0: 
 
#SERVICE: 1:0:1:378a:44c:13e:820000:0:0:0: 
---------------------------------------------------------- 
#SERVICE: - every line contains a SERVICE statement in userbouquet.dbe**.tv 1: Favorites type: -1=invalid id, 0=structure id, 1= Dvb Service, 2= File 
0: Flags (7 bit pattern expressed in hexademical form), for explanation see below 
1: Service type (1=tv, 2=radio, 3=data) 
378a: SID 
44c: TSID 
13e: ONID 
820000: Namespace 
0: maybe for future use, i don't know 
0: maybe for future use, i don't know 
0: maybe for future use, i don't know 
 
Flags (in parenthesis the decimal value of the flag is stated): 
1.Bit(01): It's about a Directory. // SHOULD enter (implies mustDescent) 
2.Bit(02): The user must change to the directory // cannot be played directly - often used with "isDirectory" (implies canDescent) 
3.Bit(04): The user may change to the directory // supports enterDirectory/leaveDirectory 
  The Bits 1-3 have sense if set together 
4.Bit(08): The content of the folder needs to be automatically sorted. // should be ASCII-sorted according to service_name. great for directories. 
5.Bit(16): The Service has (enigma-internally) a sort-key. // has a sort key in data[3]. not having a sort key implies 0. 
6.Bit(32): Sort key is 1 instead of 0 7.Bit(64): It's a marker 
8.Bit(128): The service is not playable 
 
/* 
  for example: 
  normal services have none of them - they can be fed directly into the "play"-handler. 
  normal directories have both of them set - you cannot play a directory directly and the UI should descent into it. 
  playlists have "mustDescent", but not "isDirectory" - you don't want the user to browse inside the playlist (unless he really wants) 
  services with sub-services have none of them, instead the have the "canDecsent" flag (as all of the above) 
*/
Radiovibrations.com -> Dreambox Notes