Re: [vdr] Sat>IP-plugin: how to configure 2 DD Octopus NETs with different satellites

[fnu]

Hi,

I remember that Rolf always does suggest to use "OctopusNet" or "minisatip"
as device name.

So your definition is recommended to look like this:

--server=192.168.1.21|DVBS2-4|OctopusNet1;192.168.1.20|DVBS2-2,DVBT2-2|Octop
usNet2

The other stuff, hmm, I don't know, as the plugin follows quite straight the
SAT>IP specifications. Your add-on is maybe the point to discuss with the
original author Rolf.

Regards
fnu

-Ursprüngliche Nachricht-
Von: Patrick Boettcher [mailto:patrick.boettc...@posteo.de] 
Gesendet: Montag, 18. Juli 2016 17:43
An: fnu 
Cc: 'VDR Mailing List' 
Betreff: Re: [vdr] Sat>IP-plugin: how to configure 2 DD Octopus NETs with
different satellites

Hi fnu,

Thank you for your answer.

On Mon, 18 Jul 2016 10:29:58 +0200
"fnu"  wrote:

> Dear Patrick,
> 
> changes in "sources.conf" are IIRC only necessary if you have a DiSEqC 
> configuration controlled by VDR. But using a/the generic sources.conf 
> doesn't harm VDR operation, I guess most users do have one without 
> DiSEqC.

That seems to be true. Before looking at the code of the satip-plugin I
thought that I could limit magically the created (virtual) satipDevices to
the Sources assigned to them via the diseqc.conf.

> You may use a workaround by using CAID field for specific adapter:
> 
> https://www.linuxtv.org/vdrwiki/index.php/Syntax_of_channels.conf#CA_-
> _Conditional_access

Yeah, no, I don't like this.
 
> But I do not now if it is possible to cover more than 4 devices and no 
> good idea how to tie a SAT>IP device always to the same number.

As said above, I dug into the code and saw that nothing can be done with
standard vdr-config-files. Neither diseqc.conf nor sources.conf can help.

However, I added some code and now it works as I wanted it to work.

I did this by adding a Source-member to the satipFrontend created by
satipServer and in satipFrontend::Assign() I additionally check whether the
requested source can be delivered by this frontend.

In my environment, where I have one VDR which will use all satip-devices,
this is exactly what I need.

Now, how to get that correctly done?

Automatic detection? I haven't seen any option on the Octopus-device that
would help the satip-plugin to identify automatically the source/input when
it does the discovery.

So, I'd opt for the command-line-parameter-option: I'd add an additional
parameter to the plugin which will assign the correct source to the
satipFrontend. Which would only work if the -s-option is given.
Maybe it could be even part of the -s-option.. Let's try:

  --server=192.168.1.21|DVBS2-4|Octo1;192.168.1.20|DVBS2-2,DVBT2-2|Octo2

becomes

  --server=192.168.1.21|DVBS2-4|Octo1|S19.2E,S19.2E,S19.2E,S19.2E; \
192.168.1.20|DVBS2-2,DVBT2-2|Octo2|S28.2E,S28.2E,T,T

Looks good to me. I'll try that. 

This will surely work, however, right now, the satip-plugin does not use the
fe=-parameter the RTSP-URL for that. So even with this syntax, it won't be
possible to mix different satellites on _one_ Octopus NET.

Like '[..]Octo2|S28.2E,S19.2E,S28.2E,S19.2E' wouldn't work without changing
the URL-creation-method. It even looked like that the URL is created before
the satipFrontend is chosen. That would have to be changed.

best regards,
--
Patrick Boettcher


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Sat>IP-plugin: how to configure 2 DD Octopus NETs with different satellites

[Patrick Boettcher]

Hi fnu,

Thank you for your answer.

On Mon, 18 Jul 2016 10:29:58 +0200
"fnu"  wrote:

> Dear Patrick,
> 
> changes in "sources.conf" are IIRC only necessary if you have a
> DiSEqC configuration controlled by VDR. But using a/the generic
> sources.conf doesn't harm VDR operation, I guess most users do have
> one without DiSEqC.

That seems to be true. Before looking at the code of the satip-plugin I
thought that I could limit magically the created (virtual)
satipDevices to the Sources assigned to them via the diseqc.conf.

> You may use a workaround by using CAID field for specific adapter:
> 
> https://www.linuxtv.org/vdrwiki/index.php/Syntax_of_channels.conf#CA_-_Conditional_access

Yeah, no, I don't like this.
 
> But I do not now if it is possible to cover more than 4 devices and
> no good idea how to tie a SAT>IP device always to the same number.

As said above, I dug into the code and saw that nothing can be done with
standard vdr-config-files. Neither diseqc.conf nor sources.conf can
help.

However, I added some code and now it works as I wanted it to work.

I did this by adding a Source-member to the satipFrontend created by
satipServer and in satipFrontend::Assign() I additionally check whether
the requested source can be delivered by this frontend.

