[VU+ Duo2] Timer Sanity Error (2 conflicting timers on a dual-dish/dual-tuner system)

[LeeC22]

Okay, now I can get round to posting some new information.

Setting the preferred tuner settings (either of them) has no effect on a conflict happening or not. Just one point on this, my settings were at auto and none respectively, I don't remember changing them at any point but can you confirm if that is the default setting please?

Setting a recording on any Astra channel that ends at the same time as an existing NHK World HD timer causes no conflict.
Setting a timer on another satellite (HotBird or 19.2e) that ends at a time that overlaps an existing NHK World timer causes a timer conflict.
Setting a recording on 19.2e that ends at the same time as an existing NHK World timer, also causes a conflict.

I have noticed that there is an option to turn off timer conflict messages. So what I am going to do next, is to set a timer on NHK World for a random programme over the weekend and then to set a matching timer on another satellite that would cause a conflict... that is to identify a clashing programme. I will then go and turn that setting off, set the conflicting timer again and see what the end result is for both timers.

All of this could be a glitch in the conflict detection code and it could be throwing up false positives for timers the system is more than capable of dealing with. The worst case scenario is two random programmes don't get recorded. But the best case scenario works out if the conflict is genuine and causes a problem or not. As I think of more scenarios to test this problem, I will try them and report back on the results.

 

[birdman]

In no situation is there ever an NHK World HD programme starting first... which is exactly what post #7 said.

Apologies. Somehow I read post #7 differently. I can't see how I did.....

 

[birdman]

Sorry again. I've only just noticed the version you are using. I thought you were on a recent release...
There is an issue in the conflict code (see this thread) which has been fixed.
The fix went into version 4.0_002.

If you want to confirm this fixes your problem the TimerSanityConflict.py file hasn't changed from 3.2.033 until now (apart from this fix), so perhaps your 3.2.032 is the same. So you could put the *.py file from this:

View attachment TimerSanityCheck.zip

into /usr/lib/enigma2/python/Components (but first take a backup copy of TimerSanityConflict.pyo from there) and check it fixes the issue.
Or upgrade to the latest release.

 

[Rob van der Does]

Sorry again. I've only just noticed the version you are using. ....

Ahh, good catch, I didn't notice that either
We should not be chasing shadows by looking into possible issues in ancient builds.
So indeed: please flash a recent build and see how you go from there.

 

[LeeC22]

Ahh, good catch, I didn't notice that either
We should not be chasing shadows by looking into possible issues in ancient builds.
So indeed: please flash a recent build and see how you go from there.

I won't be able to do that until in the new year. Historically, flashing to a recent build has sometimes left me with more problems that an older build and at this time of year, I have to minimise any kind of problems... that's a long and complex "personal issues" story that you don't want to hear. So if using that fix, or in fact turning off the timer conflict warnings solves the problems, I'll have to go with that for now.

Once I get the next couple of weeks out of the way, then I can look at doing an update.

But as for this part directly:

We should not be chasing shadows by looking into possible issues in ancient builds.

Rolling the dice on a new version, isn't a reliable way to deal with isolated issues in an older version... ViX doesn't have a history of reliability that makes that a valid option. Every new release carries with it an opportunity for something that does work, to turn into something that doesn't... and that's usually what I have found to be the case. On more than one occasion I have updated, then rolled back within a day or so. I don't need that level of hassle for a single module of faulty code. I have my own projects to write and test, I don't have the time to be a tester on other people's software as well, at the possible expense of my satellite receiver not working as it should. So when an older build has a proven history, that's the version I update to.

I know some people don't like dealing with users of older versions but that's the cost of releasing constantly updating software... in fact, it's the cost of being a software developer. Not everyone chooses to jump into the boat the minute a new version of anything appears. With the software I write, I respect the user's choice to use whatever version they choose to use and will support them 100% with any problems they have. That's just 30+ years of ingrained mentality... I can't operate any other way than that.

Anyway, I really do have to concentrate on the three projects I have ongoing, so I am happy to consider this resolved with that python module that birdman provided. I will try that and unsubscribe from the threads so that it can be left to sink.

 

[Rob van der Does]

.... On more than one occasion I have updated, then rolled back within a day or so. ...

I really can't believe that to be true. Being a tester here I update to every single beta-version for my main household box, which means an update virtually every day, and it very seldom (if ever) happens that I need to roll back (to which I'm prepared, as I always make a full backup when updating).
So that's quite contradictory to your statement. And then you only use updates we release as we tested them to be working fine...
And besides: if that would be true, the forum would be overloaded with issues.

Anyway: we're only maintaining and developing from the last version, not old builds. And switching off conflict management isn't a good idea.....

 

[LeeC22]

No offence but what you believe has no bearing on how I maintain my system but I do take offence at being told what I say is untrue, when you have no proof or justification to determine otherwise.

How you use your system is in no way a reflection of how I use my system. How you have your box configured is no reflection on how my box is configured. Basically, your experience with your boxes is totally irrelevant with respect to my box. Do you know how long I have had my box? Do you know how many times I have updated? Do you know what my criteria is for being satisfied with the performance of a piece of software? Of course you don't, yet you still decide to judge my statement and credibility... which I find harsh (and ironic) considering two testers took over 20 posts to notice the version I was using.

I've been on these forums long enough to see the "It works fine for me, therefore it must work fine for you" consensus that seems to be thrown out there. That is the main reason I try as much as possible to sort my own problems out, or simply roll back, rather than bring issues up on here and have to get faced with that. But I don't call people on here liars and I don't expect to get that back in my face. If you don't believe something, that's fine but don't insinuate that people are lying, when their experiences don't match up with yours. What I find particularly abhorrent, is how you have jumped on my back for saying "On more than one occasion"... more than one means more than one, not ten, not five... just more than one. And yes, it has happened on more than one occasion.

The fact is, I put a fair amount of effort into trying to diagnose this problem, which took me away from what I really should have been doing. I was trying to let this thread go as the matter seems to have been resolved. I suggest you show people the deserved respect when they put that effort in and you learn to respect their opinions on how they handle their own equipment.

I am going to request an admin lock this thread as I really don't have time to engage in an insinuation war. I've got six hours of coding ahead at least, so I'd like to get that done if at all possible. I tried to unsubscribe but my settings said I had no subscribed threads, so I will have to use the link in the last notification email. Failing that I'll have to rely on my ignore list... I'd prefer it if people just left it alone.