Project

General

Profile

Bug #4016

RTSP SETUP error -5 using DVBViewer Recording Service as SAT>IP server

Added by Laurie Davis about 8 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
SAT>IP
Target version:
-
Start date:
2016-10-10
Due date:
% Done:

0%

Estimated time:
Found in version:
2267
Affected Versions:

Description

TVH sees all the tuners on my Windows DVBViewer Service as SAT>IP servers. However, when I try to use them from TVH, I get

[ ERROR]:satip: SAT>IP DVB-T Tuner #1 (192.168.1.201) - RTSP SETUP error -5 (Input/output error) [6-404]

Running with an https trace, I see that TVH makes an initial setup call but DVBViewer replies with "404 stream not found" - see attached log. I have had this working before on TVH version 2190, but I am now using a recent nightly (2267) where it is is broken.

I raised a bug before (#3933) for another issue on 2190, and in the httpc logs for that I can see TVH was making a connection using a url of

SETUP rtsp://192.168.1.201/*stream=5?*fe=3&freq=545.833&bw=8&msys=.....

However, in the logs for this problem, the url is

SETUP rtsp://192.168.1.201/?fe=1&freq=545.833&bw=8&msys=dvbt2&mt.....

There is no 'stream' parameter passed.

Is this a bug?

Files

TVHlog.log (4.78 KB) TVHlog.log Laurie Davis, 2016-10-10 11:36
RS.JPG (24.3 KB) RS.JPG Laurie Davis, 2016-10-11 10:52
TVHlog.log (40.7 KB) TVHlog.log Laurie Davis, 2016-10-11 10:52
TVH.JPG (16.6 KB) TVH.JPG Laurie Davis, 2016-10-11 10:52
description.xml (1.5 KB) description.xml Laurie Davis, 2016-10-11 13:38
1.png (96.8 KB) 1.png DVBViewer Media Server Anton Bungin, 2019-05-03 14:46
2.png (94.7 KB) 2.png DVBViewer Media Server Anton Bungin, 2019-05-03 14:46
3.png (86.6 KB) 3.png SAT>IP DVB-C tuner Anton Bungin, 2019-05-03 14:47
4.png (66.4 KB) 4.png networks Anton Bungin, 2019-05-03 14:47
A.png (129 KB) A.png DVBViewer config Anton Bungin, 2019-05-03 14:47

History

#1

Updated by Jaroslav Kysela about 8 years ago

  • Status changed from New to Rejected

It appears like a bug in DVBViewer. The requested SETUP cmd is valid:

SETUP rtsp://192.168.1.201/?fe=1&freq=545.833&bw=8&msys=dvbt2&mtype=256qam&tmode=32k&gi=1128&pls=0 RTSP/1.0
Transport: RTP/AVP;unicast;client_port=55408-55409
CSeq: 1

Check the server what this reply does mean:

RTSP/1.0 404 Stream Not Found

The stream parameter must be returned by the server as a result for the new SETUP cmd.

SAT>IP specification:

http://www.satip.info/resources

#2

Updated by Laurie Davis about 8 years ago

Thanks for the response. I raised it with the DVBViewer guys - http://www.dvbviewer.tv/forum/topic/58808-cannot-connect-to-rs-using-satip/

Basically, in the SETUP command above, TVH is specifying 'fe=1' (ie tuner 1 in DVBViewer) and 'msys=dvbt2'. However, tuner 1 in DVBViewer is a DVB-C tuner only and so it returns the 'stream not found' error.

I think this is an issue in TVH with the order of SAT>IP tuners. In DVBViewer I have three tuners - tuner 1 is a DVB-C, and the other two are DVB-T2, and they are in that order in DVBViewer. However, the list of SAT>IP tuners I see in TVH is reversed - it shows the two DVB-T2 first and the DVB-C last - see the attached jpg. I have done a few more tests and it seems to be reversing the 'fe=x' parameter, so for example, when trying to connect to the DVB-C tuner, the SETUP command specifies (incorrectly) 'fe=3', and trying to connect to a DVB-T2 it tries with 'fe=1' (this fails and then it tries 'fe=2' which works as the second tuner is a DVB-T2).

I am sure in previous builds the order of the detected SAT>IP tuners was correct, so a recent build seems to have reversed these (possibly?).

Attached are jpgs showing the order of tuners in DVBViewer and TVH, plus a trace log from TVH.

Thanks

#3

Updated by Jaroslav Kysela about 8 years ago

It appears that the string in the SAT>IP XML description file describing the tuners is wrong from DVBViewer. TVH honors the order in the <urn:ses-com:satipX_SATIPCAP> xml tag (the description XML file). Could you check? This is only place where the tuners are described from the server.

#4

Updated by Laurie Davis about 8 years ago

I'm not sure I'm looking at the right thing but apparently doing

http://&lt;dvbviewer-url&gt;/description.xml

should produce it - this is attached. However, the content doesn't look right:

<satip:X_SATIPCAP xmlns:satip="urn:ses-com:satip">DVBS2-0,DVBT-0,DVBT2-2,DVBC-1</satip:X_SATIPCAP>

That just seems to be listing the possible types - I have no DVBS2 tuners installed in DVBViewer.

Does the satip xml from DVBViewer get saved anywhere in TVH? If so, where? Or what trace can I enable to see what TVH gets from DVBViewer when it starts up?

#5

Updated by Laurie Davis about 8 years ago

Ah, just read a little more at http://www.satip.info/sites/satip/files/resource/satip_specification_version_1_2_2.pdf and I now see the numbers after each type in that tag indicate how many tuners are available, so zero DVBS2 tuners, zero DVBT, two DVBT2 and one DVBC, which is correct.

However, in that spec I can't see where it says the order is mandatory to match the host tuners, so is it incorrect that TVH should assume this is the correct order and the 'fe=x' param should match? Would it be better to omit the 'fe=' param completely and let the host choose what tuner to use?

#6

Updated by Jaroslav Kysela about 8 years ago

Yes, the whole problem is that the spec does not handle the situation where the server uses multiple tuners with different types. The one way is to use the order from server (PnP) like tvh does by default. I don't see any other way to do it. Avoiding fe argument is not a right solution, because TVH must address the specific tuners (for example different DiseqC setup for DVB-S per tuner).

But the good thing is that you may override the reply from server in tvh - see "Tuner configuration" field - use 'DVBC-1,DVB-T2-2' for your setup (you should write string manually to the combobox field).

#7

Updated by Laurie Davis about 8 years ago

Yes, that works! Actually, a slight typo - it should be DVBC-1,DVBT2-2 (not DVB-T2-2) but I got the idea :)

