PDA

View Full Version : Back to Back Zapped timers not working



theredindian
23-10-17, 19:11
Hi,

I have created 3 zapped timers for programs across 3 channels but they don't appear to be working despite being enabled.

I have tried disabling the conflict timer detection but it's still not working. Individual zapped timers are working fine, just not the consecutive zapped timers.

I'm using vix image 5.0.027.

Any ideas what I am doing wrong?

adm
23-10-17, 20:12
Hi,

I'm using vix image 5.0.027.

Any ideas what I am doing wrong?

Possibly, timer bug fixes in 5.0.28 onwards

See post number #32 onwards in the following thread
http://www.world-of-satellite.com/showthread.php?57337-Sleep-Timer-Function-on-Vix-images/page3

birdman
24-10-17, 01:00
Hi,

I have created 3 zapped timers for programs across 3 channels but they don't appear to be working despite being enabled.In what way do they not work?

None of them is handled?
One of them is handled?
There is an issue with setting them?



I have tried disabling the conflict timer detectionTo what intent (that's the reason for my third query above).


Individual zapped timers are working fine, just not the consecutive zapped timers.Could you define what you mean by "consecutive zapped timers"?
Are you setting up three timers for one hour programmes but with gaps between them of hours or are these three programmes that run such that one starts immediately the previous one finishes?


Any ideas what I am doing wrong?Not without some detail to enable a reproduction.

birdman
24-10-17, 01:02
Possibly, timer bug fixes in 5.0.28 onwardsUnlikely to be the issue here as that's to do with the mechanism for enacting a timer. With that bug they should still run, but might be a little late in doing so (which doesn't sound as though ii's what is happening).

theredindian
24-10-17, 05:13
In what way do they not work?

None of them is handled?
One of them is handled?
There is an issue with setting them?


To what intent (that's the reason for my third query above).

Could you define what you mean by "consecutive zapped timers"?
Are you setting up three timers for one hour programmes but with gaps between them of hours or are these three programmes that run such that one starts immediately the previous one finishes?

Not without some detail to enable a reproduction.

If I set 3 zapped timers to run as follows none of them will execute;


Timer 1 zap BBC 1 HD from 17:59
Timer 2 zap BBC London from 18.29
Timer 3 zap channel 4 HD from 18.59


The timers will be in my list and you can see them in the epg guide. But for some reason it doesn't execute.

I think it might be because the timers are set to start a minute before the program starts hence the slight overlap. So I tried disabling the timer conflict detection. But that did not work either.

There might be a bug with this particular image release as the problem only started after updating around 4 weeks ago.

I will try updating to the latest release as see if that resolves the problem.

adm
24-10-17, 09:06
Just as an experiment with build 5.0.029 I found 3 programs on 3 different channels that started within 10 minutes of each other and set a zap timer for each of them - and then watched a 4th channel. All 3 zap timers changed channel for me. When the 2nd zap occurred the 1st program was still running but the box changed channels and when the 3rd zap occurred both the 1st and 2nd programs were still running and the box changed channels again as expected.

adm
24-10-17, 09:19
Unlikely to be the issue here as that's to do with the mechanism for enacting a timer. With that bug they should still run, but might be a little late in doing so (which doesn't sound as though ii's what is happening).

On the image with the bug doesn't a record timer still work because it has both a start and end time and if the end time isn't reached the timer will still kick in?
With a zap only timer there is no end time - or just the start and end times are the same?

theredindian
24-10-17, 19:16
Looks like there was a bug in that particular image release as it seems to be working fine after updating to the latest version

birdman
25-10-17, 00:59
On the image with the bug doesn't a record timer still work because it has both a start and end time and if the end time isn't reached the timer will still kick in?
With a zap only timer there is no end time - or just the start and end times are the same?You're probably (almost certainly) right. For some reason I was thinking a Zap timer had an end time too (which I suppose would make it a "reserve tuner" timer...)