Page 21 of 24

Re: SAT>IP Protocol support

Posted: Sun Jan 17, 2016 7:44 am
by Diefenthal
Prog wrote:Next step. Who can test Android version?
http://www.progdvb.com/progtva.html

i had no Smartphone sorry

Re: SAT>IP Protocol support

Posted: Thu Feb 18, 2016 7:26 am
by Prog
New style of settings for SAT>IP reqeust setup and scan channels again.
http://www.progdvb.com/download_progdvb_prerelease.html

But now cable possible also.

ps: I can test only DVB-S :(

Re: SAT>IP Protocol support

Posted: Tue Mar 15, 2016 8:49 pm
by evarost
Hi Prog (after much time)!

I'm doing some testing with TVHeadEnd as a SAT>IP server.
Now I found a big problem with ProgDVB as a SAT>IP client:

- Using version ProgDVB 7.12.07
- SAT>IP device configured only for SAT.
- When doing a Manual Scanning:
* Select a valid transponder.
* Pick "Scan"
- No channels detected.

In the logs of the server I see this:

1) ProgDVB send a SETUP command with pids=
2) After 5 seconds ProgDVB sends a TEARDOWN command.

From my experience with the SAT>IP protocol, the regular procedure is:

1) Send SETUP command (without pids=, but is valid to do it)
2) Send PLAY command (tipically with pids=, but not mandatory)
3) Get the stream over RTP.
4) Send TEARDOWN.

My question is: Why you are not sending the PLAY command?

I hope you can improve the SAT>IP client implementation. At time you can use several "software" servers.
Regards! ;)

Re: SAT>IP Protocol support

Posted: Wed Mar 16, 2016 9:25 am
by Prog
Please test prerelase also. some changes.

ps: I am use SAT>IP on my device time to time for test Android software.

Re: SAT>IP Protocol support

Posted: Mon Apr 04, 2016 11:50 am
by evarost
Hi Prog,

With last version (7.13.00 x64)) the same behaviour: no signal/lock in all transponders!

Yes, ProgDVB works with ALi SAT>IP server, but not with other SAT>IP servers.

Please, try to install some software SAT>IP server, like TVHeadend or Minisatip (Linux, free) or DVBViewer Recording Service (Windows, pay), and check compatibility. Or if you like, I can check in my environment (I have all of them for testing).

I hope you can improve SAT>IP support! :)
Best!

Re: SAT>IP Protocol support

Posted: Mon Apr 04, 2016 2:16 pm
by Prog
Can you check my logs?

Re: SAT>IP Protocol support

Posted: Tue Apr 05, 2016 5:59 am
by evarost
Prog wrote:Can you check my logs?
Yes,

Code: Select all