Thanks for all your help.

#8

Updated by Jaroslav Kysela about 8 years ago

Sorry about this typo. You may discuss with the dvbviewer developer to return the correct tuner order for the PnP configuration.

#9

Updated by Anton Bungin almost 6 years ago

Jaroslav Kysela wrote:

Yes, the whole problem is that the spec does not handle the situation where the server uses multiple tuners with different types. The one way is to use the order from server (PnP) like tvh does by default. I don't see any other way to do it. Avoiding fe argument is not a right solution, because TVH must address the specific tuners (for example different DiseqC setup for DVB-S per tuner).

But the good thing is that you may override the reply from server in tvh - see "Tuner configuration" field - use 'DVBC-1,DVB-T2-2' for your setup (you should write string manually to the combobox field).

Hi!
Is there any way to solve the problem?
As it is said on DVBViewer site:
"That's just a questionable work-around. It must be considered that the RS handles request -> tuner assignnments dynamically. If you have two DVB-T tuners and the first one is occupied by a recording or another streaming client, the RS will automatically use the second one. This feature is spoiled by using the fe parameter unnecessarily. And it spoils similar features in other Sat>IP servers as well. If the RS has started a DVB-T recording, it will reject TVH as client, because it stubbornly insists on a particular tuner that is occupied."

https://www.dvbviewer.tv/forum/topic/58808-cannot-connect-to-rs-using-satip/

Plus
Where is ""Tuner configuration" field" to be overwritten in TVH 4.3.*?

#10

Updated by Jaroslav Kysela almost 6 years ago

Disable "FE supported" in the SAT>IP server configuration (input adapter tree - the root for the SAT>IP server - the "Tuner configuration" item is there also).

#11

Updated by Anton Bungin almost 6 years ago

Jaroslav Kysela wrote:

Disable "FE supported" in the SAT>IP server configuration (input adapter tree - the root for the SAT>IP server - the "Tuner configuration" item is there also).

Thanks a lot.
I did it in the root, but anyway get errors:
2019-01-07 14:20:14.586 mpegts: 192.168.1.139 in IPTV Automatic Network - tuning on IPTV #1
2019-01-07 14:20:14.586 iptv: 192.168.1.139 in IPTV Automatic Network - unsupported scheme [none]
2019-01-07 14:20:15.555 http: 192.168.1.139: HTTP/1.1 POST (3) /api/mpegts/input/network_list -- 400
2019-01-07 14:20:15.602 http: 192.168.1.139: HTTP/1.1 POST (3) /api/mpegts/input/network_list -- 400

Maybe I missed some options, when tuning TVH as a client of DVBViewer RS

#12

Updated by Jaroslav Kysela almost 6 years ago

IPTV errors are not related to SAT>IP at all.

#13

Updated by Anton Bungin almost 6 years ago

Jaroslav Kysela wrote:

IPTV errors are not related to SAT>IP at all.

Looked hrough the optionns.
Now it works.
But TVH always crushes DVBViewer RS

#14

Updated by Anton Bungin over 5 years ago

Another try to use TVH as a SAT>IP client of DVBViewer.
But now I don't have any streams at all.

My configs are attached.

Description.xml:

