Beiträge anzeigen

Diese Sektion erlaubt es ihnen alle Beiträge dieses Mitglieds zu sehen. Beachten sie, dass sie nur solche Beiträge sehen können, zu denen sie auch Zugriffsrechte haben.


Nachrichten - Dima73

Seiten: 1 2 [3] 4 5 ... 7
31
VU+ - VU Duo Settopbox / Re:Problem video when use PiP
« am: Oktober 14, 2016, 09:09:48 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
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



32
VU+ - VU Duo Settopbox / Re:Problem video when use PiP
« am: Oktober 14, 2016, 02:33:38 Nachmittag »
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
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

33
VU+ - VU Duo Settopbox / Re:Problem video when use PiP
« am: Oktober 12, 2016, 05:48:12 Nachmittag »
Update drivers 2016-10-08.
Problem not solved.

34
VU+ - VU Duo Settopbox / Re:Problem video when use PiP
« 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:
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?

35
VU+ - VU Duo Settopbox / Re:Problem video when use PiP
« am: September 24, 2016, 11:09:02 Nachmittag »
and
dvb-fe-tool -f 10 =  Sundtek DVB-S/S2
?????
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-S2
        Name: Sundtek DVB-S/S2 (IV) (0/0) (USBDVB-S2
        Frontend_Device: 10root@vusolo4k:~#  dvb-fe-tool -f 11
ERROR    No such file or directory while opening /dev/dvb/adapter0/frontend11
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 9
Device Vuplus FE (/dev/dvb/adapter0/frontend9) 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_INVERSION_AUTO
     CAN_QPSK
     CAN_RECOVER
DVB API Version 5.10, Current v5 delivery system: DVBS
Supported delivery systems:
    [DVBS]
     DVBS2
DiSEqC VOLTAGE: OFF
ERROR    FE_SET_VOLTAGE: Operation not permitted
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:~#

36
VU+ - VU Duo Settopbox / Re:Problem video when use PiP
« am: September 23, 2016, 07:57:10 Nachmittag »

Sundtek DVB-S/S2 (IV) is type DVB-C!!!

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: DVBC/ANNEX_A
Supported delivery systems:
     DVBS
    [DVBC/ANNEX_A]
     DVBS
     DVBS2
     DVBC/ANNEX_C
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 9
Device Vuplus FE (/dev/dvb/adapter0/frontend9) 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_INVERSION_AUTO
     CAN_QPSK
     CAN_RECOVER
DVB API Version 5.10, Current v5 delivery system: DVBS
Supported delivery systems:
    [DVBS]
     DVBS2
DiSEqC VOLTAGE: OFF
ERROR    FE_SET_VOLTAGE: Operation not permitted
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:~#

37
VU+ - VU Duo Settopbox / Re:Problem video when use PiP
« am: September 22, 2016, 12:30:01 Nachmittag »
VU+solo4k
timeshift no problems
PiP no problems

Only wrong DVB API v5 statistics

38
VU+ - VU Duo Settopbox / Re:Blindscan on VU+ Solo2 with OpenPLI image
« am: Mai 29, 2016, 12:23:59 Nachmittag »
Tested.
Scan for new drivers(25.05.2016) works fine.
Fixed new output blind scan:
1)openPli image
https://github.com/OpenPLi/enigma2-plugins/commit/75aa34b103c6e78678f78f54952fb9c9fce2bd7e
2)images based of oe-alliance (openATV,openVIX and etc)
https://github.com/oe-alliance/oe-alliance-plugins/commit/96975356a3a9e67d1a948ba64f7f13a233e94819

39
VU+ - VU Duo Settopbox / Re:Blindscan on VU+ Solo2 with OpenPLI image
« am: April 21, 2016, 10:10:29 Vormittag »
Support Sundtek S2 Blindscan added in plugin Blindscan(feed avaibale):
1)openPli image
2)images based of oe-alliance (openATV,openVIX and etc)

40
VU+ - VU Duo Settopbox / Re:Problem video when use PiP
« am: April 20, 2016, 06:11:35 Nachmittag »
Ok.This not sundtek problem.
Tested on avermedia a857 same problem(stop video when close pip)

PLi and ATV image again same problem.

PiP work OK for formuler1.

PiP problem again drivers Xtrend.

41
VU+ - VU Duo Settopbox / Re:Problem video when use PiP
« am: April 20, 2016, 09:10:48 Vormittag »
Ok.
Timeshift not work only ET/xtrend box.
This problem ET/xtrend drivers.

42
VU+ - VU Duo Settopbox / Re:Questions about the plugin
« am: April 19, 2016, 07:06:21 Nachmittag »
Sundtek
I added the plugin on github and greate new version(only ipk)
https://github.com/Dima73/enigma2-plugin-extensions-sundtekcontrolcenter

45
VU+ - VU Duo Settopbox / Re:Problem video when use PiP
« am: April 17, 2016, 03:29:37 Nachmittag »
Image problem, timeshifting is working (last tested with VTI and Vu+).

