- SAT>IP Client
- SatPI
- Help
- Donate
- Contact
- Tested Programs
- Tested Hardware
- Build
- Usage
- Saved searches
- Use saved searches to filter your results more quickly
- nfedera/catalinii-minisatip
- Name already in use
- Sign In Required
- Launching GitHub Desktop
- Launching GitHub Desktop
- Launching Xcode
- Launching Visual Studio Code
- Latest commit
- Git stats
- Files
- README.md
- About
SAT>IP Client
SAT>IP (or Sat-IP) specifies an IP-based client–server communication protocol for a TV gateway. SAT>IP server connects to one or more DVB broadcast sources and provides access to channels for multiple clients over HTTP or RTSP protocols.
In this chain, Astra acts as an SAT>IP client. It can receive DVB streams over SAT>IP protocol and be used as a hub for TV Channels from different sources, for their further processing and streaming to clients.
Benefits of using SAT>IP receivers
The most important advantage is the possibility of separating the reception and processing of channels. Usually Sat-dishes and terrestrial antennas are located on the roof which requires dedicated cabling to distribute the satellite signal to DVB Server (Linux PC with Astra software) which is located in the server room. This can be costly, especially in large buildings or complexes. And with the SAT>IP solutions, on the other hand, we may use existing network infrastructure to distribute the signal (or reduce cabling to a single Ethernet cable) and this can significantly reduce installation costs. Since Astra can handle large amounts of traffic without performance degradation, it is worth an option to use.
Secondly, we can extend the variety of hardware with what you may receive a DVB signal. It is SAT>IP server hardware like: Digital Devices Octopus NET , HDHomeRun, Telestar R1, and many other devices, including low-cost options, which support SAT>IP Standard.
What is important to mention, is that with the Minisatip server software, we also may use PCIe DVB cards and/or USB sticks (tuners) as SAT>IP Adapters at Astra Cesbo. For more details on how to use the Minisatip server look at our article and on developer GitHub .
Configuration
To use the SAT>IP protocol, you need to create New Adapter in the Astra Web Interface:
SatPI
An SAT>IP server for linux, suitable for running on an Raspberry Pi, VU+, GigaBlue or any other linux box.
- DVB-S(2), DVB-T(2) and DVB-C
- Web Interface for monitoring and configuring various things (http port 8875)
- http://ip.of.your.box:8875
- FILE input, reading from an TS File
- STREAMER input, reading from an multicast/unicast input
- CHILDPIPE input, reading from an PIPE input for example wget and childpipe-hdhomerun-example.sh in combination with mapping.m3u
- The Description xml can be found like:
- http://ip.of.your.box:8875/desc.xml
- http://ip.of.your.box:8875/satPI.xml
- https://github.com/Barracuda09/SATPI/wiki
Help
Help in any way is appreciated, just send me an email with anything you can contribute to the project, like:
- coding
- web design
- ideas / feature requests
- test reports
- spread the word!
- donate
Donate
If you like and use SatPI then please consider making a donation, to support my effort in developing SatPI.
Many thanks to all who donated already.Please find the Sponsor button here:
Contact
If you like to contact me, you can do so by sending an email to:
Tested Programs
- Tvheadend: this is a TV streaming server see: https://tvheadend.org/
- DVBviewer Lite Edition. see http://www.satip.info/products
- Elgato Sat>IP App for Android
- VDR
Tested Hardware
- Raspberry Pi
- BeagleBone Black
- Orange Pi One with armbian
- Sundtek DVB-C/T/T2
- Sundtek SkyTV Ultimate Dual (2x DVB-S/S2/S2X)
- Schwaiger DSR41IP — Thanks to Axel Hartmann for kindly suppling this to me
- DIGITALBOX IMPERIAL HD 6i — Thanks to APfutura for kindly suppling this to me
- Anysee-S2(LP) STV090x Multistandard
- HMP-Combo DVB-T2/C
- VU+ Zero 4K with DVB-S2X Tuner
- VU+ Uno 4K with DVB-C FBC Tuner
- GigaBlue UHD Quad 4K with DVB-S2X FBC Tuner — Thanks to Impex-Sat GmbH & Co. KG for kindly suppling this to me
- GigaBlue Ultra SCR-LNB / 24 SCR — 2 Legacy UHD 4K LNB — Thanks to Impex-Sat GmbH & Co. KG for kindly suppling this to me
- DUR-line UK 124 — Unicable LNB
Build
- Always Update the Web folder as well, as it may contain new features
- To build SatPI just run these commands: git clone git://github.com/Barracuda09/satpi.git
cd satpi/
git branch -f devtmp 9c4b71d ->will make a branch devtmp of commit 9c4b71d
git checkout devtmp ->this will checkout devtmp
Usage
./satpi (!!Note you should have the appropriate privilege to open tcp/udp port 554!!)
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
minisatip is an SATIP server for linux using local DVB-S2, DVB-S or DVB-T cards
nfedera/catalinii-minisatip
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Sign In Required
Please sign in to use Codespaces.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching Xcode
If nothing happens, download Xcode and try again.
Launching Visual Studio Code
Your codespace will open once ready.
There was a problem preparing your codespace, please try again.
Latest commit
Git stats
Files
Failed to load latest commit information.
README.md
Minisatip is a multi-threaded satip server version 1.2 that runs under Linux and it was tested with DVB-S, DVB-S2, DVB-T, DVB-T2, DVB-C, DVB-C2, ATSC and ISDB-T cards.
The protocol specification can be found at: http://satip.info/sites/satip/files/resource/satip_specification_version_1_2_2.pdf It is very lightweight (designed for embedded systems with memory and processing constrains), does not need any additional libraries for basic functionality and can be used by existing satip clients like: Tvheadend, DVBViewer, vdr, VideoLAN or Android/iOS applications. Minisatip can act as a satip client as well in order to connect to satip servers from different networks.
The application is designed to stream the requested data to multiple clients (even with one dvb card) in the same time while opening different pids.
It is tested on x86_64, x86, ARM and MIPS platforms and it requires DVBAPI 5. Supported protocols are RTSP (both tcp and udp), HTTP (port 8080) and SSDP (as specified in the SAT>IP documentation). On top of that, it supports dvbapi protocol implemented by oscam (requires dvbcsa library) to decrypt channels using an official subscription and support dvbca protocol (requires dvben50221 library) for dvb cards with CA hardware. In order to enable/disable features, please edit the Makefile.
The application shows also a status page by default at the address: http://IP:8080 The latest binaries for embedded platforms: https://minisatip.org/forum/viewtopic.php?f=5&t=371
In order to speed up the investigation of an issue, please provide the full log and a link to the application that is not working.
minisatip version 0.5.44, compiled with s2api version: 050A
./minisatip [-[fgltz]] [-a x:y:z] [-b X:Y] [-c X] [-d A:C-U ] [-D device_id] [-e X-Y,Z] [-i prio] [-[uj] A1:S1-F1[-PIN]] [-m mac][-o oscam_host:dvbapi_port] [-p public_host] [-r remote_rtp_host] [-R document_root] [-s [DELSYS:]host[:port] [-u A1:S1-F1[-PIN]] [-w http_server[:port]] [-x http_port] [-X xml_path] [-y rtsp_port]
- -a x:y:z simulate x DVB-S2, y DVB-T2 and z DVB-C adapters on this box (0 means auto-detect)
- eg: -a 1:2:3
- it will report 1 dvb-s2 device, 2 dvb-t2 devices and 3 dvb-c devices
- eg: -b 18800:18988
- eg: -c 2048 (does not allow minisatip to send more than 2048KB/s to all remote servers)
- The first argument is the adapter number, second is the number of committed packets to send to a Diseqc 1.0 switch, third the number of uncommitted commands to sent to a Diseqc 1.1 switch The higher number between the committed and uncommitted will be sent first.
- eg: -d 0:1-0 (which is the default for each adapter).
- note: * as adapter means apply to all adapters
- note: * before committed number enables fast-switch (only voltage/tone)
- All timing values are in ms, default adapter values are: 15-54-15-15-15-0
- note: * as adapter means apply to all adapters
- eg: -D 4
- eg: —delsys 1:dvbt,2:dvbs
- specifies adapter 1 as a DVBT device, adapter 2 as DVB-S, which overrides the system detection of the adapter
- eg: —dmx-source 0:1 — enables DMX_SET_SOURCE ioctl call with parameter 1 for adapter 0
- eg: -e 0-2,5,7 (no spaces between parameters)
- keep in mind that the first adapters are the local ones starting with 0 after that are the satip adapters if you have 3 local dvb cards 0-2 will be the local adapters, 3,4, . will be the satip servers specified with argument -s
- eg: -l -l -l
- eg: -m 001122334455
- eg: -n vlan4:2
- eg: -o 192.168.9.9:9000 192.168.9.9 is the host where oscam is running and 9000 is the port configured in dvbapi section in oscam.conf
- eg: -p http://192.168.2.3:8080/playlist
- this will add X_SATIPM3U tag into the satip description xml
- eg: -r 192.168.7.9
- DELSYS — can be one of: dvbs, dvbs2, dvbt, dvbt2, dvbc, dvbc2, isdbt, atsc, dvbcb ( — DVBC_ANNEX_B ) [default: dvbs2] host — the server of the satip server port — rtsp port for the satip server [default: 554] eg: -s 192.168.1.2 -s dvbt:192.168.1.3:554 -s dvbc:192.168.1.4
- specifies 1 dvbs2 (and dvbs)satip server with address 192.168.1.2:554
- specifies 1 dvbt satip server with address 192.168.1.3:554
- specifies 1 dvbc satip server with address 192.168.1.4:554
- Allows specifying bonded adapters (multiple adapters connected with a splitter to the same LNB) Only one adapter needs to be master all others needs to have this parameter specified eg: -S 1-2
- specifies adapter 1 to 2 as slave, in this case adapter 0 can be the master that controls the LNB
- the slave adapter will not control the LNB polarity or band, but it will just change the internal frequency to tune to a different transponder
- in this way the master will be responsible for changing the LNB polarity and band
- The format is: A1:S1-F1[-PIN][,A2:S2-F2[-PIN][. ]] eg: 2:0-1284[-1111]
- When * character is used before frequency, force 13V only for setup
- eg: -w 192.168.1.1:8080
- eg: -x 9090
- by default desc.xml is provided by minisatip without needing an additional file, however satip.xml is included if it needs to be customized
- eg: -y 5544
- changing this to a port > 1024 removes the requirement for minisatip to run as root
Configures minisatip for the current system (use ./configure —help for options)
To cross compile, use something like (static compilation):
- ./configure —host=mips CC=/usr/src/./configure —host=mips —enable-static CC=/usr/src/openwrt/attitude_adjustment/staging_dir/toolchain-mips_r2_gcc-4.6-linaro_uClibc-0.9.33.2/bin/mips-openwrt-linux-gcc
To compiles the application
To add custom compilation flags you can use:
- In order to listen to a radio after minisatip is started open the following URL in your favourite media player:
- on Hotbird 13E: «http://MINISATIP_HOST:8080/?msys=dvbs&freq=11623&pol=v&sr=27500&pids=0,10750,254»
- Astra 19.2E: «http://MINISATIP_HOST:8080/?msys=dvbs&freq=12266&pol=h&sr=27500&pids=0,851»
- Astra 19.2E, Kika HD: «rtsp://MINISATIP_HOST:554/?src=1&freq=11347&pol=v&ro=0.35&msys=dvbs2&mtype=8psk&plts=on&sr=22000&fec=23&pids=0,17,18,6600,6610,6620,6630»
About
minisatip is an SATIP server for linux using local DVB-S2, DVB-S or DVB-T cards