<root xmlns="urn:schemas-upnp-org:device-1-0" configId="0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<URLBase>http://192.168.1.139:8089&lt;/URLBase>
<device>
<UDN>uuid:6AB7B0E9-E4E1-4E9E-8A80-AD5E5EB9A987</UDN>
<friendlyName>DVBViewer Media Server (TVBUNG)</friendlyName>
<manufacturer>cmuv</manufacturer>
<manufacturerURL>http://www.dvbviewer.com/&lt;/manufacturerURL>
<modelDescription>DVBViewer Mediaserver</modelDescription>
<modelName>DVBViewer Mediaserver</modelName>
<modelNumber>2.0</modelNumber>
<modelURL>http://www.dvbviewer.com/&lt;/modelURL>
<serialNumber>0815</serialNumber>
<deviceType>urn:ses-com:device:SatIPServer:1</deviceType>
<presentationURL>http://192.168.1.139:8089&lt;/presentationURL>
<iconList>
<icon>
<mimetype>image/png</mimetype>
<height>120</height>
<width>120</width>
<depth>24</depth>
<url>/gfx/dvbviewer-120.png</url>
</icon>
<icon>
<mimetype>image/png</mimetype>
<height>48</height>
<width>48</width>
<depth>24</depth>
<url>/gfx/dvbviewer-48.png</url>
</icon>
<icon>
<mimetype>image/jpeg</mimetype>
<height>48</height>
<width>48</width>
<depth>24</depth>
<url>/gfx/dvbviewer-48.jpg</url>
</icon>
<icon>
<mimetype>image/jpeg</mimetype>
<height>120</height>
<width>120</width>
<depth>24</depth>
<url>/gfx/dvbviewer-120.jpg</url>
</icon>
</iconList>
<satip:X_SATIPCAP xmlns:satip="urn:ses-com:satip">DVBS2-4,DVBT-0,DVBT2-5,DVBC-4</satip:X_SATIPCAP>
<satip:X_SATIPM3U xmlns:satip="urn:ses-com:satip">/rtspchannels.m3u</satip:X_SATIPM3U>
</device>
</root>

TVH log:
2019-05-03 17:48:44.726 mpegts: 11385V in 5 - tuning on SAT>IP DVB-S Tuner #2 (192.168.1.139@UDP)
2019-05-03 17:48:44.726 subscription: 0514: "scan" subscribing to mux "11385V", weight: 2, adapter: "SAT>IP DVB-S Tuner #2 (192.168.1.139@UDP)", network: "5", service: "Raw PID Subscription"
2019-05-03 17:48:44.727 satip: rtp - cannot bind 192.168.1.139:554 [e=Cannot assign requested address]
2019-05-03 17:48:44.727 satip: rtp - cannot bind 192.168.1.139:554 [e=Cannot assign requested address]
2019-05-03 17:48:44.727 satip: rtp - cannot bind 192.168.1.139:554 [e=Cannot assign requested address]
2019-05-03 17:48:44.727 satip: rtp - cannot bind 192.168.1.139:554 [e=Cannot assign requested address]
2019-05-03 17:48:44.777 satip: rtp - cannot bind 192.168.1.139:554 [e=Cannot assign requested address]
2019-05-03 17:48:44.777 satip: rtp - cannot bind 192.168.1.139:554 [e=Cannot assign requested address]

#15

Updated by Flole Systems over 5 years ago

Bind address is wrong.

#16

Updated by Anton Bungin over 5 years ago

Flole Systems wrote:

Bind address is wrong.

In screenshots 192.168.1.139:554 is the right address in DVBViewer configuration

#17

Updated by Flole Systems over 5 years ago

Please read documentation about that parameter again, this is not the Sat-IP server IP. In this case you most likely want to leave it empty anyways.

#18

Updated by Anton Bungin over 5 years ago

Flole Systems wrote:

Please read documentation about that parameter again, this is not the Sat-IP server IP. In this case you most likely want to leave it empty anyways.

Thanks.
I wouldn't say that documentation is overwhelming:
"Local bind IP address : Bind to specific local IP address."

Moreover, the read-only part says, that "IP address: = 192.168.1.139"

Anyway, leaving the field blank solves the binding problem.
But all the time tuners try to scan I get something like this:
"mpegts: 10979V in 19 - scan no data, failed"

Am I right configuring networks, as listed above?

#19

Updated by Anton Bungin over 5 years ago

OK, TVH seems to be unborn to work as a SAT>IP client and cannot work with CIs https://tvheadend.org/boards/4/topics/37353
Welcome dammned Windoes

#20

Updated by Anton Bungin over 5 years ago

OK, TVH seems to be unborn to work as a SAT>IP client and cannot work with CIs https://tvheadend.org/boards/4/topics/37353
Welcome dammned Windows

#21

Updated by Flole Systems over 5 years ago

To me this looks like you're just messing around with parameters that you don't understand. Start over, understand what each parameter means and set it accordingly, then you can get it to work with almost every SAT-IP Server.

#22

Updated by Anton Bungin over 5 years ago

Flole Systems wrote:

To me this looks like you're just messing around with parameters that you don't understand. Start over, understand what each parameter means and set it accordingly, then you can get it to work with almost every SAT-IP Server.

For me the manuals are in a raw state, sorry

Also available in: Atom PDF