Have a closer look at the debug logs of enigma2.
<  2428.776> [eDVBServicePlay] have 1 video stream(s) (1416), and 1 audio stream(s) (1417), and the pcr pid is 1416, and the text pid is ffffffff
<  2428.777> [eTSMPEGDecoder] decoder state: pause, vpid=1416, apid=1417
<  2428.777> [eDVBVideo0] VIDEO_SLOWMOTION 0 ok
<  2428.777> [eDVBVideo0] VIDEO_FAST_FORWARD 0 ok
<  2428.777> [eDVBVideo0] VIDEO_FREEZE ok
<  2428.777> [eDVBAudio0] AUDIO_PAUSE ok
<  2428.777> [eDVBServicePlay] timeshift
<  2428.778> [eDVBServicePlay] timeshift
<  2428.779> [eDVBServicePlay] timeshift
<  2428.780> [eDVBServicePlay] timeshift
<  2428.780> resolved to PAUSE
<  2428.780> [eDVBServicePlay] pause
<  2428.781> [eDVBServicePlay] timeshift
<  2428.781> [eDVBServicePlay] timeshift
<  2428.783> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2428.783> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2428.783> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2428.786> [eDVBServicePlay] timeshift
<  2428.787> [eDVBServicePlay] timeshift
<  2428.891> [eDVBServicePlay] seekTo -90000
<  2428.891> [eDVBChannel] seek.
<  2428.892> [eFilePushThread] wait for driver eof aborted by signal
<  2428.892> [eFilePushThread] waiting for pause
<  2428.892> [eFilePushThread] PAUSED
<  2428.894> [eDVBAudio0] AUDIO_CLEAR_BUFFER ok
<  2428.921> [eDVBVideo0] VIDEO_CLEAR_BUFFER ok
<  2428.930> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2428.930> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2428.930> [eDVBChannel] getLength failed - can't seek relative to end!
<  2428.930> [eDVBServicePlay] timeshift
<  2428.931> [eDVBServicePlay] timeshift
<  2428.932> New timeshift filename:  20160417 1624 - Riga TV24 - Rampas ugunis
<  2428.937> [eDVBChannel] pvrEvent evtStopped
<  2429.180> [eFilePushThread] wait for driver eof timeout
<  2429.284> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2429.284> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2429.285> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2429.430> [eFilePushThread] wait for driver eof timeout
<  2429.681> [eFilePushThread] wait for driver eof timeout
<  2429.784> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2429.784> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2429.784> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2429.931> [eFilePushThread] wait for driver eof timeout
<  2430.182> [eFilePushThread] wait for driver eof timeout
<  2430.284> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2430.284> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2430.284> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2430.432> [eFilePushThread] wait for driver eof timeout
<  2430.580> [eEPGCache] schedule finished(1460899475)
<  2430.682> [eFilePushThread] wait for driver eof timeout
<  2430.784> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2430.785> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2430.785> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2430.933> [eFilePushThread] wait for driver eof timeout
<  2431.183> [eFilePushThread] wait for driver eof timeout
...........................
<  2466.915> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2466.915> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2466.915> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2466.990> [eFilePushThread] wait for driver eof timeout
<  2467.240> [eFilePushThread] wait for driver eof timeout
<  2467.415> [eMPEGStreamInformation::getLastFrame] - no data (yet?)
<  2467.415> [eDVBTSTools] calcEnd [@ML] m_streaminfo.getLastFrame failed, fallback
<  2467.415> [eDVBTSTools] fixupPTS begin not valid, can't fixup
<  2467.491> [eFilePushThread] wait for driver eof timeout
<  2467.741> [eFilePushThread] wait for driver eof timeout
<  2467.992> [eFilePushThread] wait for driver eof timeout
<  2468.242> [eFilePushThread] wait for driver eof timeout
<  2468.251> [eDVBServicePlay] timeshift
<  2468.251> action ->  InfobarTimeshiftActions timeshiftStop
<  2468.251> [eDVBServicePlay] timeshift
<  2468.252> [eDVBServicePlay] timeshift
<  2468.492> [eFilePushThread] wait for driver eof timeout
<  2468.743> [eFilePushThread] wait for driver eof timeout
<  2468.993> [eFilePushThread] wait for driver eof timeout
<  2469.243> [eFilePushThread] wait for driver eof timeout
<  2469.494> [eFilePushThread] wait for driver eof timeout
<  2469.744> [eFilePushThread] wait for driver eof timeout
<  2469.782> action ->  MsgBoxActions ok
<  2469.799> [eDVBServicePlay] timeshift
<  2469.799> [eDVBServicePlay] SwitchToLive
<  2469.800> [eFilePushThread] stopping thread
<  2469.800> [eFilePushThread] wait for driver eof aborted by signal
<  2469.800> [eFilePushThread] STOP
<  2469.801> [eTSMPEGDecoder] decoder state: play, vpid=ffffffff, apid=ffffffff
<  2469.801> [eDVBVideo0] DEMUX_STOP  ok
<  2469.802> [eDVBVideo0] VIDEO_STOP ok
<  2469.802> [eDVBVideo0] destroy
<  2469.802> [eDVBAudio0] AUDIO_STOP ok
<  2469.826> [eDVBAudio0] DEMUX_STOP ok
<  2469.830> [eDVBAudio0] AUDIO_CONTINUE ok
<  2469.830> [eDVBAudio0] destroy
cleaning up
TuxTxt cache cleared
<  2469.836> [eDVBServicePlay] have 1 video stream(s) (1416), and 1 audio stream(s) (1417), and the pcr pid is 1416, and the text pid is ffffffff
<  2469.837> [eDVBChannel] getDemux cap=01
TuxTxt cache cleared
<  2469.842> [eTSMPEGDecoder] decoder state: play, vpid=1416, apid=1417
<  2469.842> [eDVBPCR0] DMX_SET_PES_FILTER pid=0x1416 ok
<  2469.842> [eDVBPCR0] DEMUX_START ok
<  2469.843> [eDVBAudio0] DMX_SET_PES_FILTER pid=0x1417 ok
<  2469.843> [eDVBAudio0] DEMUX_START ok
<  2469.843> [eDVBAudio0] AUDIO_SET_BYPASS bypass=1 ok
<  2469.843> [eDVBAudio0] AUDIO_PAUSE ok
<  2469.843> [eDVBAudio0] AUDIO_PLAY ok
<  2469.845> [eDVBVideo] Video Device: /dev/dvb/adapter0/video0
<  2469.845> [eDVBVideo] demux device: /dev/dvb/adapter0/demux0
<  2469.845> [eDVBVideo0] VIDEO_SET_STREAMTYPE 1 - ok
<  2469.846> [eDVBVideo0] DMX_SET_PES_FILTER pid=0x1416 ok
<  2469.846> [eDVBVideo0] DEMUX_START ok
<  2469.846> [eDVBVideo0] VIDEO_FREEZE ok
<  2469.846> [eDVBVideo0] VIDEO_PLAY ok
<  2469.852> [eDVBVideo0] VIDEO_SLOWMOTION 0 ok
<  2469.852> [eDVBVideo0] VIDEO_FAST_FORWARD 0 ok
<  2469.852> [eDVBVideo0] VIDEO_CONTINUE ok
<  2469.852> [eDVBAudio0] AUDIO_CONTINUE ok
<  2469.852> [eDVBTeletextParser] Starting!
<  2469.852> [eDVBTeletextParser] disable teletext subtitles page ffffffffffffffff (und)
<  2469.852> [eDVBPESReader] Created. Opening demux
<  2469.852> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  2469.852> [eDVBTeletextParser] created teletext subtitle PES reader!
<  2469.852> [eDVBPESReader] Created. Opening demux
<  2469.853> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<  2469.853> [eDVBTeletextParser] starting PES reader on pid=ffffffff
<  2469.853> [eDVBServicePlay] timeshift
<  2469.854> resolved to PLAY
<  2469.854> [eDVBServicePlay] unpause
<  2469.855> [eDVBServicePlay] timeshift
<  2469.855> [eDVBServicePlay] timeshift
<  2469.858> resolved to PLAY
<  2469.858> [eDVBServicePlay] unpause
<  2469.858> [eDVBServicePlay] timeshift
<  2469.859> [eDVBServicePlay] timeshift
<  2469.861> [eFilePushThreadRecorder] stopping thread.
<  2469.862> [eDVBRecordFileThread] waiting for aio to complete
<  2469.862> [eDVBRecordFileThread] buffer usage histogram (20 buffers of 188 kB)
<  2469.862> [eDVBRecordFileThread]   1:      2
<  2469.862> [eFilePushThreadRecorder] THREAD STOP
<  2469.863> [eDVBServicePlay] remove timeshift files
<  2469.863> [setIoPrio] best-effort level 7 ok
<  2469.863> [eBackgroundFileEraser] deleting '/media/hdd/timeshift/timeshift.jSOCkV.del'
<  2469.864> [eDVBServicePlay] timeshift
<  2469.867> not pauseable.
<  2469.868> [eDVBServicePlay] timeshift
<  2471.099> [eDVBVideo0] VIDEO_GET_EVENT SIZE_CHANGED 704x576 aspect 2
<  2471.172> [eDVBVideo0] VIDEO_GET_EVENT FRAME_RATE_CHANGED 25000 fps
<  2471.172> [eDVBVideo0] VIDEO_GET_EVENT PROGRESSIVE_CHANGED 0
<  2471.173> [eDVBVideo0] VIDEO_GET_EVENT FRAME_RATE_CHANGED 25000 fps
<  2471.173> [eDVBVideo0] VIDEO_GET_EVENT PROGRESSIVE_CHANGED 0
<  2480.830> [eEPGCache] schedule other finished(1460899526)
<  2480.831> [eEPGCache] stop caching events(1460899526)
<  2480.831> [eEPGCache] next update in 60 min
963

Seiten: 1 2 [3] 4 5 ... 7