VDR & DVBViewer Media Server

[Nayef]

hello

i have VDR and want add satip to /etc/vdr/conf.d/50-satip.conf 

i read this : https://github.com/rofafor/vdr-plugin-satip/blob/master/README

and add: 

[satip]
 

Quote

-d 12
-s 192.168.100.6:554|DVBS2-12|DVBViewer:0x08

but not working

 

my description.xml: 

Quote

 

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

<satip:X_SATIPM3U xmlns:satip="urn:ses-com:satip">/rtspchannels.m3u</satip:X_SATIPM3U>

 

 

what correct setup?

Edited yesterday at 03:29 AM by Nayef

[Griga]

Which is your DVBViewer Media Server version?

 

Does it work without the :0x08 quirk?

 

Make sure the RTSP port of your Media Server is 554. If another RTSP Server is running on your PC (e.g. the Windows Media Player as background RTSP Server), the DVBViewer Media Server may be forced to use 8554. You can see the RTSP port that is actually used on the Web Interface -> Status page.

 

[Nayef]

i have v3.3.1.12

tuner 1 to 8 = 13e

tuner 9 = 26e

tuner 10 to 12 = 7w

 

my setting now: 

Quote

[satip]
-d 12
-s 192.168.100.6:554|DVBS2-8:S13E|DVBViewer:0x08
-s 192.168.100.6:554|DVBS2-1:S26E|DVBViewer:0x08
-s 192.168.100.6:554|DVBS2-3:S7W|DVBViewer:0x08

but no connect server

[Griga]

vor 4 Stunden schrieb Griga:

Does it work without the :0x08 quirk?

 

Please answer.

 

vor 17 Minuten schrieb Nayef:

tuner 1 to 8 = 13e

tuner 9 = 26e

tuner 10 to 12 = 7w

 

Are the tuners connected to different dishes? Are you using channel groups in DVBViewer and the Media Server to tell them wich tuners must be used for channels from a certain orbital positions?

 

 

 

[Nayef]

4 hours ago, Griga said:

Does it work without the :0x08 quirk?

same issue without 

 

4 hours ago, Griga said:

Are the tuners connected to different dishes?

yes i have 3 tuners without Splitter/DiSEqC, Each tuner has its own independent satellite.

 

4 hours ago, Griga said:

Are you using channel groups in DVBViewer and the Media Server to tell them wich tuners must be used for channels from a certain orbital positions?

Yes, A: for 26e & B:7w & C for 13e

Edited 17 hours ago by Nayef

[Griga]

vor 1 Stunde schrieb Nayef:

yes i have 3 tuners without Splitter/DiSEqC, Each tuner has its own independent satellite (...) A: for 26e & B:7w & C for 13e

 

Unfortunately Sat>IP does not support such a setup. This complicates it considerably. The VDR plugin has no idea which tuners can receive which satellite position. There is nothing like "Channel Groups" in Sat>IP. Therefore the Media Server maps tune requests from the VDR to group A, because this is the default. So it should at least be possible to receive a channel from 26e. Did you try that?

 

However, you can bind channels to a specific frontend (tuner) of the Media Server by using the FE parameter in VDR. The following paragraph in the VDR plugin Readme refers to it:

 

Zitat

A channel can be assigned into a specific SAT>IP frontend by giving the
identifier number in RID field of a channels.conf entry:
FE = RID % 100
Valid range: 1 ... 99

 

The frontend numbers equal the tuner position in the Media Server device list, counted from the top. See Media Server Options (svcoptions.exe) -> Hardware. The topmost tuner has frontend number 1, the next number 2, and so on down to the bottom. So if a channel is configured for FE 1 in VDR, the Media Server will use the topmost tuner in the device list for it, provided it is free. Otherwise it will send an error code to the client.

 

This is the only way to select a specific tuner for a channel with Sat>IP.

 

For finding out what is going wrong you may want to have a look at the svcdebug.log (see DVBViewer configuration directory). There you can see if tune requests from VDR have arrived, and the Media Server response. You can also attach the zipped svcdebug.log here as file, so I can have a look at it.

 

[Nayef]

i try several option:

1- only one tuner:

Quote

-d 1 -s '192.168.100.6:554|DVBS2-1:S13E|DVBViewer'

 

or more one

set  /var/lib/vdr/sources.conf

 

Quote

S26E 1  Badr
S7W  2  Nilesat
S13E 3  Hotbird

/50-satip.conf :

Quote

-d 12 -s '192.168.100.6:554|DVBS2-8|Hotbird:S13E-3;192.168.100.6|DVBS2-1|Badrsat:S26E-1;192.168.100.6|DVBS2-3|Nilesat:S7W-2'

The problem is that it only sees one tuner. The server received 12 requests at once, but it only sees one device, as shown in my status section.

  (Digital Devices DVB-S/S2 Tuner 2 (5)-76%)

 

Log in vdr:

Quote

vdr[1284415]: [1284421] SATIP-ERROR: Connection timeout - retuning [device 0]
vdr[1284415]: [1284421] SATIP-ERROR: Detected invalid status code 454: rtsp://192.168.100.6/ [device 0]
vdr[1284415]: [1284421] SATIP-ERROR: Connect failed [device 0]
vdr[1284415]: [1284420] SATIP: Detected 1 RTP packet error [device 0]
vdr[1284415]: [1284421] SATIP-ERROR: Connection timeout - retuning [device 0]
vdr[1284415]: [1284421] SATIP-ERROR: Detected invalid status code 454: rtsp://192.168.100.6/ [device 0]
vdr[1284415]: [1284421] SATIP-ERROR: Connect failed [device 0]

 

or 

 

Quote

Mar 26 01:00:36 myast.ddns.net vdr[890756]: [890760] SATIP-ERROR: Detected invalid status code 454: rtsp://192.168.100.6/ [device 0]
Mar 26 01:00:36 myast.ddns.net vdr[890756]: [890760] SATIP-ERROR: Pid update failed - retuning [device 0]

 

Log in svcdebug & hardware: attach

 

 

svcdebug.zip hardware.xml

[Griga]

vor 1 Stunde schrieb Nayef:

Log in svcdebug & hardware: attach

 

For inspecting the Media Server tuner configuration I need the file svchardware.xml from the config sub-directory of the DVBViewer configuration folder. hardware.xml is for DVBViewer.

 

vor 1 Stunde schrieb Nayef:

The problem is that it only sees one tuner. The server received 12 requests at once, but it only sees one device, as shown in my status section.

  (Digital Devices DVB-S/S2 Tuner 2 (5)-76%)

 

I guess it is the first tuner in your device list that is configured for channel group A, right? As already said:

 

vor 13 Stunden schrieb Griga:

There is nothing like "Channel Groups" in Sat>IP. Therefore the Media Server maps tune requests from the VDR to group A, because this is the default.

 

The only way to override this is to let VDR use the frontend (fe) parameter, that selects a specific tuner in your device list. In your svcdebug.log I see two VDR tune requests that used fe=6, for example this one

 

Zitat

26.03.26 01:34:32.130 SETUP                200              src=1&fe=6&freq=11488&sr=27500&msys=dvbs2&mtype=qpsk&pol=h&fec=78&ro=0.35&pids=0,21

 

that selected the 6th tuner from the top, which is TBS 6909x DVBS/S2 Tuner 5 (9).

 

It is very difficult to address satellite positions with Sat>IP, if you are not using DiSEqC (which is the src parameter, src=1 is PosA/OptA).

 

Unfortunately I cannot help you with VDR configuration. I have never used it.