Hi,
wäre es eigentlich möglich die 920 als SAT>IP Server zu nutzen?
2xFBC und 16 Demods würden rocken
Hi,
wäre es eigentlich möglich die 920 als SAT>IP Server zu nutzen?
2xFBC und 16 Demods würden rocken
minisatip
Compiliert babe ich es schon vor einiger Zeit, aber noch nicht weiter getestet.
[12:10 root@dm900 ~] > minisatip --help
minisatip version 0.7.15, compiled with s2api version: 050A
[02/05 12:26:53.901 main]: Built with dvbcsa
[02/05 12:26:53.901 main]: Built with CI
[02/05 12:26:53.901 main]: Built with dvbapi
[02/05 12:26:53.901 main]: Built with AES (OpenSSL)
[02/05 12:26:53.901 main]: Built with tables processing
[02/05 12:26:53.902 main]: Built with pmt processing
[02/05 12:26:53.902 main]: Built with satip client
[02/05 12:26:53.902 main]: Built with linux dvb client
[02/05 12:26:53.902 main]: Built with backtrace
[02/05 12:26:53.902 main]: Built without netceiver
./minisatip [-[fgtzE]] [-a x:y:z] [-b X:Y] [-B X] [-H X:Y] [-d A:C-U ] [-D device_id] [-e X-Y,Z] [-i prio]
[-[uj] A1:S1-F1[-PIN]] [-m mac] [-P port] [-l module1[,module2]] [-v module1[,module2]][-o oscam_host:dvbapi_port] [-p public_host] [-r remote_rtp_host] [-R document_root] [-s [DELSYS:]host[:port] [-u A1:S1-F1[-PIN]] [-L A1:low-high-switch] [-w http_server[:port]]
[-x http_port] [-X xml_path] [-y rtsp_port]
Help
-------
* -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
* -b --buffers X:Y : set the app adapter buffer to X Bytes (default: 72192) and set the kernel DVB buffer to Y Bytes (default: 5775360) - both multiple of 188
* eg: -b 18800:18988
* -B X : set the app socket write buffer to X KB.
* eg: -B 10000 - to set the socket buffer to 10MB
* -2 --tcp-max-pack X : set the TCP data chunk size in MPEG-TS packets (188 bytes), default value is 42
* -d --diseqc ADAPTER1:COMMITTED1-UNCOMMITTED1[,ADAPTER2:COMMITTED2-UNCOMMITTED2[,...]
* 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)
* -q --diseqc-timing ADAPTER1:BEFORE_CMD1-AFTER_CMD1-AFTER_REPEATED_CMD1-AFTER_SWITCH1-AFTER_BURST1-AFTER_TONE1[,...]
* All timing values are in ms, default adapter values are: 15-54-15-15-15-0
- note: * as adapter means apply to all adapters
* -D --device-id DVC_ID: specify the device id (in case there are multiple SAT>IP servers in the network)
* eg: -D 4
* -0 --diseqc-multi ADAPTER1:DISEQC_POSITION[,...]
* Send diseqc to selected position before other position is set.
- note: * as adapter means apply to all adapters
* -E Allows encrypted stream to be sent to the client even if the decrypting is unsuccessful
* -Y --delsys ADAPTER1:DELIVERY_SYSTEM1[,ADAPTER2:DELIVERY_SYSTEM2[,..]] - specify the delivery system of the adapters
* 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
* --dmx-source ADAPTER1:FRONTENDX - specifies the frontend number specified as argument for DMX_SET_SOURCE
* eg: --dmx-source 0:1 - enables DMX_SET_SOURCE ioctl call with parameter 1 for adapter 0
* -e --enable-adapters list_of_enabled adapters: enable only specified adapters
* 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
* -f foreground, otherwise run in background
* -F --logfile log_file, output the debug/log information to log_file when running in background (option -f not used), default /tmp/minisatip.log
* -g use syslog instead stdout for logging, multiple -g - print to stderr as well
* -H --threshold X:Y : set the write time threshold to X (UDP) / Y (TCP) milliseconds.
* eg: -H 5:50 - set thresholds to 5ms (UDP) and 50ms (TCP)
* -i --priority prio: set the DVR thread priority to prio
* -l specifies the modules comma separated that will have increased verbosity,
logging to stdout in foreground mode or in /tmp/minisatip.log when a daemon
Possible modules: general,http,socketworks,stream,adapter,satipc,pmt,tables,dvbapi,lock,netceiver,ca,axe,socket,utils,dmx,ssdp,dvb
* eg: -l http,pmt
* -v specifies the modules comma separated that will have increased debug level (more verbose than -l),
* eg: -d http,pmt
* -L --lnb specifies the adapter and LNB parameters (low, high and switch frequency)
* eg: -L *:9750-10600-11700 - sets all the adapters to use Universal LNB parameters (default)
* eg: -L *:10750-10750-10750 - sets the parameters for Sky NZ LNB using 10750 Mhz
* eg: -L 0:10750-10750-10750,1:9750-10600-11700 - adapter 0 has a SKY NZ LNB, adapter 1 has an Universal LNB
* -m xx: simulate xx as local mac address, generates UUID based on mac
* eg: -m 001122334455
* -M multiplies the strength and snr of the DVB adapter with the specified values
* If the snr or the strength multipliers are set to 0, minisatip will override the value received from the adapter and will report always full signal 100%
* eg: -M 4-6:1.2-1.3 - multiplies the strength with 1.2 and the snr with 1.3 for adapter 4, 5 and 6
* eg: -M *:1.5-1.6 - multiplies the strength with 1.5 and the snr with 1.6 for all adapters
* -N --disable-dvb disable DVB adapter detection
* -Z --adapter-timeout ADAPTER1,ADAPTER2-ADAPTER4[,..]:TIMEOUT - specify the timeout for the adapters (0 enabled infinite timeout)
eg: --adapter-timeout 1-2:30
- sets the timeouts for adapter 1 and 2 to 30 seconds
--adapter-timeout *:0
- turns off power management for all adapters (recommended instead of --adapter-timeout 0-32:0)
- required for some Unicable LNBs
* -o --dvbapi host:port - specify the hostname and port for the dvbapi server (oscam). Port 9000 is set by default (if not specified)
* 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: -o /tmp/camd.socket
/tmp/camd.socket is the local socket that can be used
* -p url: specify playlist url using X_SATIPM3U header
* eg: -p http://192.168.2.3:8080/playlist
- this will add X_SATIPM3U tag into the satip description xml
* -P port: use port number to listen for UDP socket in the RTP communication. port + 1000 will be used to listen by the sat>ip client (option -s)
* eg: -P 5500 (default): will use for the sat>ip server 5500 + 2*A and 5500 + 2*A + 1, where A is the adapter number.
6500 + 2*A and 6500 + 2*A + 1 - will be used by the sat>ip client
* -r --remote-rtp remote_rtp_host: send the rtp stream to remote_rtp_host instead of the ip the connection comes from
* eg: -r 192.168.7.9
* -R --document-root directory: document root for the minisatip web page and images
* -s --satip-servers [DELSYS:][FE_ID@][source_ip/]host[:port] - specify the remote satip host and port with delivery system DELSYS, it is possible to use multiple -s
* 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]
FE_ID - will be determined automatically
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
eg: -s dvbt:2@192.168.1.100/192.168.1.2:555
- specifies 1 dvbt adapter to satip server with address 192.168.1.2, port 555. The client will use fe=2 (indicating adapter 2 on the server) and will connect from IP address 192.168.1.100
address 192.168.1.100 needs to be assigned to an interface on the server running minisatip.
This feature is useful for AVM FRITZ!WLAN Repeater
* --satip-xml <URL> Use the xml retrieved from a satip server to configure satip adapters
eg: --satip-xml http://localhost:8080/desc.xml
* -O --satip-tcp Use RTSP over TCP instead of UDP for data transport
* -S --slave ADAPTER1,ADAPTER2-ADAPTER4[,..]:MASTER - specify slave adapters
* Allows specifying bonded adapters (multiple adapters connected with a splitter to the same LNB)
* This feature is used by FBC receivers and AXE to specify the source input of the adapter
Only one adapter needs to be master all others needs to have this parameter specified
eg: -S 1-2:0
- specifies adapter 1 to 2 as slave, in this case adapter 0 is 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
- if there is no adapter using this link, the slave will use master adapters frontend to change the LNB polarity and band
eg: -S 2-7:0 (default for DVB-S2 FBC), adapter 0 and 1 are masters, 2-7 slave and linked to input 0 (A)
- all 8 adapters use physical input A to tune
eg: -S 2-4:0,5-7:1
- adapters 2,3,4 use physical input A to tune, while 1,5,6,7 uses input B to tune, adapter 0 and 1 are masters
* -t --cleanpsi clean the PSI from all CA information, the client will see the channel as clear if decrypted successfully
* -T --threads: enables/disable multiple threads (reduces memory consumptions) (default: ENABLED)
* -u --unicable unicable_string: defines the unicable adapters (A) and their slot (S), frequency (F) and optionally the PIN for the switch:
* 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
* -j --jess jess_string - same format as -u
* -w --http-host http_server[:port]: specify the host and the port (if not 80) where the xml file can be downloaded from [default: default_local_ip_address:8080]
* eg: -w 192.168.1.1:8080
* -x --http-port port: port for listening on http [default: 8080]
* eg: -x 9090
* -X --xml PATH: the path to the xml that is provided as part of the satip protocol
* by default desc.xml is provided by minisatip without needing an additional file,
however satip.xml is included if it needs to be customized
* -y --rtsp-port rtsp_port: port for listening for rtsp requests [default: 554]
* eg: -y 5544
- changing this to a port > 1024 removes the requirement for minisatip to run as root
* -1 --demux-dev [1|2|3]: the protocol used to get the data from demux
* 0 - use dvrX device
* 1 - use demuxX device
* 2 - use dvrX device and additionally capture PSI data from demuxX device
Alles anzeigen
Starten geht. mehr habe ich aber noch nicht gemacht.
[12:49 root@dm900 ~] > minisatip -e 0-7 -f -y 5544
[02/05 12:49:19.292 main]: Initializing with 8 devices
gruß pclin
Ich habe gerade noch die aktuelle Version compiliert.
./configure --prefix=/usr --build=arm-oe-linux-gnueabi --host=arm-oe-linux-gnueabi --with-pic --with-gnu-ld --enable-enigma
und getestet mit VLC in LinuxMint (siehe Screenshot)
# Welcome to Minisatip
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
Contact
-------
Please use https://minisatip.org/forum/ for any questions.
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.
If you like minisatip and you want to support the development of the project please make a donation:
https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=7UWQ7FXSABUH8&item_name=minisatip¤cy_code=EUR&bn=PP-DonationsBF:btn_donateCC_LG.gif:NonHostedGuest
Examples:
-------
- 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"
- Television FTA programs:
- 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"
- msys can be one of: dvbs, dvbs2, dvbt, dvbt2, dvbc, dvbc2, atsc, isdbt, dvbcb ( - DVBC_ANNEX_B )
Alles anzeigen
[15:23 root@dm900 minisatip] > minisatip -e 1-7 -f -y 5544 -x 9090
[02/05 15:24:09.199 main]: Initializing with 7 devices
[02/05 15:26:08.808 main]: tuning to 11347000(1597000) pol: v (1) sr:22000000 fec:23 delsys:dvbs2 mod:8psk rolloff:0.35 pilot:on, ts clear=119430, ts pol=119430
[02/05 15:27:53.330 main]: tuning to 11347000(1597000) pol: v (1) sr:22000000 fec:23 delsys:dvbs2 mod:8psk rolloff:0.35 pilot:on, ts clear=223850, ts pol=223851
[02/05 15:32:43.429 main]: tuning to 12266000(1666000) pol: h (2) sr:27500000 fec: delsys:dvbs mod: rolloff: pilot: , ts clear=513621, ts pol=513621
[02/05 15:34:58.935 main]: tuning to 11347000(1597000) pol: v (1) sr:22000000 fec:23 delsys:dvbs2 mod:8psk rolloff:0.35 pilot:on, ts clear=649090, ts pol=649090
[02/05 15:37:23.833 main]: tuning to 11347000(1597000) pol: v (1) sr:22000000 fec:23 delsys:dvbs2 mod:8psk rolloff:0.35 pilot:on, ts clear=793933, ts pol=793933
[02/05 15:37:29.254 main]: tuning to 11347000(1597000) pol: v (1) sr:22000000 fec:23 delsys:dvbs2 mod:8psk rolloff:0.35 pilot:on, ts clear=799782, ts pol=799783
[02/05 15:37:33.253 main]: tuning to 11347000(1597000) pol: v (1) sr:22000000 fec:23 delsys:dvbs2 mod:8psk rolloff:0.35 pilot:on, ts clear=803781, ts pol=803781
Gibt es dann im IHAD Bastelstube
gruß pclin
Das wird ohne Änderungen aber vermutlich nicht ordentlich funktionieren. Weil der FBC Tuner ja keine 8 vollwertigen Tuner bereitstellt...
Es gibt ja pro Eingang nur einmal 22Khz / Spannung.
Der Server muss angepasst werden, damit er ordentlich mit dem FBC Tuner arbeiten kann.
Ohne Änderungen wird er nur als single Tuner funktionieren.
Sobald ein Tuner geschlossen wird werden alle anderen kaputt gehen.
cya
Im Forum ist man da sehr Hilfsbereit.
@cata hat da glaube ich auch schon mal etwas angepasst.
Wie das mit den FBC Tunern ist, kann ich aber noch nicht sagen, versuche mal weiter...
gruß pclin
Wenn e2 läuft, kann ich auch minisatip starten.
Beispiel:
e2 > ZDFinfo HD
minisatip > KiKA HD
Stoppe ich jetzt minisatip bleibt das Bild in e2 stehen.
Nach rezap alles wieder IO.
Zappe ich jetzt auf einen anderen Transponder/Ebene (e2), bleibt das Bild in minisatip stehen.
Gehe ich wieder zurück, wird das Bild in minisatip (VLC) wieder aktiv.
gruß pclin
ist minisatip verwendbar als tvheadend fuer kodi?
oder gibt es auch ein tvheadend fuer die dm920?
Wenn du kodi nicht auf der Box meinst, dann ja.
Im IHAD schreibt ein User das er kodi am Raspi mit minisatip auf der dreambox verwendet.
Leider kommt aber tvheadend in kodi (auf der Box) nicht mit gstreamer zurecht.
Hier fehlt leider wieder der HW Support für ffmpeg.
gruß pclin
Wenn noch etwas fehlen sollte Posten.
gruß pclin
Ich denke da spricht nichts gegen.
Ich bin ja immer noch in diversen Boards unterwegs...
Und werde die Dramboxen weiterhin Supporten!
gruß pclin
Besten Dank @pclin
root@dm920:/data/minisatip/usr/bin# ./minisatip -e 1-7 -f -y 5544 -x 9090
./minisatip: error while loading shared libraries: libdvbcsa.so.1: cannot open shared object file: No such file or directory
Hast Du vlt die libdvbcsa.so auch noch fertig kompiliert für die 920?
Gruß und Vielen Dank
In Post 12 hinzugefügt.
gruß pclin
In Post 12 hinzugefügt.
gruß pclin
Danke, erst hatte noch libdvbapi.so gefehlt, die hattes aber in Post 10 drin.
Nun brauch ich noch libucsi.so
<strong>root@dm920:/data/minisatip/usr/bin# ./minisatip -e 1-7 -f -y 5544 -x 9090</strong>
<strong>./minisatip: error while loading shared libraries: libucsi.so: cannot open shared object file: No such file or directory</strong>
EDIT: im IHaD gefunden.
Post 12
gruß pclin