richard-nellist / satip Goto Github PK

0.0 0.0 0.0 204 KB

Automatically exported from code.google.com/p/satip

Makefile 1.23% C 98.44% Shell 0.34%

satip's People

satip's Issues

Parse signal level/quality from RTCP app packet

First of all thank you for this great SAT>IP client, works very good!

Here my issue:

Regarding to SAT>IP Spec 1.2, page 54/55, the app packet string contains 
information about the lock state, signal level and quality.

String content (from Spec):
ver=<major>.<minor>;src=<srcID>;tuner=<feID>,<level>,<lock>,<quality>,<frequency
>,<polarisation>,
<system>,<type>,<pilots>,<roll_off>,<symbol_rate>,<fec_inner>;pids=<pid0>,...,<p
idn> 


Example from my setup:
Aug 16 17:15:37 yavdr05 satip: [3380 satip_rtp.c:84] debug: RTCP: app info: 
ver=1.0;src=1;tuner=1,70,1,15,11914,h,dvbs2,qpsk,off,0.35,27500,910;pids=32,767,
770,771,1,4104,18,0,16,17,20,4098,6330,10


I'm not really sure how to interprete the level and quality, because I found no 
information about it in the spec.
But seems that Rolf Ahrenberg, the author of vdr-plugin-satip 
(http://www.saunalahti.fi/~rahrenbe/vdr/satip/) found a solution, not (yet) 
tested, but code looks good.

From vdr-plugin-satip tuner.c, thanks to Rolf Ahrenberg:

[code]
void cSatipTuner::ParseReceptionParameters(const char *paramP)
{
  //debug("cSatipTuner::%s(%s) [device %d]", __FUNCTION__, paramP, deviceM->GetId());
  // DVB-S2:
  // ver=<major>.<minor>;src=<srcID>;tuner=<feID>,<level>,<lock>,<quality>,<frequency>,<polarisation>,<system>,<type>,<pilots>,<roll_off>,<symbol_rate>,<fec_inner>;pids=<pid0>,...,<pidn>
  // DVB-T2:
  // ver=1.1;tuner=<feID>,<level>,<lock>,<quality>,<freq>,<bw>,<msys>,<tmode>,<mtype>,<gi>,<fec>,<plp>,<t2id>,<sm>;pids=<pid0>,...,<pidn>
  if (!isempty(paramP)) {
     char *s = strdup(paramP);
     char *c = strstr(s, ";tuner=");
     if (c)  {
        int value;

        // level:
        // Numerical value between 0 and 255
        // An incoming L-band satellite signal of
        // -25dBm corresponds to 224
        // -65dBm corresponds to 32
        // No signal corresponds to 0
        c = strstr(c, ",");
        value = atoi(++c);
        // Scale value to 0-100
        signalStrengthM = (value >= 0) ? (value * 100 / 255) : -1;

        // lock:
        // lock Set to one of the following values:
        // "0" the frontend is not locked
        // "1" the frontend is locked
        c = strstr(c, ",");
        hasLockM = atoi(++c);

        // quality:
        // Numerical value between 0 and 15
        // Lowest value corresponds to highest error rate
        // The value 15 shall correspond to
        // -a BER lower than 2x10-4 after Viterbi for DVB-S
        // -a PER lower than 10-7 for DVB-S2
        c = strstr(c, ",");
        value = atoi(++c);
        // Scale value to 0-100
        signalQualityM = (hasLockM && (value >= 0)) ? (value * 100 / 15) : 0;
        }
     free(s);
     }
}
[/code]

Would be nice if you could add this to your code, satip_rtp.c - static void 
rtp_data(unsigned char* buffer,int rx)

I would implement it myself, but I don't know how to process signal level and 
quality for vtuner.

Thanks in advance!


Regards
André

Original issue reported on code.google.com by [email protected] on 17 Aug 2014 at 2:42

Platform ARM: [29983 satip_main.c:149] error: unknown option �

What steps will reproduce the problem?
1. Compile on Arm (tried NSA-320 and Raspberry Pi)
2. Run

Apparently getopt does not seem to work properly/as expected. The while 
loop 

 while((opt = getopt(argc, argv, "h:p:d:f:m:l:")) != -1 )

never ends. On x86_64 the command works as expected. 

What version of the product are you using? On what operating system?
satip-0.0.2

Please provide any additional information below.
See attached patch to fix the issue.

Original issue reported on code.google.com by [email protected] on 15 May 2014 at 11:07

Attachments:

satip_main.patch

vtuner/satip and vtunerd?

Is it possible to use vtuner/satip together with the original vtunerd, or is 
this for SAT>IP Servers only?

Original issue reported on code.google.com by [email protected] on 13 Jul 2014 at 1:34

Inverto iLNB + VDR

I'm trying to use satip/vtuner with an Inverto iLNB and VDR, but i have 
problems to get it running very well.

I'm starting vtuner/satip in this way:

modprobe vtunerc devices=2 debug=0
chmod a+rw /dev/vtunerc*
chmod a+rw /dev/dvb/adapter0/*
chmod a+rw /dev/dvb/adapter1/*
/usr/local/bin/satip -h $SAT_IP_SERVER -l 10 -d /dev/vtunerc0 
>/var/log/satip/satip0.log 2>&1 &
/usr/local/bin/satip -h $SAT_IP_SERVER -l 10 -d /dev/vtunerc0 
>/var/log/satip/satip0.log 2>&1 &

Sometimes it works pretty well, but most of the time i cannot get it run. Then 
i just receive artifacts or nothing.

For example ARD SD:

It works without any problems, if i open the stream with VLC over HTTP:

http://192.168.1.45/?src=1&freq=11836&sr=27500&pol=h&msys=dvbs&pids=0,100,101,10
2,103,106

But if i try to go over satip/vtuner, i just see artifacts. Maybe u 
seesomething in the LOG:

[26599 satip_rtsp.c:460] debug: >>play:
PLAY 
rtsp://192.168.1.45/stream=2?src=1&freq=11836.0&pol=h&msys=dvbs&sr=27500&fec=34&
pids=101,18,0,20,16,17,102,103,106,105 RTSP/1.0
CSeq: 11427
Session: 1E773BF7


<<
[26599 satip_vtuner.c:321] debug: MSG_READ_STATUS
[26599 satip_vtuner.c:373] debug: ioctl: response ok
[26599 satip_rtp.c:91] debug: RTCP: packet type 200 len 6
[26599 satip_rtp.c:91] debug: RTCP: packet type 202 len 6
[26599 satip_rtp.c:77] debug: RTCP: app defined (204) name: SES1
[26599 satip_rtp.c:84] debug: RTCP: app info: 
ver=1.0;src=1;tuner=2,0,0,0,12399,h,dvbs,,,,27500,34;pids=0,16,17,18,20,10
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_rtsp.c:215] debug: rxbuf:
RTSP/1.0 200 OK
CSeq: 11427
Session: 1E773BF7
RTP-Info: url=rtsp://192.168.1.45/stream=2;seq=8521;rtptime=1412242048
Date: Thu, 02 Oct 2014 10:12:18 GMT
Range: npt=0.000-


<<
[26599 satip_rtp.c:91] debug: RTCP: packet type 200 len 6
[26599 satip_rtp.c:91] debug: RTCP: packet type 202 len 6
[26599 satip_rtp.c:77] debug: RTCP: app defined (204) name: SES1
[26599 satip_rtp.c:84] debug: RTCP: app info: 
ver=1.0;src=1;tuner=2,0,0,0,11836,h,dvbs,,,,27500,34;pids=0,16,17,18,20,101,102,
103,105,10
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 200 len 6
[26599 satip_rtp.c:91] debug: RTCP: packet type 202 len 6
[26599 satip_rtp.c:77] debug: RTCP: app defined (204) name: SES1
[26599 satip_rtp.c:84] debug: RTCP: app info: 
ver=1.0;src=1;tuner=2,0,0,0,11836,h,dvbs,,,,27500,34;pids=0,16,17,18,20,101,102,
103,105,10
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 200 len 6
[26599 satip_rtp.c:91] debug: RTCP: packet type 202 len 6
[26599 satip_rtp.c:77] debug: RTCP: app defined (204) name: SES1
[26599 satip_rtp.c:84] debug: RTCP: app info: 
ver=1.0;src=1;tuner=2,0,0,0,11836,h,dvbs,,,,27500,34;pids=0,16,17,18,20,101,102,
103,105,10
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 200 len 6
[26599 satip_rtp.c:91] debug: RTCP: packet type 202 len 6
[26599 satip_rtp.c:77] debug: RTCP: app defined (204) name: SES1
[26599 satip_rtp.c:84] debug: RTCP: app info: 
ver=1.0;src=1;tuner=2,0,0,0,11836,h,dvbs,,,,27500,34;pids=0,16,17,18,20,101,102,
103,105,10
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_vtuner.c:321] debug: MSG_READ_STATUS
[26599 satip_vtuner.c:373] debug: ioctl: response ok
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:285] debug: 100
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_rtsp.c:460] debug: >>play:
PLAY rtsp://192.168.1.45/stream=2?addpids=100 RTSP/1.0
CSeq: 11428
Session: 1E773BF7


<<
[26599 satip_vtuner.c:321] debug: MSG_READ_STATUS
[26599 satip_vtuner.c:373] debug: ioctl: response ok
[26599 satip_rtsp.c:215] debug: rxbuf:
RTSP/1.0 200 OK
CSeq: 11428
Session: 1E773BF7
RTP-Info: url=rtsp://192.168.1.45/stream=2;seq=8521;rtptime=1412242048
Date: Thu, 02 Oct 2014 10:12:19 GMT
Range: npt=0.000-


<<
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:285] debug: 100
[26599 satip_vtuner.c:285] debug: 200
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_rtsp.c:460] debug: >>play:
PLAY rtsp://192.168.1.45/stream=2?addpids=200 RTSP/1.0
CSeq: 11429
Session: 1E773BF7


<<
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:285] debug: 100
[26599 satip_vtuner.c:285] debug: 200
[26599 satip_vtuner.c:285] debug: 104
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:285] debug: 200
[26599 satip_vtuner.c:285] debug: 104
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_rtsp.c:215] debug: rxbuf:
RTSP/1.0 200 OK
CSeq: 11429
Session: 1E773BF7
RTP-Info: url=rtsp://192.168.1.45/stream=2;seq=8521;rtptime=1412242048
Date: Thu, 02 Oct 2014 10:12:19 GMT
Range: npt=0.000-


<<
[26599 satip_rtsp.c:460] debug: >>play:
PLAY rtsp://192.168.1.45/stream=2?addpids=104&delpids=100 RTSP/1.0
CSeq: 11430
Session: 1E773BF7


<<
[26599 satip_rtsp.c:215] debug: rxbuf:
RTSP/1.0 200 OK
CSeq: 11430
Session: 1E773BF7
RTP-Info: url=rtsp://192.168.1.45/stream=2;seq=8521;rtptime=1412242048
Date: Thu, 02 Oct 2014 10:12:19 GMT
Range: npt=0.000-


<<
[26599 satip_rtp.c:91] debug: RTCP: packet type 200 len 6
[26599 satip_rtp.c:91] debug: RTCP: packet type 202 len 6
[26599 satip_rtp.c:77] debug: RTCP: app defined (204) name: SES1
[26599 satip_rtp.c:84] debug: RTCP: app info: 
ver=1.0;src=1;tuner=2,171,1,15,11836,h,dvbs,qpsk,,,27500,34;pids=0,16,17,18,20,1
01,102,103,104,105,106,20
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:285] debug: 104
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_rtsp.c:460] debug: >>play:
PLAY rtsp://192.168.1.45/stream=2?delpids=200 RTSP/1.0
CSeq: 11431
Session: 1E773BF7


<<
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:285] debug: 300
[26599 satip_vtuner.c:285] debug: 104
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_rtsp.c:215] debug: rxbuf:
RTSP/1.0 200 OK
CSeq: 11431
Session: 1E773BF7
RTP-Info: url=rtsp://192.168.1.45/stream=2;seq=8521;rtptime=1412242048
Date: Thu, 02 Oct 2014 10:12:20 GMT
Range: npt=0.000-


<<
[26599 satip_rtsp.c:460] debug: >>play:
PLAY rtsp://192.168.1.45/stream=2?addpids=300 RTSP/1.0
CSeq: 11432
Session: 1E773BF7


<<
[26599 satip_rtsp.c:215] debug: rxbuf:
RTSP/1.0 200 OK
CSeq: 11432
Session: 1E773BF7
RTP-Info: url=rtsp://192.168.1.45/stream=2;seq=8521;rtptime=1412242048
Date: Thu, 02 Oct 2014 10:12:20 GMT
Range: npt=0.000-


<<
[26599 satip_vtuner.c:321] debug: MSG_READ_STATUS
[26599 satip_vtuner.c:373] debug: ioctl: response ok
[26599 satip_rtp.c:91] debug: RTCP: packet type 200 len 6
[26599 satip_rtp.c:91] debug: RTCP: packet type 202 len 6
[26599 satip_rtp.c:77] debug: RTCP: app defined (204) name: SES1
[26599 satip_rtp.c:84] debug: RTCP: app info: 
ver=1.0;src=1;tuner=2,171,1,15,11836,h,dvbs,qpsk,,,27500,34;pids=0,16,17,18,20,1
01,102,103,104,105,106,30
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_vtuner.c:321] debug: MSG_READ_STATUS
[26599 satip_vtuner.c:373] debug: ioctl: response ok
[26599 satip_rtp.c:91] debug: RTCP: packet type 200 len 6
[26599 satip_rtp.c:91] debug: RTCP: packet type 202 len 6
[26599 satip_rtp.c:77] debug: RTCP: app defined (204) name: SES1
[26599 satip_rtp.c:84] debug: RTCP: app info: 
ver=1.0;src=1;tuner=2,171,1,15,11836,h,dvbs,qpsk,,,27500,34;pids=0,16,17,18,20,1
01,102,103,104,105,106,30
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:285] debug: 104
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_rtsp.c:460] debug: >>play:
PLAY rtsp://192.168.1.45/stream=2?delpids=300 RTSP/1.0
CSeq: 11433
Session: 1E773BF7


<<
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:285] debug: 500
[26599 satip_vtuner.c:285] debug: 104
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_rtsp.c:215] debug: rxbuf:
RTSP/1.0 200 OK
CSeq: 11433
Session: 1E773BF7
RTP-Info: url=rtsp://192.168.1.45/stream=2;seq=8521;rtptime=1412242048
Date: Thu, 02 Oct 2014 10:12:20 GMT
Range: npt=0.000-


<<
[26599 satip_rtsp.c:460] debug: >>play:
PLAY rtsp://192.168.1.45/stream=2?addpids=500 RTSP/1.0
CSeq: 11434
Session: 1E773BF7


<<
[26599 satip_rtsp.c:215] debug: rxbuf:
RTSP/1.0 200 OK
CSeq: 11434
Session: 1E773BF7
RTP-Info: url=rtsp://192.168.1.45/stream=2;seq=8521;rtptime=1412242048
Date: Thu, 02 Oct 2014 10:12:20 GMT
Range: npt=0.000-


<<
[26599 satip_rtp.c:91] debug: RTCP: packet type 200 len 6
[26599 satip_rtp.c:91] debug: RTCP: packet type 202 len 6
[26599 satip_rtp.c:77] debug: RTCP: app defined (204) name: SES1
[26599 satip_rtp.c:84] debug: RTCP: app info: 
ver=1.0;src=1;tuner=2,171,1,15,11836,h,dvbs,qpsk,,,27500,34;pids=0,16,17,18,20,1
01,102,103,104,105,106,50
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 200 len 6
[26599 satip_rtp.c:91] debug: RTCP: packet type 202 len 6
[26599 satip_rtp.c:77] debug: RTCP: app defined (204) name: SES1
[26599 satip_rtp.c:84] debug: RTCP: app info: 
ver=1.0;src=1;tuner=2,171,1,15,11836,h,dvbs,qpsk,,,27500,34;pids=0,16,17,18,20,1
01,102,103,104,105,106,50
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_rtp.c:91] debug: RTCP: packet type 0 len 0
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:285] debug: 104
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_rtsp.c:460] debug: >>play:
PLAY rtsp://192.168.1.45/stream=2?delpids=500 RTSP/1.0
CSeq: 11435
Session: 1E773BF7


<<
[26599 satip_vtuner.c:277] debug: MSG_SET_PIDLIST:
[26599 satip_vtuner.c:285] debug: 18
[26599 satip_vtuner.c:285] debug: 20
[26599 satip_vtuner.c:285] debug: 0
[26599 satip_vtuner.c:285] debug: 17
[26599 satip_vtuner.c:285] debug: 16
[26599 satip_vtuner.c:285] debug: 101
[26599 satip_vtuner.c:285] debug: 102
[26599 satip_vtuner.c:285] debug: 103
[26599 satip_vtuner.c:285] debug: 106
[26599 satip_vtuner.c:285] debug: 105
[26599 satip_vtuner.c:285] debug: 600
[26599 satip_vtuner.c:285] debug: 104
[26599 satip_vtuner.c:316] debug: set_pidlist: no response required
[26599 satip_vtuner.c:321] debug: MSG_READ_STATUS
[26599 satip_vtuner.c:373] debug: ioctl: response ok
[26599 satip_rtsp.c:215] debug: rxbuf:
RTSP/1.0 200 OK
CSeq: 11435
Session: 1E773BF7
RTP-Info: url=rtsp://192.168.1.45/stream=2;seq=8521;rtptime=1412242048
Date: Thu, 02 Oct 2014 10:12:21 GMT
Range: npt=0.000-


<<
[26599 satip_rtsp.c:460] debug: >>play:
PLAY rtsp://192.168.1.45/stream=2?addpids=600 RTSP/1.0
CSeq: 11436
Session: 1E773BF7


<<
[26599 satip_rtsp.c:215] debug: rxbuf:
RTSP/1.0 200 OK
CSeq: 11436
Session: 1E773BF7
RTP-Info: url=rtsp://192.168.1.45/stream=2;seq=8521;rtptime=1412242048
Date: Thu, 02 Oct 2014 10:12:21 GMT
Range: npt=0.000-


<<

If you need more information, please let me know.

Thank you!

Original issue reported on code.google.com by [email protected] on 2 Oct 2014 at 10:20

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.