Inverto iLNB + VDR - Githubissues

GoogleCodeExporter commented 9 years ago

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 c...@crichter.net on 2 Oct 2014 at 10:20

GoogleCodeExporter commented 9 years ago

And when i register the vtuner module,what means "frontend 1140982769" and 
"frontend 1936026732"?

[148278.161753] (NULL device *): DVB: registering adapter 1 frontend 0 (vTuner 
proxyFE DVB-S2)...
[148278.172966] vtunerc3: setting DVB-S2 tuner vtype
[148278.172984] (NULL device *): DVB: registering adapter 3 frontend 0 (vTuner 
proxyFE DVB-S2)...
[148278.174649] vtunerc0: setting DVB-S2 tuner vtype
[148278.174659] (NULL device *): DVB: registering adapter 0 frontend 1140982769 
(vTuner proxyFE DVB-S2)...
[148278.175370] vtunerc2: setting DVB-S2 tuner vtype
[148278.175381] (NULL device *): DVB: registering adapter 2 frontend 1936026732 
(vTuner proxyFE DVB-S2)...

Original comment by c...@crichter.net on 2 Oct 2014 at 11:23

GoogleCodeExporter commented 9 years ago

Could it be that vtuner is the problem?

Now have this:

[148457.295522] (NULL device *): DVB: registering adapter 0 frontend 0 (vTuner 
proxyFE DVB-S2)...
[148457.295556] vtunerc1: setting DVB-S2 tuner vtype
[148457.295657] (NULL device *): DVB: registering adapter 1 frontend 1245793536 
(vTuner proxyFE DVB-S2)...
[148457.301862] vtunerc3: setting DVB-S2 tuner vtype
[148457.301872] (NULL device *): DVB: registering adapter 3 frontend 0 (vTuner 
proxyFE DVB-S2)...
[148457.301885] vtunerc2: setting DVB-S2 tuner vtype
[148457.301956] (NULL device *): DVB: registering adapter 2 frontend 491511311 
(vTuner proxyFE DVB-S2)...

Tuner 0 works normal, but on tuner 1 i have artifacts now.

Original comment by c...@crichter.net on 2 Oct 2014 at 11:28

GoogleCodeExporter commented 9 years ago

I can upload a small recording with that artifacts, if that helps to find the 
problem. Probably the frontend numbers are not the problem. But maybe some TS 
packets get lost, i dont know.

Original comment by c...@crichter.net on 3 Oct 2014 at 6:57

GoogleCodeExporter commented 9 years ago

Now i just enabled the satip-error log.The only error message i see is this:

[16605 satip_vtuner.c:166] error: invalid FEC configured
[16605 satip_vtuner.c:166] error: invalid FEC configured
[16605 satip_vtuner.c:166] error: invalid FEC configured
[16605 satip_vtuner.c:166] error: invalid FEC configured
[16605 satip_vtuner.c:166] error: invalid FEC configured
[16605 satip_vtuner.c:166] error: invalid FEC configured
[16605 satip_vtuner.c:166] error: invalid FEC configured
[16605 satip_vtuner.c:166] error: invalid FEC configured

I also enables tscheck in vtuner, but this gave me now errors, when i watch a 
program with artifacts.

Original comment by c...@crichter.net on 3 Oct 2014 at 10:32

timehlers / satip

Inverto iLNB + VDR #4