The default timeout value in the gss box is 60 seconds (at least it was in my box)
Does it also indicate that timeout value in the SETUP RTSP response or is it always empty?
The default timeout value in the gss box is 60 seconds (at least it was in my box)
Does it also indicate that timeout value in the SETUP RTSP response or is it always empty?
Hi,
good question. With telnet to Port 554 I got the following dialogue:
OPTIONS rtsp://10.0.1.90/?freq=12460.000&src=1&sr=27500&pol=h&fec=34&msys=dvbs&pids=0 RTSP/1.0
CSeq: 1
User-Agent: vdr-satip/0.1.0
RTSP/1.0 200 OK
CSeq: 1
Date: Mon, Mar 31 2014 19:12:40 GMT
Public: OPTIONS, DESCRIBE, SETUP, TEARDOWN, PLAY
SETUP rtsp://10.0.1.90/?freq=12460.000&src=1&sr=27500&pol=h&fec=34&msys=dvbs&pids=0 RTSP/1.0
CSeq: 2
Transport: RTP/AVP;unicast;client_port=57298-57299
User-Agent: vdr-satip/0.1.0
RTSP/1.0 200 OK
CSeq: 2
Date: Mon, Mar 31 2014 19:13:11 GMT
Transport: RTP/AVP;unicast;destination=10.0.1.49;source=10.0.1.90;client_port=57298-57299;server_port=6974-6975
Session: 08E310F7;timeout=60
com.ses.streamID: 9
Alles anzeigen
As you can see, the RTSP answer indeed contains the timeout value.
Best regards and many thanks for working on the plugin.
klausL
Hi!
It seems that the KeepAliveInterval was my problem too.
I changed the setting in my GSS to 60 an the settings in the plugin to 30000 and 5000 like KlausL.
There are no freezes since about 10 minutes. It seems to work!
Thank you
Niel
Yet another bug fix release is now available including tweaks to section filtering and session timeouts.
I changed it to 3000 Milliseconds (anything below 60 seconds) and it works as expected.
Ouch, my typo. Good catch, thanks! Could you check whether the attached patch works with default settings of GSSBOX?
EDIT: Download the latest plugin version instead.
The Ubuntu/Debian package in my PPA from tonight does already contain a proper patch according to klausL's input.
I still have the situation with 0.2.1 jerky video on all ZDF HD channels, significant drop-outs on other high rate german 720p channels and minor drop-outs on ServusTV HD (1080i) & ORF HD (720p) all with less bitrates compared to the german 720p channels. No difference if I tweak net.core.[rmem|wmem] from it's low default to 1 or either 2MB.
All these channels did work perfect for me with 0.1.1 on Octopus Net, without the need to tweak Network Buffers ...
Regard
fnu
The Ubuntu/Debian package in my PPA from tonight does already contain a proper patch according to klausL's input.
According to SAT>IP specs, the maximum interval of keep-alive is 30 seconds, so use 30000 instead of 3000 that's mentioned in klausL's post.
According to SAT>IP specs, the maximum interval of keep-alive is 30 seconds, so use 30000 instead of 3000 that's mentioned in klausL's post.
Hehe, I have done this intentionally, since 3secs seemed far to low to me ...
Regards
fnu
Great! If you're up to spending your free time again for non-productive testing, please let me know in IRC and let's start bisecting the bad commit that broke ZDF HD channels.
Ouch, my typo. Good catch, thanks! Could you check whether the attached patch works with default settings of GSSBOX?
It works with the gss box default timeout of 60 seconds. Thank you very much for your fast reaction.
At the moment I have no more problems with the gss box. The plugin also works great in my stable yavdr 0.5.
Best regards
klausL
A new version is out. Hopefully this time the session timeout and section filtering works a bit better than in the previous releases.
Hi,
since it seems to work for most dsi 400 users now....i'm special..
i still get artefacts. I tried now 0.2.2 too and still get artefacts and also errors in the log(had those before too, but didn't took them too serious)
Apr 5 20:58:10 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 20:58:18 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 20:58:31 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 20:58:48 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 20:58:52 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 20:59:13 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 20:59:18 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 20:59:34 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 20:59:48 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 20:59:55 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:00:16 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:00:18 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 21:00:37 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:00:48 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 21:00:58 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:01:18 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 21:01:19 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:01:40 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:01:48 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 21:02:01 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:02:18 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 21:02:22 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:02:43 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:02:48 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 21:03:04 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:03:18 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 21:03:25 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:03:46 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:03:48 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 21:04:07 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:04:18 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 21:04:28 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:04:48 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Apr 5 21:04:49 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:05:10 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 404
Apr 5 21:05:18 VDR vdr: [7983] ERROR: curl_easy_perform() [tuner.c,463] failed: RTSP session error (86)
Alles anzeigen
any idea what to do/test?
Best Regards
i still get artefacts. I tried now 0.2.2 too and still get artefacts and also errors in the log(had those before too, but didn't took them too serious)
Ok, what channels? 1080i, 720p, 576i or even lower?
How does the infrastructur look like between VDR and GSSBOX, each detail is important?
Regards
fnu
that was zdf hd, but i also get that with the normal "das erste" just less errors. (BTW: The log was a tail -f ... |grep ERROR)
network infrastructure(all 1 gbit connections):
DSI 400 <- ~80m -> smart managed zyxel switch <- ~80m -> Smart Managed switch from there all my devices are connected.
System is a Ivy Bridge based celeron. But i also tried VMs on core-i3-3xxx and core-i7-4xxx same result.
DVB Viewer doesn't have those troubles with the i3 system.
Best Regards
that was zdf hd, but i also get that with the normal "das erste" just less errors. (BTW: The log was a tail -f ... |grep ERROR)
Funny, all that issue I had with the former versions ...
Did you set the GSSBOX parameter like proposed above?
DVB Viewer doesn't have those troubles with the i3 system.
I guess we did talk about that statement already ... ... but does the PC running DVB Viewer use the same described infrastructure?
Regards
fnu
yes we did, but i wanted to repeat that because it is running on the same network infrastructure, just one switch port next to the vdr system
And i had those issues with all versions, not that they just started now again with 0.2.2.
Regards
just one switch port next to the vdr system
Ok, you did not mention that up to now ...
Did you set the GSSBOX parameter like proposed above?
I repeat that question?
What does:
say, on your VDR?
Regards
fnu
i tried several settings, default, different timeout, the suggested ones. But only checked for the artefacts.
Now i tried it again and also checked the log.
Error messages changed a bit:
Apr 5 21:47:38 VDR vdr: [7989] ERROR: Tuner detected invalid status code: 454
Apr 5 21:47:38 VDR vdr: [7989] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:02 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:02 VDR vdr: [7989] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:02 VDR vdr: [7989] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:11 VDR vdr: [7983] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:11 VDR vdr: [7983] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:11 VDR vdr: [7986] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:11 VDR vdr: [7986] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:44 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:44 VDR vdr: [7989] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:44 VDR vdr: [7989] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:53 VDR vdr: [7983] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:53 VDR vdr: [7983] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:53 VDR vdr: [7986] ERROR: Tuner detected invalid status code: 454
Apr 5 21:47:38 VDR vdr: [7989] ERROR: Tuner detected invalid status code: 454
Apr 5 21:47:38 VDR vdr: [7989] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:02 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:02 VDR vdr: [7989] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:02 VDR vdr: [7989] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:11 VDR vdr: [7983] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:11 VDR vdr: [7983] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:11 VDR vdr: [7986] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:11 VDR vdr: [7986] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:44 VDR vdr: [7948] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:44 VDR vdr: [7989] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:44 VDR vdr: [7989] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:53 VDR vdr: [7983] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:53 VDR vdr: [7983] ERROR: Tuner detected invalid status code: 454
Apr 5 21:48:53 VDR vdr: [7986] ERROR: Tuner detected invalid status code: 454
Alles anzeigen
Regards
Are all tuners connected of that box?
Regards
fnu
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!