progdvb.com

Posted: **Wed Dec 16, 2015 5:20 pm**

Here the log of a scan with DVBViewer what is working. As I thought, DVBViewer is getting PAT, then all PMTs on the transponder, then SDT and at the end NIT.

First three transponder of the scan:

Code: Select all

146	10.971805000	192.168.1.121	192.168.1.6	TCP	66	50429 > rtsp [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=4 SACK_PERM=1
148	10.975846000	192.168.1.121	192.168.1.6	TCP	54	50429 > rtsp [ACK] Seq=1 Ack=1 Win=65700 Len=0
149	10.975944000	192.168.1.121	192.168.1.6	RTSP	107	OPTIONS rtsp://192.168.1.6:554/ RTSP/1.0
152	10.987698000	192.168.1.121	192.168.1.6	RTSP	239	SETUP rtsp://192.168.1.6:554/?src=1&freq=10714&msys=dvbs&plts=off&fec=&pol=h&ro=0.35&sr=22000&mtype=qpsk&pids=0 RTSP/1.0
156	11.191612000	192.168.1.121	192.168.1.6	TCP	54	50429 > rtsp [ACK] Seq=239 Ack=353 Win=65348 Len=0
255	26.007253000	192.168.1.121	192.168.1.6	RTSP	143	PLAY rtsp://192.168.1.6:554/stream=167?delpids=0 RTSP/1.0
258	26.012829000	192.168.1.121	192.168.1.6	RTSP	143	PLAY rtsp://192.168.1.6:554/stream=167?addpids=0 RTSP/1.0
264	26.207193000	192.168.1.121	192.168.1.6	TCP	54	50429 > rtsp [ACK] Seq=417 Ack=668 Win=65032 Len=0
550	41.017832000	192.168.1.121	192.168.1.6	RTSP	143	PLAY rtsp://192.168.1.6:554/stream=167?delpids=0 RTSP/1.0
552	41.020678000	192.168.1.121	192.168.1.6	RTSP	218	PLAY rtsp://192.168.1.6:554/stream=167?src=1&freq=10729&msys=dvbs2&plts=off&fec=23&pol=v&ro=0.35&sr=22000&mtype=8psk&pids=0 RTSP/1.0
558	41.247784000	192.168.1.121	192.168.1.6	TCP	54	50429 > rtsp [ACK] Seq=670 Ack=982 Win=64716 Len=0
571	41.777885000	192.168.1.121	192.168.1.6	RTSP	143	PLAY rtsp://192.168.1.6:554/stream=167?delpids=0 RTSP/1.0
573	41.781664000	192.168.1.121	192.168.1.6	RTSP	221	PLAY rtsp://192.168.1.6:554/stream=167?addpids=1024,1025,1026,1027,1028,1029,1030,1031,1032,1033,1034,1038,1039,1041,1043,1044 RTSP/1.0
580	41.977808000	192.168.1.121	192.168.1.6	TCP	54	50429 > rtsp [ACK] Seq=926 Ack=1296 Win=64404 Len=0
582	42.005879000	192.168.1.121	192.168.1.6	RTSP	221	PLAY rtsp://192.168.1.6:554/stream=167?delpids=1024,1025,1026,1027,1028,1029,1030,1031,1032,1033,1034,1038,1039,1041,1043,1044 RTSP/1.0
584	42.008935000	192.168.1.121	192.168.1.6	RTSP	148	PLAY rtsp://192.168.1.6:554/stream=167?addpids=17,16 RTSP/1.0
589	42.207819000	192.168.1.121	192.168.1.6	TCP	54	50429 > rtsp [ACK] Seq=1187 Ack=1611 Win=65700 Len=0
650	43.963937000	192.168.1.121	192.168.1.6	RTSP	148	PLAY rtsp://192.168.1.6:554/stream=167?delpids=17,16 RTSP/1.0
652	43.968107000	192.168.1.121	192.168.1.6	RTSP	218	PLAY rtsp://192.168.1.6:554/stream=167?src=1&freq=10744&msys=dvbs&plts=off&fec=56&pol=h&ro=0.35&sr=22000&mtype=qpsk&pids=0 RTSP/1.0
659	44.173900000	192.168.1.121	192.168.1.6	TCP	54	50429 > rtsp [ACK] Seq=1445 Ack=1928 Win=65380 Len=0
667	44.340938000	192.168.1.121	192.168.1.6	RTSP	144	PLAY rtsp://192.168.1.6:554/stream=167?delpids=0 RTSP/1.0
669	44.342121000	192.168.1.121	192.168.1.6	RTSP	172	PLAY rtsp://192.168.1.6:554/stream=167?addpids=100,200,300,400,500,600,17,16 RTSP/1.0
684	44.540905000	192.168.1.121	192.168.1.6	TCP	54	50429 > rtsp [ACK] Seq=1653 Ack=2246 Win=65064 Len=0
690	44.745969000	192.168.1.121	192.168.1.6	RTSP	172	PLAY rtsp://192.168.1.6:554/stream=167?delpids=100,200,300,400,500,600,17,16 RTSP/1.0
692	44.748966000	192.168.1.121	192.168.1.6	RTSP	145	PLAY rtsp://192.168.1.6:554/stream=167?addpids=16 RTSP/1.0
697	44.955926000	192.168.1.121	192.168.1.6	TCP	54	50429 > rtsp [ACK] Seq=1862 Ack=2564 Win=64744 Len=0
866	52.873289000	192.168.1.121	192.168.1.6	RTSP	145	PLAY rtsp://192.168.1.6:554/stream=167?delpids=16 RTSP/1.0

To scan 130 transponder it takes 16 minutes and 1349 channels where found.
If a transponder is offline or wrong in the list DVBViewer will skip waiting for data after 30 seconds.
Also DVBViewer waits 30s if PAT got read but PMT faild. This waiting time is realy high.
If the transponder is alive the scan take ~2-10s

I don't think that pids=all would be faster because there you have to do the scan also step by step (PAT -> PMT, SDT,...).
And the data is repeated all 100-500ms.

Anyway, if it takes longer than the methode with pids=all I think it should not be a problem because of the working result.
Myself, I do not scan every day the whole satellite.

Posted: **Thu Dec 17, 2015 8:44 am**

ProgDVB spend ~10 minutes on DVB device. I think need 40-60minutes in "by pid" mode. Because need wait more then 10 seconds of every pid.

Posted: **Thu Dec 17, 2015 8:59 am**

Hopefully you will fix this, because otherwise ProgDVB can't be used for this SAT>IP servers:

Inverto IDL 400s
Telestar Digbit R1
GSS DSI 400

Posted: **Wed Dec 23, 2015 5:04 pm**

Portisch wrote:Hopefully you will fix this, because otherwise ProgDVB can't be used for this SAT>IP servers:

Inverto IDL 400s
Telestar Digbit R1
GSS DSI 400

hmm that had i tested some time ago and it had worked with the Digibit R1 ,Octopus Net

what i at time not know if Prog have something changed in the Rtsp Rtp Code

and yes i prefer the pids=all mode not ! the triax tss400 (Ses Reference Device ) cant handle that

Posted: **Wed Dec 23, 2015 5:06 pm**

Is Digibit R1 and Octopus Net support pids=all?

Posted: **Wed Dec 23, 2015 5:15 pm**

Prog wrote:Is Digibit R1 and Octopus Net support pids=all?

yes i you want can you see it
over teamviewer

edit

with the new ProgDVB build had i a param called fr=1 should it be fe = 1 ? and why is it one more than one ?

edit 2

@portisch

if you want can you try that builds

Posted: **Thu Dec 24, 2015 6:21 am**

Yes. Must be "fe=". Try last prerelease.

Posted: **Thu Dec 24, 2015 6:46 am**

here is a wireshark capture testdevice Telestar Digibit r1

rtsp rtp Looks ok

https://onedrive.live.com/redir?resid=6 ... e%2cpcapng

but progdvb list nothing in channel / Service scan

https://onedrive.live.com/redir?resid=6 ... lder%2clog

Posted: **Thu Dec 24, 2015 10:47 am**

I am not have access to these links. But is it device support pids=all?

Posted: **Thu Dec 24, 2015 1:13 pm**

Prog wrote:I am not have access to these links. But is it device support pids=all?

yes the Telestar Digibit R1, Octopus Net both Support the pid=all Parameter
but None of this 3 Satip Server find anything in Progdvb but in every other app

you must anything changed since my old release test

had found an older progdvb Version

ProgDVB7.07.3x64 this found channels with the Telestar Digibit R1 and with the Octopus Net

Posted: **Thu Dec 24, 2015 1:26 pm**

Please send me logs of ProgDVB after scan.

Posted: **Thu Dec 24, 2015 1:31 pm**

had found an older progdvb Version

ProgDVB7.07.3x64 this found channels with the Telestar Digibit R1 and with the Octopus Net

Posted: **Thu Dec 24, 2015 1:37 pm**

Same links? Try install over and check old channels.

Posted: **Thu Dec 24, 2015 1:52 pm**

ProgDVB7.07.3x64 had i on my HDD

and scan and preview working

update this install with 7.12.0a preview is working of old scanned channels ,scan itself isnt working

Posted: **Thu Dec 24, 2015 2:44 pm**

hm. Can you scan and new version and check links in my log? It is correct?
Also send me ProgDVB logs.

ps: I am not have onedrive account. But you can send me like attach.

progdvb.com

SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support

Re: SAT>IP Protocol support