SAT>IP

[Guest Diefenthal]

i had hope that two or three devs are interested , for one is this really much work

[Schimi]

I would definitely donate as soon the plugin is ready and works :-)

[Notfast]

@@Schimi - You should support now, and then voice your feelings about sat>IP.

 

If the Emby team should code more, they need time and money is time.

[e123enitan]

I will donate if the plugin is meant for the integration of dvbviewer into emby server,

has there been any interesting developers who can take on the project?

Has there being any feasibilty analysis on plug in by anyone todate?

 

Also for my understanding is this plugin intended to integrate any HTPC dvb software that have sat>ip into emby, or it is specific to dvbviewer only,

appreciate if anyone could help clarify this few questions

[Luke]

Not only are there discussions, but I would like to have it built-in like the HDHR support and not require a plugin. The challenge though for us is cost/benefit, because it would be a large and costly project for us.

[e123enitan]

Not only are there discussions, but I would like to have it built-in like the HDHR support and not require a plugin. The challenge though for us is cost/benefit, because it would be a large and costly project for us.

I am guessing the cost efforts would be subjective, won't be a bad idea if the topic is presented to the community explaining the benefits, especially to currents users of HTPC such as DVBViewer, TVHeadend, DVBLogic if they would like SAT>IP similar to HDHR and what contributions are needed in terms of manpower and costs etc, the benefits should not be perceived only from currently users point in mind, but to those that may be drawn to emby due to this plugin.  

 

Just to add I currently have 4 channels SAT>IP on HTPC LAN connecting to Emby/Kodi android & openelec on laptops, iphone all is working perfectly. 

 

Just my thoughts 

[Lee]

Not only are there discussions, but I would like to have it built-in like the HDHR support and not require a plugin. The challenge though for us is cost/benefit, because it would be a large and costly project for us.

 

Would be a definite sell point for emby in Europe i'd guess.. how to monetize it i'm not sure? maybe make it a premium/supporter only user item?

[Guest Diefenthal]

why only Europe ?

 

every Country that use DVB  can use Sat>Ip

 

https://www.dvb.org/news/worldwide

[pir8radio]

There is an emby plugin for TvHeadend, doesn't TvHeadend support SAT>IP?  Might help with some of you SAT>IP users that run linux.   I have not messed with TvHeadend server, so I do not  know much about it, just came to mind when reading around the net....  Pretty sure its for the linux users only.

Edited February 6, 2016 by pir8radio

[Schimi]

DVBlink and nextPVR support SAT>IP too...

 

but it would be very nice it would be a built-in support and we don´t need another Software.

[Guest Diefenthal]

had look into the file HdhomerunDiscovery.cs and Hdhomerunhost.cs

 

the deviceType should be  "urn:ses-com:device:SatIPServer:1"

 

so is it call in the device Description as exsample one of my three Devices 

 

<?xml 
version="1.0" ?>

- <root 
xmlns="urn:schemas-upnp-org:device-1-0" 
configId="1">


- <specVersion>


  <major>1</major>

  <minor>1</minor>
  </specVersion>

- <device>


  <deviceType>urn:ses-com:device:SatIPServer:1</deviceType>

  <friendlyName>OctopusNet</friendlyName>

  <manufacturer>Digital Devices GmbH</manufacturer>

  <manufacturerURL>http://www.digitaldevices.de</manufacturerURL>

  <modelDescription>OctopusNet</modelDescription>

  <modelName>OctopusNet</modelName>

  <modelNumber>1.0</modelNumber>

  <modelURL>http://www.digitaldevices.de/OctopusNet.html</modelURL>

  <serialNumber>2370</serialNumber>

  <UDN>uuid:dd848d00-26ec-11eb-8000-54847b001284</UDN>

- <iconList>


- <icon>


  <mimetype>image/png</mimetype>

  <width>120</width>

  <height>120</height>

  <depth>24</depth>

  <url>/icons/dd-120.png</url>
  </icon>

- <icon>


  <mimetype>image/jpeg</mimetype>

  <width>120</width>

  <height>120</height>

  <depth>24</depth>

  <url>/icons/dd-120.jpg</url>
  </icon>

- <icon>


  <mimetype>image/png</mimetype>

  <width>48</width>

  <height>48</height>

  <depth>24</depth>

  <url>/icons/dd-48.png</url>
  </icon>

- <icon>


  <mimetype>image/jpeg</mimetype>

  <width>48</width>

  <height>48</height>

  <depth>24</depth>

  <url>/icons/dd-48.jpg</url>
  </icon>
  </iconList>

  <presentationURL>/</presentationURL>

  <satip:X_SATIPCAP xmlns:satip="urn:ses-com:satip">DVBS2-2</satip:X_SATIPCAP>

  <satip:X_SATIPM3U xmlns:satip="urn:ses-com:satip">/channellist.lua?select=m3u</satip:X_SATIPM3U>
  </device>
  </root>

