- standalone - where minisatip is using a tuner exclusively. In this mode, you need to assign tunners (1-X) to enigma2, the remaining tuners (X-N) to minisatip. The advantage of this method is that minisatip can use all the features as on x86/arm Linux systems, but a static partition of the tuners in which minisatip will use just the assigned devices. Personally I use the following way to start minisatip:
Code: Select all
echo 'ps ax | grep minisatip | grep -v grep | grep -v tail || /usr/bin/minisatip -e 4-8 -R /usr/share/minisatip/html/' >> /etc/cron/crontabs/root
- using enigma2 as backend
Minisatip can share the enigma2 backend to be able to tune to several channels while enigma2 is also in use. The advantage of this mode is that minisatip can share the same tuner with enigma2 and all the tuners when enigma2 is not in use. It can also use enigma2 to decrypt channels with CI(+) card. The disadvantage of this method is related to a driver bug that does not allow scanning or listening to radio channels due to low bit rate. For this you need to revert to the standalone mode. Some satip clients when they tune, they request just pid 0 (PAT). Because of this, the tuning may fail.
Code: Select all
minisatip -N --satip-xml http://127.0.0.1:8554 -R /usr/share/minisatip/html
In Tvheadend for example, an additional setting needs to be made for everything to work correctly (due to the driver bug):
Configuration -> DVB Input -> TV Adapters -> on SAT IP adapters -> Enable 'Send Full Play Command'
This setting works perfectly also on standalone mode.
Additional details: https://www.opena.tv/openatv-6-2-image- ... -test.html