AutoTimer issue - again 2

[leshay]

Hi

This is an issue that I remember being discussed and I thought was fixed a while ago, but apparently not.

I had clashes while trying to add a Timer for AirCrash Confidential, Quest HD, Tues 15th, 2100hrs for 60min. Box Pre and Post Recording Margins are set at zero.

AutoTimer set Timers already for Catastrophy start 2200, Secret Life of the Holiday Resort start 2200, Colony start 2200, The Secret Life of the Zoo ending 2100 and New: Animal Airport starting 2100 ending 2200.

I have 4 tuners separately fed from a Quad LNB.

The clash showed ALL of the item I listed as being involved in the clash!

Obviously, the Timer attemp is NOT REALLY clashing at all and should succeed.

Why can VIX not adjust things to allow this Timer?

[ccs]

There is a clash condition because consecutive timers (with the same end and start times) requiring different multiplexers (in terrestrial lingo), require 2 tuners.

[leshay]

Hi

Yres, but my point is that VIX should be able to adjust things (start/end/duration) such that 2 tuners are not required.

I do know that this apparent clash CAN be dealt with - my own app can manage it (which I am already considering going back to for AutoTimers)

[abu baniaz]

There is a clash condition because consecutive timers (with the same end and start times) requiring different multiplexers (in terrestrial lingo), require 2 tuners.

I am sure we catered for this situation

Autotimer
https://github.com/oe-alliance/enigm...ca3f1a7b728e29

PLI
https://github.com/OpenPLi/enigma2/c...7a38e78da24ec5

[leshay]

I am sure we catered for this situation

Autotimer
https://github.com/oe-alliance/enigm...ca3f1a7b728e29

PLI
https://github.com/OpenPLi/enigma2/c...7a38e78da24ec5

Hi

I did remember correctly when I thought it had been fixed. Unfortunatly, it seems to have regressed because I still had/have the above conflicts.

Why not allow the pre/post recording maargins to be made negative - that would allow the user to decide prioroty of less conflict versus loss of start/end of recording?

BTW: that is the method I use in my own app. Having used for many months with no issues of un-needed conflicts and not had any problems with loss of start/ending of recordings.

[birdman]

I am sure we catered for this situation

Only if all (or most) of the ATs involved had no pre- or post-padding.

[abu baniaz]

Only if all (or most) of the ATs involved had no pre- or post-padding.

Which was the case reported by the OP

Pre and Post Recording Margins are set at zero.

Can yo have a look at improving this please?

[leshay]

"Pre and Post Recording Margins are set at zero"

Can yo have a look at improving this please?

Hi

What do you mean?
I do have pre and post margins set at zero.

[ccs]

Hi

What do you mean?
I do have pre and post margins set at zero.

That is what abu is saying, that you do have pre and post margins set to zero, so the fix needs looking at again.

[leshay]

Hi

Ah OK then - I thought the comment was aimed at me for having them set at zero.

[ccs]

I am sure we catered for this situation

Autotimer
https://github.com/oe-alliance/enigm...ca3f1a7b728e29

PLI
https://github.com/OpenPLi/enigma2/c...7a38e78da24ec5

If I'm looking in the right place (for the latest version of Autotimer.py), I can see no reference to the 30 second increment mentioned in the commit.

[birdman]

If I'm looking in the right place (for the latest version of Autotimer.py), I can see no reference to the 30 second increment mentioned in the commit.

It starts on line 655.

[ccs]

… I guess I'm not looking in the right place then.

https://github.com/oe-alliance/enigma2-plugins/blob/master/autotimer/src/AutoTimerEditor.py

[ccs]

… I guess I'm not looking in the right place then.

https://github.com/oe-alliance/enigma2-plugins/blob/master/autotimer/src/AutoTimerEditor.py

Right place, wrong file!, apologies all round.

[ccs]

duplicate post, can't even get that right.