Btw, the same file is being updated most likely when I push new code to github. So re-downloading can get different sizes at different times.
Last time I checked the binary was not added to the zip file for arm.
minisatip for VU+ Ultimo 4K
Re: minisatip for VU+ Ultimo 4K
If you have VU+ ultimo available, try the latest binary for arm.
Thank you
Thank you
Re: minisatip for VU+ Ultimo 4K
Hello there,
I try to get minisatip running on a VU+ Uno 4K se (ARM) with FRITZ!Box 6490 DVB-C tuner as source. I'm using the ARM binary from the binary Thread here.
I tried to start the server with the following parameters:
./minisatip -f -N -s dvbc:1@192.168.178.54/192.168.178.253:554
I've also generated a log when tried to switch to the DVB-C Channel "Das Erste": https://pastebin.com/QfRJ1cFg
It seems that the PIDs are missing in the rtsp:// URL.
This URL is generated by minisatip:
rtsp://192.168.178.253:554/?freq=314.0&sr=6900&msys=dvbc&mtype=256qam&pids=0
If I download the Channellist as m3u file from my FRITZ!Box the URL for this channel that works looks like:
rtsp://192.168.178.253:554/?freq=314&msys=dvbc&mtype=256qam&sr=6900&pids=0,16,17,18,20,100,101,84,102,103,104,105,106,1176,2070,2171
have I forgotten something or why are the PIDs missing ?
hope someone can help me here
thanks
a13xde
I try to get minisatip running on a VU+ Uno 4K se (ARM) with FRITZ!Box 6490 DVB-C tuner as source. I'm using the ARM binary from the binary Thread here.
I tried to start the server with the following parameters:
./minisatip -f -N -s dvbc:1@192.168.178.54/192.168.178.253:554
I've also generated a log when tried to switch to the DVB-C Channel "Das Erste": https://pastebin.com/QfRJ1cFg
It seems that the PIDs are missing in the rtsp:// URL.
This URL is generated by minisatip:
rtsp://192.168.178.253:554/?freq=314.0&sr=6900&msys=dvbc&mtype=256qam&pids=0
If I download the Channellist as m3u file from my FRITZ!Box the URL for this channel that works looks like:
rtsp://192.168.178.253:554/?freq=314&msys=dvbc&mtype=256qam&sr=6900&pids=0,16,17,18,20,100,101,84,102,103,104,105,106,1176,2070,2171
have I forgotten something or why are the PIDs missing ?
hope someone can help me here
thanks
a13xde
Re: minisatip for VU+ Ultimo 4K
The issueseemsto be related to the fact that your Fritz does not like addpids=0 which results in an error.
Change opts.satip_addpids = 0; in minisatip (replace 1 with 0)
Thanks
Change opts.satip_addpids = 0; in minisatip (replace 1 with 0)
Thanks
Re: minisatip for VU+ Ultimo 4K
Thank you cata, but I'm not sure if I understood that correctly.
I tried to change "opts.satip_addpids = 1" to "opts.satip_addpids = 0" in src/minisatip.c and then compiled it again, but the result is the same.
The rtsp URL generated then while tried to tune is still with pids=0. Because I don't know how to cross compile for ARM I tried this on a x64 Debian but the result should be the same. VU+ is then connected to the minisatip Server on Debian.
Is it correct that the request from VU+ Sat>IP Client already comes with pids=none ?
From Log Line 105:
[09/02 00:28:55.058 main]: detect_dvb_parameters (S)-> freq=314&msys=dvbc&mtype=256qam&sr=6900&pids=none
I tried to change "opts.satip_addpids = 1" to "opts.satip_addpids = 0" in src/minisatip.c and then compiled it again, but the result is the same.
The rtsp URL generated then while tried to tune is still with pids=0. Because I don't know how to cross compile for ARM I tried this on a x64 Debian but the result should be the same. VU+ is then connected to the minisatip Server on Debian.
Is it correct that the request from VU+ Sat>IP Client already comes with pids=none ?
From Log Line 105:
[09/02 00:28:55.058 main]: detect_dvb_parameters (S)-> freq=314&msys=dvbc&mtype=256qam&sr=6900&pids=none
Re: minisatip for VU+ Ultimo 4K
Hi,
ich habe minisatip für die Dreambox DM900/DM920 UHD compiliert, geht soweit ganz gut.
./configure --prefix=/usr --build=arm-oe-linux-gnueabi --host=arm-oe-linux-gnueabi --with-pic --with-gnu-ld --enable-enigma
[16:00 root@dm900 ~] > minisatip --help
minisatip version 0.7.15, compiled with s2api version: 050A
[02/05 18:03:15.617 main]: Built with dvbcsa
[02/05 18:03:15.617 main]: Built with CI
[02/05 18:03:15.617 main]: Built with dvbapi
[02/05 18:03:15.617 main]: Built with AES (OpenSSL)
[02/05 18:03:15.617 main]: Built with tables processing
[02/05 18:03:15.617 main]: Built with pmt processing
[02/05 18:03:15.617 main]: Built with satip client
[02/05 18:03:15.617 main]: Built with linux dvb client
[02/05 18:03:15.617 main]: Built with backtrace
[02/05 18:03:15.617 main]: Built without netceiver
Ich bin aber noch Anfäger mit minisatip.
Für mich gibt es jetzt die Frage wie es mit FBC Tunern funktioniert.
Vielen Dank für minisatip
gruß pclin
ich habe minisatip für die Dreambox DM900/DM920 UHD compiliert, geht soweit ganz gut.
./configure --prefix=/usr --build=arm-oe-linux-gnueabi --host=arm-oe-linux-gnueabi --with-pic --with-gnu-ld --enable-enigma
[16:00 root@dm900 ~] > minisatip --help
minisatip version 0.7.15, compiled with s2api version: 050A
[02/05 18:03:15.617 main]: Built with dvbcsa
[02/05 18:03:15.617 main]: Built with CI
[02/05 18:03:15.617 main]: Built with dvbapi
[02/05 18:03:15.617 main]: Built with AES (OpenSSL)
[02/05 18:03:15.617 main]: Built with tables processing
[02/05 18:03:15.617 main]: Built with pmt processing
[02/05 18:03:15.617 main]: Built with satip client
[02/05 18:03:15.617 main]: Built with linux dvb client
[02/05 18:03:15.617 main]: Built with backtrace
[02/05 18:03:15.617 main]: Built without netceiver
Ich bin aber noch Anfäger mit minisatip.
Für mich gibt es jetzt die Frage wie es mit FBC Tunern funktioniert.
Code: Select all
Zitat:
Ghost DEV dreambox.de
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.
gruß pclin