Posts by EnoSat

Quote from Turksat Uzmani

After the above-mentioned TPs were switched over, a data channel 11004 V 34286 DVBS QPSK was activated.

Yes, two IP transponders launched

I am asking because 4T2 identifies SCTE 35 but does not process it, which was (is) used in Russian T2MI.

3758L - PLP1
Is any DATA being transferred or just an empty 8191?

If someone uses Edge to view XML file, line 44 must
</AutoScan>
move to the end of the file

Some support is available at https://gtmedia.cc/pages/download-center

The problem is not money, but the health condition of Flysat's administrator.
It is also possible to use

https://www.lyngsat.com/

Satbeams - World Of Satellites at your fingertips

Satbeams - Satellite footprints, news and charts

www.satbeams.com

KingOfSat - Annuaire & Zapping Satellite Européen
ÖйúµØÇøÉÏ¿ÕÎÀÐǵçÊÓ½ÓÊÕÑ°ÐDzÎÊý¡ª¡ªÖÐÎÄÑ°ÐÇ
PORTAL BSD
https://www.tvrosat.com/cgi-bin/portal_charts.cgi

For e2, you can use record_ts or dvbstream. For me, record_ts gives better results. Null packets from 8191 are not stored.
I think there is a maximum of 64 PIDs in e2.

vs card

PS: Alternatively, you can try a simple analysis

dvbsnoop 101

PID: 101 (0x0065)

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: 52 (0x34)
MACaddrbyte/DeviceID 5: 18 (0x12)
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: 52 (0x34)
MACaddrbyte/DeviceID 3: 18 (0x12)
MACaddrbyte/DeviceID 2: 52 (0x34)
MACaddrbyte/DeviceID 1: 18 (0x12) => MAC-Address/DeviceID: 121212:34

IP_datagram_bytes:
Version: 4 (0x04)
IP header length: 5 (0x05)
Type of service: 0 (0x00)
Total length: 1447 (0x05a7)
Identification: 30591 (0x777f)
Reserved: 0 (0x00)
DF: 1 (0x01)
MF: 0 (0x00)
Fragment offset: 0 (0x0000)
Time to live: 127 (0x7f)
Protocol: 17 (0x11) [= UDP]
Header checksum: 24356 (0x5f24)
Source address: c0a8507a [= 192.168.80.122]
Destination address: 0a9603ea [= 10.150.3.234]

UDP_datagram:
Source port: 63626 (0xf88a)
Destination port: 12010 (0x2eea)
Length: 1427 (0x0593)
Checksum: 65116 (0xfe5c)
Data
0000: 7e ff 08 29 8d cd 05 80 e4 bf 86 10 31 c7 9d bb ~..)........1...
0010: af 80 61 17 b1 e1 25 38 e7 5d 3e 1c 26 e6 4b c0 ..a...%8.]>.&.K.
0020: 40 b4 4a 2e 40 f5 a0 d4 c3 33 a3 25 f4 e8 46 8a @.J.@....3.%..F.
...

astra --analyze pipe://"dvbsnoop 101 -b"
Jan 11 23:03:03: INFO: Starting Astra SM 0.2
Jan 11 23:03:03: INFO: [pipe_input analyze] process started (pid = 19287)
Jan 11 23:03:04: INFO: Bitrate: 4801 Kbit/s
Jan 11 23:03:04: ERROR: Scrambled: 0=8
Jan 11 23:03:05: INFO: Bitrate: 4935 Kbit/s
Jan 11 23:03:05: ERROR: CC: PID:0=7
Jan 11 23:03:05: ERROR: Scrambled: 0=7
Jan 11 23:03:06: INFO: Bitrate: 4529 Kbit/s
Jan 11 23:03:06: ERROR: CC: PID:0=5 PID:17=2
Jan 11 23:03:06: ERROR: Scrambled: 0=5 17=1
Jan 11 23:03:07: INFO: Bitrate: 4951 Kbit/s
Jan 11 23:03:07: ERROR: CC: PID:0=6
Jan 11 23:03:07: ERROR: Scrambled: 0=6
Jan 11 23:03:08: INFO: Bitrate: 4874 Kbit/s
Jan 11 23:03:08: ERROR: CC: PID:0=6
Jan 11 23:03:08: ERROR: Scrambled: 0=6
Jan 11 23:03:09: INFO: Bitrate: 4919 Kbit/s
Jan 11 23:03:09: ERROR: CC: PID:0=5
Jan 11 23:03:09: ERROR: Scrambled: 0=5
Jan 11 23:03 INFO: Bitrate: 4967 Kbit/s
Jan 11 23:03 ERROR: CC: PID:0=5
Jan 11 23:03 ERROR: Scrambled: 0=5
Jan 11 23:03 INFO: Bitrate: 4927 Kbit/s
Jan 11 23:03 ERROR: CC: PID:0=2 PID:18=1
Jan 11 23:03 ERROR: Scrambled: 0=3 18=1
...

