minisatip and satip-receiver and oscam

Support forum for minisatip
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: minisatip and satip-receiver and oscam

Post by cata »

Do you see continuity errors?

I looked couple of weeks ago and checked the continuity where the data read from dvr but saw them too. Basically I could not see any bug in minisatip.
sharky
Posts: 11
Joined: Sat May 14, 2016 6:15 pm

Re: minisatip and satip-receiver and oscam

Post by sharky »

Yes , I have a lot of them.

RTL HD choppy

Code: Select all

Message repeated 49 times
[01/07 10:01:45.789 signal]: BW 1775KB/s, Total BW: 7014 MB, ns/read 1530, r: 32, w: 72 fw: 0, tt: 48 ms
[01/07 10:01:45.803 AD0]: PID Continuity error (adapter 0): pid: 048, Expected CC: 0, Actual CC: F
Message repeated 49 times
[01/07 10:01:46.802 signal]: BW 1543KB/s, Total BW: 7015 MB, ns/read 1533, r: 28, w: 64 fw: 0, tt: 42 ms
[01/07 10:01:46.809 AD0]: PID Continuity error (adapter 0): pid: 048, Expected CC: 0, Actual CC: F
Message repeated 49 times
[01/07 10:01:47.808 signal]: BW 1595KB/s, Total BW: 7017 MB, ns/read 1538, r: 29, w: 66 fw: 0, tt: 44 ms
[01/07 10:01:47.815 AD0]: PID Continuity error (adapter 0): pid: 048, Expected CC: 0, Actual CC: F
Message repeated 50 times
[01/07 10:01:48.814 signal]: BW 1440KB/s, Total BW: 7018 MB, ns/read 1587, r: 26, w: 59 fw: 0, tt: 41 ms
[01/07 10:01:48.835 AD0]: PID Continuity error (adapter 0): pid: 048, Expected CC: 0, Actual CC: F
Message repeated 49 times
[01/07 10:01:49.821 signal]: BW 1209KB/s, Total BW: 7020 MB, ns/read 1579, r: 22, w: 49 fw: 0, tt: 34 ms
[01/07 10:01:49.858 AD0]: PID Continuity error (adapter 0): pid: 048, Expected CC: 0, Actual CC: F
Message repeated 23 times
[01/07 10:01:50.325 AD0]: PID Continuity error (adapter 0): pid: 255, Expected CC: 0, Actual CC: 1
[01/07 10:01:50.326 AD0]: PID Continuity error (adapter 0): pid: 048, Expected CC: 0, Actual CC: F
Message repeated 20 times
[01/07 10:01:50.712 main]: read RTSP (from handle 7 sock_id 7, len: 0, sid 0):
[01/07 10:01:50.713 main]: OPTIONS rtsp://192.168.10.11:5544/ RTSP/1.0
Session: 0412776091
CSeq: 5


[01/07 10:01:50.713 main]: reply -> 7 (192.168.10.14:48188) CL:0 [sock_id 7]:
[01/07 10:01:50.714 main]: RTSP/1.0 200 OK
Date: Sat, Jul 1 10:01:50 2017 GMT
Session: 0412776091
Cseq: 5
Public: OPTIONS, DESCRIBE, SETUP, PLAY, TEARDOWN
Server: minisatip/0.7.4
Das Erste HD no problem

Code: Select all