[ProgDVBEngine.log]
09:16:07.691 - FilterManager::OnSetTransponder CScannerManager::CreateEnvironment
09:16:07.691 - 
09:16:07.691 - DevicesManager::SetTransponder 11856000
09:16:07.691 - 
09:16:07.691 - TransponderManager::SetTransponder (TR) satip://192.168.1.60/?src=1&fe=1&freq=11856.0&sr=27500&pol=v&msys=dvbs&fec=34&pids=0,1,16,17,18
09:16:07.691 - --SwitchEngineTransport TS
09:16:07.691 - --SwitchEngineTransport end
09:16:07.691 - Api2Device::SetTransponder satip://192.168.1.60/?src=1&fe=1&freq=11856.0&sr=27500&pol=v&msys=dvbs&fec=34&pids=0,1,16,17,18
09:16:07.691 - Api2Device::SetTransponder result OK delay 0 ms
09:16:07.691 - TsInputTrafficProcessor::OpenTransponder 0
09:16:07.691 - FilterManager::OnSetTransponder SetTransponder
09:16:07.691 - ModuleList::ChangeChannel 0
09:16:07.691 - FilterManager::OnSetTransponder ScanTrasponderParseTS - satip://192.168.1.60/?src=1&fe=1&freq=11856.0&sr=27500&pol=v&msys=dvbs&fec=34&pids=0,1,16,17,18
09:16:10.895 - FilterManager::OnSetTransponder ScanTrasponderParseTS - satip://192.168.1.60/?src=1&fe=1&freq=11856.0&sr=27500&pol=v&msys=dvbs&fec=34&pids=0,1,16,17,18
09:16:12.880 - * s:0 q:0 tr=0 (0) NotSupported
09:16:13.662 - * s:0 q:0 tr=0 (0) NotSupported
09:16:14.162 - * s:0 q:0 tr=0 (0) NotSupported
09:16:14.662 - * s:0 q:0 tr=0 (0) NotSupported
09:16:15.162 - * s:0 q:0 tr=0 (0) NotSupported
09:16:15.662 - * s:0 q:0 tr=0 (0) NotSupported
09:16:16.162 - * s:0 q:0 tr=0 (0) NotSupported
09:16:16.663 - * s:0 q:0 tr=0 (0) NotSupported
09:16:17.163 - * s:0 q:0 tr=0 (0) NotSupported
09:16:17.663 - * s:0 q:0 tr=0 (0) NotSupported
09:16:18.163 - * s:0 q:0 tr=0 (0) NotSupported
09:16:18.663 - * s:0 q:0 tr=0 (0) NotSupported
09:16:19.163 - * s:0 q:0 tr=0 (0) NotSupported
09:16:19.663 - * s:0 q:0 tr=0 (0) NotSupported
09:16:20.163 - * s:0 q:0 tr=0 (0) NotSupported
09:16:20.664 - * s:0 q:0 tr=0 (0) NotSupported
09:16:21.164 - * s:0 q:0 tr=0 (0) NotSupported
09:16:21.664 - * s:0 q:0 tr=0 (0) NotSupported
09:16:22.164 - * s:0 q:0 tr=0 (0) NotSupported
09:16:22.664 - * s:0 q:0 tr=0 (0) NotSupported
09:16:23.165 - * s:0 q:0 tr=0 (0) NotSupported
09:16:23.665 - * s:0 q:0 tr=0 (0) NotSupported
09:16:24.164 - * s:0 q:0 tr=0 (0) NotSupported
09:16:24.665 - * s:0 q:0 tr=0 (0) NotSupported
09:16:25.165 - * s:0 q:0 tr=0 (0) NotSupported
09:16:25.665 - * s:0 q:0 tr=0 (0) NotSupported
09:16:26.165 - * s:0 q:0 tr=0 (0) NotSupported
09:16:26.666 - * s:0 q:0 tr=0 (0) NotSupported
09:16:27.166 - * s:0 q:0 tr=0 (0) NotSupported
09:16:27.666 - * s:0 q:0 tr=0 (0) NotSupported
09:16:28.166 - * s:0 q:0 tr=0 (0) NotSupported
09:16:28.667 - * s:0 q:0 tr=0 (0) NotSupported
09:16:29.167 - * s:0 q:0 tr=0 (0) NotSupported
09:16:29.667 - * s:0 q:0 tr=0 (0) NotSupported
09:16:30.167 - * s:0 q:0 tr=0 (0) NotSupported
09:16:30.652 - * s:0 q:0 tr=0 (0) NotSupported
09:16:31.152 - * s:0 q:0 tr=0 (0) NotSupported
09:16:31.652 - * s:0 q:0 tr=0 (0) NotSupported
09:16:32.152 - * s:0 q:0 tr=0 (0) NotSupported
09:16:32.652 - * s:0 q:0 tr=0 (0) NotSupported
09:16:33.152 - * s:0 q:0 tr=0 (0) NotSupported
09:16:33.653 - * s:0 q:0 tr=0 (0) NotSupported
09:16:34.153 - * s:0 q:0 tr=0 (0) NotSupported
09:16:34.653 - * s:0 q:0 tr=0 (0) NotSupported
09:16:35.153 - * s:0 q:0 tr=0 (0) NotSupported
09:16:35.653 - * s:0 q:0 tr=0 (0) NotSupported
09:16:36.153 - * s:0 q:0 tr=0 (0) NotSupported
09:16:36.653 - * s:0 q:0 tr=0 (0) NotSupported
09:16:37.153 - * s:0 q:0 tr=0 (0) NotSupported
09:16:37.654 - * s:0 q:0 tr=0 (0) NotSupported
09:16:38.154 - * s:0 q:0 tr=0 (0) NotSupported
09:16:38.654 - * s:0 q:0 tr=0 (0) NotSupported
09:16:39.154 - * s:0 q:0 tr=0 (0) NotSupported
09:16:39.654 - * s:0 q:0 tr=0 (0) NotSupported
09:16:40.154 - * s:0 q:0 tr=0 (0) NotSupported
09:16:40.654 - * s:0 q:0 tr=0 (0) NotSupported
09:16:41.154 - * s:0 q:0 tr=0 (0) NotSupported
09:16:41.655 - * s:0 q:0 tr=0 (0) NotSupported
09:16:42.155 - * s:0 q:0 tr=0 (0) NotSupported
09:16:42.655 - * s:0 q:0 tr=0 (0) NotSupported
09:16:43.155 - * s:0 q:0 tr=0 (0) NotSupported
09:16:43.656 - * s:0 q:0 tr=0 (0) NotSupported
09:16:44.171 - * s:0 q:0 tr=0 (0) NotSupported
09:16:45.156 - * s:0 q:0 tr=0 (0) NotSupported
09:16:45.422 - 
09:16:45.422 - Stop engine
09:16:45.422 - DevicesManager::Stop
09:16:45.422 - DevicesManager::Free devices
09:16:45.437 - TransponderManager::~TransponderManager
09:16:45.437 - ModuleList::Free
09:16:45.437 - DevicesManager::Free RC
09:16:45.437 - Engine stopped
09:16:45.703 - HugeMemoryBlocksManager::FreeAll

