Results 1 to 19 of 19

Thread: Separator

  1. #1
    Junior Member
    Join Date
    Jan 2008
    Posts
    35
    Thanks
    2
    Thanked 7 Times in 4 Posts
    Rep Power
    201
    Reputation
    103

    Default Separator

    Hi
    Could anybody put some infos how to find proper separator; what soft to use. There is no problem to find EMMpid for providers but there is a problem to find correct separator. Any help appreciated.



Look Here ->
  • #2
    Premium Member
    Al Bundy's Avatar
    Join Date
    Jan 2008
    Location
    Tazzie
    Posts
    4,479
    Thanks
    2,005
    Thanked 5,193 Times in 1,905 Posts
    Rep Power
    2204
    Reputation
    92850

    Default

    Gizmo, what are you using to look at the stream, SAT card or Decoder, and what brand and model?
    Cheers
    Ted (Al)

  • #3
    Junior Member
    Join Date
    Jan 2008
    Posts
    35
    Thanks
    2
    Thanked 7 Times in 4 Posts
    Rep Power
    201
    Reputation
    103

    Default

    I can use both methods:
    1. Hauppauge WinTV-Nexus-s with MasterLog
    2. Dreambox 7020
    where is the place to find separator for each provider

  • #4
    Premium Member
    Al Bundy's Avatar
    Join Date
    Jan 2008
    Location
    Tazzie
    Posts
    4,479
    Thanks
    2,005
    Thanked 5,193 Times in 1,905 Posts
    Rep Power
    2204
    Reputation
    92850

    Default

    Okay, its easy for me, I have a couple of Nokias, a DBox and a 9500S so I can use the Autodetect feature in MLog to get the PID and Seperator.

    As you know the PID of the stream you want to search just save a log of few seconds to a bin file, then view the file in an editor such as Hex Workshop or Ultra Edit you will get something like this, a sample from Aurora's IRD1 data Stream,

    401CC3482E8801000014680D11002F9251B69807513C008B2E 60F6F98D5B82401CC3482E8401000014680D1100B7C3D34B8A6F5CA2008B2F74 877F0B32FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF0082401CC3482E8001000014680D110008654282BAF8E50D008B3051 02C30A7982401CC3482E7B01000014680D1100C36EAEC41C290BD5008B3171 FB97CEA782401CC3482E7701000014680D110092356520015E9637008B32F7 36F0E35382401CC3482E7101000014680D1100AB36C0C842424465008B334A 5A2BC09682401CC3482E6D01000014680D1100084D5E59ECF11CC4008B347A 85648551FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF0082401CC3482E6901000014680D1100AD4EDE83F9E196D1008B35CB EC71AC4482401CC3482E6401000014680D11005304E666554598C5008B36B4 1187DA6982401CC3482E6001000014680D110048484803ADA7CF69008B3705 AD5F20B482401CC3482E5C01000014680D110014FB23F5430F08E5008B3893 573D98C482401CC3482E5801000014680D1100365E660F22D7B83B008B396C 749FD9F3FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFF0082401CC3482E

    As you can see every now and then you will get "filler bytes" of FF's with 00 after it, then 8240, thats the seperator, if you look through the sample provided you will see a few 8240's.

    Now I don't have a Dreambox or a Sat card so if some have an easier option i.e. software wise, maybe they can let you know, but probably the easiest way is to ask for the information,

    Aurora's Irdeto1 is 8240, so is Austar's Irdeto2, Aurora Irdeto2 is 8240 (was 8270).

    Just a note not as many "Filler Bytes" used in Austar Irdeto2 stream
    Cheers
    Ted (Al)

  • The Following User Says Thank You to Al Bundy For This Useful Post:

    OSIRUS (27-07-12)

  • #5
    Junior Member
    Join Date
    Jan 2008
    Posts
    35
    Thanks
    2
    Thanked 7 Times in 4 Posts
    Rep Power
    201
    Reputation
    103

    Default

    Thank you mate

  • #6
    Junior Member
    Join Date
    May 2008
    Posts
    12
    Thanks
    1
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    Does anyone log the UBI stream and if so could they post what the seperator is for this data or if anyone knows could they post it. many thanks

  • #7
    Junior Member
    Join Date
    Jan 2008
    Posts
    190
    Thanks
    1
    Thanked 25 Times in 15 Posts
    Rep Power
    205
    Reputation
    81

    Default

    Quote Originally Posted by Gizmo View Post
    Hi
    Could anybody put some infos how to find proper separator; what soft to use. There is no problem to find EMMpid for providers but there is a problem to find correct separator. Any help appreciated.
    The main issue with logging from a dream is the does not pass the whole packet. (The header is missing). As a result a slightly differnet way was needed to id the "start" of the packet. This method uses the "separator" to id the start of the packet, then applys know packet formats to work out the length etc.

    In most cases the seperator will be the 2 byte id for the EMM (when you are logging the EMM stream/PID). So if you know what sort of data you are looking at it should become clear. As others have stated, a raw log sample should show a pattern. eg: 0x8240... EMMs tend to cam in batchs of the same size. So the seperator will be at a constent offset for that batch. But remember the EMM packet size will change as needed, so this is just a way to try to ID the seperator.

  • #8
    Senior Member gw1's Avatar
    Join Date
    Jan 2008
    Location
    Hobart
    Posts
    957
    Thanks
    49
    Thanked 608 Times in 213 Posts
    Rep Power
    267
    Reputation
    1901

    Default

    Now there's a voice I recognise. Welcome crypto7, nice to see you again.

  • #9
    Junior Member
    Join Date
    Jan 2008
    Posts
    230
    Thanks
    12
    Thanked 44 Times in 28 Posts
    Rep Power
    211
    Reputation
    309

    Default

    one nice thing about a lot of dream box images, dvbsnoop is already there

    telenet into the box and at the prompt type dvbsnoop, to see if it is already installed, 7000-S and 7020's seem to have.

    As for the commands, umm well that is a little harder to work out, but all the information needed to log can be found.

  • #10
    Junior Member
    Join Date
    Jan 2008
    Posts
    190
    Thanks
    1
    Thanked 25 Times in 15 Posts
    Rep Power
    205
    Reputation
    81

    Default

    From al's post
    749FD9F3FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
    FFFFFFFFFFFFFF0082401CC3482E

    The CA stream is 184 data bytes long... that is, mlog will send 184 bytes of data after it drops the dvb header.
    This means that at some point they will decide not pad out a packet and start the next "command" in the new packet.

    To look at the last little bit

    FFFFFFFFFFFFFF0082401CC3482E

    FFFFFFFFFFFFFF <- Pad bytes so look for lines that have many FF one after the other (or what ever pad they may use)
    00 <- this is the offset to the next command... ie: 00 bytes away.
    8240 <- Seperator
    1CC3482E .... <-data

    To repeat.
    1. find a heap of pad bytes
    2. at the end of those should be 00
    3. the next 2 bytes should be the seperator.

    As to getting the CA_PID
    Using a dream and dvbsnoop
    1. Put the dreambox on a channel for the service you want to log (does not need to be decoding and giving pic, just on that channel.
    2. type in : dvbsnoop 1 -n 1

    this will give something like

    dvbsnoop V1.4.50 -- dvbsnoop - DVB Stream Analyzer, MPEG Analyzer[/url]

    ------------------------------------------------------------
    SECT-Packet: 00000001 PID: 1 (0x0001), Length: 36 (0x0024)
    Time received: Wed 2008-08-27 1914.892
    ------------------------------------------------------------
    0000: 01 b0 21 ff ff dd 00 00 09 04 09 6c e0 c0 09 04 ..!........l....
    0010: 09 0b e0 c0 09 04 06 24 e3 ea 09 04 06 04 e3 ea .......$........
    0020: ac 00 28 97 ..(.

    PID: 1 (0x0001) [= assigned for: ISO 13818-1 Conditional Access Table (CAT)]

    Guess table from table id...
    CAT-decoding....
    Table_ID: 1 (0x01) [= Conditional Access Table (CAT)]
    section_syntax_indicator: 1 (0x01)
    (fixed): 0 (0x00)
    reserved_1: 3 (0x03)
    Section_length: 33 (0x0021)
    reserved_2: 262143 (0x3ffff)
    Version_number: 14 (0x0e)
    current_next_indicator: 1 (0x01) [= valid now]
    Section_number: 0 (0x00)
    Last_Section_number: 0 (0x00)

    MPEG-DescriptorTag: 9 (0x09) [= CA_descriptor]
    descriptor_length: 4 (0x04)
    CA_system_ID: 2412 (0x096c) [= News Datacom (Videoguard)]
    reserved: 7 (0x07)
    CA_PID: 192 (0x00c0)

    MPEG-DescriptorTag: 9 (0x09) [= CA_descriptor]
    descriptor_length: 4 (0x04)
    CA_system_ID: 2315 (0x090b) [= News Datacom (Videoguard)]
    reserved: 7 (0x07)
    CA_PID: 192 (0x00c0)

    MPEG-DescriptorTag: 9 (0x09) [= CA_descriptor]
    descriptor_length: 4 (0x04)
    CA_system_ID: 1572 (0x0624) [= Irdeto]
    reserved: 7 (0x07)
    CA_PID: 1002 (0x03ea)

    MPEG-DescriptorTag: 9 (0x09) [= CA_descriptor]
    descriptor_length: 4 (0x04)
    CA_system_ID: 1540 (0x0604) [= Irdeto]
    reserved: 7 (0x07)
    CA_PID: 1002 (0x03ea)

    CRC: 2885691543 (0xac002897)
    ================================================== ========

  • #11
    Junior Member
    Join Date
    Jan 2009
    Age
    47
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    Quote Originally Posted by crypto7 View Post
    From al's post
    749FD9F3FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
    FFFFFFFFFFFFFF0082401CC3482E

    The CA stream is 184 data bytes long... that is, mlog will send 184 bytes of data after it drops the dvb header.
    This means that at some point they will decide not pad out a packet and start the next "command" in the new packet.

    To look at the last little bit

    FFFFFFFFFFFFFF0082401CC3482E
    I need to find the separator for nova package.
    Could you please help me log this CA stream? I have installed dvbsnoop. btw i can't make mlog to work (shouldn't it connect to my dm500 IP? I can't find any kind of network setting... but anyway)

  • #12
    Junior Member
    Join Date
    Jan 2008
    Posts
    144
    Thanks
    0
    Thanked 43 Times in 16 Posts
    Rep Power
    205
    Reputation
    198

    Default

    Here's a great document, when combined with DVBsnoop, will allow you to find all the information you need for any stream.



    Hope it helps.

  • #13
    Junior Member
    Join Date
    Jan 2008
    Posts
    190
    Thanks
    1
    Thanked 25 Times in 15 Posts
    Rep Power
    205
    Reputation
    81

    Default

    If you can dump 3 or 4 of the DVBSnoop packets I will see if I can id the seperator for you and outline how i did it.

  • #14
    Senior Member z80's Avatar
    Join Date
    Jan 2008
    Posts
    5,840
    Thanks
    112
    Thanked 77 Times in 48 Posts
    Rep Power
    0
    Reputation
    708

    Default

    Quote Originally Posted by drysa View Post
    Does anyone log the UBI stream and if so could they post what the seperator is for this data or if anyone knows could they post it. many thanks

    PID 0500
    seperator 8240

  • #15
    Junior Member
    Join Date
    Jan 2009
    Age
    47
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    thank you all for you answers!

    i tryed: dvbsnoop -b 0x0500 > /var/capture.bin

    but I really can't see any instance of "FFFFFF.." The only string I can see after a single FF is 0020 is this the separator?

    These are the logs

    h**p://rapidshare.com/files/185521493/capture1.zip.html

    Thanks in advance

  • #16
    Premium Member
    Join Date
    Jan 2008
    Location
    Melbourne
    Posts
    854
    Thanks
    246
    Thanked 87 Times in 69 Posts
    Rep Power
    243
    Reputation
    886

    Default

    Quote Originally Posted by mxantho View Post
    thank you all for you answers!

    i tryed: dvbsnoop -b 0x0500 > /var/capture.bin

    but I really can't see any instance of "FFFFFF.." The only string I can see after a single FF is 0020 is this the separator?

    These are the logs

    h**p://rapidshare.com/files/185521493/capture1.zip.html

    Thanks in advance
    Looks to me like 8240 is the separator,.. but the key is sinking to the beginning of a message. But then I'm very green at this. The 'padding', i.e. FFs, can, and usually vary in size.

  • #17
    Senior Member z80's Avatar
    Join Date
    Jan 2008
    Posts
    5,840
    Thanks
    112
    Thanked 77 Times in 48 Posts
    Rep Power
    0
    Reputation
    708

    Default

    Just use dvblogger...posted elsewhere in this forum.

  • #18
    Junior Member
    Join Date
    Jan 2009
    Age
    47
    Posts
    3
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Reputation
    10

    Default

    I used 8240 as a separator. I keep getting logs, but also have an error in ird_logextractor:

    19 Ιαν 2009 0242 Invalid First Packet
    19 Ιαν 2009 0242 Invalid First Packet
    19 Ιαν 2009 0242 First EMM TS Byte too big
    19 Ιαν 2009 0242 First EMM TS Byte too big
    19 Ιαν 2009 0242 Invalid First Packet
    19 Ιαν 2009 0242 Invalid First Packet

    I will try dvblogger, thanks !

  • #19
    Junior Member
    Join Date
    Jan 2008
    Posts
    190
    Thanks
    1
    Thanked 25 Times in 15 Posts
    Rep Power
    205
    Reputation
    81

    Default

    Ive had a look and it is not using padding but a full on stream of bytes.
    DVB Logger and IRD Log extract assume a std dvb stream and looking at this its a little different.

    Example from your log (broken down)
    The very first packet ad the Seperator 82 40

    82 40 3F <- where 3F is the length of payload bytes
    02 06 55 00 00 30 38
    E5 02 B1 E2 8E 02 B3 DB 60 0F 40 5B 22 49 C8 28
    35 7B 0B 48 CD E4 4A 13 BF AA 81 19 C2 E4 EC D3
    B5 BC D2 FC D7 F9 8D A9 D2 8A 74 72 32 FD 93 E2
    57 60 CF E7 0D FC 27 A9

    82 40 3F <- where 3F is the length of payload bytes
    02 06 56 00 00 30 38
    21 83 DD FD 91 2F 21 13 57 FD 3D 9A EE 79 23 4B
    B3 14 3F 3D D4 28 F0 1C 6D 08 C1 03 4B CD 1F A1
    99 33 E1 AD 08 B1 8E 10 B5 20 3A 73 2F 90 1E 73
    CA 36 04 5E D1 0A 6B A2

    82 40 3F <- where 3F is the length of payload bytes
    02 06 57 00 00 30 38
    4B 8E 3A 5F 8F 92 02 0E 6E 6B 83 55 F5 82 ED CA
    E0 36 6E 18 07 99 26 B3 6F F3 8D CA 02 8B 84 6B
    3F FB 7B E5 55 3B BB 20 63 7A _1 _2 _3 _4 _5 _6
    _7 _8 _9 _A _B _C _D _E (0x0E 14 Bytes Short)

    The last section above is the last packet (incomplete) in the first 184 byte block. Note it is 14 dec bytes short....

    This is where it varies.... In all dvb streams I have seen the first byte of the next packet is the "offset" to the start of the next full Packet. The ONLY time it is actual data is when ONLY the reaminder of the last packet is in the 184 byte block... followed by the 0xFF pad bytes....

    With this log, it always continues with the prev. packet.... (DVBLogger and Ird extract expect the offset byte to be present!)

    This means there is no wasted space in the stream.

    Next Pkt
    06 AA 92 C6 40 12 69 8E E6 96 B6 12 4C 34 <- 14 Bytes from prev packet

    82 40 3F .... And so on....
    02 06 58 00 00 30 38
    2C ED 45 45 3B DE 9D 5F A8 1D 01 18 B0 41 EB BB
    61 AB CB 67 B3 D8 78 56 3E 75 31 1D A1 85 1E C1
    65 07 78 FA CE 84 5A BB 9E 41 07 94 73 C4 C6 51
    E9 2B A1 DD 7D 15 A7 7E

    82 40 3F
    02 06 59 00 00 30 38
    D0 57 68 15 58 A3 25 87 6D FD 89 E2 0B 31 CF 15
    07 8F 6A 86 46 73 85 58 8D AF 39 A3 27 50 36 B7
    62 A7 89 77 1F 41 37 A8 E1 5A FF D8 49 0B F4 6F
    A5 64 1C E7 94 98 F3 7F


    82 40 3F
    02 06 5A 00 00 30 38
    94 DC 53 E5 19 ED 90 CA A5 BA 8E A1 4B 70 11 41
    E7 EB 26 C1 F8 49 36 43 CA C5 18 05 .... Continues in next Packet

  • Bookmarks

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •