« vorheriges nächstes »
Seiten: 1 [2]

Autor Thema: Problem video when use PiP  (Gelesen 30264 mal)

Dima73

  • Jr. Member
  • **
  • Beiträge: 92
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #15 am: September 25, 2016, 11:18:27 Nachmittag »
The problem arises only after booting from a deep sleep mode.

Everything works correctly if you change the file sun_dvb.sh:
Code: [Auswählen]
case "$1" in
start_c)
echo $LINE
echo "DVB-C Tuner start"
echo $LINE
if [ "$usepsax" = "1" ]; then
if [ `ps ax | grep mediasrv | grep -v grep | wc -l` -gt 0 ];then killall -9 mediasrv >/dev/null 2>&1; sleep 1; fi
else
if [ `ps | grep mediasrv | grep -v grep | wc -l` -gt 0 ];then killall -9 mediasrv >/dev/null 2>&1; sleep 1; fi
fi
#wait for devices will block until all devices are initialized
$NICECMD $DRIVERPATH/mediasrv -d --no-nodes --wait-for-devices
sleep 2
$DRIVERPATH/mediaclient --loglevel=off

FRONTEND=`$DRIVERPATH/mediaclient -e |grep -A 5 '\[DVB' -m 1 | grep -m 1 FRONTEND: | sed 's#.*/dev#/dev#g'`

if [ "$FRONTEND" = "" ]; then
echo `date +"%Y-%m-%d %H:%M:%S [$$]"`" No Sundtek device Detected" >> /var/log/mediasrv.log
exit 1
fi
if [ -f /proc/stb/info/vumodel ] && [ ! -e /tmp/.startsolo4k ] ; then
BOXNAME=$( cat /proc/stb/info/vumodel )
if [ $BOXNAME = "solo4k" ]; then
echo `date +"%Y-%m-%d %H:%M:%S"`" need pause start 4 sec. for vu+solo4k" >> /var/log/mediasrv.log
touch /tmp/.startsolo4k
sleep 2
if [ "$usepsax" = "1" ]; then
if [ `ps ax | grep mediasrv | grep -v grep | wc -l` -gt 0 ];then killall -9 mediasrv >/dev/null 2>&1; sleep 1; fi
else
if [ `ps | grep mediasrv | grep -v grep | wc -l` -gt 0 ];then killall -9 mediasrv >/dev/null 2>&1; sleep 1; fi
fi
$NICECMD $DRIVERPATH/mediasrv -d --no-nodes --wait-for-devices
sleep 2
$DRIVERPATH/mediaclient --loglevel=off

fi
fi
if [ -e /etc/sundtek.conf ] && [ "`grep -c dreambox_support_fe1 /etc/sundtek.conf`" != "0" ]; then
echo `date +"%Y-%m-%d %H:%M:%S [$$]"`" Using /etc/sundtek.conf for deviceconfiguration" >> /var/log/mediasrv.log
else
$DRIVERPATH/mediaclient -D DVBC -d $FRONTEND
$DRIVERPATH/mediaclient --enabledreambox=$FRONTEND
fi
if [ "$usepsax" = "1" ]; then
if [ `ps ax | grep enigma2 | grep -v boblight-enigma2 | grep -v grep | wc -l` -gt 0 ] ;then
re_enigma
else
echo $LINE
fi
else
if [ `ps | grep enigma2 | grep -v boblight-enigma2 | grep -v grep | wc -l` -gt 0 ] ;then
re_enigma
else
echo $LINE
fi
fi
        ;;
    start_t2)You consider this offer?
« Letzte Änderung: September 25, 2016, 11:23:35 Nachmittag von Dima73 »
Gespeichert

Dima73

  • Jr. Member
  • **
  • Beiträge: 92
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #16 am: Oktober 12, 2016, 05:48:12 Nachmittag »
Update drivers 2016-10-08.
Problem not solved.
Gespeichert

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #17 am: Oktober 14, 2016, 10:32:01 Vormittag »
Sorry we need to break this down to make it optional and only use it on a settopbox where it is needed, not all settopboxes are broke. It might have some other consequences with other settopboxes if we just change it that way.

Not all Vu+ Settopboxes are broke (according to our information).

What is the final problem if you don't restart it (register it a second time)?
Gespeichert
Failure is a good thing! I'll fix it

Dima73

  • Jr. Member
  • **
  • Beiträge: 92
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #18 am: Oktober 14, 2016, 02:33:38 Nachmittag »
Zitat von: Sundtek am Oktober 14, 2016, 10:32:01 Vormittag
What is the final problem if you don't restart it (register it a second time)?
Sundtek MediaTV Digital Home III (DVB-C/T/T2) use dvb-t type --> start type always dvb-c

Sundtek SkyTV Ultimate simple not work
when show info, this is multi tuner (dvb-c/dvb-s2 type) --> start type always dvb-c and not name this is vtuner fe

this code solved problem
Code: [Auswählen]
if [ -f /proc/stb/info/vumodel ] && [ ! -e /tmp/.startsolo4k ] ; then
BOXNAME=$( cat /proc/stb/info/vumodel )
if [ $BOXNAME = "solo4k" ]; then
echo `date +"%Y-%m-%d %H:%M:%S"`" need pause start 4 sec. for vu+solo4k" >> /var/log/mediasrv.log
touch /tmp/.startsolo4k
sleep 2
if [ "$usepsax" = "1" ]; then
if [ `ps ax | grep mediasrv | grep -v grep | wc -l` -gt 0 ];then killall -9 mediasrv >/dev/null 2>&1; sleep 1; fi
else
if [ `ps | grep mediasrv | grep -v grep | wc -l` -gt 0 ];then killall -9 mediasrv >/dev/null 2>&1; sleep 1; fi
fi
$NICECMD $DRIVERPATH/mediasrv -d --no-nodes --wait-for-devices
sleep 2
$DRIVERPATH/mediaclient --loglevel=off

fi
fi
Gespeichert

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #19 am: Oktober 14, 2016, 05:00:24 Nachmittag »
Can you show /proc/bus/nim_sockets before and after restarting it?

Do you only see this with Vu Solo 4k or also other Vu+ settopboxes?
Gespeichert
Failure is a good thing! I'll fix it

Dima73

  • Jr. Member
  • **
  • Beiträge: 92
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #20 am: Oktober 14, 2016, 09:09:48 Nachmittag »
Zitat von: Sundtek am Oktober 14, 2016, 05:00:24 Nachmittag
Can you show /proc/bus/nim_sockets before and after restarting it?

Do you only see this with Vu Solo 4k or also other Vu+ settopboxes?
'other Vu+ settopboxes' I do not know

openPli for init fist use DVB API v5 statistics
Code: [Auswählen]
openpli 4 vusolo4k

vusolo4k login: root
root@vusolo4k:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 0
NIM Socket 1:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 1
NIM Socket 2:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 2
NIM Socket 3:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 3
NIM Socket 4:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 4
NIM Socket 5:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 5
NIM Socket 6:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 6
NIM Socket 7:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 7
NIM Socket 8:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 8
        I2C_Device: 4
NIM Socket 9:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 9
        I2C_Device: 4

NIM Socket 10:
        Type: DVB-T
        Name: Sundtek DVB-T (III) (1/0) (USB)
        Frontend_Device: 10
NIM Socket 11:
        Type: DVB-S2
        Name: Sundtek DVB-S/S2 (IV) (0/0) (USBDVB-S2
        Frontend_Device: 11root@vusolo4k:~#

root@vusolo4k:~# dvb-fe-tool -f 10
Device vtuner fe (/dev/dvb/adapter0/frontend10) capabilities:
     CAN_FEC_1_2
     CAN_FEC_2_3
     CAN_FEC_3_4
     CAN_FEC_5_6
     CAN_FEC_7_8
     CAN_FEC_AUTO
     CAN_GUARD_INTERVAL_AUTO
     CAN_INVERSION_AUTO
     CAN_QAM_16
     CAN_QAM_64
     CAN_QAM_AUTO
     CAN_QPSK
     CAN_TRANSMISSION_MODE_AUTO
DVB API Version 5.10, Current v5 delivery system: DVBS
Supported delivery systems:
    [DVBS]
     DVBC/ANNEX_A
    [DVBS]
     DVBS2
     DVBC/ANNEX_C
DiSEqC VOLTAGE: OFF
ERROR    FE_SET_VOLTAGE: Operation not permitted
root@vusolo4k:~# dvb-fe-tool -f 11
Device vtuner fe (/dev/dvb/adapter0/frontend11) capabilities:
     CAN_FEC_1_2
     CAN_FEC_2_3
     CAN_FEC_3_4
     CAN_FEC_5_6
     CAN_FEC_7_8
     CAN_FEC_AUTO
     CAN_GUARD_INTERVAL_AUTO
     CAN_INVERSION_AUTO
     CAN_QAM_16
     CAN_QAM_64
     CAN_QAM_AUTO
     CAN_QPSK
     CAN_TRANSMISSION_MODE_AUTO
DVB API Version 5.10, Current v5 delivery system: DVBS2
Supported delivery systems:
     DVBS
     DVBC/ANNEX_A
     DVBS
    [DVBS2]
     DVBC/ANNEX_C
DiSEqC VOLTAGE: OFF
ERROR    FE_SET_VOLTAGE: Operation not permitted

After "Save and start tuner" !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

vusolo4k login: root
root@vusolo4k:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 0
NIM Socket 1:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 1
NIM Socket 2:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 2
NIM Socket 3:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 3
NIM Socket 4:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 4
NIM Socket 5:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 5
NIM Socket 6:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 6
NIM Socket 7:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 7
NIM Socket 8:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 8
        I2C_Device: 4
NIM Socket 9:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 9
        I2C_Device: 4

NIM Socket 10:
        Type: DVB-T
        Name: Sundtek DVB-T (III) (1/0) (USB)
        Frontend_Device: 10
NIM Socket 11:
        Type: DVB-S2
        Name: Sundtek DVB-S/S2 (IV) (0/0) (USBDVB-S2
        Frontend_Device: 11root@vusolo4k:~#

root@vusolo4k:~#  dvb-fe-tool -f 10
Device Sundtek DVB-T (III) (1/0) (/dev/dvb/adapter0/frontend10) capabilities:
     CAN_FEC_1_2
     CAN_FEC_2_3
     CAN_FEC_3_4
     CAN_FEC_5_6
     CAN_FEC_7_8
     CAN_FEC_AUTO
     CAN_GUARD_INTERVAL_AUTO
     CAN_INVERSION_AUTO
     CAN_QAM_16
     CAN_QAM_64
     CAN_QAM_AUTO
     CAN_QPSK
     CAN_TRANSMISSION_MODE_AUTO
DVB API Version 5.10, Current v5 delivery system: DVBT
Supported delivery systems:
    [DVBT]
     DVBC/ANNEX_A
     DVBS
     DVBS2
     DVBC/ANNEX_C

root@vusolo4k:~# dvb-fe-tool -f 11
Device Sundtek DVB-S/S2 (IV) (0/0) (/dev/dvb/adapter0/frontend11) capabilities:
     CAN_2G_MODULATION
     CAN_FEC_1_2
     CAN_FEC_2_3
     CAN_FEC_3_4
     CAN_FEC_4_5
     CAN_FEC_5_6
     CAN_FEC_6_7
     CAN_FEC_7_8
     CAN_FEC_AUTO
     CAN_INVERSION_AUTO
     CAN_QPSK
     CAN_RECOVER
DVB API Version 5.10, Current v5 delivery system: DVBS
Supported delivery systems:
    [DVBS]
     DVBC/ANNEX_A
    [DVBS]
     DVBS2
     DVBC/ANNEX_C
DiSEqC VOLTAGE: OFF
ERROR    FE_SET_VOLTAGE: Operation not permitted


Gespeichert

Dima73

  • Jr. Member
  • **
  • Beiträge: 92
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #21 am: Oktober 20, 2016, 05:32:35 Nachmittag »
Just for your information.
New drivers 2016-10-20
Code: [Auswählen]
vusolo4k login: root
root@vusolo4k:~# cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 0
NIM Socket 1:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 1
NIM Socket 2:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 2
NIM Socket 3:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 3
NIM Socket 4:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 4
NIM Socket 5:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 5
NIM Socket 6:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 6
NIM Socket 7:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(7376 FBC)
        Frontend_Device: 7
NIM Socket 8:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 8
        I2C_Device: 4
NIM Socket 9:
        Type: DVB-S2
        Name: Vuplus DVB-S NIM(AVL6222)
        Frontend_Device: 9
        I2C_Device: 4

NIM Socket 10:
        Type: DVB-T
        Name: Sundtek DVB-T (III) (1/0) (USB)
        Frontend_Device: 10
NIM Socket 11:
        Type: DVB-S2
        Name: Sundtek DVB-S/S2 (IV) (0/0) (USBDVB-S2
        Frontend_Device: 11root@vusolo4k:~#

info NIM Socket 11
Gespeichert

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8604
    • Profil anzeigen
Re:Problem video when use PiP
« Antwort #22 am: Oktober 31, 2016, 03:39:22 Nachmittag »
I think I know what's wrong contact us via chat please.
I would need remote access if possible (ssh/telnet or chrome remote desktop)
http://chat.sundtek.de

Gespeichert
Failure is a good thing! I'll fix it
Seiten: 1 [2]
« vorheriges nächstes »