Code: Select all

[rtsp.log]
09:16:05.300 - ====================
09:16:07.660 - ----- too long wait of TEARDOWN answer
09:16:07.691 - ------ rtsp://192.168.1.60/?src=1&fe=1&freq=11856.0&sr=27500&pol=v&msys=dvbs&fec=34&pids=0,1,16,17,18
09:16:07.691 - delayed add pid17
09:16:07.691 - delayed add pid1
09:16:07.691 - delayed add pid16
09:16:07.707 - delayed add pid0
09:16:07.722 - >> OPTIONS rtsp://192.168.1.60/?src=1&fe=1&freq=11856.0&sr=27500&pol=v&msys=dvbs&fec=34&pids=0,1,16,17,18 RTSP/1.0
CSeq: 15724
User-Agent: Wget/1.9.1


09:16:07.769 - ==================== 78
09:16:07.769 - RTSP/1.0 200 OK
CSeq: 15724
Public: OPTIONS,DESCRIBE,SETUP,PLAY,TEARDOWN


09:16:07.769 - ====================
09:16:07.769 - -- TS RTP Client
09:16:07.769 - >> SETUP rtsp://192.168.1.60/?src=1&fe=1&freq=11856.0&sr=27500&pol=v&msys=dvbs&fec=34&pids=0,1,16,17,18 RTSP/1.0
CSeq: 15725
Transport: RTP/AVP;unicast;client_port=57456-57457
User-Agent: Wget/1.9.1


09:16:07.800 - ==================== 136
09:16:07.800 - RTSP/1.0 200 OK
CSeq: 15725
Session: BF185908;timeout=30
Transport: RTP/AVP;unicast;client_port=57456-57457
com.ses.streamID: 10


09:16:07.800 - ====================
09:16:10.895 - delayed del pid0
09:16:10.895 - delayed del pid1
09:16:10.895 - delayed del pid17
09:16:10.895 - delayed del pid16
09:16:12.817 - >> TEARDOWN rtsp://192.168.1.60/?src=1&fe=1&freq=11856.0&sr=27500&pol=v&msys=dvbs&fec=34&pids=0,1,16,17,18 RTSP/1.0
CSeq: 15726
Session: BF185908
User-Agent: Wget/1.9.1


09:16:12.848 - << RTSP/1.0 404 Not Found
CSeq: 15726
Session: BF185908

Code: Select all

