Page 20 of 24
Re: SAT>IP Protocol support
Posted: Wed Jan 13, 2016 6:53 pm
by Diefenthal
Prog wrote:Please try download "a" again. Updated with same version.
scan is currently running at time is no pids all seen
but what i not under stand sometime add you pids=0,1,16,17,18
and in the next call Play add you addpid=16 once more why?
in the first can you use Pids =0
in the next Request addpid =16
if you parsed 16
new Request with addpid=17
if that parsed too
make a new Request with delpid= 16,17
scan end with no found Services /Channels
the next request change then the Tuning Details with pids=0
and so Long
Re: SAT>IP Protocol support
Posted: Thu Jan 14, 2016 4:56 am
by Prog
Pids in first url not important. But do you have signal? I think problem on some other parameters.
ps: Yes, scanner wihtout pids=all - very long. It is normal(!!!).
Re: SAT>IP Protocol support
Posted: Thu Jan 14, 2016 1:03 pm
by Prog
And so, I need good idea about debug of scanner. Now it is working on my TSS 400. May be delay too small? Try add 500ms in options->Scanner.
It is "fe" is correct?
ps: What most exotic sat>ip device? 4 DVB+S + DVBC+DVBT is maximum?
Re: SAT>IP Protocol support
Posted: Thu Jan 14, 2016 4:06 pm
by Diefenthal
Prog wrote:Pids in first url not important. But do you have signal? I think problem on some other parameters.
ps: Yes, scanner wihtout pids=all - very long. It is normal(!!!).
yes Signal is present
sure it Need time but if you want try DVBviewer this is really fast without pids=all
Prog wrote:And so, I need good idea about debug of scanner. Now it is working on my TSS 400. May be delay too small? Try add 500ms in options->Scanner.
It is "fe" is correct?
ps: What most exotic sat>ip device? 4 DVB+S + DVBC+DVBT is maximum?
i can try with screw up the delay
fe was corret
the Minimum is an STB that can be used as SatIp> Server there is is it DVBS-1
but this info can be read and parsed from Device Description (upnp ssdp)
Re: SAT>IP Protocol support
Posted: Thu Jan 14, 2016 4:28 pm
by Prog
Code: Select all
sure it Need time but if you want try DVBviewer this is really fast without pids=all
DVBViewer not important. Slow devices working slow. It is normal.
But I am not have idea why scanner working on my stupid device and not working on your...
Re: SAT>IP Protocol support
Posted: Thu Jan 14, 2016 4:32 pm
by Diefenthal
Prog wrote:Code: Select all
sure it Need time but if you want try DVBviewer this is really fast without pids=all
DVBViewer not important. Slow devices working slow. It is normal.
But I am not have idea why scanner working on my stupid device and not working on your...
firmeware Version of your triax
Re: SAT>IP Protocol support
Posted: Thu Jan 14, 2016 4:35 pm
by Prog
0.5.12
teamviewer not very help. But you can check rtsp.log at self and send me all logs of scanner.
Total same logs like in previous versions?
Re: SAT>IP Protocol support
Posted: Thu Jan 14, 2016 4:46 pm
by Diefenthal
Prog wrote:0.5.12
teamviewer not very help. But you can check rtsp.log at self and send me all logs of scanner.
Total same logs like in previous versions?
here are the last logs
Re: SAT>IP Protocol support
Posted: Thu Jan 14, 2016 4:51 pm
by Prog
Hm... &pids=0,1,16,17,18 not open PID=0.
Re: SAT>IP Protocol support
Posted: Thu Jan 14, 2016 4:53 pm
by Prog
Thanks for the log. I meed more tests on my side...
Re: SAT>IP Protocol support
Posted: Fri Jan 15, 2016 10:24 am
by Prog
btw, what mean "503 Service Unavailable" for sat>ip?
14:31:03.501 - Start logging...
14:31:03.502 - ------ rtsp://192.168.88.24/?src=1&fe=1&freq=11747.0&sr=27500&pol=v&msys=dvbs2&mtype=8psk&fec=34&pids=0,1,16,17,18
14:31:03.531 - >> OPTIONS rtsp://192.168.88.24/?src=1&fe=1&freq=11747.0&sr=27500&pol=v&msys=dvbs2&mtype=8psk&fec=34&pids=0,1,16,17,18 RTSP/1.0
CSeq: 41
User-Agent: ProgDVB
14:31:03.535 - -- TS RTP Client
14:31:03.535 - >> SETUP rtsp://192.168.88.24/?src=1&fe=1&freq=11747.0&sr=27500&pol=v&msys=dvbs2&mtype=8psk&fec=34&pids=0,1,16,17,18 RTSP/1.0
CSeq: 42
Transport: RTP/AVP;unicast;client_port=60505-60506
User-Agent: ProgDVB
14:31:03.538 - !! RTSP/1.0 503 Service Unavailable
Content-Type:text/parameters
CSeq:42
Content-Length: 19
Re: SAT>IP Protocol support
Posted: Fri Jan 15, 2016 11:54 am
by Diefenthal
Prog wrote:btw, what mean "503 Service Unavailable" for sat>ip?
14:31:03.501 - Start logging...
14:31:03.502 - ------ rtsp://192.168.88.24/?src=1&fe=1&freq=11747.0&sr=27500&pol=v&msys=dvbs2&mtype=8psk&fec=34&pids=0,1,16,17,18
14:31:03.531 - >> OPTIONS rtsp://192.168.88.24/?src=1&fe=1&freq=11747.0&sr=27500&pol=v&msys=dvbs2&mtype=8psk&fec=34&pids=0,1,16,17,18 RTSP/1.0
CSeq: 41
User-Agent: ProgDVB
14:31:03.535 - -- TS RTP Client
14:31:03.535 - >> SETUP rtsp://192.168.88.24/?src=1&fe=1&freq=11747.0&sr=27500&pol=v&msys=dvbs2&mtype=8psk&fec=34&pids=0,1,16,17,18 RTSP/1.0
CSeq: 42
Transport: RTP/AVP;unicast;client_port=60505-60506
User-Agent: ProgDVB
14:31:03.538 - !! RTSP/1.0 503 Service Unavailable
Content-Type:text/parameters
CSeq:42
Content-Length: 19
in 503 Content is the reason defined type is text
can be wrong Parameter
Re: SAT>IP Protocol support
Posted: Fri Jan 15, 2016 1:35 pm
by Prog
Please test "c" prerelase.
Re: SAT>IP Protocol support
Posted: Fri Jan 15, 2016 3:54 pm
by Diefenthal
Prog wrote:Please test "c" prerelase.
scan done and Looks like that it works
Re: SAT>IP Protocol support
Posted: Sun Jan 17, 2016 6:42 am
by Prog
Next step. Who can test Android version?
http://www.progdvb.com/progtva.html