Feature request: add option for RTP unicast over TCP about vdr-plugin-satip HOT 12 CLOSED

@HellGL fyi the OctopusNet has the same problem but sadly no RTP/TCP support (not that I know)

from vdr-plugin-satip.

The specs don't support TCP and I hesitate adding such non-compliant features.

from vdr-plugin-satip.

This additional feature will improve the usefulness of the vdr-plugin-satip and will help many people to get rid of artifacts.
Do the specs specifically do not allow to do this?
If the implementation does not break anything that the specs require the plugin will still be compliant. I will just have additional features.

from vdr-plugin-satip.

Can you, please, verify the functionality of this PR: #24

from vdr-plugin-satip.

RTP/UDP is "broken" by design - that is why "every" sat>ip server supports also RTP/TCP (at least minisatip, Tvh and DVBViewer). For example at an Raspberry Pi you have nearly no chance to use VDR without errors due dropped udp packages (because the RPi has an shitty network stack). Also at normal hardware you can get these problems - mostly if you use more then one switch in the network.

from vdr-plugin-satip.

Well, I don't have any issues on my network with multiple switches or even with Android tablet over WiFi using RTP-over-UDP.

from vdr-plugin-satip.

@CvH: can you provide the friendly names (root/device/friendlyName in their discovery xml) of Tvheadend and DVBViewer, so I can add RTP-over-TCP quirks for them too?

from vdr-plugin-satip.

@rofafor
DVBViewer

<friendlyName>DVBViewer Media Server (HOSTNAME-of-SERVER)</friendlyName>
<manufacturer>cmuv</manufacturer>
<manufacturerURL>http://www.dvbviewer.com/</manufacturerURL>
<modelDescription>DVBViewer Mediaserver</modelDescription>
<modelName>DVBViewer Mediaserver</modelName>

%s%s is the Tvheadend server name - this could be freely changed in the settings

<friendlyName>%s%s</friendlyName>
<manufacturer>TVHeadend Team</manufacturer>
<manufacturerURL>http://tvheadend.org</manufacturerURL>
<modelDescription>TVHeadend %s</modelDescription>
<modelName>TVHeadend SAT>IP</modelName>

from vdr-plugin-satip.

Feature merged into master - although no support for TVHeadend.

from vdr-plugin-satip.

@rofafor any particular reason to not support Tvh ?

from vdr-plugin-satip.

The plugin is using friendlyName for detection and that field seems to be totally user configurable in Tvh. Ofcourse, you can provide me a PR with a more complete mechanism, but for today the friendlyName has been the only single field differentiating all the devices.

Ps.I guess one can configure Tvh to be shown as minisatip and everything should work.

from vdr-plugin-satip.

@rofafor tx for explenation

from vdr-plugin-satip.