Location: northwest Uzbekistan
Hmm, PIDs are different from LyngSat and TSR.

Quote from N_Stanislav

First regular TV transmition.

It's big regional package from North Korea!!

What encoding (CAID) did they use ?

Previously, MODCOD was not used and all data was transmitted to PID 2060.

It looks like a PCR processing problem.

osmio4kplus login: root
root@osmio4kplus:~# t2mi_decap -p 7 -p 6 -i 21E11403V.TS -o decap.ts
Jan 03 2311: INFO: [main] option: PLP ID = 7
Jan 03 2311: INFO: [main] option: PLP ID = 6
Jan 03 2311: INFO: [main] in: 21E11403V.TS, out: decap.ts
Jan 03 2311: INFO: [main] joining pid 0
Jan 03 2311: INFO: [main] joining pid 1
Jan 03 2311: DEBUG: [t2mi decap] PAT: pnr 4001, PMT pid 4096
Jan 03 2311: DEBUG: [t2mi decap] PAT: selected PMT pid 4096
Jan 03 2311: INFO: [main] joining pid 4096
Jan 03 2311: DEBUG: [t2mi decap] PMT: pid 4095, type 0x06
Jan 03 2311: DEBUG: [t2mi decap] PMT: selected payload pid 4095
Jan 03 2311: INFO: [main] joining pid 4095
Jan 03 2311: DEBUG: [t2mi decap] added PLP 0
Jan 03 2311: DEBUG: [t2mi decap] added PLP 1
Jan 03 2311: DEBUG: [t2mi decap] added PLP 2
Jan 03 2311: DEBUG: [t2mi decap] added PLP 3
Jan 03 2311: DEBUG: [t2mi decap] added PLP 4
Jan 03 2311: DEBUG: [t2mi decap] added PLP 5
Jan 03 2311: DEBUG: [t2mi decap] added PLP 6
Jan 03 2311: DEBUG: [t2mi decap] added PLP 7
Jan 03 2311: INFO: [t2mi decap] L1-current: PLP 0 (Data Type 1), group 1
Jan 03 2311: INFO: [t2mi decap] L1-current: PLP 1 (Data Type 1), group 1
Jan 03 2311: INFO: [t2mi decap] L1-current: PLP 2 (Data Type 1), group 1
Jan 03 2311: INFO: [t2mi decap] L1-current: PLP 3 (Data Type 1), group 1
Jan 03 2311: INFO: [t2mi decap] L1-current: PLP 4 (Data Type 1), group 1
Jan 03 2311: INFO: [t2mi decap] L1-current: PLP 5 (Data Type 1), group 1
Jan 03 2311: INFO: [t2mi decap] L1-current: PLP 6 (Data Type 1), group 1 (*)
Jan 03 2311: INFO: [t2mi decap] L1-current: PLP 7 (Data Type 1), group 1
Jan 03 2311: INFO: [t2mi decap] selected data PLP 6
Jan 03 2313: DEBUG: [t2mi decap] CC error (expect 11, got 13), discarding T2-MI packet
Jan 03 2313: DEBUG: [t2mi decap] T2-MI packet_count discontinuity (expect 100, got 101)
Jan 03 2313: DEBUG: [t2mi decap] CC error (expect 5, got 7), discarding T2-MI packet
Jan 03 2313: DEBUG: [t2mi decap] T2-MI packet_count discontinuity (expect 6, got 7)
Jan 03 2315: DEBUG: [t2mi decap] CC error (expect 3, got 5), discarding T2-MI packet
Jan 03 2315: DEBUG: [t2mi decap] T2-MI packet_count discontinuity (expect 23, got 24)
Jan 03 2315: DEBUG: [t2mi decap] CC error (expect 7, got 9), discarding T2-MI packet
Jan 03 2315: DEBUG: [t2mi decap] T2-MI packet_count discontinuity (expect 161, got 162)
Jan 03 2316: DEBUG: [t2mi decap] CC error (expect 3, got 5), discarding T2-MI packet
Jan 03 2316: DEBUG: [t2mi decap] T2-MI packet_count discontinuity (expect 13, got 14)
Jan 03 2316: INFO: [main] cleaning up
Jan 03 2316: INFO: [main] leaving pid 0
Jan 03 2316: INFO: [main] leaving pid 1
Jan 03 2316: INFO: [main] leaving pid 4095
Jan 03 2316: INFO: [main] leaving pid 4096

