Jump to content


Photo

Autotimer is slow


  • Please log in to reply
25 replies to this topic

Re: Autotimer is slow #21 Weiti

  • Senior Member
  • 53 posts

0
Neutral

Posted 26 January 2015 - 22:58

update: 2.1 runs with 2 min timeout. greenscreen happens when time is up



Re: Autotimer is slow #22 Dimitrij

  • PLi® Core member
  • 9,994 posts

+338
Excellent

Posted 27 January 2015 - 06:48

_mod 2.1 crashes

[AutoTimer] No changes in configuration, won't parse
lookup events with 'The Knick' as title (case sensitive)
main thread is non-idle! display spinner!
[AutoTimer] Won't modify existing timer because either no modification allowed or repeated timer
[AutoTimer] We found a timer (similar service) with same description, skipping event
[AutoTimer] We found a timer (similar service) with same description, skipping event
[AutoTimer] We found a timer (similar service) with same description, skipping event
action ->  WizardActions back
ERROR reading PES (fd=51) - Value too large for defined data type
poll: unhandled POLLERR/HUP/NVAL for fd 51(8)
lookup events with 'Life' as title (case sensitive)
main thread is non-idle! display spinner!
[AutoTimer] We found a matching recorded movie, skipping event: Life
[AutoTimer] We found a matching recorded movie, skipping event: Life
[AutoTimer] We found a matching recorded movie, skipping event: Life
ERROR reading PES (fd=51) - Value too large for defined data type
poll: unhandled POLLERR/HUP/NVAL for fd 51(8)
lookup events with 'Up All Night' as title (case sensitive)
main thread is non-idle! display spinner!
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[AutoTimer] We found a matching recorded movie, skipping event: Up All Night
[ePopen] command: ('hdparm', 'hdparm', '-y', '/dev/sda')
[ePopen] command: ('hdparm', 'hdparm', '-y', '/dev/sdb')
ERROR reading PES (fd=51) - Value too large for defined data type
poll: unhandled POLLERR/HUP/NVAL for fd 51(8)
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
Failure: exceptions.ValueError: Reactor no longer active, aborting.
PC: 00462a28
00000000 00000001 00000011 00000000
00000015 018bd750 0000001c 016b2ed8
00040000 00000001 00000000 63616265
00000002 2e676f6c 00000000 4f746c75
018bd0d0 019412e0 00000017 00000017
7ff11c10 005ba084 00000001 7ff11df4
0000000e 76a891e4 76af10b8 00000000
00643930 7ff11b78 7ff11d10 00585d44
-------
getResolvedKey config.plugins.crashlogautosubmit.sendAnonCrashlog failed !! (Typo??)
getResolvedKey config.plugins.crashlogautosubmit.addNetwork failed !! (Typo??)
getResolvedKey config.plugins.crashlogautosubmit.addWlan failed !! (Typo??)
main thread is non-idle! display spinner!
Killed

I tried the version from plugins menue, the number changed so I thought it could be a newer version. But it still records absolutely everything with the same name. 

Does someone have a .ipk from the old autotimer, not the _mod version?

eEPGCache-->Milo


Edited by Dimitrij, 27 January 2015 - 06:49.

GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Autotimer is slow #23 Weiti

  • Senior Member
  • 53 posts

0
Neutral

Posted 28 January 2015 - 20:41

eEPGCache-->Milo

 

I dont understand this. 


Edited by Weiti, 28 January 2015 - 20:42.


Re: Autotimer is slow #24 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 29 January 2015 - 15:29

He means that he thinks it's caused by a change by MiLo in the EPG code.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Autotimer is slow #25 MiLo

  • PLi® Core member
  • 14,045 posts

+298
Excellent

Posted 29 January 2015 - 17:32

I think he is not running the AutoTimer from the OpenPLi repository.
Real musicians never die - they just decompose

Re: Autotimer is slow #26 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 30 January 2015 - 20:25

We recently merged the AutoTimer from dimitrij which is quite a lot newer than our version. And it has been working for some time.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.



1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users