Display posts from previous
Sort by

Re: SAT>IP Protocol support

#106 by evarost
Prog wrote:Yes, I do this in near versions. Please wait some days (week?) I am very busy now.
OK! I'm very pleased to wait until you have time to complete this. :D

When you post a message about new version I'll test it. Also, I'll provide to you more logs and my trials using direct calls to the device using RTSP commands.

Regards!

Re: SAT>IP Protocol support

#108 by evarost
Prog wrote:One small change for you in last prereleaase - modules/plugins for DVB over IP. Please test that.
Hi Prog,

After test these two versions: 7.05.9b (pre-release) and 7.06 (release), the result is the same:

Code: Select all

-----rtsp://192.168.210.181:554/?src=1&fe=1&freq=12402&pol=v&msys=dvbs&sr=27500&fec=34&pids=all
>> OPTIONS rtsp://192.168.210.181:554/?src=1&fe=1&freq=12402&pol=v&msys=dvbs&sr=27500&fec=34&pids=all RTSP/1.0
CSeq: 1
User-Agent: ProgDVB

<< RTSP/1.0 200 OK
CSeq: 1
Date: Sun, Jul 13 2014 16:52:35 GMT
Public: OPTIONS, DESCRIBE, SETUP, TEARDOWN, PLAY


>> DESCRIBE rtsp://192.168.210.181:554/?src=1&fe=1&freq=12402&pol=v&msys=dvbs&sr=27500&fec=34&pids=all RTSP/1.0
CSeq: 2
Accept: application/sdp
User-Agent: ProgDVB

<< RTSP/1.0 404 Stream Not Found
CSeq: 2
Date: Sun, Jul 13 2014 16:52:35 GMT
Please, remember that the command DESCRIBE is UNUSABLE in SAT-IP protocol, and you really need to forget it! Please, add an option in the "DVB over IP" device to "Disable describe". If you make this optional, you don't break your code. If you don't add this minimal change, I can't do anything! :(

Re: SAT>IP Protocol support

#109 by evarost
Hi,

Related to the TEARDOWN command using "program" mode and the bug of the channel change, I see the changes in the log. But the problem continues. I post here the rtsp.log of this action: I open ProgDVB and I select only one channel (previously scanned), and then I close ProgDVB:
-----rtsp://192.168.210.181:554/programID=5259265
>> OPTIONS rtsp://192.168.210.181:554/programID=5259265 RTSP/1.0
CSeq: 1
User-Agent: ProgDVB

<< RTSP/1.0 200 OK
CSeq: 1
Date: Sun, Jul 13 2014 17:04:03 GMT
Public: OPTIONS, DESCRIBE, SETUP, TEARDOWN, PLAY


>> DESCRIBE rtsp://192.168.210.181:554/programID=5259265 RTSP/1.0
CSeq: 2
Accept: application/sdp
User-Agent: ProgDVB

<< RTSP/1.0 200 OK
CSeq: 2
Date: Sun, Jul 13 2014 17:04:03 GMT
Content-Base: rtsp://192.168.210.181/
Content-Type: application/sdp
Content-Length: 222


v=0
o=- 1404246770434000 1 IN IP4 192.168.210.181
s=SatIPServer:1 1
t=0 0
a=control:rtsp://192.168.210.181/programID=5259265
m=video 0 RTP/AVP 33
c=IN IP4 0.0.0.0
a=control:rtsp://192.168.210.181/programID=5259265

>> SETUP rtsp://192.168.210.181/programID=5259265 RTSP/1.0
CSeq: 3
Transport: RTP/AVP;unicast;client_port=57936-57937
User-Agent: ProgDVB

-----rtsp://192.168.210.181:554/programID=5259265
>> OPTIONS rtsp://192.168.210.181:554/programID=5259265 RTSP/1.0
CSeq: 1
User-Agent: ProgDVB

<< RTSP/1.0 200 OK
CSeq: 3
Date: Sun, Jul 13 2014 17:04:03 GMT
Transport: RTP/AVP;unicast;destination=192.168.210.101;source=192.168.210.181;client_port=57936-57937;server_port=6970-6971
Session: 5076599A;timeout=60


>> PLAY rtsp://192.168.210.181/programID=5259265 RTSP/1.0
CSeq: 4
Range: npt=now-
Session: 5076599A
User-Agent: ProgDVB

<< RTSP/1.0 200 OK
CSeq: 1
Date: Sun, Jul 13 2014 17:04:04 GMT
Public: OPTIONS, DESCRIBE, SETUP, TEARDOWN, PLAY


>> DESCRIBE rtsp://192.168.210.181:554/programID=5259265 RTSP/1.0
CSeq: 2
Accept: application/sdp
User-Agent: ProgDVB