In my environment, where I have one VDR which will use all
satip-devices, this is exactly what I need.

Now, how to get that correctly done?

Automatic detection? I haven't seen any option on the Octopus-device
that would help the satip-plugin to identify automatically the
source/input when it does the discovery.

So, I'd opt for the command-line-parameter-option: I'd add an
additional parameter to the plugin which will assign the correct source
to the satipFrontend. Which would only work if the -s-option is given.
Maybe it could be even part of the -s-option.. Let's try:

  --server=192.168.1.21|DVBS2-4|Octo1;192.168.1.20|DVBS2-2,DVBT2-2|Octo2

becomes

  --server=192.168.1.21|DVBS2-4|Octo1|S19.2E,S19.2E,S19.2E,S19.2E; \
192.168.1.20|DVBS2-2,DVBT2-2|Octo2|S28.2E,S28.2E,T,T

Looks good to me. I'll try that. 

This will surely work, however, right now, the satip-plugin does not
use the fe=-parameter the RTSP-URL for that. So even with this syntax,
it won't be possible to mix different satellites on _one_ Octopus NET.

Like '[..]Octo2|S28.2E,S19.2E,S28.2E,S19.2E' wouldn't work without
changing the URL-creation-method. It even looked like that the URL is
created before the satipFrontend is chosen. That would have to be
changed.

best regards,
-- 
Patrick Boettcher

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] SatIP>plugin: how to configure 2 DD Octopus NETs with different satellites

[fnu]

Dear Patrick,

changes in "sources.conf" are IIRC only necessary if you have a DiSEqC 
configuration controlled by VDR. But using a/the generic sources.conf doesn't 
harm VDR operation, I guess most users do have one without DiSEqC. And well, 
"diseqc.conf" does IMHO explain by itself it's function.

With SAT>IP you don't use DiSEqC and it is from my understanding not foreseen 
to distinguish within the SAT>IP clients configuration between different 
orbital positions. SAT>IP specs do cover several positions but managed by the 
SAT>IP server. In your case one Octopus Net mainboard holding all of your flex 
modules and VDR is asking for the different positions by using the different 
channel.conf entries.

You may use a workaround by using CAID field for specific adapter:

https://www.linuxtv.org/vdrwiki/index.php/Syntax_of_channels.conf#CA_-_Conditional_access

But I do not now if it is possible to cover more than 4 devices and no good 
idea how to tie a SAT>IP device always to the same number.

Regards
fnu

-Ursprüngliche Nachricht-
Von: vdr [mailto:vdr-boun...@linuxtv.org] Im Auftrag von Patrick Boettcher
Gesendet: Sonntag, 17. Juli 2016 15:36
An: VDR Mailing List 
Betreff: [vdr] SatIP>plugin: how to configure 2 DD Octopus NETs with different 
satellites

Hi,

I have 2 DD Octopus NET devices. One is a 2x DVB-S(2) + 2x DVB-T(2) (let's call 
it AA) and the other one is 4x DVB-S(2) (BB).

AA's satellite orientation is Astra 28.2, BB's one is Astra 19.2.

How can I associate AA's or BB's inputs in VDR's configuration so that it uses 

  1) the right input for the right source

  2) the maximum number of devices in parallel for recording,
 epg-scanning etc.

conf.d/50-satip.conf contains 

  --devices=8
  --server=192.168.1.21|DVBS2-4|Octo1;192.168.1.20|DVBS2-2,DVBT2-2|Octo2


I found discussions where they say that in sources.conf one needs to assigned 
device numbers, so I tried:

  S19.2E 1 Astra 1KR/1L/1M/2C
  S19.2E 2 Astra 1KR/1L/1M/2C
  S19.2E 3 Astra 1KR/1L/1M/2C
  S19.2E 4 Astra 1KR/1L/1M/2C
  S28.2E 5 Astra 1N/2A/2F
  S28.2E 6 Astra 1N/2A/2F

This isn't working, it seems that even for S28.2 channels it selects the 
S19.2-devices.

Then I changed the diseqc.conf to

  1 2 3 4:
  S19.2E  11700 V  9750  t v W15 [E0 10 38 F0] W15 A W15 t
  S19.2E  9 V 10600  t v W15 [E0 10 38 F1] W15 A W15 T
  S19.2E  11700 H  9750  t V W15 [E0 10 38 F2] W15 A W15 t
  S19.2E  9 H 10600  t V W15 [E0 10 38 F3] W15 A W15 T

  5 6:
  S28.2E  11700 V  9750  t v W15 [E0 10 38 F4] W15 B W15 t
  S28.2E  9 V 10600  t v W15 [E0 10 38 F5] W15 B W15 T
  S28.2E  11700 H  9750  t V W15 [E0 10 38 F6] W15 B W15 t
  S28.2E  9 H 10600  t V W15 [E0 10 38 F7] W15 B W15 T

Didn't help.

Is there anything I can do? 

Thanks in advance for any help.

Best regards,
--
Patrick.

___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr