[ViX_Misc] EPG Refresh, iEPG and VPS

[ronand]

Autotimers have been working perfectly from the start but you do need to specify it when creating it (I dont think they are intended to be enabled by default). When setting up the autotimer just "ActivateVPS=YES" and then the second line "control recording completely by service" and that seems to work fine for me. The soaps are recording fine with no bits missing

 

[ronand]

Deary me. I went in and changed the autotimer defaults and enabled the vps settings there. Now they will be on by default for all new autotimers.

 

[ccs]

Deary me. I went in and changed the autotimer defaults and enabled the vps settings there. Now they will be on by default for all new autotimers.

Are you suggesting that turning the option off doesn't work?

 

[ronand]

Enabling VPS by default in the plugin has nothing to do with autotimers (or the timers created by them).

Enabling VPS recording by default for autotimers is set in the autotimer plugin

 

[ccs]

Enabling VPS recording by default for autotimers is set in the autotimer plugin

I understand that, it was the "Deary me" that confused me.

 

[ronand]

Just hitting myself on the head that's all!

 

[birdman]

Well that answers that one. I was finding that it was enabled on a few more channels but couldn't see a pattern. I suppose it always helps to RTFM! I will do a short recording on 5.4.008.002 to check if thats the case.

That notice is not necessarily related to the current code (which is v1.33).

For some reason all of the VPS threads end up having masses of, "I did this and it didn't work", followed by, "when I tired it today it was different" followed by several other people all chipping in with confusing references (no context) saying it was the same for them.

None of this helps at all.

 

[birdman]

All channels essentially support VPS on irish/UK terrestrial and sat.

That may be true, but the VPS plugin can't detect that for UK Freeview when it looks for it.

 

[Joe_90]

I understand that, it was the "Deary me" that confused me.

Threw me also!

VPS works very well on BBC/ITV/C4, where the programme changeover in the EIT (which is what VPS is monitoring) actually coincides with the programme start. This means that if a programme starts later than scheduled (usually Graham Norton on Friday night) then it will catch the entire programme properly. It's of no benefit on C5 (or possibly others on sat) or on Saorview, where the programme EIT changes happen at the scheduled EPG time, irregardless of when the programme actually starts. If it's just a few minutes early or late, then you're better off with some padding set in your timer defaults.

 

[ccs]

That notice is not necessarily related to the current code (which is v1.33).

For some reason all of the VPS threads end up having masses of, "I did this and it didn't work", followed by, "when I tired it today it was different" followed by several other people all chipping in with confusing references (no context) saying it was the same for them.

None of this helps at all.

Only reporting what we were seeing.

There's plenty of context, but when something works one day and not the next it was very difficult to understand what was the root cause, but we got there in the end.

 

[Joe_90]

That may be true, but the VPS plugin can't detect that for UK Freeview when it looks for it.

Detect what on Freeview? @ccs has reported it working for him IIRC. Freeview should have the programme change and running status in the EIT same as on Freesat/Sky. Even our basic terrestrial service in Ireland (which is based on Nordig standards) triggers the programme change and running status in the EIT.

 

[birdman]

Detect what on Freeview? @ccs has reported it working for him IIRC.

Whatever it wants to detect when it pops up the window saying it is trying to detect it and, when it fails, asks 1."No", 2."Yes" or 3."Yes, and don't ask again".

All I'm doing is fixing the (previously broken) code that drives the menus and settings. The underlying mechanisms are unaltered.

 

[ccs]

That notice is not necessarily related to the current code (which is v1.33).

Maybe not but it was posted only a few months before 1.3 came in (in 2012).

 

[birdman]

There's plenty of context, but when something works one day and not the next it was very difficult to understand what was the root cause, but we got there in the end.

Got where in the end?

That's the problem.

As far as I can tell some people still thinks there is a problem. But I have to read back through 20+ posts trying to find it and discover whether any of the others refer to it.

 

[ccs]

I give up.

 

[Joe_90]

Whatever it wants to detect when it pops up the window saying it is trying to detect it and, when it fails, asks 1."No", 2."Yes" or 3."Yes, and don't ask again".

All I'm doing is fixing the (previously broken) code that drives the menus and settings. The underlying mechanisms are unaltered.

It's not failing! It does this every time when you set a timer on a new channel. It's just asking you to confirm whether you want the plugin to operate on the recording on this channel this time or to assume that futher recordings on this channel are to be ok without asking any question in future. Try respond "Yes and don't ask again" - vps will write an entry into the timers_vps.xml file and will record the programme.

 

[birdman]

It's not failing!

It is failing to detect something.
It is carrying out a test and discovers it can't get a result one way or the other.

Note that I did not say the VPS plugin was not working, just that the plugin itself reports than it can't detect something and asks whether you want to use it anyway.

 

[birdman]

I give up.

But I can't, as somewhere on here are reports of things not working correctly.

 

[ccs]

But I can't, as somewhere on here are reports of things not working correctly.

Such as ??

Try starting here, https://www.world-of-satellite.com/...h-iEPG-and-VPS&p=510202&viewfull=1#post510202

the explanation took some finding out.

 

[Huevos]

Something wrong there. Those last two entries are shown as on/off switches, but actually each has 3 possible values No, Yes(safe mode) and Yes. They are both ConfigSelection entries.

Something wrong in your skin?

No nothing wrong with the skin. With ConfigSelections it is a user option to show switches for yes/no types.

pixmap = "menu_on" if self._descr in (_('True'), _('true'), _('Yes'), _('yes'), _('Enable'), _('enable'), _('Enabled'), _('enabled'), _('On'), _('on')) else "menu_off" if self._descr in (_('False'), _('false'), _('No'), _('no'), _("Disable"), _('disable'), _('Disabled'), _('disabled'), _('Off'), _('off'), _('None'), _('none')) else None