Seite 1 von 2 12 LetzteLetzte
Ergebnis 1 bis 10 von 18
  1. #1
    Anfänger
    Registriert seit
    09.02.2016
    Beiträge
    28
    Thanks (gegeben)
    24
    Thanks (bekommen)
    1
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten

    USB stick at fault for glitchy timeshift?

    Hi everyone, I have a question about timeshift. I personally rarely use it, but I got my folks set up with a box running openATV 6.1 and they can't do without this function, so they have "automatic timeshift" enabled. Anyway, I mounted a 128 GB 3.0 USB stick as HDD, and everything works quite well, recordings are always fine and even timeshift is okay for the most part, except for the fact that, from time to time, when in timeshift mode (or when watching a programme whilst it is still recording, for that matter), the playback either appears to freeze (hence, no audio either) for a few seconds before readjusting itself, or it just skips forward a couple of seconds.

    The thing is that if I rewind when that happens, the playback at that exact same point is always smooth, which obviously means that the timeshift/recording is okay and no frames were actually dropped, but it's just the video playback that gets choppy for some reason. Don't get me wrong, that doesn't happen very often (I'd say once or twice in an hour), and I've noticed it only seems to affect channels that have a very high bit rate, and even those channels may be totally fine for several hours on end. Still, when it does happen, it is quite annoying.

    Now, I'm no expert, but I can think of two logical reasons for this. Either the box (Zgemma H2H) gets overwhelmed at times when in timeshift mode (or, like I said, when watching an unfinished recording), therefore it's unable to properly handle simultaneous recording and playback, or the flash drive's speed is at fault here and, when faced with bitrate spikes while recording, it prevents the box from accessing the recorded file fast enough to have a smooth playback. What do you think, and is there anything I could try to fix this? I've already gone through a few things both in the timeshift and recordings menus, such as enabling a single or multiple buffer files, but I saw no improvements either way.

    •   Alt Advertising

       

  2. #2
    Senior Mitglied Avatar von s3n0
    Registriert seit
    02.01.2017
    Beiträge
    1.150
    Thanks (gegeben)
    71
    Thanks (bekommen)
    281
    Total Downloaded
    323,0 KB
    Total Downloaded
    323,0 KB
    ReceiverDankeAktivitäten
    Box 1:
    Formuler F3
     
     
    Box 2:
    Vu+ Solo SE V2
     
     
    Box 3:
    Formuer F4-TURBO
     
     
    Zitat Zitat von veronik96 Beitrag anzeigen
    therefore it's unable to properly handle simultaneous recording and playback, or the flash drive's speed is at fault here and, when faced with bitrate spikes while recording, it prevents the box from accessing the recorded file fast enough to have a smooth playback.
    Speed limit (maximum speed) according to USB version:

    USB 1.1 = 12 Mbit/s (1,5 MB/s)
    USB 2.0 = 480 Mbit/s (60 MB/s) - Zgemma H.2H
    USB 3.0 = 5 Gbit/s (628 MB/s)
    USB 3.1 = 10 Gbit/s (1 250 MB/s)

    Bandwidth rate of the FullHD video (H264/MPEG) with more languages than one (more sound-tracks) in one stream is about 7 Mbit/s - 14 Mbit/s cca = > it means 0,8 MB/s - 1,7 MB/s cca. All newest USB 3.0 memory sticks are branded for write speed between 10 MB/s - 40 MB/s (reading speed is much higher).

    However, the problem is not even at the access time of the device - simultaneous data writing or reading of data through multiple portions of memory chips in a USB storage device.

    Your USB memory stick is definitely newer and even USB 3.0 technology. These USB 3.0 memory sticks, even if you buy a cheaper version, have a write speed of at least 10 MB/s. So the problem should not be even when using your USB 3.0 memory stick, in the USB 2.0 port on your Zgemma H2H box.

    As a potential problem, it could be a universal Linux driver for all USB memory sticks. You could try other brands as totally different USB memory sticks in your satellite box.

    Just for interest, what file system do you use on USB stick ? Ext3 or Ext4 ? Or are you using NTFS-3G (NTFS formatted disk with write support in linux kernel) ? When using the timeshift function, the file system Ext3 or Ext4 is highly recommended.
    Geändert von s3n0 (01.12.2017 um 02:15 Uhr)
    Formuler F3 (BCM 7362-A0, 2x 750 MHz, mips)
    Formuler F4 TURBO (BCM 7362-5, 2x 750 MHz, mips)
    Vu+ Solo SE V2 (BCM 7429, 2x 1300 MHz, mips)

  3. Thanks veronik96 bedankten sich
  4. #3
    Anfänger
    Registriert seit
    09.02.2016
    Beiträge
    28
    Thanks (gegeben)
    24
    Thanks (bekommen)
    1
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Ext4. Regardless, the issue is now gone after re-initialising the stick. Anyway, thanks for your explanation.

  5. #4
    Avatar von Papi2000
    Registriert seit
    20.04.2013
    Beiträge
    18.336
    Thanks (gegeben)
    3180
    Thanks (bekommen)
    5780
    Total Downloaded
    595,11 MB
    Total Downloaded
    595,11 MB
    ReceiverDankeAktivitäten
    Box 1:
    GB Q4K-SC / UE4K-SC / UE4K-C
     
     
    Box 2:
    GigaBlue Q-SSC / Q+-SSC
     
     
    Box 3:
    DM900uhd-SS / Vu+Duo
     
     
    Box 4:
    E4HD ZGemma H7/H9 SF8008
     
     
    Box 5:
    diverse andere . . .
     
     
    So the stick may have had a filesystem error. That occures when users hardpower OFF the box.
    Grüßle
    Ralf
    ------------------------------------------------------------------------------------------------------------------------
    Gigablue Quad 4K-multi,Quad+-SSC,Quad-SSC, andere Gigas, Astra 19.2E, UniCable & KabelBW, oATV/ teamBlue
    (weitere: DM900uhd,Vu+Duo,Technisat,Edision),PC-DVB-S/C/T,PCH-A110,Xtreamer,BDP5200
    UE32C5700,Philips65OLED865,Tosh40xyz
    ---- Einen Receiver kann sich jeder kaufen - Eine stabile E²-Box muß man sich verdienen! ----



  6. Thanks veronik96 bedankten sich
  7. #5
    Anfänger
    Registriert seit
    09.02.2016
    Beiträge
    28
    Thanks (gegeben)
    24
    Thanks (bekommen)
    1
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Hey guys, can you clear something up for me? Since I'm randomly still getting this issue from time to time (although it only seems to affect a handful of channels), what I've noticed is that when this stick (128GB) is mounted, the box jumps straight from 50 to 99 at boot-up, hanging at 99 for a few seconds. I'd say that happens at least 99 percent of the time (boot-up time is normal and fast, though). In fact, on a few rare occasions at random, I do see a regular boot-up process, normally building up to 99.

    However, a 64GB version of the exact same stick, which I've used on this same box for a long time and I don't recall ever experiencing this freezing issue, lets the box have a normal boot-up at all times when mounted instead.

    Now, I'm curious, what does openATV do during the second part of the boot-up process after reaching 50%? Does it perform some sort of check on the mounted drives or something like that? If not, what could it be that makes the box boot up in that weird way, and is that normal? Still, I'm pretty sure it has something to do with the flash drive, because if I unmount/remount the 128GB version or if I were to change the mount location and reboot, the box will boot up fine the first time and then resumes skipping to 99 again. I have timeshift permanently enabled on this box and I have already tried reflashing it.

    Like I said, this freezing issue when using the 128GB stick does not happen a lot, so it's not a deal breaker at all. But I still can't explain that 50-99 jump at boot-up and if that might somehow be a clue to figure out the reason behind this problem. Thanks in advance.

  8. #6
    Senior Mitglied Avatar von s3n0
    Registriert seit
    02.01.2017
    Beiträge
    1.150
    Thanks (gegeben)
    71
    Thanks (bekommen)
    281
    Total Downloaded
    323,0 KB
    Total Downloaded
    323,0 KB
    ReceiverDankeAktivitäten
    Box 1:
    Formuler F3
     
     
    Box 2:
    Vu+ Solo SE V2
     
     
    Box 3:
    Formuer F4-TURBO
     
     
    Turn on the DebugLOG function in the OpenATV MENU, and then reboot the box. After booting, see the DebugLOG file (/home/root/logs), for example, with FTP connection.

    I do not know exactly how to scan a USB memory device every time I boot, but it's natural for me. For example, when you have the Timeshift feature enabled, it's enough to check or verify the available space / file for Timeshift when booting. Or, when there are plenty of media files on a USB storage device, enigma2 can be scanned when booting. The DebugLOG file could indicate the cause of slow booting.
    Formuler F3 (BCM 7362-A0, 2x 750 MHz, mips)
    Formuler F4 TURBO (BCM 7362-5, 2x 750 MHz, mips)
    Vu+ Solo SE V2 (BCM 7429, 2x 1300 MHz, mips)

  9. Thanks veronik96 bedankten sich
  10. #7
    Anfänger
    Registriert seit
    09.02.2016
    Beiträge
    28
    Thanks (gegeben)
    24
    Thanks (bekommen)
    1
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Okay, thanks. I'll try that out.

    But perhaps I didn't make myself clear enough. Boot-up time is normal, in fact it's very fast. It's just that after getting to 50%, it skips forward to 99 and hangs there for a little bit, but then loads up normally, and overall it takes exactly the same time as when openATV gradually builds up to 100, when the 64GB stick is mounted.

    So, I was wondering if this 50-99 jump is par for the course in some cases, what the reason behind it could be, and if this might indicate an issue of some sort with the 128GB stick, which in turn causes the freezing problem.

  11. #8
    Anfänger
    Registriert seit
    09.02.2016
    Beiträge
    28
    Thanks (gegeben)
    24
    Thanks (bekommen)
    1
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    So, I turned on the DebugLOG function and then fully rebooted the box (or just the gui) several times, either right away or after zapping and timeshifting for a few minutes. I managed to get the box to boot up properly a few times, and here's the first few seconds of that log file after a gui reboot. I rebooted exactly at 9:30 but, like I said, it was a smooth boot-up, which means it gradually went from 50 to 100, so I guess there's nothing to see here:

    Code:
    09:30:00.723 [   ] driver/rcinput.cpp:23 handleCode 1 160 1
    09:30:00.725 {   } Screens/InfoBarGenerics.py:204 actionA KEY: 352 0 KEY_OK OK
    09:30:00.726 {   } Components/ActionMap.py:46 action action ->  OkCancelActions ok
    09:30:00.734 [   ] dvb/cahandler.cpp:329 unregisterService [eDVBCAService] free slot 0 demux 0 for service 1:0:1:FA5:3AC:110:EEEE0000:0:0:0:
    09:30:00.734 [   ] dvb/cahandler.cpp:474 ~eDVBCAService [eDVBCAService] free service 1:0:1:FA5:3AC:110:EEEE0000:0:0:0:
    09:30:00.746 [   ] dvb/decoder.cpp:815 setState decoder state: play, vpid=-1, apid=-1, pcrpid=-1
    09:30:00.746 <   > dvb/decoder.cpp:710 stop DEMUX_STOP - pcr - ok
    09:30:00.746 <   > dvb/decoder.cpp:413 stop DEMUX_STOP - video - ok
    09:30:00.747 <   > dvb/decoder.cpp:422 stop VIDEO_STOP - ok
    09:30:00.748 <   > dvb/decoder.cpp:157 stop AUDIO_STOP - ok
    09:30:00.779 <   > dvb/decoder.cpp:165 stop DEMUX_STOP - audio - ok
    09:30:00.779 <   > dvb/decoder.cpp:201 unfreeze AUDIO_CONTINUE - ok
    09:30:00.779 <   > dvb/decoder.cpp:786 stop DEMUX_STOP - ttx - ok
    09:30:00.787 [   ] dvb/dvb.cpp:1254 DVBChannelStateChanged start release channel timer
    09:30:00.793 {   } skin.py:1034 readSkin [SKIN] processing screen QuitMainloopScreen:
    09:30:00.800 [ E ] gdi/accel.cpp:357 accelAlloc accel alloc failed
    
    09:30:00.801 [ E ] gdi/gpixmap.cpp:140 gSurface ERROR: accelAlloc failed
    09:30:00.980 {   } Screens/Screen.py:150 show [SCREENNAME]  QuitMainloopScreen
    09:30:00.981 {   } Screens/Standby.py:293 close [Standby] quitMainloop #1
    09:30:00.982 {   } skin.py:847 readSkin [SKIN] Parsing embedded skin <embedded-in-'TryQuitMainloop'>
    09:30:00.984 {   } skin.py:1034 readSkin [SKIN] processing screen <embedded-in-'TryQuitMainloop'>:
    09:30:00.987 {   } skin.py:847 readSkin [SKIN] Parsing embedded skin <embedded-in-'SimpleSummary'>
    09:30:00.989 {   } skin.py:1034 readSkin [SKIN] processing screen <embedded-in-'SimpleSummary'>:
    09:30:00.994 [ E ] gui/ewindowstyle.cpp:35 getStyle eWindowStyleManager::getStyle(style_id=1): NOT FOUND
    09:30:00.996 {   } Screens/Screen.py:150 show [SCREENNAME]  ['TryQuitMainloop_summary', 'SimpleSummary']
    09:30:01.000 {   } Screens/Screen.py:150 show [SCREENNAME]  TryQuitMainloop
    09:30:01.001 [   ] driver/rcinput.cpp:23 handleCode 0 160 1
    09:30:01.003 {   } Screens/InfoBarGenerics.py:204 actionA KEY: 352 1 KEY_OK OK
    09:30:01.011 { E } Components/InputHotplug.py:33 connectionLost connectionLost? [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.
    ]09:30:01.011 {   } Components/InputHotplug.py:33 connectionLost 
    09:30:01.018 {   } mytest.py:629 runScreenTest [mytest.py] normal shutdown
    09:30:01.021 {   } mytest.py:705 runScreenTest ====================================================================================================
    09:30:01.022 {   } mytest.py:728 runScreenTest [mytest.py] set next wakeup type to 'record-timer' and starts in standby
    09:30:01.023 {   } mytest.py:731 runScreenTest [mytest.py] set next wakeup time to Sab, 2018/02/03 12:19:40
    09:30:01.024 {   } mytest.py:743 runScreenTest ====================================================================================================
    09:30:01.245 {   } Plugins/Extensions/EPGImport/log.py:25 write [EPGImport] autostart (1) occured at 1517646601.25
    09:30:01.246 {   } Plugins/Extensions/EPGImport/log.py:25 write [EPGImport] Stop
    09:30:01.250 {   } Plugins/Extensions/AutoTimer/AutoTimer.py:100 readXml [AutoTimer] No changes in configuration, won't parse
    09:30:01.256 {   } Plugins/SystemPlugins/VFDControl/plugin.py:293 sessionstart [F3 LED] sessionstart
    09:30:01.256 {   } Plugins/SystemPlugins/VFDControl/plugin.py:288 controliniVfd [F3 LED] Stopping !!
    09:30:01.429 [ E ] ../lib/base/cfile.h:17 CFile error /proc/stb/vmpeg/1/dst_left [No such file or directory]
    09:30:01.430 [ E ] ../lib/base/cfile.h:17 CFile error /proc/stb/vmpeg/1/dst_top [No such file or directory]
    09:30:01.430 [ E ] ../lib/base/cfile.h:17 CFile error /proc/stb/vmpeg/1/dst_width [No such file or directory]
    09:30:01.430 [ E ] ../lib/base/cfile.h:17 CFile error /proc/stb/vmpeg/1/dst_height [No such file or directory]
    09:30:01.430 [ E ] ../lib/base/cfile.h:17 CFile error /proc/stb/vmpeg/1/dst_apply [No such file or directory]
    09:30:01.431 [   ] dvb/db.cpp:606 saveServicelist ---- saving lame channel db
    09:30:01.456 [   ] dvb/db.cpp:728 saveServicelist saved 98 channels and 909 services!
    09:30:01.472 [   ] dvb/dvb.cpp:1265 releaseCachedChannel release cached channel (timer timeout)
    09:30:01.472 [   ] dvb/dvbtime.cpp:581 DVBChannelStateChanged [eDVBLocalTimerHandler] remove channel 0x132cd40
    09:30:01.473 [   ] dvb/epgcache.cpp:616 DVBChannelStateChanged [eEPGCache] remove channel 0x132cd40
    09:30:01.473 [   ] dvb/dvb.cpp:1248 DVBChannelStateChanged stop release channel timer
    09:30:01.475 [   ] dvb/epgcache.cpp:1384 save [EPGC] store epg to realpath '/media/hdd/epg.dat'
    09:30:01.484 [   ] dvb/epgcache.cpp:1430 save [EPGC] 2717 events written to /media/hdd/epg.dat
    09:30:03.741 [   ] dvb/dvbtime.cpp:251 ~eDVBLocalTimeHandler set RTC to previous valid time
    09:30:03.741 [   ] dvb/dvbtime.cpp:49 setRTC [eDVBLocalTimerHandler] set RTC Time
    09:30:03.742 [   ] base/init.cpp:58 setRunlevel - (41) eServiceFactoryDVD
    09:30:03.742 [   ] base/init.cpp:58 setRunlevel - (41) eServiceFactoryHDMI
    09:30:03.742 [   ] base/init.cpp:58 setRunlevel - (41) eServiceFactoryM2TS
    09:30:03.742 [   ] base/init.cpp:58 setRunlevel - (41) eServiceFactoryMP3
    09:30:03.742 [   ] base/init.cpp:58 setRunlevel - (41) eServiceFactoryFS
    09:30:03.742 [   ] base/init.cpp:58 setRunlevel - (41) eServiceFactoryDVB
    09:30:03.743 [   ] base/init.cpp:58 setRunlevel - (41) Encoders
    09:30:03.743 [   ] base/init.cpp:58 setRunlevel - (41) Stream server
    09:30:03.743 [   ] base/init.cpp:58 setRunlevel - (40) eServiceCenter
    09:30:03.743 [   ] base/init.cpp:58 setRunlevel - (35) CI Slots
    09:30:03.743 [   ] base/init.cpp:58 setRunlevel - (35) CA handler
    09:30:03.744 [   ] base/init.cpp:58 setRunlevel - (30) eActionMap
    09:30:03.745 [   ] base/init.cpp:58 setRunlevel - (22) Hdmi CEC driver
    09:30:03.745 [   ] base/init.cpp:58 setRunlevel - (21) input device driver
    09:30:03.820 [   ] base/init.cpp:58 setRunlevel - (20) DVB-CI UI
    09:30:03.820 [   ] base/init.cpp:58 setRunlevel - (20) UHF Modulator
    09:30:03.820 [   ] base/init.cpp:58 setRunlevel - (20) RC Input layer
    09:30:03.820 [   ] base/init.cpp:58 setRunlevel - (20) misc options
    09:30:03.820 [   ] base/init.cpp:58 setRunlevel - (20) AVSwitch Driver
    09:30:03.820 [   ] base/init.cpp:58 setRunlevel - (15) eWindowStyleManager
    09:30:03.820 [   ] base/init.cpp:58 setRunlevel - (10) gRC
    09:30:03.821 [   ] gdi/grc.cpp:57 ~gRC waiting for gRC thread shutdown
    09:30:03.821 [   ] gdi/grc.cpp:59 ~gRC gRC thread has finished
    09:30:03.822 [   ] base/init.cpp:58 setRunlevel - (9) GFBDC
    09:30:03.837 [   ] base/init.cpp:58 setRunlevel - (9) gLCDDC
    09:30:03.837 [   ] base/init.cpp:58 setRunlevel - (9) Font Render Class
    09:30:03.838 [   ] base/init.cpp:58 setRunlevel - (8) graphics acceleration manager
    09:30:03.838 [   ] base/init.cpp:58 setRunlevel - (5) Tuxtxt
    09:30:03.838 [   ] base/init.cpp:58 setRunlevel - (1) Background File Eraser
    09:30:03.839 [   ] base/init.cpp:63 setRunlevel reached rl -1
    09:30:03.839 [   ] dvb/frontend.cpp:653 closeFrontend close frontend 1
    TuxTxt cache cleared
    cleaning up
    TuxTxt cache cleared
    TuxTxt cache cleared
    TuxTxt cache cleared
    TuxTxt: initialized
    TuxTxt service started 653
    TuxTxt running thread...(653)
    TuxTxt stopped service 653
    cleaning up
    TuxTxt cache cleared
    TuxTxt cache cleared
    TuxTxt cache cleared
    TuxTxt: initialized
    TuxTxt service started 653
    TuxTxt running thread...(653)
    TuxTxt stopped service 653
    cleaning up
    TuxTxt cache cleared
    TuxTxt cache cleared
    TuxTxt cache cleared
    TuxTxt: initialized
    TuxTxt service started 653
    TuxTxt running thread...(653)
    TuxTxt stopped service 653
    cleaning up
    TuxTxt cache cleared
    TuxTxt cache cleared
    TuxTxt cache cleared
    TuxTxt: initialized
    TuxTxt service started 653
    TuxTxt running thread...(653)
    TuxTxt stopped service 653
    cleaning up
    TuxTxt cache cleared
    On the other hand, here's part of the log file after another gui reboot: the box displayed 50 and then skipped straight to 99 which is what happens most times when rebooting, like I explained yesterday.

    Code:
    09:15:00.685 [   ] driver/rcinput.cpp:23 handleCode 1 160 1
    09:15:00.687 {   } Screens/InfoBarGenerics.py:204 actionA KEY: 352 0 KEY_OK OK
    09:15:00.688 {   } Components/ActionMap.py:46 action action ->  OkCancelActions ok
    09:15:00.697 [   ] base/filepush.cpp:438 stop [eFilePushThreadRecorder] stopping thread.
    09:15:00.698 [   ] dvb/demux.cpp:576 flush [eDVBRecordFileThread] waiting for aio to complete
    09:15:00.699 [   ] dvb/demux.cpp:445 wait [eDVBRecordFileThread] Waiting for I/O to complete
    09:15:00.700 [   ] dvb/demux.cpp:582 flush [eDVBRecordFileThread] buffer usage histogram (20 buffers of 188 kB)
    09:15:00.700 [   ] dvb/demux.cpp:585 flush       1:     12
    09:15:00.704 [   ] base/filepush.cpp:422 thread [eFilePushThreadRecorder] THREAD STOP
    09:15:00.708 [   ] service/servicedvb.cpp:2507 stopTimeshift remove timeshift files
    09:15:00.709 [   ] base/ioprio.cpp:83 setIoPrio setIoPrio best-effort level 7 ok
    09:15:00.709 [   ] components/file_eraser.cpp:85 gotMessage [eBackgroundFileEraser] deleting '/media/hdd/timeshift/timeshift.fVliLq.del'
    09:15:00.710 [   ] dvb/cahandler.cpp:329 unregisterService [eDVBCAService] free slot 0 demux 0 for service 1:0:1:81:385:110:EEEE0000:0:0:0:
    09:15:00.710 [   ] components/file_eraser.cpp:85 gotMessage [eBackgroundFileEraser] deleting '/media/hdd/timeshift/timeshift.fVliLq.sc.del'
    09:15:00.710 [   ] dvb/cahandler.cpp:474 ~eDVBCAService [eDVBCAService] free service 1:0:1:81:385:110:EEEE0000:0:0:0:
    09:15:00.725 [   ] dvb/decoder.cpp:815 setState decoder state: play, vpid=-1, apid=-1, pcrpid=-1
    09:15:00.725 <   > dvb/decoder.cpp:710 stop DEMUX_STOP - pcr - ok
    09:15:00.725 <   > dvb/decoder.cpp:413 stop DEMUX_STOP - video - ok
    09:15:00.726 <   > dvb/decoder.cpp:422 stop VIDEO_STOP - ok
    09:15:00.733 [   ] dvb/dvb.cpp:1254 DVBChannelStateChanged start release channel timer
    09:15:00.740 {   } skin.py:1034 readSkin [SKIN] processing screen QuitMainloopScreen:
    09:15:00.748 [ E ] gdi/accel.cpp:357 accelAlloc accel alloc failed
    
    09:15:00.748 [ E ] gdi/gpixmap.cpp:140 gSurface ERROR: accelAlloc failed
    09:15:00.934 {   } Screens/Screen.py:150 show [SCREENNAME]  QuitMainloopScreen
    09:15:00.935 {   } Screens/Standby.py:293 close [Standby] quitMainloop #1
    09:15:00.936 {   } skin.py:847 readSkin [SKIN] Parsing embedded skin <embedded-in-'TryQuitMainloop'>
    09:15:00.938 {   } skin.py:1034 readSkin [SKIN] processing screen <embedded-in-'TryQuitMainloop'>:
    09:15:00.941 {   } skin.py:847 readSkin [SKIN] Parsing embedded skin <embedded-in-'SimpleSummary'>
    09:15:00.943 {   } skin.py:1034 readSkin [SKIN] processing screen <embedded-in-'SimpleSummary'>:
    09:15:00.947 [ E ] gui/ewindowstyle.cpp:35 getStyle eWindowStyleManager::getStyle(style_id=1): NOT FOUND
    09:15:00.950 {   } Screens/Screen.py:150 show [SCREENNAME]  ['TryQuitMainloop_summary', 'SimpleSummary']
    09:15:00.955 {   } Screens/Screen.py:150 show [SCREENNAME]  TryQuitMainloop
    09:15:00.956 [   ] driver/rcinput.cpp:23 handleCode 0 160 1
    09:15:00.958 {   } Screens/InfoBarGenerics.py:204 actionA KEY: 352 1 KEY_OK OK
    09:15:00.965 { E } Components/InputHotplug.py:33 connectionLost connectionLost? [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.
    ]09:15:00.965 {   } Components/InputHotplug.py:33 connectionLost 
    09:15:00.973 {   } mytest.py:629 runScreenTest [mytest.py] normal shutdown
    09:15:00.977 {   } mytest.py:705 runScreenTest ====================================================================================================
    09:15:00.977 {   } mytest.py:728 runScreenTest [mytest.py] set next wakeup type to 'record-timer' and starts in standby
    09:15:00.978 {   } mytest.py:731 runScreenTest [mytest.py] set next wakeup time to Sab, 2018/02/03 12:19:40
    09:15:00.979 {   } mytest.py:743 runScreenTest ====================================================================================================
    09:15:01.227 {   } Plugins/Extensions/EPGImport/log.py:25 write [EPGImport] autostart (1) occured at 1517645701.23
    09:15:01.227 {   } Plugins/Extensions/EPGImport/log.py:25 write [EPGImport] Stop
    09:15:01.231 {   } Plugins/Extensions/AutoTimer/AutoTimer.py:100 readXml [AutoTimer] No changes in configuration, won't parse
    09:15:01.238 {   } Plugins/SystemPlugins/VFDControl/plugin.py:293 sessionstart [F3 LED] sessionstart
    09:15:01.238 {   } Plugins/SystemPlugins/VFDControl/plugin.py:288 controliniVfd [F3 LED] Stopping !!
    09:15:01.414 [ E ] ../lib/base/cfile.h:17 CFile error /proc/stb/vmpeg/1/dst_left [No such file or directory]
    09:15:01.414 [ E ] ../lib/base/cfile.h:17 CFile error /proc/stb/vmpeg/1/dst_top [No such file or directory]
    09:15:01.415 [ E ] ../lib/base/cfile.h:17 CFile error /proc/stb/vmpeg/1/dst_width [No such file or directory]
    09:15:01.415 [ E ] ../lib/base/cfile.h:17 CFile error /proc/stb/vmpeg/1/dst_height [No such file or directory]
    09:15:01.415 [ E ] ../lib/base/cfile.h:17 CFile error /proc/stb/vmpeg/1/dst_apply [No such file or directory]
    09:15:01.416 [   ] dvb/db.cpp:606 saveServicelist ---- saving lame channel db
    09:15:01.444 [   ] dvb/db.cpp:728 saveServicelist saved 98 channels and 909 services!
    09:15:01.460 [   ] dvb/dvb.cpp:1265 releaseCachedChannel release cached channel (timer timeout)
    09:15:01.460 [   ] dvb/dvbtime.cpp:581 DVBChannelStateChanged [eDVBLocalTimerHandler] remove channel 0x13d3d60
    09:15:01.461 [   ] dvb/epgcache.cpp:616 DVBChannelStateChanged [eEPGCache] remove channel 0x13d3d60
    09:15:01.462 [   ] dvb/dvb.cpp:1248 DVBChannelStateChanged stop release channel timer
    09:15:01.465 [   ] dvb/epgcache.cpp:1384 save [EPGC] store epg to realpath '/media/hdd/epg.dat'
    09:15:01.474 [   ] dvb/epgcache.cpp:1430 save [EPGC] 2752 events written to /media/hdd/epg.dat
    09:15:01.517 [   ] dvb/dvbtime.cpp:251 ~eDVBLocalTimeHandler set RTC to previous valid time
    09:15:01.517 [   ] dvb/dvbtime.cpp:49 setRTC [eDVBLocalTimerHandler] set RTC Time
    09:15:01.517 [   ] base/init.cpp:58 setRunlevel - (41) eServiceFactoryDVD
    09:15:01.518 [   ] base/init.cpp:58 setRunlevel - (41) eServiceFactoryHDMI
    09:15:01.518 [   ] base/init.cpp:58 setRunlevel - (41) eServiceFactoryM2TS
    09:15:01.518 [   ] base/init.cpp:58 setRunlevel - (41) eServiceFactoryMP3
    09:15:01.518 [   ] base/init.cpp:58 setRunlevel - (41) eServiceFactoryFS
    09:15:01.518 [   ] base/init.cpp:58 setRunlevel - (41) eServiceFactoryDVB
    09:15:01.518 [   ] base/init.cpp:58 setRunlevel - (41) Encoders
    09:15:01.518 [   ] base/init.cpp:58 setRunlevel - (41) Stream server
    09:15:01.519 [   ] base/init.cpp:58 setRunlevel - (40) eServiceCenter
    09:15:01.519 [   ] base/init.cpp:58 setRunlevel - (35) CI Slots
    09:15:01.519 [   ] base/init.cpp:58 setRunlevel - (35) CA handler
    09:15:01.519 [   ] base/init.cpp:58 setRunlevel - (30) eActionMap
    09:15:01.519 [   ] base/init.cpp:58 setRunlevel - (22) Hdmi CEC driver
    09:15:01.520 [   ] base/init.cpp:58 setRunlevel - (21) input device driver
    09:15:01.593 [   ] base/init.cpp:58 setRunlevel - (20) DVB-CI UI
    09:15:01.593 [   ] base/init.cpp:58 setRunlevel - (20) UHF Modulator
    09:15:01.593 [   ] base/init.cpp:58 setRunlevel - (20) RC Input layer
    09:15:01.593 [   ] base/init.cpp:58 setRunlevel - (20) misc options
    09:15:01.593 [   ] base/init.cpp:58 setRunlevel - (20) AVSwitch Driver
    09:15:01.594 [   ] base/init.cpp:58 setRunlevel - (15) eWindowStyleManager
    09:15:01.594 [   ] base/init.cpp:58 setRunlevel - (10) gRC
    09:15:01.594 [   ] gdi/grc.cpp:57 ~gRC waiting for gRC thread shutdown
    09:15:01.595 [   ] gdi/grc.cpp:59 ~gRC gRC thread has finished
    09:15:01.595 [   ] base/init.cpp:58 setRunlevel - (9) GFBDC
    09:15:01.610 [   ] base/init.cpp:58 setRunlevel - (9) gLCDDC
    09:15:01.611 [   ] base/init.cpp:58 setRunlevel - (9) Font Render Class
    09:15:01.611 [   ] base/init.cpp:58 setRunlevel - (8) graphics acceleration manager
    09:15:01.612 [   ] base/init.cpp:58 setRunlevel - (5) Tuxtxt
    09:15:01.612 [   ] base/init.cpp:58 setRunlevel - (1) Background File Eraser
    09:15:01.614 [   ] base/init.cpp:63 setRunlevel reached rl -1
    09:15:01.615 [   ] dvb/frontend.cpp:653 closeFrontend close frontend 1
    TuxTxt cache cleared
    cleaning up
    TuxTxt cache cleared
    TuxTxt cache cleared
    cleaning up
    TuxTxt cache cleared
    Again, I want to stress that boot-up is nonetheless always normal and extremely fast, and the box works excellently, but I was wondering if this might be part of the reason behind that freezing issue. By all means, I'm no expert, but what I noticed in this log is that in the first second, which is basically when the skipping occurs, there's something going on with the files lingering in the timeshift folder. As a matter of fact, I started noticing this skipping thing after enabling automatic timeshift, which I didn't have when I was using that 64GB stick. Which is why I decided to test the 64GB version as well this morning with automatic timeshift enabled, and the same skipping occured several times.

    So, is this skipping thing normal behaviour for openATV if the timeshift folder is not empty or something at boot-up? I mean, have you guys ever had something like this happen and could this thing at boot-up potentially cause that freezing issue when timeshifting, or is that irrelevant? The thing is, I use a power strip for this box and other stuff, and often shut it down at night, so perhaps before doing that I should somehow properly power down the box by putting it into deep standy so that the timeshift files get flushed or something along those lines. Sorry for all the questions, but I'm really a newbie at this and would like to figure out how to fix this problem. Thanks in advance for any answers.

  12. #9
    Avatar von Papi2000
    Registriert seit
    20.04.2013
    Beiträge
    18.336
    Thanks (gegeben)
    3180
    Thanks (bekommen)
    5780
    Total Downloaded
    595,11 MB
    Total Downloaded
    595,11 MB
    ReceiverDankeAktivitäten
    Box 1:
    GB Q4K-SC / UE4K-SC / UE4K-C
     
     
    Box 2:
    GigaBlue Q-SSC / Q+-SSC
     
     
    Box 3:
    DM900uhd-SS / Vu+Duo
     
     
    Box 4:
    E4HD ZGemma H7/H9 SF8008
     
     
    Box 5:
    diverse andere . . .
     
     
    Those extra large USB-Devices typically have very bad transferrates. And for Timeshift, you need at least about 10MB for small blocksizes in write and read parallel. So try using a device as small as 32GB first. Those have in most times better performance.
    Geändert von Papi2000 (03.02.2018 um 23:06 Uhr)
    Grüßle
    Ralf
    ------------------------------------------------------------------------------------------------------------------------
    Gigablue Quad 4K-multi,Quad+-SSC,Quad-SSC, andere Gigas, Astra 19.2E, UniCable & KabelBW, oATV/ teamBlue
    (weitere: DM900uhd,Vu+Duo,Technisat,Edision),PC-DVB-S/C/T,PCH-A110,Xtreamer,BDP5200
    UE32C5700,Philips65OLED865,Tosh40xyz
    ---- Einen Receiver kann sich jeder kaufen - Eine stabile E²-Box muß man sich verdienen! ----



  13. Thanks veronik96 bedankten sich
  14. #10
    Anfänger
    Registriert seit
    09.02.2016
    Beiträge
    28
    Thanks (gegeben)
    24
    Thanks (bekommen)
    1
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Okay, thanks a lot for the tip. As a matter of fact, the 64GB doesn't seem to have any freezing issues at all, I'll just stick with that one then.

    But how about that boot-up thing I described, is it a non-issue? Do you have any idea why that happens and is it in fact related to permanent timeshift?


Seite 1 von 2 12 LetzteLetzte

Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •  
Alle Zeitangaben in WEZ +1. Es ist jetzt 18:30 Uhr.
Powered by vBulletin® Version 4.2.5 (Deutsch)
Copyright ©2021 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.
Resources saved on this page: MySQL 5,88%
Parts of this site powered by vBulletin Mods & Addons from DragonByte Technologies Ltd. (Details)
vBulletin Skin By: PurevB.com