<< RTSP/1.0 200 OK
CSeq: 2
Date: Sun, Jul 13 2014 17:04:04 GMT
Content-Base: rtsp://192.168.210.181/
Content-Type: application/sdp
Content-Length: 222


v=0
o=- 1404246770434000 1 IN IP4 192.168.210.181
s=SatIPServer:1 1
t=0 0
a=control:rtsp://192.168.210.181/programID=5259265
m=video 0 RTP/AVP 33
c=IN IP4 0.0.0.0
a=control:rtsp://192.168.210.181/programID=5259265

>> SETUP rtsp://192.168.210.181/programID=5259265 RTSP/1.0
CSeq: 3
Transport: RTP/AVP;unicast;client_port=57937-57938
User-Agent: ProgDVB

<< RTSP/1.0 200 OK
CSeq: 3
Date: Sun, Jul 13 2014 17:04:04 GMT
Transport: RTP/AVP;unicast;destination=192.168.210.101;source=192.168.210.181;client_port=57937-57938;server_port=6970-6971
Session: 3801942C;timeout=60


>> PLAY rtsp://192.168.210.181/programID=5259265 RTSP/1.0
CSeq: 4
Range: npt=now-
Session: 3801942C
User-Agent: ProgDVB

<< RTSP/1.0 200 OK
CSeq: 4
Date: Sun, Jul 13 2014 17:04:04 GMT
Session: 3801942C
RTP-Info: url=rtsp://192.168.210.181/programID=5259265


.marker

.marker

>> TEARDOWN rtsp://192.168.210.181:554/programID=5259265 RTSP/1.0
CSeq: 5
Session: 5076599A
User-Agent: ProgDVB

>> TEARDOWN rtsp://192.168.210.181:554/programID=5259265 RTSP/1.0
CSeq: 5
Session: 3801942C
User-Agent: ProgDVB
I see that the last two TEARDOWN commands are anoying. The first is writed in the log when the channel STARTS to play. The second, is writed when I close the ProgDVB program. Why you send one of these messages when you start to play?

I feel that I need to prepare some captures of RTPS play with VLC and the SATIP software. I'll try to do as an example for you.

Regards!

Re: SAT>IP Protocol support

#111 by evarost
Prog wrote:I have all information but need some time :(
Ok, sorry! I'm also very busy!
Thank you for your effort! I'm sure that you will that very good. I only like to list the improvements that I suggest:

1) Add one option in the "DVB over IP" device to "disable DESCRIBE command".

2) Rewrite TEARDOWN command in RTSP to fix change channel bug.

3) Enable (directly or with an option) the plugins support for the "DVB over IP" device.


I like also to suggest this simple option in the scanning process: When the first channel is found (one packet of video and audio pid) stop the scanning and continue with the next. This is for improve scanning time when the TS has only one channel. I suggest to implement this as an "option" (like "import wihtout scanning" in the IPTV device).

Regards! :wink:

Re: SAT>IP Protocol support

#116 by Diefenthal
evarost wrote:
Diefenthal wrote:my Project Refereceshas eva rost here published
Hi D.

Nice to meet you! You know about any software SAT>IP server implementation?
what should be the target ?

1. Software Emulation of an Sat>Ip Server for BDA Cards ?
2. or give ProgDVB the function to find and controll the avaible Sat>Ip Server inside the Network

for 2. find and Controll have i a Sample writen ,called "SatIp Rtsp Sample" is on github too
it reads data from an .m3u and Sends so the RTSP Request to the SatIp Server
and feed the Windows MediaPlayer Active X with the RTP Destination and RTP Port Values

Re: SAT>IP Protocol support

#118 by Diefenthal
Prog wrote:That is for testing of ProgDVB.

My target is sat ip client in ProgDVB. Do you have some sample of upnp detection of sat ip servers? I plan use c# for that.


evarost: Last prerelease for you.

2 ways ;-)

the first use the MS upnp lib

https://github.com/Diefenthal/SatIp-Rts ... Locator.cs
https://github.com/Diefenthal/SatIp-Rts ... r/Form1.cs

the second was a try for understanding how upnp ssdp works

https://github.com/Diefenthal/SatIp-Dis ... pClient.cs
https://github.com/Diefenthal/SatIp-Dis ... r/Form1.cs

the second way isnt not really stable

Re: SAT>IP Protocol support

#120 by Diefenthal
evarost wrote:
Diefenthal wrote: 1. Software Emulation of an Sat>Ip Server for BDA Cards ?
Hi,

This sounds interesting! Can be feasible? :D

that is possible but for an hobbiest like me too much
for that is deep directshow C++ knowlege required
but a test implementation is in work ;-) https://github.com/MediaPortal/MediaPor ... rver_merge

and is really offtopic
if i can helping prog with his progdvb than will i try to help him
so good i can