[01/07 10:04:08.471 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: D, Actual CC: C
Message repeated 114 times
[01/07 10:04:08.795 signal]: BW 1544KB/s, Total BW: 7226 MB, ns/read 1768, r: 28, w: 65 fw: 0, tt: 49 ms
[01/07 10:04:08.896 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: 7, Actual CC: 6
Message repeated 111 times
[01/07 10:04:08.901 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: 0, Actual CC: F
Message repeated 87 times
[01/07 10:04:08.950 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: 1, Actual CC: 0
Message repeated 111 times
[01/07 10:04:09.417 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: B, Actual CC: A
Message repeated 61 times
[01/07 10:04:09.420 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: C, Actual CC: B
Message repeated 111 times
[01/07 10:04:09.507 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: 0, Actual CC: F
Message repeated 92 times
[01/07 10:04:09.557 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: 1, Actual CC: 0
Message repeated 111 times
[01/07 10:04:09.801 signal]: BW 1286KB/s, Total BW: 7227 MB, ns/read 2405, r: 24, w: 55 fw: 0, tt: 57 ms
[01/07 10:04:10.139 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: 5, Actual CC: 4
Message repeated 65 times
[01/07 10:04:10.142 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: 6, Actual CC: 5
Message repeated 111 times
[01/07 10:04:10.279 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: 0, Actual CC: F
Message repeated 52 times
[01/07 10:04:10.337 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: D, Actual CC: C
Message repeated 8 times
[01/07 10:04:10.338 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: 6, Actual CC: 5
Message repeated 71 times
[01/07 10:04:10.389 AD0]: PID Continuity error (adapter 0): pid: 5101, Expected CC: 7, Actual CC: 6

DMAX HD no problem

Code: Select all

[01/07 10:05:18.390 main]: read RTSP (from handle 7 sock_id 7, len: 0, sid 0):
[01/07 10:05:18.391 main]: OPTIONS rtsp://192.168.10.11:5544/ RTSP/1.0
Session: 0412776091
CSeq: 24


[01/07 10:05:18.391 main]: reply -> 7 (192.168.10.14:48188) CL:0 [sock_id 7]:
[01/07 10:05:18.391 main]: RTSP/1.0 200 OK
Date: Sat, Jul 1 10:05:18 2017 GMT
Session: 0412776091
Cseq: 24
Public: OPTIONS, DESCRIBE, SETUP, PLAY, TEARDOWN
Server: minisatip/0.7.4


[01/07 10:05:19.341 signal]: BW 1415KB/s, Total BW: 7346 MB, ns/read 1491, r: 26, w: 60 fw: 0, tt: 38 ms
[01/07 10:05:20.347 signal]: BW 746KB/s, Total BW: 7346 MB, ns/read 1201, r: 20, w: 33 fw: 0, tt: 24 ms
[01/07 10:05:21.354 signal]: BW 952KB/s, Total BW: 7347 MB, ns/read 1446, r: 19, w: 42 fw: 0, tt: 27 ms
[01/07 10:05:22.360 signal]: BW 823KB/s, Total BW: 7348 MB, ns/read 1286, r: 20, w: 35 fw: 0, tt: 25 ms
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: minisatip and satip-receiver and oscam

Post by cata »

Hi,

The only problem is that they are not on the same transponder.

So most likely is a signal problem.
woec007
Posts: 12
Joined: Mon Jun 19, 2017 7:25 pm

Re: minisatip and satip-receiver and oscam

Post by woec007 »

Hi,

I have still no success with dvbapi / oscam. Sometimes I succeed with the ORF III channel, most of time screen remains black. Below I enclose a piece of oscam log when switching to ORF III (without success) - does somebody see any reason for failing decryption?
Thanks, woec

2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 serving srvid 33FC (ORF III HD) on adapter 0002 camask 0004 index 0002 pmtpi
d 0000
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0/16 lets start descrambling (srvid = 33FC fd = 15 ecmpids = 8)
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 ignore ecmpid 1 0650@000000:09D0 all chids (file)
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 ignore ecmpid 3 0648@000000:09D2 all chids (file)
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 ignore ecmpid 6 09C4@000000:0A3B all chids (file)
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 ignore ecmpid 5 098C@000000:0A31 all chids (file)
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 ignore ecmpid 4 06E2@000000:09D3:10000 (no matching reader)
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 ignore ecmpid 7 0500@051900:0A48:10000 (no matching reader)
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 prio ecmpid 0 0D98@000000:09CF:10000 weight: 1 (1 readers)
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 prio ecmpid 2 0D95@000000:09D1:10000 weight: 1 (1 readers)
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 prio ecmpid 2 0D95@000000:09D1 weight: 2 (found caid/provid in cache)
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 sorting the ecmpids took 1 ms
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 trying to descramble PID 2 CAID 0D95 PROVID 000000 ECMPID 09D1 ANY CHID PMTP
ID 0000 VPID 0000
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 try to start new filter for caid: 0D95, provid: 000000, pid: 09D1
2017/07/03 19:43:24 4D33449D c (dvbapi) Sending packet to dvbapi client (fd=15):
2017/07/03 19:43:24 4D33449D c (dvbapi) 40 3C 6F 2B 02 00 01 09 D1 80 00 00 00 00 00 00
2017/07/03 19:43:24 4D33449D c (dvbapi) 00 00 00 00 00 00 00 00 00 F0 00 00 00 00 00 00
2017/07/03 19:43:24 4D33449D c (dvbapi) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2017/07/03 19:43:24 4D33449D c (dvbapi) 00 00 00 00 00 00 00 00 00 00 00 0B B8 00 00 00
2017/07/03 19:43:24 4D33449D c (dvbapi) 04
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 Filter 2 started successfully (caid 0D95 provid 000000 pid 09D1)
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 trying to descramble PID 0 CAID 0D98 PROVID 000000 ECMPID 09CF ANY CHID PMTP
ID 0000 VPID 0000
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 try to start new filter for caid: 0D98, provid: 000000, pid: 09CF
2017/07/03 19:43:24 4D33449D c (dvbapi) Sending packet to dvbapi client (fd=15):
2017/07/03 19:43:24 4D33449D c (dvbapi) 40 3C 6F 2B 02 00 02 09 CF 80 00 00 00 00 00 00
2017/07/03 19:43:24 4D33449D c (dvbapi) 00 00 00 00 00 00 00 00 00 F0 00 00 00 00 00 00
2017/07/03 19:43:24 4D33449D c (dvbapi) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2017/07/03 19:43:24 4D33449D c (dvbapi) 00 00 00 00 00 00 00 00 00 00 00 0B B8 00 00 00
2017/07/03 19:43:24 4D33449D c (dvbapi) 04
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 Filter 3 started successfully (caid 0D98 provid 000000 pid 09CF)
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 try to start new filter for caid: 0001, provid: 000001, pid: 0001
2017/07/03 19:43:24 4D33449D c (dvbapi) Sending packet to dvbapi client (fd=15):
2017/07/03 19:43:24 4D33449D c (dvbapi) 40 3C 6F 2B 02 00 03 00 01 01 00 00 00 00 00 00
2017/07/03 19:43:24 4D33449D c (dvbapi) 00 00 00 00 00 00 00 00 00 FF 00 00 00 00 00 00
2017/07/03 19:43:24 4D33449D c (dvbapi) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2017/07/03 19:43:24 4D33449D c (dvbapi) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
2017/07/03 19:43:24 4D33449D c (dvbapi) 04
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 Filter 4 started successfully (caid 0001 provid 000001 pid 0001)
2017/07/03 19:43:24 4D33449D c (dvbapi) Got packet with opcode 9F803F04 and size 8
2017/07/03 19:43:24 4D33449D c (-) -- Skipped 1 duplicated log lines --
2017/07/03 19:43:24 4D33449D c (dvbapi) Demuxer 0 stop descrambling program number 33FC (ORF III HD)
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: minisatip and satip-receiver and oscam

Post by cata »

Hi woec007,

please send me the latest log from minisatip.

Please use -l satipc,http

Thank you
woec007
Posts: 12
Joined: Mon Jun 19, 2017 7:25 pm

Re: minisatip and satip-receiver and oscam

Post by woec007 »

Hi,

ok, I enclose a minisatip.log with the recommended parameters for -l.
Thank you,
woec
Attachments
minisatip_log.tgz
(18.9 KiB) Downloaded 403 times
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: minisatip and satip-receiver and oscam

Post by cata »

Hi,

Try latest and upload tge log if not worling.

Thanks
woec007
Posts: 12
Joined: Mon Jun 19, 2017 7:25 pm

Re: minisatip and satip-receiver and oscam

Post by woec007 »

Hi,

now it works! Still some minor problems when other oscam client switches channel, then frequently transmission stops - but maybe a problem of the oscam/dvbapi configuration.

Would be nice, to have the dvbapi_offset as commandline parameter for flexible configuration.

On compilation of the code I received some warning messages, as listed below:

satipc.c: In function ‘http_request’:
satipc.c:863:5: warning: too many arguments for format [-Wformat-extra-args]
version);
^
satipc.c: In function ‘satip_getxml’:
satipc.c:1290:2: warning: implicit declaration of function ‘http_client’ [-Wimplicit-function-declaration]
http_client("http://10.0.0.3:8080/desc.xml", "", satip_getxml_data, "");
^
satipc.c:1270:6: warning: unused variable ‘la’ [-Wunused-variable]
int la;
^
satipc.c:1269:8: warning: unused variable ‘arg’ [-Wunused-variable]
char *arg[50];
^
satipc.c:1268:7: warning: unused variable ‘satip_xml’ [-Wunused-variable]
char satip_xml[SATIP_STR_LEN];
^
satipc.c:1267:7: warning: unused variable ‘satip_xml_servers’ [-Wunused-variable]
char satip_xml_servers[SATIP_STR_LEN];
^

Thank you very much for your effort!
woec
cata
Site Admin
Posts: 768
Joined: Tue May 12, 2015 1:01 am

Re: minisatip and satip-receiver and oscam

Post by cata »

Hi,

does setting dvbapi_offset from the code works for you ? Meaning can you have multiple clients to the same oscam ?


About the warnings, is still WP, but did not finish it yet.

Thanks
woec007
Posts: 12
Joined: Mon Jun 19, 2017 7:25 pm

Re: minisatip and satip-receiver and oscam

Post by woec007 »

Hi,
I am not sure about. I have influcence on the 2nd client (vdr with dvbapi plugin), when I start or stop play on the minisatip client - it frequently stops playing the current channel. This occurs with both settings 0 offset or 2 offset.
So, I tried to put the offset on the vdr client by specifying the offset to the dvbapi of the vdr, and this seems to be more stable - less disturbance of the 2nd client.

Is there a log message, which tells me the offset to be used or not?

Thanks,
woec
Post Reply