or

root@osmio4kplus:~# astra --analyze "t2mi://#t2mi_input=file://21E11403V.TS"
Jan 03 2324: INFO: Starting Astra SM 0.2
Jan 03 2324: ERROR: [file_input 21E11403V.TS] first PCR is not found
Jan 03 2324: ERROR: [analyze] end of file
Jan 03 2325: INFO: Bitrate: 0 Kbit/s
Jan 03 2326: INFO: Bitrate: 0 Kbit/s
Jan 03 2327: INFO: Bitrate: 0 Kbit/s
Jan 03 2328: INFO: Bitrate: 0 Kbit/s
^CJan 03 23:33:28: INFO: [main] shutting down
root@osmio4kplus:~#

Now on 13E/11355V test MODCOD1 and MODCOD2 for Inavatech - can some app process or select MODCOD independently ?
low signal for MODCOD2

normal signal for MODCOD2

Quote from Butacas

The problem with MPC-HC is that if I record the entire TS file, I don't know how to change the channel (if it's even possible) within the recorded file.

try MPC-BE - https://github.com/Aleksoid1978/MPC-BE/releases/tag/1.8.9

Quote from elamin66

After the VIDI TV package was working normally on the 21.6° East satellite on frequency 11402 Vertical 21900,
using the ALTDVB program with T2-MI technology, it stopped working even though the channels still appear during scanning.

Today, we present a simple explanation of how to run it using the ABC4T2ContentAnalyser program,
which is considered a leader in T2-MI technology.

https://www.youtube.com/watch?v=2qxUkO6HIAE

If you correct ServiceType, you should see the channel again.

Quote from satesco

It is still at 11118H, but according to the image, all frequencies are shifted by -3MHz. It would be advisable to change the LOF by 3 MHz.

Quote from Butacas

Example Hispasat URL:

http://192.168.0.126:8001/1:0:1:1:2C53:901:0:0:0:0:http%3a//0.0.0.0%3a9999/abertis/pid2305:TVG TDT-Sat [2305]

I've also tried it with the Astra 4.8°E channels on T2-MI, but it doesn't play at all on my PC.

Tested URL:

http://192.168.0.126:8001/1:0:1:3:2DE3:30:0:0:0:0:http%3a//0.0.0.0%3a9999/krrt/mx1:%D0%9C%D0%95GOGO СПОРТ

You would have to open a link for port 9999, but you get the whole TS.
http://192.168.0.126:9999/abertis/pid2305
http://192.168.0.126:9999/krrt/mx1
If you want to open only one channel, you would have to modify astra.conf by creating "zombie" channels.

Would it be possible to add RDS (Radio Data System) reading in VMA?

Most satellite cards have problems with correct MODCODs processing.

Post

RE: 45.0°W Intelsat 14

Now, night update after rain. Cloudy wheater, for the moment.

11638 H 37491 - New, I think

11543 H 12724 - Changed SR. By "Updating Modulation Info" flagged box, Stream Type changes from Continous to Transport. Probably S2X, Signal's jumping

satellitescommunity.de/index.php?attachment/115055/ satellitescommunity.de/index.php?attachment/115056/ satellitescommunity.de/index.php?attachment/115057/ satellitescommunity.de/index.php?attachment/115058/

superdish66

December 17, 2025 at 1:11 AM

Unfortunately, tuners in enigma2 cannot send the entire TS stream, only PIDs (I think the maximum is 64 PIDs).
So the consideration was more directed towards processing such a stream in VMA Transport Stream Analyzer than in VMA Enigma 2 Client.

Hi. Do you think it would be possible to send all the PIDs from the enigma transponder to the PC ?

Quote from VMA

There is an issue, where not all services are listed. I am still working on it, but I have not found the reason, yet.

Simplest case: 19.2E - 10891 - H:

hr2, hr3 and hr4 radio channels are missing in the list.

1, At the same time
https://www.lyngsat.com/muxes/Eutelsat-7-West-A_MENA_11680-H.html
from #1510 is displayed in full and correct
2, Displays non-existent SIDs in incomplete transponders