DVB-MPE
- Thread starter EnoSat
- Start date
I'm wondering if the codec being used on 5°W for the MPX services is microMPX. This system can use bitrates from 100-800kbps (these feeds are ~700kbps), and is made for distribution over UDP, as these feeds are (in DVB-MPE).
I will have a go with this tool at some point when I get a chance - https://www.thimeo.com/how-to-use-the-raspberry-pi-sd-card-image/
I will have a go with this tool at some point when I get a chance - https://www.thimeo.com/how-to-use-the-raspberry-pi-sd-card-image/
EnoSat
Senior Member
- Messages
- 1,978
Has anyone tried to "disassemble" the 30W/10850V?
Code:
root@osmio4kplus:~# dvbsnoop -s pidscan
dvbsnoop V1.4.56 -- https://github.com/OpenVisionE2/dvbsnoop
---------------------------------------------------------
Transponder PID-Scan...
---------------------------------------------------------
PID found: 100 (0x0064) [SECTION: DSM-CC - private data section // DVB datagram]
root@osmio4kplus:~#
Code:
PID: 100 (0x0064)
Guess table from table id...
DSM-CC DATAGRAM-decoding....
Table_ID: 62 (0x3e) [= DSM-CC - private data section // DVB datagram]
section_syntax_indicator: 1 (0x01)
private_indicator: 0 (0x00)
reserved_1: 3 (0x03)
Section_length: 1460 (0x05b4)
MACaddrbyte/DevicdID 6: 3 (0x03)
MACaddrbyte/DeviceID 5: 3 (0x03)
reserved_2: 3 (0x03)
payload_scrambling_control: 0 (0x00) [= unscrambled]
address_scrambling_control: 0 (0x00) [= unscrambled]
LLC_SNAP_flag: 0 (0x00)
current_next_indicator: 1 (0x01) [= valid now]
Section_number: 0 (0x00)
Last_Section_number: 0 (0x00)
MACaddrbyte/DeviceID 4: 1 (0x01)
MACaddrbyte/DeviceID 3: 94 (0x5e)
MACaddrbyte/DeviceID 2: 0 (0x00)
MACaddrbyte/DeviceID 1: 1 (0x01) => MAC-Address/DeviceID: 01:00:5e:01:03:03
IP_datagram_bytes:
Version: 4 (0x04)
IP header length: 5 (0x05)
Type of service: 0 (0x00)
Total length: 1447 (0x05a7)
Identification: 23372 (0x5b4c)
Reserved: 0 (0x00)
DF: 0 (0x00)
MF: 0 (0x00)
Fragment offset: 0 (0x0000)
Time to live: 16 (0x10)
Protocol: 17 (0x11) [= UDP]
Header checksum: 38794 (0x978a)
Source address: c0a80ec3 [= 192.168.14.195]
Destination address: e0010303 [= 224.1.3.3]
UDP_datagram:
Source port: 52851 (0xce73)
Destination port: 6533 (0x1985)
Length: 1427 (0x0593)
Checksum: 25022 (0x61be)
Data
0000: 39 53 00 00 00 00 7f 05 03 ba b0 02 c3 20 00 80 9S........... ..
0010: 02 01 ce 14 00 00 14 00 00 00 e4 fc 19 00 68 05 ..............h.
0020: 71 83 dd ce 24 99 12 24 59 0c 43 da 0d f5 f6 5c q...$..$Y.C....\
0030: e3 b3 5d 47 15 49 bb c9 24 f9 78 6a ab bc e8 ca ..]G.I..$.xj....
...
Code:
root@osmio4kplus:~# astra --analyze pipe://"dvbsnoop 100 -b"
Feb 21 20:00:59: INFO: Starting Astra SM 0.2
Feb 21 20:00:59: INFO: [pipe_input analyze] process started (pid = 4898)
Feb 21 20:01:00: INFO: Bitrate: 28276 Kbit/s
Feb 21 20:01:00: ERROR: Scrambled: 0=2 17=1 18=1
Feb 21 20:01:01: INFO: Bitrate: 28391 Kbit/s
Feb 21 20:01:01: ERROR: CC: PID:0=15 PID:1=2 PID:17=3
Feb 21 20:01:01: ERROR: Scrambled: 17=2
Feb 21 20:01:02: INFO: Bitrate: 28647 Kbit/s
...According to Wireshark, it has two IPs (224.1.3.1 and 224.1.3.3), 224.1.3.3 seems to be the larger one with some kind of big data stream, and 224.1.3.1 seems to contain some kind of clear metadata, maybe about the content of the other IP -
"tar ar 1.log" "PDSender"