the next interessted field is <satip:X_SATIPCAP xmlns:satip="urn:ses-com:satip">DVBS2-2</satip:X_SATIPCAP>

 

that describe what for Broadcasttypes are Supported  and how many Frontends / Tuners are avaible

at time Supported Broadcasts are DVBS, DVBS2, DVBT, DVBT2, DVBC and DVBC2

 

the Exsample  let us know  that the Supported Broadcast Type is DVBS2  and had 2 Frontends /Tuners

 

the most Sat>Ip devices not use this field <satip:X_SATIPM3U xmlns:satip="urn:ses-com:satip">/channellist.lua?select=m3u</satip:X_SATIPM3U>

so it must be checked for availability

 

that is all for the discovery  the next is

 

for Tuning(RTSP) receiving Media(RTP) and Control (RTCP)

for an channel scan  is needed too some Parser for PAT PMT CAT BAT NIT SDT and later for the Guide Data EIT

and for this things had i nothing see in the emby code

 

 

 

 

 

 

 

 

Edited February 7, 2016 by Diefenthal

[Lee]

why only Europe ?

 

every Country that use DVB  can use Sat>Ip

 

https://www.dvb.org/news/worldwide

I didn't mean exclusively europe.. just the HDHomerun implementation is mainly a US thing. Obviously any sat>ip receiver would work. Seems to be most common in europe atm...

[Lee]

There is an emby plugin for TvHeadend, doesn't TvHeadend support SAT>IP?  Might help with some of you SAT>IP users that run linux.   I have not messed with TvHeadend server, so I do not  know much about it, just came to mind when reading around the net....  Pretty sure its for the linux users only.

 

Most of the Enigma2 satellitte receivers have sat>ip plugin capability too. (although there is a Vuplus plugin too)

[Guest Diefenthal]

I didn't mean exclusively europe.. just the HDHomerun implementation is mainly a US thing. Obviously any sat>ip receiver would work. Seems to be most common in europe atm...

not really,  i had helping out in some Projects

from new zealand and russia

both are not an part of europe

same here if you want my help, let it me know  (but it looks different here )

[Guest Diefenthal]

can i use the Emby DeviceDiscovery with an other searchterm as exsample "urn:ses-com:device:SatIPServer:1" ?

[Luke]

yes making that reusable was my plan

[Guest Diefenthal]

i had load the last source of emby and tried with vs 2015 community Edition

but it Looks like that there somethings more needed the Portable Lib as exsample so is it not possible to build it  for testing

 

or make i something wrong ?

[Luke]

i had load the last source of emby and tried with vs 2015 community Edition

but it Looks like that there somethings more needed the Portable Lib as exsample so is it not possible to build it  for testing

 

or make i something wrong ?

 

Not sure community version will work. I'll have to test. You can temporarily remove the portable project.

 

Fyi, we already search for all, shouldn't that be good enough?

            var values = new Dictionary<string, string>(StringComparer.OrdinalIgnoreCase);

            values["HOST"] = "239.255.255.250:1900";
            values["USER-AGENT"] = "UPnP/1.0 DLNADOC/1.50 Platinum/1.0.4.2";

            values["MAN"] = "\"ssdp:discover\"";

            // Search target
            values["ST"] = "ssdp:all";

            // Seconds to delay response
            values["MX"] = "3";

            // UDP is unreliable, so send 3 requests at a time (per Upnp spec, sec 1.1.2)
            SendDatagram("M-SEARCH * HTTP/1.1", values, _ssdpEndp, localIp, true, 2);

[Guest Diefenthal]

here is the updated Basic Sat>ip Discovery Sample  with an sample.log inside the Logs Folder

so can you look what they send

this sample can handle all SSDP Message Types Http, M-Search and Notify

and reacts  to them

 

i hope it helps a Little bit for step one of the implementation

[Luke]

here is the updated Basic Sat>ip Discovery Sample  with an sample.log inside the Logs Folder

so can you look what they send

this sample can handle all SSDP Message Types Http, M-Search and Notify

and reacts  to them

 

i hope it helps a Little bit for step one of the implementation

 

What are the changes?

[Guest Diefenthal]

it use the ssdp.Client class instead of MS Upnp control stack  wich is used in the satip rtsp sample

[Luke]

in the latest stable release, enable debug logging  under advanced, then restart the server.

 

then let me know if you see any messages in your log starting with "SAT IP found at ". I'm curious if we're at least seeing the devices. Thanks.

[Guest Diefenthal]

Hi Luke,

 

sadly is there nothing found i attach the logs so can you look over it

 

 

[Luke]

Hi Luke,

 

sadly is there nothing found i attach the logs so can you look over it

 

Under dlna you can also enable dlna debug logging. this will create a massive log but will contain all the messages received by all devices.

 

Also keep in mind Unicast support is not in this build. I've just turned that on in Dev.

[Guest Diefenthal]

Hi Luke there are some notify Messages

 

i had look fast over it and think there not all Servers found