There's a file in
/tuxbox/apps/dvb/libdvb++/include/dvb/id/Attic/service_type.h
which contains this table:
enum ServiceType {
/* 0x00 - 0x10: ETSI EN 300 468 V1.5.1 (2003-01) */
ST_RESERVED = 0x00,
ST_DIGITAL_TELEVISION_SERVICE = 0x01,
ST_DIGITAL_RADIO_SOUND_SERVICE = 0x02,
ST_TELETEXT_SERVICE = 0x03,
ST_NVOD_REFERENCE_SERVICE = 0x04,
ST_NVOD_TIME_SHIFTED_SERVICE = 0x05,
ST_MOSAIC_SERVICE = 0x06,
ST_PAL_CODED_SIGNAL = 0x07,
ST_SECAM_CODED_SIGNAL = 0x08,
ST_D_D2_MAC = 0x09,
ST_FM_RADIO = 0x0A,
ST_NTSC_CODED_SIGNAL = 0x0B,
ST_DATA_BROADCAST_SERVICE = 0x0C,
ST_COMMON_INTERFACE_RESERVED = 0x0D,
ST_RCS_MAP = 0x0E,
ST_RCS_FLS = 0x0F,
ST_DVB_MHP_SERVICE = 0x10,
/* 0x11 - 0x7F: reserved for future use */
ST_MULTIFEED = 0x69
/* 0x80 - 0xFE: user defined */
/* 0xFF: reserved for future use */
};
I'm looking for defining a 0x96 so it's known as a digital TV service
but since no multiple same name labels can be used here to assign different entries/values to the same label,
I'm rather looking for the other part of the process, where
the actual service type parsing will occur, and do a case condition
to switch to 0x01 in case it reads 0x96, yet before the value is returned
to the process.
This way I'd likely be able to get those TV services of a certain provider,
which otherwise Dreambox won't bother with, since they show 0x96 and not 0x01, to be considered TV service after all, and reported as available
TV services back by Dreambox.
Right now, those are getting recognized as Data service, with no other
PIDs detected.
any ideas to help me get on the right track, folks?
TIA,
jarek
Service Type parsing and switching the value...(??)
-
- Neugieriger
- Beiträge: 10
- Registriert: Donnerstag 15. Juli 2004, 21:34
-
- Developer
- Beiträge: 331
- Registriert: Freitag 7. Februar 2003, 22:17
hi,
a) at first these declarations are only SYMBOLS for the programmes - it is easier not to have every hex number in mind, but to have symbols which represent those.
b) 0x96 is declared as "user defined" which means there is no standardisation for this hex value. you may treat the scan procedures that parse the SDT to cast 0x96 to 0x01.
c) on which satellite/transponder did you find this value?
regards
mws
a) at first these declarations are only SYMBOLS for the programmes - it is easier not to have every hex number in mind, but to have symbols which represent those.
b) 0x96 is declared as "user defined" which means there is no standardisation for this hex value. you may treat the scan procedures that parse the SDT to cast 0x96 to 0x01.
c) on which satellite/transponder did you find this value?
regards
mws
cu
mws
mws
-
- Neugieriger
- Beiträge: 10
- Registriert: Donnerstag 15. Juli 2004, 21:34
>at first these declarations are only SYMBOLS for the programmes
Correct, but from this point on, the particular service type
is being referred to as a label and not a value, so as I said,
I'd be rather looking for the actual piece of sourcecode elsewhere,
to swap it with 0x01 as soon as it's being parsed as 0x96
and what I'm actually looking for, is where it is being so I could
add an extra condition there.
To answer your other question, the satellite we're talking about here,
is Nimiq1, 91W and the actual "problem" regards pretty much all the transponders of this particular (sole, to this satellite) provider.
There's a similar situation as well, with some other satellites nearby,
Echostar 6,8 110W and Echostar 7 119W, except those use 0x9A
instead.
There's lots more little annoying differencies to cover (as compared to standard DVB protocol) here at 70W and beyond...
Correct, but from this point on, the particular service type
is being referred to as a label and not a value, so as I said,
I'd be rather looking for the actual piece of sourcecode elsewhere,
to swap it with 0x01 as soon as it's being parsed as 0x96
and what I'm actually looking for, is where it is being so I could
add an extra condition there.
To answer your other question, the satellite we're talking about here,
is Nimiq1, 91W and the actual "problem" regards pretty much all the transponders of this particular (sole, to this satellite) provider.
There's a similar situation as well, with some other satellites nearby,
Echostar 6,8 110W and Echostar 7 119W, except those use 0x9A
instead.
There's lots more little annoying differencies to cover (as compared to standard DVB protocol) here at 70W and beyond...
-
- Developer
- Beiträge: 331
- Registriert: Freitag 7. Februar 2003, 22:17
-
- Neugieriger
- Beiträge: 10
- Registriert: Donnerstag 15. Juli 2004, 21:34
-
- Senior Member
- Beiträge: 5071
- Registriert: Dienstag 18. September 2001, 00:00
-
- Neugieriger
- Beiträge: 10
- Registriert: Donnerstag 15. Juli 2004, 21:34
Sure I can do that.
Please pm me with some ftp space or e-mail adderess,
I could send you an attachment to... (can't do here)
Pieces of a complete ts might possibly be a more valuable information
than some (not always complete) text extracts.
I could also open up the ports on my router to let you
in my receiver temporarily, if you needed live access
to those birds...
jarek
Please pm me with some ftp space or e-mail adderess,
I could send you an attachment to... (can't do here)
Pieces of a complete ts might possibly be a more valuable information
than some (not always complete) text extracts.
I could also open up the ports on my router to let you
in my receiver temporarily, if you needed live access
to those birds...
jarek
-
- Senior Member
- Beiträge: 5071
- Registriert: Dienstag 18. September 2001, 00:00
-
- Neugieriger
- Beiträge: 10
- Registriert: Donnerstag 15. Juli 2004, 21:34