[NetClient.log]
09:16:05.128 - Starting new channel: 
09:16:05.128 - SubID 0 index=0
09:16:05.128 - closesocket 2540 0x23038790
09:16:05.128 - closesocket 2584 0x2308AFD0
09:16:05.128 - opensocket TCP 1300 0x23066680 net 0.0.0.0 554
09:16:05.159 - connected 1300
09:16:05.206 - UDP & Bind 57454
09:16:05.300 - RTSP: Error! not server port and dest.
09:16:07.660 - Async close 1300
09:16:07.660 - SubID 0 on founded.
09:16:07.660 - DoNextSubChannel - no next url!
09:16:07.691 - Starting new channel: 
09:16:07.691 - SubID 0 index=0
09:16:07.691 - opensocket TCP 2540 0x23000DB0 net 0.0.0.0 554
09:16:07.722 - connected 2540
09:16:07.769 - UDP & Bind 57456
09:16:07.800 - RTSP: Error! not server port and dest.
09:16:07.816 - exit thread 0x23066680 st=4
09:16:10.301 - Skip error 10060
09:16:12.817 - Skip error 10060
09:16:12.848 - exit thread 0x23000DB0 st=4
09:16:12.880 - Async close 2540
09:16:12.880 - SubID 0 on founded.
09:16:12.880 - DoNextSubChannel - no next url!
09:16:45.422 - closesocket 1304 0x23038790
09:16:45.422 - closesocket 1300 0x23066680
09:16:45.437 - closesocket 2616 0x2308AFD0
09:16:45.437 - closesocket 2540 0x23000DB0
In my opinion is relevant:

1) The message "RTSP: Error! not server port and dest." in NetClient.log

2) After the SETUP message ProgDVB doesn't sends the PLAY command. Remember that the protocol steps are: OPTIONS, SETUP (mandatory), DESCRIBE (optinal), PLAY (mandatory), TEARDOWN. So, after the SETUP if you like to test the tuner status, then you need to use the DESCRIBE command. So, if you wait for packets without sending the PLAY command, you will never received them!

I hope you can improve the SAT>IP support!

Re: SAT>IP Protocol support

Posted: Tue Apr 05, 2016 11:13 am
by Prog
try setup SAT>IP again.

On my PC logs like
OPTIONS rtsp://192.168.88.24/?src=1&fe=1&freq=11053.0&sr=2894&pol=v&msys=dvbs&fec=34&pids=0,1,16,17,18
SETUP rtsp://192.168.88.24/?src=1&fe=1&freq=11053.0&sr=2894&pol=v&msys=dvbs&fec=34&pids=0,1,16,17,18
PLAY rtsp://192.168.88.24:554/stream=3?src=1&fe=1&freq=11053.0&sr=2894&pol=v&msys=dvbs&fec=34&pids=0,1,16,17,18
PLAY rtsp://192.168.88.24/?addpids=17,1,16,0
...

Re: SAT>IP Protocol support

Posted: Wed Apr 06, 2016 5:41 am
by evarost
Prog wrote:try setup SAT>IP again.
:?: :?: :?: My test is after changing the SAT>IP DVB-S2 server IP in the options window.

I the logs I see that ProgDVB doesn't sends the PLAY command (yes with ALi server).
And, why the error "RTSP: Error! not server port and dest." ?

I feel the problem can be: ProgDVB doesn't parse some RTSP response right... and consequently discards the response, and then it don't continue.
This can be real?

Re: SAT>IP Protocol support

Posted: Wed Apr 06, 2016 7:07 am
by Prog
Can you add log2=1 to ProgDVB.ini -> [Debug] and send me all files from logs.

Re: SAT>IP Protocol support

Posted: Thu Apr 07, 2016 4:46 am
by Prog
And try setup ProgDVB again. In new folder. Because this is not sat>ip mode. This is rtsp mode.

Re: SAT>IP Protocol support

Posted: Thu Apr 07, 2016 7:51 am
by Prog
new update in prerelease. Please test diseq switch case. I am not have hardware for that.

Re: SAT>IP Protocol support

Posted: Fri Jul 08, 2016 5:01 am
by Prog
Try any problem in 7.14.6?

Re: SAT>IP Protocol support

Posted: Mon Feb 27, 2017 3:47 am
by No Spam
Hi,
Triax TSS 400 does not work for me. What am I doing wrong?
I have configured ProgDVB with Sat>IP source, pointed it to the Triax, scanning found a huge bunch of channels, but playback shows just "Error!" in the status line.
Con you please help me? Thanks in advance!

Re: SAT>IP Protocol support

Posted: Mon Feb 27, 2017 3:52 am
by Prog
Please send me logs. I have this device but not test every version with it.