jeanclaude

why waste your time on this ? not useful :

you set up a recording, this new recording has a conflict, the recorder conflict list appears

here you solve the conflict in any way you like, either by de-activating other timer(s) or by changing the start/end times of the new or the existing timers.

once the conflict is solved, the new timers are saved in memory.

any automatic process will only create more incertainties. Don't do it.

Pr2 does have a point, though ....... It's you who setup the timers so it's up to you to make sure that those recordings are possible at all.

but the system will help you by pointing out any timer conflicts when an impossible request is being made - and again it will be up to you to decide how to solve that conflict.

the golden rule is that the more tuners you have, the less problems you will have setting any recorder timings.

de BBC HD kanalen ? de FEC is gewijzigd naar 3/4, dus even opnieuw inscannen met de juiste FEC en het zou terug moeten werken.

OK - checked the timerlist again - by now all of the timers have been set by the modified autotimer script.

result : no more double timer entries to be found !

good job, dimitrij

enigma2 is unix, en die werkt niet met driveletters dus een ':' is waarschijnlijk wel toegelaten, hoewel windows hiervan op zijn bek gaat (ik lees dat je totalcommander gebruikt dus je maakt contact met je ET8000 via windows dus géén ':' in de namen gebruiken'

bedenk ook dat unix case-sensitive is (windows niet) dus hoofdletters en kleine letters moeten exact hetzelfde zijn

de lengte van een folder maakt in unix ook niet veel uit denk ik (is wel beperkt in windows)

maar hoe zet je eigenlijk een timer ? Je kan daar toch geen directory intoetsen ? Je moet eerst de directory aanmaken, dan deze aanmelden in de lijst van opnamefolders, en dan kan je vanuit het timer-scherm via de links/rechts pijltjes de juiste folder aanduiden.

je zet toch geen timers door via totalcommander het bestand timers.xml te editeren ?

ik zou graag hebben dat de klinkers bij de ondertiteling in het geel getoond worden, en de medeklinkers in het blauw. Lijkt me veel duidelijker. En als het even kan ook de cijfers en de leestekens in het rood. En niet vergeten om alle blanco's te onderlijnen zodat het absoluut duidelijk is dat er een blanco staat !

much less, sometimes a timer is inserted which generates a timer conflict, after which all timer events are inserted as "deactivated"

so I still check the timers list daily

but generally speaking I have very few problems any more 

new autotimer.py installed & box restarted - we'll see how this goes.

standard settings for autotimer recordings are as follows :

start 9 minutes before EPG time, continue 15 minutes after EPG time ends.

Teo epg sources with different times... Use reytec -or- epg from dvb... Not -and-

I use only rytec, nothing else.

yes.

I notice 2 problems :

- first the creation of double timers, often with the same starting & ending time

- second (though much more rare nowadays) the insertion of a timer conflict

I'm performing regular (weekly) updates. I've learned to live with it, I'm checking the timerlist daily to de-activate the double timers and resolve any conflicts should they arise.

but the problem is still there, I'm just not making any noise about it any more 

plugins installed, compiled, new EPG loaded & autotimer plugin finished. Let's have a look at the result, shall we 

these are my running timers :

case 1. Let's check a listed timer - in this case Stargate Universe at 10.51 - and indee the timer conflict window popps up :

seems to be a conflict for next sunday, so no relation whatsoever with the Stargate Universe timer I was checking. let's try & solve the conflict and see what happens. I go to the last timer "Houdini & Doyle" and I press the yellow "OFF" button. I get the following popup :

and I'm returned to the timer conflict screen :

yes, this is what I want. the first timer is not automatically de-activated as in the past, and I can continue to de-activate selected timers until the conflict is resolved, after which the timer conflict screen disappears and I'm back in the timers list.

got it : I wanted to set a timer on the following programme :

but when trying to add this timer I got the following timer conflict screen :

those timers have nothing to do with the timer I wanted to add. So, looking at the timers list, I decide to deactivate the 2nd timer of the list "I didn't do it" (quite appropriate don't you think  ). Anyhow after moving to the 2nd timer and pressing the yellow "off" button, I get the following screen :

followed by :

as you can see, not only was the 2nd timer de-activated, but also the 1st ! As I want to keep the 1st recording, I try to activate it using the yellow button, but nothing happens. The conflict still doesn't seem to be solved, so I go to the 2nd "I didn't do it" it timer and de-activate it with the yellow button. The timer conflict screen now disappears, and I'm taken back to the EPG list I started off with, but still with no recording set. I am now able to set the requested recording, no more errors pop up.

but now I'm still missing the "Rizolli & isles" timer which was de-activated by the timers conflict screen. So I enter the timers list and locate this timer :

pressing the yellow "on" button ....... seems to activate the timer again. this is new as up to now the yellow button didn't react and I had to delete the timer entirely and re-create the timer manually. Could be due to the fact that this timer was originally set manually, and not by autotimer. Nevertheless, I suppose you can see that there is a problem - conflicting timers are being inserted from somewhere and the only source that's setting timers is me manually and the autotimer plugin.

fallback tuner werkt ook voor opnames op locale box, ook via timers. wel opletten met de timer conflict handling want die werkt niet goed meer indien er een fallback tuner gedefinieerd is (doordat de conflict handling routine niet kan bepalen of die fallback tuner op het gevraagde moment ook werkelijk zal beschikbaar zijn).

om opnames op de remote box te bekijken map je het beste een netwerk verbinding naar de hdd van de remote box, daarmee kan je alle opnames gewoon bekijken alsof ze op de locale box staan.

ok, one week later, let's try this one again.

I have copied your new "timersanitycheck.py" and have restarted enigma2. I am now UNABLE to reproduce the error :

so I get no more error if I want to start a new recording on CT2.

here are my current timers :

 timers.xml   136.08KB   2 downloads

this is the trace log of enigma2 :

 trace.txt   6.57MB   1 downloads

can I keep this "timersanitycheck.pyo" or do I need to reinstate the previous version (I took a copy, of course)

jeanclaude

Please add /usr/lib/enigma2/python/Components/TimerSanityCheck.py

install PuTTY

open PuTTY,enable log PuTTY

connected to the receiver

init 4

enigma2

and please  simulates a situation again.

ok, but this will have to wait until my next day "off" - I'll give it a try this weekend or next monday. I'll send the output as soon as I've been able to execute this test.