View Full Version : [ViX_Misc] EPG Refresh, iEPG and VPS
If I have EPG refresh configured to use iEPG-1 to provide EPG data
VPS plugin no longer starts and ends programmes - there are 2 scenarios, the timer never starts and eventually gets cancelled after 3+ hours; the timer starts and immediately ends.
If I switch to safe mode, then I can see the start and end recording signals displayed in the recording (at playback time)
If I purge the EPG data and use EPG refresh on a per channel basis, then VPS plugin accurately starts and ends recordings correctly.
Is the data provided by iEPG-1 somehow wrong, does EPG refresh process it incorrectly or is there some other error?
Thanks
OK, now I've got time on my hands again:
1. If I clear the epg and then use crossepg to populate the sky epg then the programme EITs that work with VPS ie the EIT matches that of the now/next EIT used for programme signalling but,
2. If I clear the epg and then tune to IEPG-1 to populate the sky epg then different EITs are downloaded, EIT does NOT match the now/next EIT and recordings fail
This can be examined by downloading the timers.xml and the EITs are massively different for given programmes - EIT for pointless today (after channel swap for covid) from IEPG is 49684; whereas from crossepg it is 18580
So EPG refresh is not fit for this purpose
abu baniaz
18-01-21, 18:19
EPG refresh is just a channel zapper. The code to do the zapping is built into Enigma2, but people obstruct request to add the functionality to add timers using Enigma2 and suggests we use EPG refresh.
There are two types of EIT EPG. Now/next is one type and changes while you are on the channel. Can you explain more by what you mane by EIT?
EPG refresh is just a channel zapper. The code to do the zapping is built into Enigma2, but people obstruct request to add the functionality to add timers using Enigma2 and suggests we use EPG refresh.
There are two types of EIT EPG. Now/next is one type and changes while you are on the channel. Can you explain more by what you mane by EIT?
Thanks for the quick response.
Yes EPG refresh is just a zapper, I get the same result by tuning to IEPG-1
The correct EIT is produced by crossepg - I'm unsure where this comes from (you know that black box that appears at the top of the screen)
If you look at the EIT number in timers.xml that comes from IEPG v crossepg (by adding a timer from one source, clearing the epg.dat) they are different numbers for the same programme, VPS uses the now/next EIT for programme signalling (it allocates the channel 10 mins before scheduled recording start by default) and waits for the EIT data to match that within the entry timer.xml; when that doesn't match you get a 0:00 recording or very short recording before VPS notices the EIT from now/next now no longer matches the now/next.
I come from a toppy background where EIT was used extensively
abu baniaz
18-01-21, 18:31
Posted in error. Please ignore.
alexwilmac
22-01-21, 06:34
VPS, unfortunately, very unfortunately, does not work any longer under 5.4, even 5.4.004 as well as in OBH 4.4.004, its derivative.
This is an already discussed problem. I find VPS, for the channels where it work, one of the most useful plugins.
That's why I'm not using these two images and went back to ViX 5.3 and OBH 4.3.
VPS, unfortunately, very unfortunately, does not work any longer under 5.4, even 5.4.004 as well as in OBH 4.4.004, its derivative.
This is an already discussed problem. I find VPS, for the channels where it work, one of the most useful plugins.
That's why I'm not using these two images and went back to ViX 5.3 and OBH 4.3.Sorry, the changes made to VIX in 5.4.xxx have made VPS display and selection awkward (but it functions in webif and for autotimers), BUT the issue I describe existed prior to 5.4.xxx.
My original post is 10 months old predating 5.4.xxx, if you follow the steps to replicate on 5.3.xxx then the issue as reported (EIT mismatch between iepg-1 and the actual channels is there)
Thanks
Sent from my IN2013 using Tapatalk
alexwilmac
22-01-21, 10:47
Now I don't have ViX 5.3 installed any more but it surely under its cousin OBH 4.3 whilst it surely doesn't under ViX 5.4 and OBH 4.4, that's why I got back to OBH 4.3, at the moment, where I use it everyday.
About OWIF, it seems to work, in the sense you are there able to set it or edit an existing one. But then it doesn't really work.
Maybe it happens only if you just access the timer by the GUI (I can't remember now). But even if it were so, it'd be unbearable the same.
Now I don't have ViX 5.3 installed any more but it surely under its cousin OBH 4.3 whilst it surely doesn't under ViX 5.4 and OBH 4.4, that's why I got back to OBH 4.3, at the moment, where I use it everyday.
About OWIF, it seems to work, in the sense you are there able to set it or edit an existing one. But then it doesn't really work.
Maybe it happens only if you just access the timer by the GUI (I can't remember now). But even if it were so, it'd be unbearable the same.I'm referring to the eit on the ipeg channel v the actual channel transmission NOT the issue with VPS.
Sent from my IN2013 using Tapatalk
EPG refresh is just a channel zapper. The code to do the zapping is built into Enigma2, but people obstruct request to add the functionality to add timers using Enigma2 A crazy idea.
Just to add,
the EIT on sat (via crossepg) and terrestrial match for a given programme (as they should),
so either iepg-1 is transmitting the incorrect data *or* the inbuilt epg harvester is incorrectly populating the EIT field.
There is no EIT on 28 east.
There is now/next, proprietary 7 day Freesat and proprietary 7 day Sky.
If you zap to IEPG directly, or use epgrefresh, or use CrossEPG the data source is always the same, i.e. 11778 V.
Crossepg doesn't download the EIT data (it downloads EPG data). EIT data is broadcast on the actual channel you are watching/recording and will be read by the EIT reader if enabled. Some channels just do NOW/NEXT while it is increasingly common to get up to 7 days data using this method. The data can (and usually will) be different from the EPG. EIT data is likely to be updated on the fly and will be more accurate at broadcast time. On satellite there are several sources of epg data (freesat/sky/EIT) so care must be taken not to mix them up. A proprietary box will be preset so no confusion arises. Comparing satellite and freeview EPGs is not valid as they have different providers (and different epg providers)
Crossepg doesn't download the EIT data (it downloads EPG data). EIT data is broadcast on the actual channel you are watching/recording and will be read by the EIT reader if enabled. Some channels just do NOW/NEXT while it is increasingly common to get up to 7 days data using this method. The data can (and usually will) be different from the EPG. EIT data is likely to be updated on the fly and will be more accurate at broadcast time. On satellite there are several sources of epg data (freesat/sky/EIT) so care must be taken not to mix them up. A proprietary box will be preset so no confusion arises. Comparing satellite and freeview EPGs is not valid as they have different providers (and different epg providers)I'll say again... there is no EIT on 28 east.
Where does the Now/next data come from then? That is EIT data AFAIK
I'll say again... there is no EIT on 28 east.
1. So what's the field in the timers labelled eit?:
<timer begin="1611478800" end="1611482520" serviceref="1:0:19:1B1D:802:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="The Andrew Marr Show" description="Andrew Marr is joined by Nicola Sturgeon MSP, Matt Hancock MP, Lisa Nandy MP and Yuli Edelstein. With news review by Geri Scott. [S] [HD]" afterevent="auto" eit="19211" tags="AutoTimer The_Andrew_Marr_Show" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="1">
<log code="500" time="1610921689">[AutoTimer] Try to add new timer based on AutoTimer The Andrew Marr Show.</log>
<log code="509" time="1610921689">[AutoTimer] Timer start on: Sun Jan 24 09:00:00 2021</log>
</timer>
<timer begin="1611478801" end="1611482520" serviceref="1:0:19:4484:4083:233A:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="The Andrew Marr Show" description="Andrew Marr is joined by Nicola Sturgeon MSP, Matt Hancock MP, Lisa Nandy MP and Yuli Edelstein. With news review by Geri Scott. [S] [HD]" afterevent="auto" eit="19211" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0">
<log code="15" time="1611476550">record time changed, start prepare is now: Sun Jan 24 08:59:41 2021</log>
</timer>
[28.2e and terrestrial]
2. And what does the VPS plugin interrogate then?
3. Why doesn't the eit field populated from iepg-1 match that from crossepg - if, as you assert, they are from the same source then the inbuilt harvester must be incorrectly populating the field:
Crossepg:
<timer begin="1610996400" end="1611000120" serviceref="1:0:19:52D0:814:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Channel 4 News" description="Channel 4's flagship news programme. Including the weather." afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="1" eit="4934" tags="AutoTimer Channel_4_News" autoTimerId="172">
<log code="500" time="1610394313">[AutoTimer] Try to add new timer based on AutoTimer Channel 4 News.</log>
<log code="509" time="1610394313">[AutoTimer] Timer start on: Mon Jan 18 19:00:00 2021</log>
</timer>
iepg-1:
<timer begin="1610990101" end="1610992920" serviceref="1:0:19:1B1C:802:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Pointless" description="" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="49684" tags="">
<log code="15" time="1610987462">record time changed, start prepare is now: Mon Jan 18 17:14:41 2021</log>
</timer>
Not sure what you're trying to prove, you've shown 3 different programmes from 3 different sources?
EIT Schedule is not present on 28 east so anything that is not now/next must come from a proprietary EPG, i.e Sky, Frresat or online download.
The only EIT data on 28e is NOW & NEXT data (but it is EIT data). Freeview (terrestrial) has full 7 day EIT data.
Not sure what you're trying to prove, you've shown 3 different programmes from 3 different sources?
and 3 different numbered questions - so we can see the answers to each question.
The first sample shows the identical eit data on DVB-S and DVB-T and asks where that comes from on DVB-S
The 2nd 2 samples show DVB-T sampled from iepg-1 and crossepg and that the eit field is different (and incorrect) on iepg-1
EIT Schedule is not present on 28 east so anything that is not now/next must come from a proprietary EPG, i.e Sky, Frresat or online download.
which of the numbered questions are you answering?
The only EIT data on 28e is NOW & NEXT data (but it is EIT data). Freeview (terrestrial) has full 7 day EIT data.
Where does the eit field in the timers I posted get populated from and how does it manage to match the now/next data which VPS uses for signalling?
The 2nd 2 samples show DVB-T sampled from iepg-1 and crossepg and that the eit field is different (and incorrect) on iepg-1
Surely they're different because they are for 2 different programmes, "Channel 4 News" and "Pointless", or are am I losing the plot completely?
Surely they're different because they are for 2 different programmes, "Channel 4 News" and "Pointless", or are am I losing the plot completely?
My mistake corrected samples for the same programme (pointless being the next pgm on the epg at the time, not something I watch):
iepg-1:
<timer begin="1610990101" end="1610992920" serviceref="1:0:19:1B1C:802:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Pointless" description="" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="49684" tags="">
<log code="15" time="1610987462">record time changed, start prepare is now: Mon Jan 18 17:14:41 2021</log>
</timer>
crossepg:
<timer begin="1610990100" end="1610992920" serviceref="1:0:19:1B1C:802:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Pointless" description="" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="18580" tags=""/>
As you see - same pgm, totally different eit (where does the eit field get populated from on 28,2e?)
Its getting the EIT data OTA on 28e (where else would it get it?). As you have said its the NEXT program in the epg then EIT data will be available for it. There is no EIT possible when using crossepg or IEPG1 etc.
Its getting the EIT data OTA on 28e (where else would it get it?). As you have said its the NEXT program in the epg then EIT data will be available for it. There is no EIT possible when using crossepg or IEPG1 etc.
Please follow the steps I detailed to replicate the problem.
1. All of the timers set from autotimers for the next 7 days contain eit data, I only record from DVB-S, where does the eit data come from (I can purge the epg.dat and disable DVB-T harvesting)?
2. Why does the eit number for iepg-1 harvested data differ from that harvested by crossepg
3. Why does the crossepg eit data (for timers set days in advance) match the now/next eit data when iepg-1 eit data does not?
abu baniaz
24-01-21, 18:57
There are two types of EIT EPG. 7 days and now/next. 28.2 also Freesat EPG. Please try disabling Freesat EPG reader and see what happens.
Your posts about EIT number are the first time that I noticed them. I never knew they existed.
There are two types of EIT EPG. 7 days and now/next. 28.2 also Freesat EPG. Please try disabling Freesat EPG reader and see what happens.
Yes, I'm aware that there are 2 types of EIT, they have to match for VPS to function.
What do you mean by "Freesat EPG", I'm using OPENTV 28.2e within crossepg.
You seem to be getting several sets of epg data and getting mixed up. The freesat epg also uses an extended set of EIT data.
abu baniaz
24-01-21, 19:04
The Freesat EPG reader being enabled means whenever you are on a service that has Freest EPG, it will absorb the EPG data. Go to your EPG settings page, you will see it. Then disable it.
You seem to be getting several sets of epg data and getting mixed up. The freesat epg also uses an extended set of EIT data.I'll repeat, I do not harvest the Freesat epg as I have that option disabled, I only harvest the opentv stream
Sent from my IN2013 using Tapatalk
The Freesat EPG reader being enabled means whenever you are on a service that has Freest EPG, it will absorb the EPG data. Go to your EPG settings page, you will see it. Then disable it.What "Freesat epg", I have that disabled and only enable opentv?
Sent from my IN2013 using Tapatalk
BrokenUnusableAccount
24-01-21, 19:38
What "Freesat epg", I have that disabled and only enable opentv?
I think so.
I've noticed that sometimes the EPG from "IEPG data 1" gets a little messed up if I leave Freesat EPG enabled and I don't even try and use VPS.
It's annoying because there is no other obvious way to get an EPG for any of the radio channels.
No need to respond, I don't want to steal your thread.
FWIW, here is "Pointless" on freeview HD and SD, 2 more eit's to worry about...
<timer begin="1611594780" end="1611597960" serviceref="1:0:1:104F:104F:233A:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="Pointless" description="35/55. The quiz in which contestants try to score as few points as possible by plumbing the depths of their general knowledge to come up with the answers no-one else could think of. Also in HD. [S]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="18588" tags="Pointless"/>
<timer begin="1611594781" end="1611597960" serviceref="1:0:19:4484:4089:233A:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="Pointless" description="35/55. The quiz in which contestants try to score as few points as possible by plumbing the depths of their general knowledge to come up with the answers no-one else could think of. [S] [HD]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="19084" tags="Pointless">
FWIW, here is "Pointless" on freeview HD and SD, 2 more eit's to worry about...
<timer begin="1611594780" end="1611597960" serviceref="1:0:1:104F:104F:233A:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="Pointless" description="35/55. The quiz in which contestants try to score as few points as possible by plumbing the depths of their general knowledge to come up with the answers no-one else could think of. Also in HD. [S]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="18588" tags="Pointless"/>
<timer begin="1611594781" end="1611597960" serviceref="1:0:19:4484:4089:233A:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="Pointless" description="35/55. The quiz in which contestants try to score as few points as possible by plumbing the depths of their general knowledge to come up with the answers no-one else could think of. [S] [HD]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="19084" tags="Pointless">SD and HD aren't the same programme, whereas dvb-t and dvb-s are
Sent from my IN2013 using Tapatalk
SD and HD aren't the same programme, whereas dvb-t and dvb-s are
Sent from my IN2013 using Tapatalk
I know - the point I'm making is that different providers are using different "eit's", neither of the ones I posted match yours.
Edit: maybe because the one you posted was an episode broadcast 6 days ago?
I know - the point I'm making is that different providers are using different "eit's", neither of the ones I posted match yours.
Edit: maybe because the one you posted was an episode broadcast 6 days ago?Each programme has a unique eit, HD on dvb-t or dvb-s is the same programme which is why the eit matches.
SD is not the same programme as hd hence the different eit.
There's also different data relating to the overarching programme and the episode within, but that doesn't seem to be exposed on enigma2 whereas with a hack it was on toppy.
The point remains that the eit harvested from iepg-1 does not match the now/next whereas crossepg does. Which is why, when crossepg was removed and we were directed to epgrefresh/iepg-1, I started having VPS issues which prompted my original post
I'll test the newly released new dvb-t module tomorrow.
The pointless episode data was captured 6 days ago but not posted as the admin withdrew his incorrect post.
Sent from my IN2013 using Tapatalk
This is a good read if you're interested in Event Information Tables.....
https://wiki.hummy.tv/etsi.pdf
abu baniaz
24-01-21, 23:11
SD and HD aren't the same programme, whereas dvb-t and dvb-s are
Enigma2 uses service references for recordings. So those are different.
Which channels on 28e send data VPS plugin needs?
From the plugin:
Supported channels
Germany:
ARD and ZDF
Austria:
ORF
Switzerland:
SF
Czech Republic:
CT
BrokenUnusableAccount
25-01-21, 01:34
EPG refresh is just a channel zapper. The code to do the zapping is built into Enigma2, but people obstruct request to add the functionality to add timers using Enigma2
A crazy idea.
@Abu Why do you put up with this?
@Abu Why do you put up with this?Perhaps not everybody expects everyone to think that all of their suggestions are good ones.
Enigma2 uses service references for recordings. So those are different.The eit is the same, that's what's being discussed.
Sent from my IN2013 using Tapatalk
Which channels on 28e send data VPS plugin needs?
From the plugin:
Supported channels
Germany:
ARD and ZDF
Austria:
ORF
Switzerland:
SF
Czech Republic:
CTNearly all of them, that's very old text written by the German author.
Sent from my IN2013 using Tapatalk
BrokenUnusableAccount
25-01-21, 03:49
Perhaps not everybody expects everyone to think that all of their suggestions are good ones.
Okay.
If someone on here suggests something I don't think is what I want I will now call it a crazy idea instead of trying to explain why it's not what I want.
Trying to explain often just resulted in all the OpenViX fanboys on here ganging up on me with more and more ludicrous reasons to reject my ideas anyway.
If someone on here suggests something I don't think is what I want I will now call it a crazy idea instead of trying to explain why it's not what I want.Whereas I was presuming that had all been gone over before and there was no need to repeat it here.
BrokenUnusableAccount
25-01-21, 04:29
Whereas I was presuming that had all been gone over before and there was no need to repeat it here.
Says mr it wouldn't help me the way I use it so I'm not going to listen at all, just keep saying over and over and over that it wouldn't help.
abu baniaz
25-01-21, 09:09
The eit is the same, that's what's being discussed.
Sent from my IN2013 using Tapatalk
Please describe exactly what you mean
EIT Now/next EPG data
EIT EPG data upto 7 days?
EIT number?
Please describe exactly what you mean
EIT Now/next EPG data
EIT EPG data upto 7 days?
EIT number?
In the context of your reply, I was replying to a person who'd posted SD and HD data for a programme from timer.xml and stated that they were different - which is correct as they are different programmes, whereas the HD stream of a programme on DVB-T and DVB-S in the same D has the same eit.
Here's another example for tomorrow evening, it's also noteworthy that when using crossepg one does not require opentv to be active in epg settings as crossepg handles the harvesting within its own code (eit of 186 on C4HD both DVB-S and DVB-T):
<timer begin="1611687600" end="1611691320" serviceref="1:0:19:52D0:814:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Channel 4 News" description="Channel 4's flagship news programme. Including the weather." afterevent="auto" eit="186" tags="AutoTimer Channel_4_News" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="1">
<log code="500" time="1611081419">[AutoTimer] Try to add new timer based on AutoTimer Channel 4 News.</log>
<log code="509" time="1611081419">[AutoTimer] Timer start on: Tue Jan 26 19:00:00 2021</log>
<log code="15" time="1611081419">record time changed, start prepare is now: Tue Jan 26 18:59:41 2021</log>
<log code="15" time="1611082092">record time changed, start prepare is now: Tue Jan 26 18:59:40 2021</log>
</timer>
<timer begin="1611687601" end="1611691320" serviceref="1:0:19:4500:4083:233A:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="Channel 4 News" description="Channel 4's flagship news programme. Including the weather. [S]" afterevent="auto" eit="186" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0">
<log code="15" time="1611559777">record time changed, start prepare is now: Tue Jan 26 18:59:41 2021</log>
</timer>
abu baniaz
25-01-21, 09:28
So when you say "EIT", you mean "EIT number"?
CrossEPG does nothing with Freeview/Terrestrial EPG.
So when you say "EIT", you mean "EIT number"?
CrossEPG does nothing with Freeview/Terrestrial EPG.
That's correct, I continue to refer to the programme eit - that within the epg stream and the now/next data, I await a comment on why that harvested from iEPG-1 doesn't match that from now/next, crossepg or DVB-T use of epgrefresh.
I'm well aware that crossepg only reads the 28.2e data, the discussion relates to a programme of a given density having the same eit identifier whichever platform it is broadcast on i.e. DVB-T or DVB-S.
abu baniaz
25-01-21, 09:47
You need to be specific to avoid confusion. The "EIT number" is new to me, I appreciate that it has "always been there", but it isn't used by Enigma2 for recording. We don't have the CRID system
I am guessing that the EIT number is designed for systems that do not have multiple reception facilities. e.g 28.2 and Freeview. Otherwise if you scheduled a recording on Terrestrial and satellite, they would be identified as the same event, when they are different services.
The OpenTV EPG reader code was added by LraiZer not too long ago. Not sure when he will be back here, but someone else mentioned radio EPG not being absorbed.
In the context of your reply, I was replying to a person who'd posted SD and HD data for a programme from timer.xml and stated that they were different - which is correct as they are different programmes, whereas the HD stream of a programme on DVB-T and DVB-S in the same D has the same eit.
I posted SD and HD data to see if there was a match with the timers you'd referred to as nowhere had you said whether yours were HD or SD.
I hadn't a clue what your service references referred to.
You need to be specific to avoid confusion. The "EIT number" is new to me, I appreciate that it has "always been there", but it isn't used by Enigma2 for recording. We don't have the CRID system
I am guessing that the EIT number is designed for systems that do not have multiple reception facilities. e.g 28.2 and Freeview. Otherwise if you scheduled a recording on Terrestrial and satellite, they would be identified as the same event, when they are different services.
The OpenTV EPG reader code was added by LraiZer not too long ago. Not sure when he will be back here, but someone else mentioned radio EPG not being absorbed.
Abu, everything you state is already in this thread, when something is quoted that should be read to provide context rather than simply reading my response and asking what I refer to.
There's no need to guess why eit number exists, as I've stated only this morning, it's there to identify a programme (not event)
So it's entirely possible that the OpenTV EPG reader code is incorrectly populating the eit data. I only became aware of that feature when crossepg was removed and we were instructed to use epgrefresh (which I note has now been removed from the builds and requires manual installation *even if someone was using it prior to the .005 release*
Hopefully @LraiZer will join this discussion
Crossepg has not been removed - it is just not installed by default. You are free to install it yourself. For most people just using 28e using a channel zapper/epg reader system is simpler. There is no "one size fits all" method and those with motorized systems will use a combination of epg harvesters.
Crossepg has not been removed - it is just not installed by default. You are free to install it yourself. For most people just using 28e using a channel zapper/epg reader system is simpler. There is no "one size fits all" method and those with motorized systems will use a combination of epg harvesters.
No one's disputing that, I'm highlighting an issue that's all.
We now seem to be settling on the issue is within OpenTV
Be grateful we can get anything at all with the opentv reader - despite its name its actually not an "open" system.
Is it really that important to have this EIT data?? Most people seem to manage quite recording quite well.
Be grateful we can get anything at all with the opentv reader - despite its name its actually not an "open" system.
Is it really that important to have this EIT data?? Most people seem to manage quite recording quite well.
What's wrong with reporting a bug and asking for it to be remediated, surely that will benefit all (even those no experiencing the bug) and improve user experience going forward?
For OpenTV and some other built-in E2 readers, a raw data packet is constructed first before it is sent to be read. The eEPGCache::submitEventData() function performs a Bitwise AND operator calculation on the programs start time to set an eventid here in this preprocessing stage. The actual eventid harvested in the opentv reader code was not used here, as at the time there was no existing coding in the eEPGCache::submitEventData() function to pass eventid data.
config.recording.margin_before=3
<timer begin="1611601020" eit="5424">
eEPGCache::submitEventData() "example for opentv eit number"
1611601020 + (3*60sec) = 1611601200
1611601200 = 0x600F1530
0x600F1530 & 0xFFFF = 0x1530
0x1530 = 5424
As far as i am aware, crossepg loads without any preprocessing in E2 as raw data, so probably has the eventid in its raw data that is also read by the opentv built-in reader code but not used.
Another thing to note for any title string comparisons is the later OpenTV patches that added a hack to concatenate title... and ...summary data when they are detected as truncated. You can briefly observe this title string difference to EIT now/next data when the infobar display appears as you zap to concatenated titles. I think this feature could have been an optional.
https://github.com/OpenViX/enigma2/commit/9259e4d30402cad5c7b04ba71501332bbec78373#diff-b15024bd2b4ea380025955f8d690ba180059716f8f64bd2366 de9dcd0d44b0c0
For OpenTV and some other built-in E2 readers, a raw data packet is constructed first before it is sent to be read. The eEPGCache::submitEventData() function performs a Bitwise AND operator calculation on the programs start time to set an eventid here in this preprocessing stage. The actual eventid harvested in the opentv reader code was not used here, as at the time there was no existing coding in the eEPGCache::submitEventData() function to pass eventid data.
config.recording.margin_before=3
<timer begin="1611601020" eit="5424">
eEPGCache::submitEventData() "example for opentv eit number"
1611601020 + (3*60sec) = 1611601200
1611601200 = 0x600F1530
0x600F1530 & 0xFFFF = 0x1530
0x1530 = 5424
As far as i am aware, crossepg loads without any preprocessing in E2 as raw data, so probably has the eventid in its raw data that is also read by the opentv built-in reader code but not used.
Another thing to note for any title string comparisons is the later OpenTV patches that added a hack to concatenate title... and ...summary data when they are detected as truncated. You can briefly observe this title string difference to EIT now/next data when the infobar display appears as you zap to concatenated titles. I think this feature could have been an optional.
https://github.com/OpenViX/enigma2/commit/9259e4d30402cad5c7b04ba71501332bbec78373#diff-b15024bd2b4ea380025955f8d690ba180059716f8f64bd2366 de9dcd0d44b0c0
Thanks for taking the time to reply
As far as i am aware, crossepg loads without any preprocessing in E2 as raw data, so probably has the eventid in its raw data that is also read by the opentv built-in reader code but not used.So that would mean "event_id" would not be available for this comparison (https://github.com/OpenPLi/enigma2/blob/develop/lib/dvb/epgcache.cpp#L601), right?
A program start time only has to change by only 1 minute, and the already existing function that was used by the opentv reader to submit its data to cache would generate a different eventId to the one already cached for that same event. It also does not match with that of the now/next eit.
You can test this little patch to use the actual REAL opentv eventId data, as that would then match exactly with the now/next EIT eventId for PDC checking and should produce exactly the same timer EIT numbers as was created by CrossEPG. See how this affects any program overlapping also?
I don't do any builds for OpenViX anymore, so I cant test this myself on an OpenViX image. I don't have an OpenViX supported box since they dropped my xpeedlx3.
Thanks,
We can make an image available if you want one.
@LraiZer, is the whole EPG cache just populated using sid, tsid, and onid? No namespace or orbital position? e.g. a "uniqueEPGKey" does not have either of those.
https://github.com/OpenPLi/enigma2/blob/develop/lib/dvb/epgcache.h#L30-L74
If true how is possible to avoid collisions between different satellites or between satellite and terrestrial, and other combinations of S/T/C? Or does it rely on luck?
Cache has no namespace or orbital position, just "uniqueEPGKey" from sid, tsid, and onid. If it matches between any type of T/S/C, then it rely's on the cache source type. These are priority checks performed before overwriting any current cached data.
Cache also has a type to check against where the epg came from, this is eg. if(source > type):
https://github.com/OpenPLi/enigma2/blob/3664db5f91860c05a80962ec9127f885daecd515/lib/dvb/epgcache.cpp#L40
The only epg with a lower write priority than opentv at the moment is EPG_IMPORT, but you may notice epg from this EPG_IMPORT sets a do not update from eit flag on its uniqueEPGKey's.
https://github.com/OpenPLi/enigma2/blob/103d129496df5b236473dc134d2554ba45456f9c/lib/dvb/epgcache.h#L249
Based on same uniqueEPGKey from different epg sources:
EIT schedule would overwrite FREESAT_SCHEDULE
FREESAT_SCHEDULE_OTHER would overwrite VIRGIN_SCHEDULE
OPENTV would not overwrite any of the above..
How can we verify if EIT and OpenTV are using the same event_id. Can you see it in SI?
E.g. I can see it here... but I wouldn't have a clue where to find it in OpenTV data.
61350
Thanks @Huevos. I used the TS analyser also to compare the event ids I could see in the timer entries. Obviously only could check the Freesat info as the OpenTV data is held in private tables, but I'm assuming the event ids are consistent between OpenTv and Freesat?
BrokenUnusableAccount
30-01-21, 15:17
While work is being done on OpenTV EPG may I ask if anyone can think of a way it might be made to work for Radio as well as TV.
+1 on this. I wonder if the private sections for the radio EPG on the OpenTV transponder have somehow changed in a way that they are not being retrieved or parsed correctly. The standard Freesat EIT data for the radio channels works ok.
Create a timer from ONLY the EIT enabled epg for a next program as it populates by only EIT now/next data.
Then delete that timer and clear the epg and create another timer from ONLY the OpenTV epg for the exact same program.
You will see that eit="18742" for both are now identical as OpenTV eventId is no longer based on start time!
EIT now/next timer:
<timer begin="1612017720" end="1612026900" serviceref="1:0:1:1929:7FF:2:11A0000:0:0:0:" repeated="0" name="?MOTD Live: West Bromwich Albion...?" description="...v Fulham. Live coverage of West Bromwich Albion v Fulham. Also in HD. [S]" afterevent="auto" eit="18742" justplay="0" always_zap="0" pipzap="0" zap_wakeup="always" rename_repeat="1" conflict_detection="1" descramble="1" record_ecm="0">
OpenTV timer:
<timer begin="1612017720" end="1612026900" serviceref="1:0:1:1929:7FF:2:11A0000:0:0:0:" repeated="0" name="MOTD Live: West Bromwich Albion v Fulham" description="Live coverage of West Bromwich Albion v Fulham. Also in HD. [S]" afterevent="auto" eit="18742" justplay="0" always_zap="0" pipzap="0" zap_wakeup="always" rename_repeat="1" conflict_detection="1" descramble="1" record_ecm="0">
+1 on this. I wonder if the private sections for the radio EPG on the OpenTV transponder have somehow changed in a way that they are not being retrieved or parsed correctly. The standard Freesat EIT data for the radio channels works ok.What is the status of that in Cross?
FWIW, this is what I see on freeview (only), SD and HD....
<timer begin="1612017780" end="1612026960" serviceref="1:0:1:104F:104F:233A:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="MOTD Live: West Bromwich Albion..." description="...v Fulham. Live coverage of West Bromwich Albion v Fulham. Also in HD. [S]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="18746" tags="MOTD_Live:_West_Bromwich_Albion...">
<timer begin="1612017781" end="1612026960" serviceref="1:0:19:4484:4089:233A:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="MOTD Live: West Bromwich Albion..." description="...v Fulham. Live coverage of West Bromwich Albion v Fulham. [S] [HD]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="19322" tags="MOTD_Live:_West_Bromwich_Albion...">
FWIW, this is what I see on freeview (only), SD and HD....
<timer begin="1612017780" end="1612026960" serviceref="1:0:1:104F:104F:233A:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="MOTD Live: West Bromwich Albion..." description="...v Fulham. Live coverage of West Bromwich Albion v Fulham. Also in HD. [S]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="18746" tags="MOTD_Live:_West_Bromwich_Albion...">
<timer begin="1612017781" end="1612026960" serviceref="1:0:19:4484:4089:233A:EEEE0000:0:0:0:" repeated="0" rename_repeat="1" name="MOTD Live: West Bromwich Albion..." description="...v Fulham. Live coverage of West Bromwich Albion v Fulham. [S] [HD]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="19322" tags="MOTD_Live:_West_Bromwich_Albion...">
Two different services so the event_id is different.
What is the status of that in Cross?
TV services only. Cross doesn't seem to be able to get radio EPG either. I am pretty sure it used to work, but I don't know if I always had Freesat EPG enabled in the past - too much wine may have killed brain cells.
Create a timer from ONLY the EIT enabled epg for a next program as it populates by only EIT now/next data.
Then delete that timer and clear the epg and create another timer from ONLY the OpenTV epg for the exact same program.
You will see that eit="18742" for both are now identical as OpenTV eventId is no longer based on start time!
EIT now/next timer:
<timer begin="1612017720" end="1612026900" serviceref="1:0:1:1929:7FF:2:11A0000:0:0:0:" repeated="0" name="?MOTD Live: West Bromwich Albion...?" description="...v Fulham. Live coverage of West Bromwich Albion v Fulham. Also in HD. [S]" afterevent="auto" eit="18742" justplay="0" always_zap="0" pipzap="0" zap_wakeup="always" rename_repeat="1" conflict_detection="1" descramble="1" record_ecm="0">
OpenTV timer:
<timer begin="1612017720" end="1612026900" serviceref="1:0:1:1929:7FF:2:11A0000:0:0:0:" repeated="0" name="MOTD Live: West Bromwich Albion v Fulham" description="Live coverage of West Bromwich Albion v Fulham. Also in HD. [S]" afterevent="auto" eit="18742" justplay="0" always_zap="0" pipzap="0" zap_wakeup="always" rename_repeat="1" conflict_detection="1" descramble="1" record_ecm="0">
One more question: :)
So event_id is the same in both cases, so if a change is detected the event entry will be modified...
What would happen if the data in epgcache if the event were removed from EIT and OpenTV SI?
abu baniaz
30-01-21, 17:09
I think there is something wrong with the patch. It is blocking some Freesat EPG. This is 28.2, BBC One HD for London Area. I was getting EPG and set a timer before I updated the image.
I can't reproduce that. I started with OpenTV setup.
61354
Reconfigured to your setup, deleted epgcache, switched to BBC One HD.
61355
Also notice in my screen grabs that Freesat reader is truncating the titles.
I can't reproduce that. I started with OpenTV setup.
Reconfigured to your setup, deleted epgcache, switched to BBC One HD.
I found that changing some settings in
menu -> setup -> epg -> settings and then pressing green to save also seemed to required a reboot of the box. When I was testing for now/next operation I first deleted the epg cache, then saved the now empty RAM cache to disk before rebooting the box.
abu baniaz
30-01-21, 18:29
Please ignore my previous post. Looks like 5 minutes was not enough for Freesat EPG. I should really have used the fast transponder.
With the patch, I can confirm that the event_ID/ EIT number is now the same.
Old Freesat
<?xml version="1.0" ?>
<timers>
<timer begin="1612027680" end="1612029720" serviceref="1:0:19:1B1D:802:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Celebrity Catchpoint" description="2/4. Paddy McGuinness is the man with big questions and even bigger balls in Celebrity Catchpoint. Ore Oduba and Kelvin Fletcher take on the Rev Kate Bottley and the Rev Richard Coles. [S] [HD]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="19327" tags="Celebrity_Catchpoint"/>
</timers>
Old OpenTV
<?xml version="1.0" ?>
<timers>
<timer begin="1612027680" end="1612029720" serviceref="1:0:19:1B1D:802:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Celebrity Catchpoint" description="2/4. Paddy McGuinness is the man with big questions and even bigger balls in Celebrity Catchpoint. Ore Oduba and Kelvin Fletcher take on the Rev Kate Bottley and the Rev Richard Coles. [S] [HD]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="38808" tags="Celebrity_Catchpoint"/>
</timers>
New Freesat
<?xml version="1.0" ?>
<timers>
<timer begin="1612027680" end="1612029720" serviceref="1:0:19:1B1D:802:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Celebrity Catchpoint" description="2/4. Paddy McGuinness is the man with big questions and even bigger balls in Celebrity Catchpoint. Ore Oduba and Kelvin Fletcher take on the Rev Kate Bottley and the Rev Richard Coles. [S] [HD]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="19327" tags="Celebrity_Catchpoint"/>
</timers>
New OpenTV
<?xml version="1.0" ?>
<timers>
<timer begin="1612027680" end="1612029720" serviceref="1:0:19:1B1D:802:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Celebrity Catchpoint" description="2/4. Paddy McGuinness is the man with big questions and even bigger balls in Celebrity Catchpoint. Ore Oduba and Kelvin Fletcher take on the Rev Kate Bottley and the Rev Richard Coles. [S] [HD]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="19327" tags="Celebrity_Catchpoint"/>
</timers>
Please ignore my previous post. Looks like 5 minutes was not enough for Freesat EPG. I should really have used the fast transponder.
With the patch, I can confirm that the event_ID/ EIT number is now the same.
Old Freesat
<?xml version="1.0" ?>
<timers>
<timer begin="1612027680" end="1612029720" serviceref="1:0:19:1B1D:802:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Celebrity Catchpoint" description="2/4. Paddy McGuinness is the man with big questions and even bigger balls in Celebrity Catchpoint. Ore Oduba and Kelvin Fletcher take on the Rev Kate Bottley and the Rev Richard Coles. [S] [HD]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="19327" tags="Celebrity_Catchpoint"/>
</timers>
Old OpenTV
<?xml version="1.0" ?>
<timers>
<timer begin="1612027680" end="1612029720" serviceref="1:0:19:1B1D:802:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Celebrity Catchpoint" description="2/4. Paddy McGuinness is the man with big questions and even bigger balls in Celebrity Catchpoint. Ore Oduba and Kelvin Fletcher take on the Rev Kate Bottley and the Rev Richard Coles. [S] [HD]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="38808" tags="Celebrity_Catchpoint"/>
</timers>
New Freesat
<?xml version="1.0" ?>
<timers>
<timer begin="1612027680" end="1612029720" serviceref="1:0:19:1B1D:802:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Celebrity Catchpoint" description="2/4. Paddy McGuinness is the man with big questions and even bigger balls in Celebrity Catchpoint. Ore Oduba and Kelvin Fletcher take on the Rev Kate Bottley and the Rev Richard Coles. [S] [HD]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="19327" tags="Celebrity_Catchpoint"/>
</timers>
New OpenTV
<?xml version="1.0" ?>
<timers>
<timer begin="1612027680" end="1612029720" serviceref="1:0:19:1B1D:802:2:11A0000:0:0:0:" repeated="0" rename_repeat="1" name="Celebrity Catchpoint" description="2/4. Paddy McGuinness is the man with big questions and even bigger balls in Celebrity Catchpoint. Ore Oduba and Kelvin Fletcher take on the Rev Kate Bottley and the Rev Richard Coles. [S] [HD]" afterevent="auto" justplay="0" always_zap="0" pipzap="0" conflict_detection="1" descramble="1" record_ecm="0" isAutoTimer="0" eit="19327" tags="Celebrity_Catchpoint"/>
</timers>
That's great that the correct eit is now produced from openTV, but is that just coming from now/next, in which case it looks complex to update all timers as they roll into the now/next window
or have I misses something?
abu baniaz
30-01-21, 18:44
I did not use now/next EIT EPG as I wanted to test something further ahead to allow more tests.
I did not use now/next EIT EPG as I wanted to test something further ahead to allow more tests.
OK, so are you saying that openTV from iEPG-1 is now processed correctly giving a valid eit?
@gort - I've just updated to the latest dev version. Cleared EPG cache and have disabled the Freesat EPG reader. Just enabled the OpenTV reader and allowed it to repopulate the EPG. I set a timer for QI XL on BBC2HD for 21.15. The timer has the event id 18679. I separately fired up my TS analyser on my PC and analysed the schedule EIT (Freesat) for the same channel. It has the same event id of 0x48F7 - which is the hex equivalent of 18679. So, I believe the event ID will match what will be delivered in the now/next EIT that VPS is expecting.
@gort - I've just updated to the latest dev version. Cleared EPG cache and have disabled the Freesat EPG reader. Just enabled the OpenTV reader and allowed it to repopulate the EPG. I set a timer for QI XL on BBC2HD for 21.15. The timer has the event id 18679. I separately fired up my TS analyser on my PC and analysed the schedule EIT (Freesat) for the same channel. It has the same event id of 0x48F7 - which is the hex equivalent of 18679. So, I believe the event ID will match what will be delivered in the now/next EIT that VPS is expecting.That's excellent news, thank you
Sent from my IN2013 using Tapatalk
Yes - I've confirmed that a timer set from the EPG generated by the updated reader code will have a match with the EIT now/next event Id. Just tested it with an upcoming programme. I have not used the VPS plugin, but I may experiment with it. Most programmes work ok for me with the existing auto timers. I presume the VPS plugin interacts with the timers.xml data and modifies the settings "on the fly"?
Yes - I've confirmed that a timer set from the EPG generated by the updated reader code will have a match with the EIT now/next event Id. Just tested it with an upcoming programme. I have not used the VPS plugin, but I may experiment with it. Most programmes work ok for me with the existing auto timers. I presume the VPS plugin interacts with the timers.xml data and modifies the settings "on the fly"?That's how it appears to work, when you look at timers.xml after recordings then you see the start time being delayed until the now/next signal changes, at the end then the end time is similarly updated.
Sent from my IN2013 using Tapatalk
I separately fired up my TS analyser on my PC and analysed the schedule EIT.
Out of interest, which TS analyser are you using, I'm sure I've used one in the dim and distant past, but can't for the life of me find it anymore?
It's the TS Analyser that comes with DVBViewer. I bought a licence years ago. It's on my Windows 7 machine which I use only rarely.
@gort - I've just updated to the latest dev version. Cleared EPG cache and have disabled the Freesat EPG reader. Just enabled the OpenTV reader and allowed it to repopulate the EPG. I set a timer for QI XL on BBC2HD for 21.15. The timer has the event id 18679. I separately fired up my TS analyser on my PC and analysed the schedule EIT (Freesat) for the same channel. It has the same event id of 0x48F7 - which is the hex equivalent of 18679. So, I believe the event ID will match what will be delivered in the now/next EIT that VPS is expecting.
I also get an eit of 18679 from crossEPG and freeview.
@gort - I've just updated to the latest dev version. Cleared EPG cache and have disabled the Freesat EPG reader. Just enabled the OpenTV reader and allowed it to repopulate the EPG. I set a timer for QI XL on BBC2HD for 21.15. The timer has the event id 18679. I separately fired up my TS analyser on my PC and analysed the schedule EIT (Freesat) for the same channel. It has the same event id of 0x48F7 - which is the hex equivalent of 18679. So, I believe the event ID will match what will be delivered in the now/next EIT that VPS is expecting.Freesat doesn't have EIT schedule. There is no EIT schedule on 28 east, only now/next. Freesat EPG is a proprietary system.
Have you got a transport stream recorded?
I also get an eit of 18679 from crossEPG and freeview.Do you mean Freesat? Freeview is terrestrial.
Freesat doesn't have EIT schedule. There is no EIT schedule on 28 east, only now/next. Freesat EPG is a proprietary system.
Have you got a transport stream recorded?I've asked previously where the eit field populated in the timers comes from, no one has answered but software has been developed to utilise it
Sent from my IN2013 using Tapatalk
Ok, well I can't test Freeview because I live on the moon.
I also get an eit of 18679 from crossEPG and freeview.
Do you mean Freesat? Freeview is terrestrial.
I checked freeview earlier and got eit=18679.
Freesat doesn't have EIT schedule. There is no EIT schedule on 28 east, only now/next. Freesat EPG is a proprietary system.
Have you got a transport stream recorded?
It most certainly does! The DVBViewer Pro TS Analyser shows the Freesat EIT now/next and the schedule on most transponders. The SKY-specific transponder has no EIT showing as you say - just the private sections which I presume the OpenTV reader is parsing.
EDIT - I'll see if I can extract an XML file of the schedule from BBC2HD on 10847V and post it later
Here is an XML file from TS Analyser. The longer you leave the analyser on the channel transponder, the more data is downloaded. Just like the Freesat reader in Vix - after 10-15 minutes the whole week's EPG is transmitted? Just search this file for "QI XL" and you will see the details for the current programme being transmitted.
Here is a screenshot of the TS Reader from my Win 7 machine showing the transponder analysis where I drilled down to BBC Two HD.
If the image is too small to view, try the attached zip file which should blow up sufficiently.
It most certainly does! The DVBViewer Pro TS Analyser shows the Freesat EIT now/next and the schedule on most transponders. The SKY-specific transponder has no EIT showing as you say - just the private sections which I presume the OpenTV reader is parsing.
EDIT - I'll see if I can extract an XML file of the schedule from BBC2HD on 10847V and post it later
Here is an XML file from TS Analyser. The longer you leave the analyser on the channel transponder, the more data is downloaded. Just like the Freesat reader in Vix - after 10-15 minutes the whole week's EPG is transmitted? Just search this file for "QI XL" and you will see the details for the current programme being transmitted.Your image confirms it does not have "EIT schedule", just now/next. Freesat EPG is something else.
EIT schedule looks like this:
61361
Your image confirms it does not have "EIT schedule", just now/next. Freesat EPG is something else.
EIT schedule looks like this:
61361I'll ask again, where does the eit field get populated from in the examples I and others have posted, I do NOT have Freesat enabled?
Also now the code's been remediated how is it picking up the correct values from iepg-1?
Thanks
Sent from my IN2013 using Tapatalk
where does the eit field get populated fromFrom the SI tables.
Your image confirms it does not have "EIT schedule", just now/next. Freesat EPG is something else.
EIT schedule looks like this:
61361
So "Other TS - Schedule" is not a schedule? The EPG will be populated from the transponder over a period of 10'ish minutes with the Freesat reader enabled and no other reader enabled. If I drill down into the items marked "Other TS - Schedule" (as per the xml file above) I see all the EPG entry details - date/time/Programme Name/synopsis/event id etc. Is this just a question of terminology? @goRt was asking about the source of the eit field (actually the Event ID). The Event Id is available in the tables as parsed by TS Analyser on a per transponder/service table entry. The OpenTV data is held in private data tables which the TS Analyser can't parse, but which the OpenTV reader can, presumably?
abu baniaz
31-01-21, 00:29
Following LraiZer's patch, the "OpenTV EPG reader" will now obtain the same "EIT number" as "now/next EIT EPG reader".
From the SI tables.In the broadcast stream [emoji2357]
Sent from my IN2013 using Tapatalk
Is there some guide on manually updating the files so I can test this also? I would need the broadcom binaries (Solo2).
But tbh I only ever had occasional issue previously when I used EPGRefresh (none with CrossEPG). Not yet noticed it using OpenTV.
Is there some guide on manually updating the files so I can test this also? I would need the broadcom binaries (Solo2).
But tbh I only ever had occasional issue previously when I used EPGRefresh (none with CrossEPG). Not yet noticed it using OpenTV.It's offered on the other thread.
Opentv processes the data from iepg-1, so you will have the issue until the patch is applied
Sent from my IN2013 using Tapatalk
It's offered on the other thread.
Opentv processes the data from iepg-1, so you will have the issue until the patch is appliedI must have missed that. Where? I know @Heuvus offered the arm binary but I would need the broadcom or a guide on how I compile it (is it like py to pyo)?
.... the binaries haven't been made available to download, the patch is in c++ which can't be added like .py files, they need compiling first.
BrokenUnusableAccount
31-01-21, 13:35
Presumably those that are testing it have built it themselves.
https://www.world-of-satellite.com/showthread.php?61295-Build-my-own-Vix-image
I can build myself but was looking at a manual method like py but obviously not. I may look at rebuilding Dev release rather than normal release.
... there may be a short cut way of compiling an individual module, but I've not spotted anyone mentioning it before.
... there may be a short cut way of compiling an individual module, but I've not spotted anyone mentioning it before.
cd /home/openvix/5.4/builds/openvix/experimental/vuultimo4k
. env.source
bitbake enigma2
If you build one package, packages.gz doesn't update as it is openvix-image.bb that does that job. Therefore you would have to grab the ipk manually from:
/home/openvix/5.4/builds/openvix/experimental/vuultimo4k/tmp/deploy/ipk/vuultimo4kenigma2_5.4+git26187+3794707-r0_vuultimo4k.ipk
@goRt - question regarding VPS usage!
Does it work on single (one-off) recordings scheduled from the EPG using the green button? I tried a couple of recordings, but it just seemed to use my normal settings with padding before and after recording.
I then tried an autotimer (blue button) and it offered to enable VPS in the AT settings. However, the recording I set failed to start, so I figured that I might have some old data in the EPG cache. I cleared the EPG cache completely and re-ran the OpenTvzapper and set another AT. This seems to have kicked off ok, so I will wait until it's finished and check results. I'll give it an extensive test during the week to see if there are any other issues, before I install VPS on the main box.
@goRt - question regarding VPS usage!
Does it work on single (one-off) recordings scheduled from the EPG using the green button? I tried a couple of recordings, but it just seemed to use my normal settings with padding before and after recording.
I then tried an autotimer (blue button) and it offered to enable VPS in the AT settings. However, the recording I set failed to start, so I figured that I might have some old data in the EPG cache. I cleared the EPG cache completely and re-ran the OpenTvzapper and set another AT. This seems to have kicked off ok, so I will wait until it's finished and check results. I'll give it an extensive test during the week to see if there are any other issues, before I install VPS on the main box.
There's a mention here....
https://www.world-of-satellite.com/showthread.php?63409-5-4-001-VPS-plugin-Bootloop&p=505071&viewfull=1#post505071
I'm 95% sure it applies to manual timers, but openwebif is the main issue.
BrokenUnusableAccount
31-01-21, 14:55
If you build one package, packages.gz doesn't update as it is openvix-image.bb that does that job. Therefore you would have to grab the ipk manually from:
/home/openvix/5.4/builds/openvix/experimental/vuultimo4k/tmp/deploy/ipk/vuultimo4kenigma2_5.4+git26187+3794707-r0_vuultimo4k.ipk
What's the difference between experimental and developer?
Thanks @ccs - I had forgotten that thread. Seems to only work with autotimers. I used to use the "exact recording" functionality on my Humax Freesat recorder and it worked very well. Normal autotimers work 90+% for me as I have padding before and after the event. It's only the very occasional event that gets delayed and I miss the end! Playing with the VPS plugin is mostly just an exercise in testing the functionality for me!
Thanks @ccs - I had forgotten that thread. Seems to only work with autotimers. I used to use the "exact recording" functionality on my Humax Freesat recorder and it worked very well. Normal autotimers work 90+% for me as I have padding before and after the event. It's only the very occasional event that gets delayed and I miss the end! Playing with the VPS plugin is mostly just an exercise in testing the functionality for me!
I used topfield series links with great success for many years, but have found autotimers equal to the task.
Reschedules actually work well, although I run autotimer every 25 minutes to make sure they're caught - they usually are soon after the epg changes.
I adjust things a bit during Wimbledon to take into account the bbc's obsession with moving bbc1 programmes over to bbc2 instead of leaving them well alone.
What's the difference between experimental and developer?That is my build using my enigma2 repository.
ok, so I built current developer image today to try the new OpenTV changes. However, I came across is no way to manually force OpenTV downloader from the Blue button from Live TV!!
I have posted this here as don't know if its related to recent few changes to OpenTV?
Below is screenshot of OpenTV settings and what is displayed when I press Blue button from live TV...
61369 61368
The only way I was able to force a download was to toggle it off/on etc which triggered download. I also didn't get the full 7 days EPG.
Is this just me having no easy way of manually downloading EPG via OpenTV?
ok, so I built current developer image today to try the new OpenTV changes. However, I came across is no way to manually force OpenTV downloader from the Blue button from Live TV!!
I have posted this here as don't know if its related to recent few changes to OpenTV?
Below is screenshot of OpenTV settings and what is displayed when I press Blue button from live TV...
61369 61368
The only way I was able to force a download was to toggle it off/on etc which triggered download. I also didn't get the full 7 days EPG.
Is this just me having no easy way of manually downloading EPG via OpenTV?Use epg refresh ???
Sent from my IN2013 using Tapatalk
abu baniaz
31-01-21, 19:23
Shows for me. Have you tried a restart?
Yea and I even removed plugin, init 4 and removed opentv settings from settings file, rebooted and installed again.
BrokenUnusableAccount
31-01-21, 19:39
Try just a 'Restart GUI'.
After installing and enabling 'enable OpenTV download' in opentvzapper you need to do 'restart GUI' before the option appears on the blue button menu.
Try just a 'Restart GUI'.
After installing and enabling 'enable OpenTV download' in opentvzapper you need to do 'restart GUI' before the option appears on the blue button menu.
Correct.
if config.plugins.opentvzapper.enabled.value and config.plugins.opentvzapper.extensions.value:
Both of those have to be True at the time of the reboot. Says this in the plugin.
"When enabled a forced download will be possible from the extensions menu (blue button). Shows after next restart."
Reboot didn't work but did get it working again by removing the specific settings file after doing init 4 then another reboot.
I'm assuming little issue with settings file. Working now and i've checked settings file and it's now matches what I have it set as in plugin settings.
Edit:
Suspect user error in that I can't remember whether the settings file I edited in FileZilla, whether I allowed it to write back before getting carried away and rebooting :)
@goRt - question regarding VPS usage!
Does it work on single (one-off) recordings scheduled from the EPG using the green button? I tried a couple of recordings, but it just seemed to use my normal settings with padding before and after recording.
I then tried an autotimer (blue button) and it offered to enable VPS in the AT settings. However, the recording I set failed to start, so I figured that I might have some old data in the EPG cache. I cleared the EPG cache completely and re-ran the OpenTvzapper and set another AT. This seems to have kicked off ok, so I will wait until it's finished and check results. I'll give it an extensive test during the week to see if there are any other issues, before I install VPS on the main box.The only ways to get the interface to VPS to function are:
Roll back to 5.3.39 or
Use autotimers or
Use the webif but rather than adding a timer to a specific programme you have to select "edit timer" that allows webif to correctly display the VPS fields, if you already have a timer for that programme then edit doesn't provide the correct input, it let's you think it doesn't but it's broken.
(As an aside, why don't I get notified when I'm @ ed?, which setting have I broken on the forum?)
Sent from my IN2013 using Tapatalk
The only ways to get the interface to VPS to function are:
Roll back to 5.3.39 or
Use autotimers or
Use the webif but rather than adding a timer to a specific programme you have to select "edit timer" that allows webif to correctly display the VPS fields, if you already have a timer for that programme then edit doesn't provide the correct input, it let's you think it doesn't but it's broken.
(As an aside, why don't I get notified when I'm @ ed?, which setting have I broken on the forum?)
Sent from my IN2013 using TapatalkCan you post some screen grabs so we know exactly what you are talking about.
The only ways to get the interface to VPS to function are:
Roll back to 5.3.39 or
Use autotimers or
Use the webif but rather than adding a timer to a specific programme you have to select "edit timer" that allows webif to correctly display the VPS fields, if you already have a timer for that programme then edit doesn't provide the correct input, it let's you think it doesn't but it's broken.
(As an aside, why don't I get notified when I'm @ ed?, which setting have I broken on the forum?)
Sent from my IN2013 using Tapatalk
It's working fine for me on the dev build on autotimers only. Set up a bunch of autotimers on the soaps. Worked perfectly today on Channel 5 and ITV. Will keep it running for the rest of the week.
I don't know what setting (if any) notifies you when you're referenced by @ in a post.
BrokenUnusableAccount
02-02-21, 00:41
It puzzles me that it only works for autotimers.
Surely at the point when it has to work it's the just the times in an ordinary (non auto) timer that needs to be overridden?
How does it make a difference whether the ordinary (non auto) timer was put there directly by a person or automatically by an autotimer?
It puzzles me that it only works for autotimers.
Surely at the point when it has to work it's the just the times in an ordinary (non auto) timer that needs to be overridden?
How does it make a difference whether the ordinary (non auto) timer was put there directly by a person or automatically by an autotimer?
As I understand things there's a property that has been renamed in openVIX so VPS misses this, there was a patch released for .001 which got us to this position (it's included in the build), but no further.
Can you post some screen grabs so we know exactly what you are talking about.
How it should be:
61383613846138561386
Those images are too small for my old eyes, goRt! I wasn't using the web interface in any case - just the normal menu dialogues.
@BefuddledBrian - when you set up an autotimer, there are two extra settings parameters available to you in the menu - (i) enable VPS and (ii) allow broadcaster settings to control recording (I'm paraphrasing here). Works similarly on an instant record as it pops up a VPS dialogue also. Just the manual, one-off recording when pressing GREEN from the EPG seems not to work, but I'll check the edit option and see if that works.
Those images are too small for my old eyes, goRt! I wasn't using the web interface in any case - just the normal menu dialogues.
@BefuddledBrian - when you set up an autotimer, there are two extra settings parameters available to you in the menu - (i) enable VPS and (ii) allow broadcaster settings to control recording (I'm paraphrasing here). Works similarly on an instant record as it pops up a VPS dialogue also. Just the manual, one-off recording when pressing GREEN from the EPG seems not to work, but I'll check the edit option and see if that works.
Sorry about that, technology failure!
Have fun with the edit option as sometimes it displays the VPS field, but when you tab to adjust it it just goes to the name field without making any changes
When I edited the timer option and blanked out the name field I got the VPS enable option. Then I set the VPS and went back to the name field and re-named it. All very strange. The actual VPS exact recording functions very well, though. Just like my old Humax. Very channel/broadcaster dependent. BBC/ITV/Channel4 all seem to trigger the EIT now/next change correctly just before the programme starts. Channel 5 seems to trigger the change at the schedule time but the programme might not start for a minute or two after. It depends on the level of automation and settings of the playout equipment I think. Some of the non-mainstream channels like Pick seem to be entirely automated and the EIT change and the programme start are completely synchronised.
When I edited the timer option and blanked out the name field I got the VPS enable option. Then I set the VPS and went back to the name field and re-named it. All very strange. The actual VPS exact recording functions very well, though. Just like my old Humax. Very channel/broadcaster dependent. BBC/ITV/Channel4 all seem to trigger the EIT now/next change correctly just before the programme starts. Channel 5 seems to trigger the change at the schedule time but the programme might not start for a minute or two after. It depends on the level of automation and settings of the playout equipment I think. Some of the non-mainstream channels like Pick seem to be entirely automated and the EIT change and the programme start are completely synchronised.
Looks like the VPS plugin looks after the name and description.... ?
The VPS-plugin can determine whether a mission begins earlier or lasts longer than the timer is programmed. For this, the channels provide reliable data.
Features:
- Each timer can be enabled VPS
- Evaluation of the Running status of a program (not running, starts in a few seconds, pausing, running)
- Enter the VPS / PDC time possible
- Control-flow time (eg 10 minutes before the actual beginning of the recording captures the plugin to the monitoring of running status)
- Recordings can be completely controlled by the sender information, ie the programmed timer periods are not observed.
The channels provide reliable data? (Running status)
ARD and ZDF to provide for their shipments usually an accurate running status.
Sky delivers (for the Sky-owned channels and some non-transmitters) are often an accurate running status. Unlike ARD / ZDF, the (program) advertising before / after a show but as a "running" is specified.
The private stations adjust their status to not running when a program starts earlier or is coated. The VPS function should therefore not be turned on when recording from the private sector.
Exceptions seem to be TV DMAX and Servus.
What is VPS-time?
ARD and ZDF state in their EPG data, the VPS-time (PDC descriptor).
The VPS time should be the starting time published in magazines. ZDF is the time to on their website and Teletext.
be specified for manual timer programming, the VPS time when you turn the VPS function.
The VPS time can find the plugin, the event ID of the item and can then begin the evaluation of the Running status. When programming via the EPG must not VPS time be specified because, in the case already saved an event ID in the timer.
This looks for the plug after the VPS time, no name for the timer must be specified. The Name and Description fields are filled in by the plugin if a program of the VPS time is found.
What does complete control of broadcasting information?
When this feature is enabled (in the plugin settings and the timer!), Then the plugin can start recording only when the mission is stated as "running", and ends the timer when the Running status to "not running "is set. In that case, the programmed timer periods are therefore not considered for inclusion. The start time of the timer should be programmed but still correct, since this time will be used for this, from when the plug begins to monitor the timer.
The disadvantage of the function is that the program möglicherwise or not taken wrong, when the station is giving incorrect information. This is even on ARD / ZDF irregular times the case.
If the function is not used, then considered the plugin the programmed start and end time and can start recording only if, sooner or run longer, never shorter.
Lead-Time Control
The plugin by default starts 10 minutes before the actual start of recording to monitor the running status.
If no free tuner is there, then tried the plugin on the current transponder / channel for information search. ARD will broadcast e.g. on their transponders and EPG information from ZDF and vice versa. However, it is expected with a slight delay.
For timers that are to be controlled by the sender information on the plugin if necessary in order for the lead time on the included transmitter.
Installation
The plugin is installed like any other.
To use the functions must be changed two files (/ usr/lib/enigma2/python/RecordTimer.py and / usr/lib/enigma2/python/Screens/TimerEntry.py). The files will be patched automatically by the plugin.
Enigma has to be restarted after installation. Maybe even twice.
ccs - I did see that in your previous post and that is why I tried it out. The language translation from German to English doesn't make things easy to understand. I'm not sure why VPS wants the timer name to be blank. Generally the user wants the default programme name. It's only a minor issue on manual timers. It works fine on autotimers.
Looks like the VPS plugin looks after the name and description.... ?
The VPS-plugin can determine whether a mission begins earlier or lasts longer than the timer is programmed. For this, the channels provide reliable data.
Features:
- Each timer can be enabled VPS
- Evaluation of the Running status of a program (not running, starts in a few seconds, pausing, running)
- Enter the VPS / PDC time possible
- Control-flow time (eg 10 minutes before the actual beginning of the recording captures the plugin to the monitoring of running status)
- Recordings can be completely controlled by the sender information, ie the programmed timer periods are not observed.
The channels provide reliable data? (Running status)
ARD and ZDF to provide for their shipments usually an accurate running status.
Sky delivers (for the Sky-owned channels and some non-transmitters) are often an accurate running status. Unlike ARD / ZDF, the (program) advertising before / after a show but as a "running" is specified.
The private stations adjust their status to not running when a program starts earlier or is coated. The VPS function should therefore not be turned on when recording from the private sector.
Exceptions seem to be TV DMAX and Servus.
What is VPS-time?
ARD and ZDF state in their EPG data, the VPS-time (PDC descriptor).
The VPS time should be the starting time published in magazines. ZDF is the time to on their website and Teletext.
be specified for manual timer programming, the VPS time when you turn the VPS function.
The VPS time can find the plugin, the event ID of the item and can then begin the evaluation of the Running status. When programming via the EPG must not VPS time be specified because, in the case already saved an event ID in the timer.
This looks for the plug after the VPS time, no name for the timer must be specified. The Name and Description fields are filled in by the plugin if a program of the VPS time is found.
What does complete control of broadcasting information?
When this feature is enabled (in the plugin settings and the timer!), Then the plugin can start recording only when the mission is stated as "running", and ends the timer when the Running status to "not running "is set. In that case, the programmed timer periods are therefore not considered for inclusion. The start time of the timer should be programmed but still correct, since this time will be used for this, from when the plug begins to monitor the timer.
The disadvantage of the function is that the program möglicherwise or not taken wrong, when the station is giving incorrect information. This is even on ARD / ZDF irregular times the case.
If the function is not used, then considered the plugin the programmed start and end time and can start recording only if, sooner or run longer, never shorter.
Lead-Time Control
The plugin by default starts 10 minutes before the actual start of recording to monitor the running status.
If no free tuner is there, then tried the plugin on the current transponder / channel for information search. ARD will broadcast e.g. on their transponders and EPG information from ZDF and vice versa. However, it is expected with a slight delay.
For timers that are to be controlled by the sender information on the plugin if necessary in order for the lead time on the included transmitter.
Installation
The plugin is installed like any other.
To use the functions must be changed two files (/ usr/lib/enigma2/python/RecordTimer.py and / usr/lib/enigma2/python/Screens/TimerEntry.py). The files will be patched automatically by the plugin.
Enigma has to be restarted after installation. Maybe even twice.
But VPS functions correctly on 5.3.039 and was only broken by the changes made to openVIX 5.4.xxx
But VPS functions correctly on 5.3.039 and was only broken by the changes made to openVIX 5.4.xxx
I was commenting on @fat-tony's post which basically said that blanking out the name field in a manual timer invoked the VPS options, I thought you'd been saying manual timers don't work??
I was commenting on @fat-tony's post which basically said that blanking out the name field in a manual timer invoked the VPS options, I thought you'd been saying manual timers don't work??
Clearly @fat-tony has found a workaround.
Thanks ccs.
@goRt - are you still using the Release version 5.4? I'm testing this on a development image which has had fixes made to the Event Id (sourced from the Sky IEPG transponder) which now matches the EIT now/next data. There have been a few tweaks to the menus system also, but I don't know if they will have any effect on VPS function.
Just for clarity.
1) AutoTimer setting from EPG works fine for me. It provides a VPS setting option in the menu dialogue. The subsequent timers generated by AutoTimer have the VPS info in them and they appear to be working fine.
2) Manual timer setting from EPG does not provide any VPS options. No VPS info visible in the subsequently generated timer unless I delete the timer name in the menu dialogue. Then I get VPS option.
3) Instant record pops up a VPS dialogue once the recording starts.
This is through the menu system. I haven't tried OpenwebIF.
Thanks ccs.
@goRt - are you still using the Release version 5.4? I'm testing this on a development image which has had fixes made to the Event Id (sourced from the Sky IEPG transponder) which now matches the EIT now/next data. There have been a few tweaks to the menus system also, but I don't know if they will have any effect on VPS function.
Just for clarity.
1) AutoTimer setting from EPG works fine for me. It provides a VPS setting option in the menu dialogue. The subsequent timers generated by AutoTimer have the VPS info in them and they appear to be working fine.
2) Manual timer setting from EPG does not provide any VPS options. No VPS info visible in the subsequently generated timer unless I delete the timer name in the menu dialogue. Then I get VPS option.
3) Instant record pops up a VPS dialogue once the recording starts.
This is through the menu system. I haven't tried OpenwebIF.
Yes sir, my day to day is 5.3.039, I flip onto 5.4.004 release to test, if I change to dev in the menus will I pull the version you're working on? I want to avoid building yet another environment to build the dev branch from.
abu baniaz
02-02-21, 16:16
Posted in error.
@fat-tony, is the problem related to the timer name and description fields being prepopulated?
Maybe try reversing this code and testing again...
https://github.com/OpenViX/enigma2/commit/9945c0dd79bf0582514dc1c7d4f5bcdd4f4e152a#diff-7052796837b65112c64a709cd7c0dc99a105b80950c8c89a25 ef71c5be824122
This is GREEN GREEN from live tv though, not from EPG.
There appears to have been more activity on VPS in OpenPLi over recent years....
https://github.com/OpenPLi/enigma2-plugins/tree/master/vps/src_py
OE-Alliance....
https://github.com/oe-alliance/enigma2-plugins/tree/master/vps/src_py
There appears to have been more activity on VPS in OpenPLi over recent years....
https://github.com/OpenPLi/enigma2-plugins/tree/master/vps/src_py
OE-Alliance....
https://github.com/oe-alliance/enigma2-plugins/tree/master/vps/src_py
Last I looked they were on 1.6, we're on 1.3
..... version 1.7 two years ago. :)
abu baniaz
02-02-21, 17:15
@fat-tony, is the problem related to the timer name and description fields being prepopulated?
Maybe try reversing this code and testing again...
https://github.com/OpenViX/enigma2/commit/9945c0dd79bf0582514dc1c7d4f5bcdd4f4e152a#diff-7052796837b65112c64a709cd7c0dc99a105b80950c8c89a25 ef71c5be824122
This is GREEN GREEN from live tv though, not from EPG.
In channel selection as well as grid EPG, I select Green to add timer, there is definitely an Enable VPS option.
Thanks abu - I definitely don't get the "enable VPS" option in GREEN (add timer), only in BLUE (add autotimer). I wonder if I have a rogue .py file somewhere? I'll check and then maybe do a couch flash and restore.
Here's a screenshot of a timer selection from grid EPG:
@fat-tony, is the problem related to the timer name and description fields being prepopulated?
Maybe try reversing this code and testing again...
https://github.com/OpenViX/enigma2/commit/9945c0dd79bf0582514dc1c7d4f5bcdd4f4e152a#diff-7052796837b65112c64a709cd7c0dc99a105b80950c8c89a25 ef71c5be824122
This is GREEN GREEN from live tv though, not from EPG.
Thanks @Huevos. GREEN GREEN on the current code - no VPS option. When I reverse the code as suggested, then GREEN GREEN from the current live service provides a VPS option. No effect on EPG as you say.
I am using current code in the enigma repo and plugin repo.
From GREEN GREEN I get this:
61393
From EPG GREEN I get this:
61394
No idea what is supposed to be wrong.
Very mysterious - you and abu have the VPS option from grid EPG. I only get the option when name field is empty (as per your suggested change) or in autotimer or instant record. Either I have a odd setting in the user interface or a rogue piece of code somewhere. I'll try a download flash and no restore and install VPS clean, then try a settings restore.
This was a clean install without restoring anything.
This was a clean install without restoring anything.
Does a restore change anything?
Does a restore change anything?I got the box out of the cupboard for this test. I haven't got anything to restore (for this box).
abu baniaz
02-02-21, 20:21
@Fat Tony, I am on 5.4 006.011. Which image are you on?
Same abu. I haven't done a flash yet. Will report back!
Downloaded dev 5.4.006.011, flashed and restored settings. Same - autotimers provide a VPS enable setting, manual timer nothing.
I installed VPS on my GB Quad Plus. Dev 5.4.006.011 - exactly the same result. Autotimers ok, but manual timer shows no sign of VPS. I must have some fundamental difference in settings which is blocking VPS on manual timers.
So can we have a copy of the backup. :)
Thought I'd give it a try with a bog standard flash of 5.4.005, with no settings restored.
Added VPS plugin and both timers and autotimers showed the option to enable VPS.
Then tried a settings restore and got a crash :confused:, removing VPS and the settings restore worked ok.
Added VPS again, both timers and autotimers showed the option to enable VPS, but a settings restore crashed the box.
(Freeview only.)
Simplified version....
Added VPS plugin and both timers and autotimers showed the option to enable VPS, took a settings restore and restored it, got the crash.
Settings....
config.autobouquetsmaker.FTA_only=terrestrial_uk_f reeview
config.autobouquetsmaker.providers=terrestrial_uk_ freeview:belmont____________:13:
config.av.videomode.HDMI=1080i
config.backupmanager.backupdirs=['/etc/enigma2/', '/etc/fstab', '/etc/hostname', '/etc/network/interfaces', '/etc/passwd', '/etc/shadow', '/etc/etc/shadow', '/etc/resolv.conf', '/etc/ushare.conf', '/etc/inadyn.conf', '/etc/tuxbox/config/', '/etc/wpa_supplicant.conf', '/usr/softcams/', '/etc/auto.network', '/etc/samba', '/usr/keys']
config.misc.firstrun=False
config.misc.initialchannelselection=False
config.misc.languageselected=False
config.misc.restorewizardrun=True
config.misc.startCounter=2
config.misc.videowizardenabled=False
config.Nims.0.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.1.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.2.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.3.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.4.multiType=1
config.Nims.4.terrestrial=All regions, United Kingdom, (Europe DVB-T/T2)
config.Nims.5.multiType=nothing
config.plugins.epgsearch.numorbpos=0
config.tv.lastroot=1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "bouquets.tv" ORDER BY bouquet;1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.abm.terrestrial_uk_freeview.main.tv" ORDER BY bouquet;
config.tv.lastservice=1:0:19:4484:4089:233A:EEEE00 00:0:0:0:
config.usage.date.compact=%-d %b
config.usage.date.compressed=%-d%b
config.usage.date.displayday=%a %-d %b
config.version=53023
Extrainstalled plugins...
enigma2-plugin-systemplugins-vps
run-postinsts
Crash....
< 104.6909> 10:20:28.1104 [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.abm.terrestrial_uk_freeview.main.radio
< 104.6910> 10:20:28.1105 [eDVBDB] 1 entries in Bouquet userbouquet.abm.terrestrial_uk_freeview.main.radio
< 104.6911> 10:20:28.1105 [eDVBDB] loading bouquet... /etc/enigma2//userbouquet.favourites.radio
< 104.6911> 10:20:28.1106 [eDVBDB] 0 entries in Bouquet userbouquet.favourites.radio
< 104.6911> 10:20:28.1106 [eDVBDB] 2 entries in Bouquet bouquets.radio
< 104.6911> 10:20:28.1106 [eDVBDB] Renumbering...
< 104.6918> 10:20:28.1113 Traceback (most recent call last):
< 104.6918> 10:20:28.1113 File "/usr/lib/enigma2/python/Components/Console.py", line 45, in finishedCB
< 104.6922> 10:20:28.1117 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/ViX/BackupManager.py", line 456, in Stage1SettingsComplete
< 104.6924> 10:20:28.1119 TypeError: new_RecordTimer_loadTimer() got an unexpected keyword argument 'justLoad'
< 104.6926> 10:20:28.1121 [ePyObject] (CallObject(<bound method EnigmaLogFatal.write of <bound method ConsoleItem.dataAvailCB of <bound method EnigmaLogDebug.write of <bound method ConsoleItem.__init__ of <bound method Progress.checkSuspend of <bound method ActionMap.action of <bound method eActionMap.eActionMap_unbindAction of <bound method eActionMap.eActionMap_unbindAction of <bound method eLabel.eLabel_setText of <bound method eSlider.eSlider_setValue of <bound method Pixmap.changed of <bound method CList.__call__ of <bound method ConditionalShowHide.__getattr__ of <bound method ActionMap.__init__ of <bound method Label.changed of <bound method CList.__call__ of <bound method eLabel.eLabel_setText of <bound method Label.changed of <bound method CList.__call__ of <unbound method eLabel.eLabel_setText>>>>>>>>>>>>>>>>>>>>,(0,)) failed)
So can we have a copy of the backup. :)
I did a clean flash, no restore and downloaded VPS plugin and configured settings. Same issue - no VPS option on manual record from EPG. So, I went back to my actual VPS settings and turned them all off except "Enable VPS plugin" and I got the VPS option on manual record from EPG!
So, my initial setting of yes to "VPS enabled by default" seems to be the source of the problem. With the setting to no as per attached screenshot, then I get the VPS option in manual record settings. However, after setting that to yes and saving with the GREEN button a subsequently checking the setting menu, it appears that the VPS setting has remained at no. Can anyone confirm this?
Thought I'd give it a try with a bog standard flash of 5.4.005, with no settings restored.
Added VPS plugin and both timers and autotimers showed the option to enable VPS.
Then tried a settings restore and got a crash :confused:, removing VPS and the settings restore worked ok.
Added VPS again, both timers and autotimers showed the option to enable VPS, but a settings restore crashed the box.
(Freeview only.)
Hi ccs - is there not an issue with Release code and VPS which is causing crashes? The development code to address various issues has not made it to Release yet.
I did a clean flash, no restore and downloaded VPS plugin and configured settings. Same issue - no VPS option on manual record from EPG. So, I went back to my actual VPS settings and turned them all off except "Enable VPS plugin" and I got the VPS option on manual record from EPG!
So, my initial setting of yes to "VPS enabled by default" seems to be the source of the problem. With the setting to no as per attached screenshot, then I get the VPS option in manual record settings. However, after setting that to yes and saving with the GREEN button a subsequently checking the setting menu, it appears that the VPS setting has remained at no. Can anyone confirm this?
Can confirm I replicate this.
To add - when in create timer, toggling VPS the focus jumps to the title rather than remaining on the VPS option
Yes - I got that too. It seems to be channel dependent. I couldn't get it to work at all on our terrestrial service (Saorview) here in Ireland.
If it's any help I added the "justLoad" item mentioned in the crash (some time ago).
It is to stop sanity checking on timers as the system starts up as it's possible at that point for the tuner config to be incomplete and hence checking for clashes at that point would be unreliable, and quite likely to fail (and often did for me, hence the code change).
EDIT: That was 3 years ago (and the call is currently on line 466, not 456).
So the issue is in what self.session.nav.RecordTimer.loadTimer is set to.
Does the VPS plugin do something with this?
.... my timers.xml file was empty, if that could be significant...
<?xml version="1.0" ?>
<timers>
</timers>
and in my basic test I didn't configure VPS at all.
Hi ccs - is there not an issue with Release code and VPS which is causing crashes? The development code to address various issues has not made it to Release yet.
Not that I'm aware of, but could easily be wrong.
If it's any help I added the "justLoad" item mentioned in the crash (some time ago).
It is to stop sanity checking on timers as the system starts up as it's possible at that point for the tuner config to be incomplete and hence checking for clashes at that point would be unreliable, and quite likely to fail (and often did for me, hence the code change).
EDIT: That was 3 years ago (and the call is currently on line 466, not 456).
So the issue is in what self.session.nav.RecordTimer.loadTimer is set to.
Does the VPS plugin do something with this?
The version of BackupManager.py in 5.4.005 is this.....
https://github.com/OpenViX/vix-core/blob/1d3988c712516d33ae7f9b281b0ab800b2586f5b/src/BackupManager.py which does crash at line 456.
I reckon you're looking at the current master version...
https://github.com/OpenViX/vix-core/blob/master/src/BackupManager.py
I reckon you're looking at the current master version...Yes - I just went to github to look.
Where is the source of the VPS plugin?
I'm wondering whether it is intercepting the loadTimer call incorrectly. Any such intercept has to be able to handle anything thrown at it (not difficult - I had to ensure this in the EPG Translator plugin).
The version of BackupManager.py in 5.4.005 is this.....
https://github.com/OpenViX/vix-core/blob/1d3988c712516d33ae7f9b281b0ab800b2586f5b/src/BackupManager.py which does crash at line 456.
I reckon you're looking at the current master version...
https://github.com/OpenViX/vix-core/blob/master/src/BackupManager.pyThat is not the current version.
Where is the source of the VPS plugin?
Here are a couple of choices...
https://www.world-of-satellite.com/showthread.php?62706-EPG-Refresh-iEPG-and-VPS&p=508825&viewfull=1#post508825
I'm wondering whether it is intercepting the loadTimer call incorrectly. Any such intercept has to be able to handle anything thrown at it (not difficult - I had to ensure this in the EPG Translator plugin).Yes - it's a bug in the plugin.
It's intercepting calls (code in Modifications.py) and making assumptions about the args they will be passed. So if the intercepted call actually has additional ones (as the Vix one does) it crashes.
I'll see about making a working plugin....
Here are a couple of choices...
https://www.world-of-satellite.com/showthread.php?62706-EPG-Refresh-iEPG-and-VPS&p=508825&viewfull=1#post508825
Found it in enigma2-plugins.
That is not the current version.
Not easy to find, some of these .py's, where should I have been looking?
I'll see about making a working plugin....Here's a Modifications.py with the intercepts coded such that they can handle any caller. (I think).
(attachment removed - I spotted an error...)
I can't download the current plugin to put it into it as:
[et8000]: opkg download enigma2-plugin-systemplugins-vps
Downloading http://openvixdev.satellites-xml.org/feeds/openvix/developer/5.4/et8000/et8000/enigma2-plugin-systemplugins-vps_5.4+git6872+101e697-r0_et8000.ipk.
Removing corrupt package file /var/cache/opkg/149de60da1622c41645f8e9162da73e0_enigma2-plugin-systemplugins-vps_5.4+git6872+101e697-r0_et8000.ipk.
Collected errors:
* pkg_verify: File size mismatch: /var/cache/opkg/149de60da1622c41645f8e9162da
73e0_enigma2-plugin-systemplugins-vps_5.4+git6872+101e697-r0_et8000.ipk is 3762
2 bytes, expecting 37600 bytes
* opkg_download_cmd: Failed to download enigma2-plugin-systemplugins-vps.
EDIT: Fixed that. Had to do an update first....but the files are compiled in it and these are arch-specific(?) so I can't just replace the *.pyo file there.
Here's a Modifications.py with the intercepts coded such that they can handle any caller. (I think).
61409
I can't download the current plugin to put it into it as:
EDIT: Fixed that. Had to do an update first....but the files are compiled in it and these are arch-specific(?) so I can't just replace the *.pyo file there.
Any reason not to go the 1.7 version mentioned as being in openPLI?
Any reason not to go the 1.7 version mentioned as being in openPLI?Well, I was using the one that is in the enimga2-plugins source and so ends up in the package manager.
If there's anther one that should be used then there's more than one thing that requires fixing here.
But I'd still need to know where the v1.7 PLi code is (OK - found it).
Can confirm I replicate this.
To add - when in create timer, toggling VPS the focus jumps to the title rather than remaining on the VPS optionTo update,while adding a timer presents the VPS option and appears to let you select yes and save, if you subsequently edit the timer then the VPS option hasn't been saved.
Sent from my IN2013 using Tapatalk
Here's a Modifications.py with the intercepts coded such that they can handle any caller. (I think).
(attachment removed - I spotted an error...)
I can't download the current plugin to put it into it as:
EDIT: Fixed that. Had to do an update first....but the files are compiled in it and these are arch-specific(?) so I can't just replace the *.pyo file there.
I didn't spot you spotting an error.
The settings restore now works ok, but epg/green causes a crash, you probably know already..
< 46.2044> 18:39:50.1219 [InfoBarGenerics] Key: 399 (Break) KeyID='KEY_GREEN' Binding='('GREEN',)'.
< 46.2045> 18:39:50.1220 [ActionMap] Keymap 'ColorActions' -> Action = 'green'.
< 46.2183> 18:39:50.1358 Traceback (most recent call last):
< 46.2183> 18:39:50.1358 File "/usr/lib/enigma2/python/Components/ActionMap.py", line 57, in action
< 46.2186> 18:39:50.1361 File "/usr/lib/enigma2/python/Screens/UserDefinedButtons.py", line 30, in keypressHandler
< 46.2187> 18:39:50.1362 File "/usr/lib/enigma2/python/Screens/EpgSelectionBase.py", line 359, in addEditTimer
< 46.2189> 18:39:50.1364 File "/usr/lib/enigma2/python/Screens/TimerEntry.py", line 286, in addTimerFromEvent
< 46.2191> 18:39:50.1366 File "/usr/lib/enigma2/python/mytest.py", line 324, in openWithCallback
< 46.2193> 18:39:50.1368 dlg = self.open(screen, *arguments, **kwargs)
< 46.2193> 18:39:50.1369 File "/usr/lib/enigma2/python/mytest.py", line 334, in open
< 46.2195> 18:39:50.1371 dlg = self.current_dialog = self.instantiateDialog(screen, *arguments, **kwargs)
< 46.2196> 18:39:50.1371 File "/usr/lib/enigma2/python/mytest.py", line 271, in instantiateDialog
< 46.2198> 18:39:50.1373 return self.doInstantiateDialog(screen, arguments, kwargs, self.desktop)
< 46.2198> 18:39:50.1373 File "/usr/lib/enigma2/python/mytest.py", line 294, in doInstantiateDialog
< 46.2200> 18:39:50.1376 dlg = screen(self, *arguments, **kwargs)
< 46.2201> 18:39:50.1376 File "/usr/lib/enigma2/python/Screens/TimerEntry.py", line 23, in __init__
< 46.2202> 18:39:50.1377 File "/usr/lib/enigma2/python/Screens/TimerEntryBase.py", line 20, in __init__
< 46.2203> 18:39:50.1378 File "/usr/lib/enigma2/python/Screens/Setup.py", line 44, in __init__
< 46.2205> 18:39:50.1380 File "/usr/lib/enigma2/python/Plugins/SystemPlugins/vps/Modifications.py", line 191, in new_TimerEntry_createSetup
< 46.2214> 18:39:50.1389 self._createSetup_old_rn_vps(*args, **kwargs)
< 46.2215> 18:39:50.1390 NameError: global name 'args' is not defined
< 46.2215> 18:39:50.1391 [ePyObject] (CallObject(<bound method HelpableActionMap.action of <Components.ActionMap.HelpableActionMap instance at 0xb0e799e0>>,('ColorActions', 'green')) failed)
I'm only trying to fix the crash. Which occurs as the plugin code expects the enigma2 code to be using a specific API, and it can't cater for any change to this (although it should, and can).
There is some attempt to do this in both the Vix and PLi plugin, but they've both just hardwired specific hacks to one specific call rather than generalizing everything.
Here are versions which I think should fix the crash for both the Vix and PLi version of the plugin.
But it would help if there were some agreement on which should be used, and the other one to be deleted (to avoid further confusion).
PLi plugin: 61410
Vix pugin: Updated, see: https://www.world-of-satellite.com/showthread.php?62706-EPG-Refresh-iEPG-and-VPS&p=509007&viewfull=1#post509007
I thought the last version fixed the crash? Anyway, I'll try again later this evening when recordings are finished.
I thought the last version fixed the crash?That was the intent, but I forgot to edit one line.
To update,while adding a timer presents the VPS option and appears to let you select yes and save, if you subsequently edit the timer then the VPS option hasn't been saved.
Sent from my IN2013 using Tapatalk
I was getting the same issue. It looked like I was selecting VPS=yes on the timer edit and saving with GREEN as usual, but looking at the timer subsequently the setting was =no.
I'm only trying to fix the crash. Which occurs as the plugin code expects the enigma2 code to be using a specific API, and it can't cater for any change to this (although it should, and can).
There is some attempt to do this in both the Vix and PLi plugin, but they've both just hardwired specific hacks to one specific call rather than generalizing everything.
Here are versions which I think should fix the crash for both the Vix and PLi version of the plugin.
But it would help if there were some agreement on which should be used, and the other one to be deleted (to avoid further confusion).
PLi plugin: 61410
Vix pugin: 61411
ViX version works fine doing a settings restore, and there is no longer a crash in epg/green mentioned in post #181.
VPS option shows in timers and autotimers.
Selecting VPS=yes still gets lost after saving.
Based on a bog standard 5.4.005
ViX version works fine doing a settings restoreGood news, thanks
, and there is no longer a crash in epg/green mentioned in post #181. That was my fault (and why I removed the original).
Selecting VPS=yes still gets lost after saving.Since the crash is fixed I may look at that next.
I'm only trying to fix the crash. Which occurs as the plugin code expects the enigma2 code to be using a specific API, and it can't cater for any change to this (although it should, and can).
There is some attempt to do this in both the Vix and PLi plugin, but they've both just hardwired specific hacks to one specific call rather than generalizing everything.
Here are versions which I think should fix the crash for both the Vix and PLi version of the plugin.
But it would help if there were some agreement on which should be used, and the other one to be deleted (to avoid further confusion).
PLi plugin: 61410
Vix pugin: 61411
No point doing anything with the PLi plugin because we are OE-A and build from our repos.
Gordon, you have removed P3 compatibility. This plugin is used in P3 images.
Gordon, you have removed P3 compatibility. This plugin is used in P3 images.Not knowingly. All I've done is make the call interceptions totally generic (in that they can handle being called with any args).
What is the actual issue?
No point doing anything with the PLi plugin because we are OE-A and build from our repos.OK; but I was asked to do so, so someone here is using the PLi version.
Selecting VPS=yes still gets lost after saving.OK. I've actually installed the plugin (but, from what I've picked up in the past it will be of no use to me as Freeview doesn't send the expected signals?).
Now sure what you mean by "setting VPS=yes".
I can see "Enable VPS plugin" (which is on by default) and "VPS enabled by default" (which is No by default).
Ah!!! I see.
If you disable the plugin, that works. But you then can't turn it back on!!!
Should be simple to track that down (hopefully...)
Forcing the config.plugins.vps.enabled setting to be written out whatever its value fixes the issue.
Not sure that this should be required, but if you drop this plugin.py in place it will at least let it be switched back on.
61412
Not knowingly. All I've done is make the call interceptions totally generic (in that they can handle being called with any args).
What is the actual issue?
Well done for making progress with this. Re: P3 I was talking about removal of absolute import.
Once this is working someone needs give it a test in P3 (maybe Twol).
abu baniaz
04-02-21, 02:41
Plugin "version number" is a subjective thing as that is based on the repo that it is built from. As we use boxbranding, the two versions are going to be different. If anybody is using a PLI version on our Distro, they are confusing things. Please don't spend your time trying to fix the PLI version. Ideally, we should add the fixes/improvements from PLI to our version. And send our fixes to PLI too. There haven't been any functional changes to our version since 2013
The commit histories are:
PLI
https://github.com/OpenPLi/enigma2-plugins/commits/master/vps
OE-A images
https://github.com/oe-alliance/enigma2-plugins/commits/master/vps
Well done for making progress with this. Re: P3 I was talking about removal of absolute import.Nothing to do with me. All I changed was a set of def () statements (and the calls to their intercepted originals) and removed a bit of code that was no longer necessary.
No changes at all to any imports.
So if P3 has a problem with them I'd need to know which they are to see what the problem might be.
EDIT: By P3 do you mean Python3? I was going to look at that, but I've done nothing that isn't Py3 compatible.
(I did remove an attempted import of six, as the associated hack is no longer required).
Please don't spend your time trying to fix the PLI version. Ideally, we should add the fixes/improvements from PLI to our version.That was basically what I was going to do.
(Although originally all I was going to do was to fix the fact the code couldn't handle the "justLoad" optional parameter.)
So if anyone knows of anything that the PLi code can do that the Vix code doesn't it would help me whilst I look.
Turns out the code I put in for the optional widget parameter in the new_TimerEntry_createSetup() function was wrong.
Oddly, thanks to Pythons bizarre mixing of its two parameter passing methods, it would actually work. Not sure that Vix ever sends one anyway (PLi does, but it always sends it).
I also notice that the Information screen doesn't actually show all of the text that it should (is there a length/line limit to a ScrollLabel() text?).
And the part that gets chopped off is quite important...
Gordon, my mistake. I was diffing against the Dev branch.
Turns out the code I put in for the optional widget parameter in the new_TimerEntry_createSetup() function was wrong.
Oddly, thanks to Pythons bizarre mixing of its two parameter passing methods, it would actually work. Not sure that Vix ever sends one anyway (PLi does, but it always sends it).
I also notice that the Information screen doesn't actually show all of the text that it should (is there a length/line limit to a ScrollLabel() text?).
And the part that gets chopped off is quite important...
Info screen works for me.
Can you post your updated version please.
alexwilmac
04-02-21, 12:27
I was really sceptical about this claimed workaround because I knew I must've already tried almost everything. And, as a matter of fact, it doesn't work.
As before, it seems to accept the VPS setting but, if you enter the timer immediately after having created it, it is set to NO, as before.
And, anyway, it'd be a very limited workaround as 99% of the non-Autotimer created timers come from EPG, not from a totally new setting from scratch.
Yes , I found that the the manual timer setting just doesn't stick. Only timers generated by AutoTimer seem to work. Furthermore, I can't get the plugin to work at all on Irish terrestrial TV (Saorview), only on satellite. I think the VPS plugin is possibly looking for the presence of the PDC_descriptor field (0x69) in the EIT and it won't activate if it doesn't find it. One of the devs here is tweaking the code to see if he can get manual EPG timers to work. To be honest, I think the plugin has limited scope without a lot of work. Ordinary AutoTimer works most of the time for most users.
I did a test yesterday on vix 5.3 using epg data downloaded with crosspeg and it seems to work very well with autotimers on 28e. Recordings started and stopped on event change as expected. I wouldn't be expecting much of saorview though - they haven't grasped the concept of surround sound or full HD yet. If manual epg timers can be got working then I would imagine it to be quite useful.
Yes , I found that the the manual timer setting just doesn't stick. Only timers generated by AutoTimer seem to work. Furthermore, I can't get the plugin to work at all on Irish terrestrial TV (Saorview), only on satellite. I think the VPS plugin is possibly looking for the presence of the PDC_descriptor field (0x69) in the EIT and it won't activate if it doesn't find it. One of the devs here is tweaking the code to see if he can get manual EPG timers to work. To be honest, I think the plugin has limited scope without a lot of work. Ordinary AutoTimer works most of the time for most users.
Actually - scratch that. That PDC descriptor field is not present in the satellite EIT stream, so it must be something else that it is looking for. Maybe I'll have a look in the code to see if I can see what it's trying to find. It works fine, though, on autotimers on satellite, providing the broadcaster is sending the now/next changes accurately. Channel 5 seems to trigger the running status change based on a clock timer (the EPG scheduled time) rather than the actual transmission. BBC/ITV/C4 are all ok.
Freeview seems to work ok (only) using autotimers ....
Here's a complete bbc1 recording, padding had it originally timed from 12:55 until 13:35. The end of the recording missed about 1 second.
(Debug logs only show the same details as timer/info.)
Info screen works for me.That looks as though the Simple_1080 skin has produced that?
I use ViXBMC_Confluence_1080, and with that it uses the compiled-in skin. And with that the final lines don't show.
Can you post your updated version please.I will once I make a few more changes. The "correction" I mentioned will make no difference at the moment (possibly never, but...).
I've looked at the code and the plugin is definitely looking for the PDC (Programme Delivery Control) descriptor (0x69 or 105 decimal) in the EIT. I don't see any PDC when I analyse the EIT on 28.2. If I look at the plugin's vps.xml file in /etc/enigma2 it contains the entry "has_pdc=0" in each line, however it seems to work ok on autotimers on satellite and now apparently on Freeview.
@ccs - I get the same on satellite. My original padding is ignored (as expected) and the recording starts and stops on the broadcast programme boundaries.
Gordon, my mistake. I was diffing against the Dev branch.You mean the dev branch.
Hmm...so there's a dev branch, and I'm fixing master. Does that make sense?
Much of the "messy" change to Modifications.py in dev goes away once you handle all incoming args "properly".
I suppose that the plugin is targeted at German channels and they probably use that descriptor in their EIT. Its probably a needless compatibility check on manual timers but then again some some of check would be advisable. I had noticed it when setting up manual timers that this check was failing and it would proceed in "safe mode".
@birdman - any testing would be done on a dev build I presume? I'm testing here on dev and the plugin seems to be working ok on autotimers. One-off timers set from the EPG are not working properly. The VPS setting on a manual timer doesn't seem to stick after saving.
@ronand - it's my day for apologies, apparently! I did another test on Saorview, setting an autotimer and enabling VPS on an event that was about 30 minutes ahead. Worked fine - VPS modified the start time (ignoring my padding) and started the recording as the event in the EIT changed. It terminated the recording when the event changed again at the end. So it's working for me on autotimers on sat and terrestrial. Overall, I'd question how useful it is over an autotimer unless you are using a broadcaster who is accurately modifying the now/next events to align with the actual programme start. BBC/ITV/C4 certainly automate the now/next changeover with the actual programme start, but other broadcasters don't - like C5 for example, or Saorview which just uses the scheduled event time to send now/next change.
@ronand - it's my day for apologies, apparently! I did another test on Saorview, setting an autotimer and enabling VPS on an event that was about 30 minutes ahead. Worked fine - VPS modified the start time (ignoring my padding) and started the recording as the event in the EIT changed. It terminated the recording when the event changed again at the end. So it's working for me on autotimers on sat and terrestrial. Overall, I'd question how useful it is over an autotimer unless you are using a broadcaster who is accurately modifying the now/next events to align with the actual programme start. BBC/ITV/C4 certainly automate the now/next changeover with the actual programme start, but other broadcasters don't - like C5 for example, or Saorview which just uses the scheduled event time to send now/next change.When you come from a toppy it's the way things should be
Sent from my IN2013 using Tapatalk
I've never noticed these debug entries before (5.4.005, Freeview, no VPS in sight)...
18:24:41.6992 [eDVBServiceRecord] now running: BBC News at Six (1800 seconds)
18:32:21.7105 [eDVBServiceRecord] pcr of eit change for event 18827: 19514571c
18:32:21.7106 [eDVBServiceRecord] now running: Look North (East Yorkshire and... (1800 seconds)
@birdman - any testing would be done on a dev build I presume?I'm talking about a dev branch of oe-alliance/enigma2-plugins. Not sure whether anything uses that for a build.
I've never noticed these debug entries before (5.4.005, Freeview, no VPS in sight)...
18:24:41.6992 [eDVBServiceRecord] now running: BBC News at Six (1800 seconds)
18:32:21.7105 [eDVBServiceRecord] pcr of eit change for event 18827: 19514571c
18:32:21.7106 [eDVBServiceRecord] now running: Look North (East Yorkshire and... (1800 seconds)
I would see entries like these (pre-VPS) when I was recording. Are you saying that you weren't recording BBC News?
I'm talking about a dev branch of oe-alliance/enigma2-plugins. Not sure whether anything uses that for a build."dev" branch => used by OpenATV. Also used by our P3 project.
"dev" branch => used by OpenATV. Also used by our P3 project.Well, it needs to be fixed too.
I'll tidy up the master version (as used by Vix) then make the same changes to dev.
After that I'll look at adding PLi changes into both (from a quick look earlier today that only seemed to involve "pausing").
I would see entries like these (pre-VPS) when I was recording. Are you saying that you weren't recording BBC News?
Look North was the first recording, it's been a busy night recording wise, but it looks like they're all linked with recordings about to start.
I'll have another look tomorrow when there are no recordings, it's very cluttered at the moment, like all these threads!
VPS is reported to work with Freeview, so it should work for you. Mind you, I have only got it working with timers generated by AutoTimer. I have my doubts about the usefulness of VPS on its own. Really needs to be combined with CRID handling to have a killer series-link and exact time recording plug-in. :cool: ...continue in other thread!
Just a note regarding the other thread - I think birdman said he couldn't find any working services. Recording on the likes of BBC and ITV on 28e is working fine on 5.4.005 (release) using autotimers. I found that the only epg data that would work correctly is the openTV data downloaded with crossepg. Manual recording fails the check (but that is known already)
abu baniaz
05-02-21, 01:11
Just in case anyone is unaware, Birdman is UK Terrestrial only. So he can't test satellite reception.
VPS is reported to work with Freeview, so it should work for you.Is there anyway to check whether the data is being seen?
abu baniaz
05-02-21, 08:21
@Fat-Tony, on the FTP site, there is a folder with raw stream recordings of UK Terrestrial in the AV folder. Let me know if you want a more recent grab.
Bit confused by @birdman saying "I don't think I have a single service that VPS works with, but will attempt to get it working."
I thought my posts confirmed yesterday that freeview works? :confused:
eg https://www.world-of-satellite.com/showthread.php?62706-EPG-Refresh-iEPG-and-VPS&p=508950&viewfull=1#post508950
Bit confused by @birdman saying "I don't think I have a single service that VPS works with, but will attempt to get it working."
I thought my posts confirmed yesterday that freeview works? :confused:
eg https://www.world-of-satellite.com/showthread.php?62706-EPG-Refresh-iEPG-and-VPS&p=508950&viewfull=1#post508950
I can confirm VPS works on FreeView
@Fat-Tony, on the FTP site, there is a folder with raw stream recordings of UK Terrestrial in the AV folder. Let me know if you want a more recent grab.
Works fine with Irish terrestrial service (Saorview). You need a live stream where the now/next EIT changes status to (4/running) when the programme starts.
I've never noticed these debug entries before (5.4.005, Freeview, no VPS in sight)...
18:24:41.6992 [eDVBServiceRecord] now running: BBC News at Six (1800 seconds)
18:32:21.7105 [eDVBServiceRecord] pcr of eit change for event 18827: 19514571c
18:32:21.7106 [eDVBServiceRecord] now running: Look North (East Yorkshire and... (1800 seconds)
I would see entries like these (pre-VPS) when I was recording. Are you saying that you weren't recording BBC News?
They only appear during a recording, they indicate the setting of start (and finish) markers that appear in the progress bar. (Apologies if the terminology is wrong.)
So Look North started at 18:25 with pre-padding, actually started at 18:32:21 (the marker confirms this), and the eit number in the timer was 18827.
I guess any type of source - cable, satellite, aerial, could be checked this way.
Bit confused by @birdman saying "I don't think I have a single service that VPS works with, but will attempt to get it working."That was based on looking at the VPS plugin several years ago and being told then that it only applied to a few services, none of which was Freeview.
EDIT: Although if I try to use it (on a timer set by AutoTimer) it says that it can't determine whether the channel supports VPS.
It's those EIT changes (now/next running status and event ID) that the VPS plugin looks for and then starts (and stops) the recording. @goRt's Topfield recorder and my old Humax Freesat recorder do exactly the same. The VPS plugin also looking for another field (PDC) in the EIT which doesn't seem to be present in the satellite stream, but it seems to work anyway. I don't know if it will actually switch channels if an event gets moved due to the PDC not being present. The PDC is just a field indicating the day/month/hour/minute of the event, so I'm not sure what information it would use to switch channels. The CRID system is normally used for that - (series link on Sky/Freesat).
Info screen works for me.Thanks. Turns out that it actually works for me too. Just that when you scroll down the scrollbar appears to have reached the end, but it hasn't. Another press reveals the "missing" text.
The built-in skin data needs to be changed to allow a larger one for Full-HD screens.
I don't know if it will actually switch channels if an event gets moved due to the PDC not being present.
I doubt the system is that advanced. It seems to switch to the designated recording channel 5 minutes before scheduled start and then begins monitoring the event info. I would imagine if the program started 10 minutes early then it will miss the start. If the program has changed channel I don't think the plugin has any way of knowing that and won't find it. That is my observation from very limited use of it although I'm sure goRt should be able to confirm its behaviour.
Here are 2 updated files.
Removed - see: https://www.world-of-satellite.com/showthread.php?62706-EPG-Refresh-iEPG-and-VPS&p=509030&viewfull=1#post509030
I've changed the builtin config and information screen skin so that it is larger on HD screens.
I've also changed Modifications.py to handle the fact that the plugin makes a call using a non-Vix API to createSetup(). (So I had a crash while checking things).
Looks like the hack is needed after all.
That was based on looking at the VPS plugin several years ago and being told then that it only applied to a few services, none of which was Freeview.
EDIT: Although if I try to use it (on a timer set by AutoTimer) it says that it can't determine whether the channel supports VPS.
You can ignore that.
Forcing the config.plugins.vps.enabled setting to be written out whatever its value fixes the issue.
Not sure that this should be required, but if you drop this plugin.py in place it will at least let it be switched back on.
61412
Is this change still needed?
Is this change still needed?It was needed when I changed it, and no-one else has changed anything since.
So I'd say that it is. It's not affected by Updates.zip (if that is what you were querying).
It was needed when I changed it, and no-one else has changed anything since.
So I'd say that it is. It's not affected by Updates.zip (if that is what you were querying).
Thanks, I just half expected plugin.py to be in the zip file.
I doubt the system is that advanced. It seems to switch to the designated recording channel 5 minutes before scheduled start and then begins monitoring the event info. I would imagine if the program started 10 minutes early then it will miss the start. If the program has changed channel I don't think the plugin has any way of knowing that and won't find it. That is my observation from very limited use of it although I'm sure goRt should be able to confirm its behaviour.Isn't the look ahead a configurable item, I think the default is 10 mins
Sent from my IN2013 using Tapatalk
Isn't the look ahead a configurable item, I think the default is 10 mins
Sent from my IN2013 using Tapatalk
Programmes tend to start later than scheduled or are switched to a different channel, can VPS cope with a channel change?
Here are 2 updated files.
61421
I've changed the builtin config and information screen skin so that it is larger on HD screens.
I've also changed Modifications.py to handle the fact that the plugin makes a call using a non-Vix API to createSetup(). (So I had a crash while checking things).
Looks like the hack is needed after all.
Hi birdman. I've installed the .py files in the zip plus the plugin.py file from earlier. What differences should I see? I'm on a dev build and using the simple 1080 skin. I don't notice any difference in behaviour. Still working on AutoTimers but setting reverts to no when I enable it on manual timer (EPG GREEN) same as before.
Programmes tend to start later than scheduled or are switched to a different channel, can VPS cope with a channel change?No channel change capability even though the eit remains constant :-(
Sent from my IN2013 using Tapatalk
Hi birdman. I've installed the .py files in the zip plus the plugin.py file from earlier. What differences should I see?You should no longer see a crash when trying to enable VPS on an AutoTimer (which my previous Modifications.py had let creep in).
Still working on AutoTimers but setting reverts to no when I enable it on manual timer (EPG GREEN) same as before.Haven't looked at that yet. Should be able to have a poke around this evening.
Although when I look at adding a manual timer there is no VPS option at all!!
EDIT: and that would be a result of the TimerEntry code knowing nothing about VPS at all (the AutoTimerEntry code does).
So the mystery is how you ever see it in a manual timer at all!?!
The only reason I started to look at anything was the fact that the optional "justLoad" parameter (which I'd added to Vix 3 years ago) was causing a crash.
You can ignore that.Why can't it determine whether the channel supports VPS?
Surely if it can't work that out then VPS isn't going to work well?
Programmes tend to start later than scheduled or are switched to a different channel, can VPS cope with a channel change?Even if VPS could, I doubt that AutoTimer would like it.
Why can't it determine whether the channel supports VPS?
Surely if it can't work that out then VPS isn't going to work well?
No idea, the tests I've done work with autotimers. The code is in Vps_check.py
Even if VPS could, I doubt that AutoTimer would like it.
I try to anticipate channel changes, once or twice a year, by adding an extra service to an autotimer.
It usually catches them when the epg changes, I run autotimer every 25 minutes, so a programme which is delayed gets the correct end time at the very least.
No idea whether this is anything to do with the VPS plugin but I've just got this:
< 4600.0235> 19:05:00.0023 [RecordTimer] stop recording on tuner: A
< 4600.0238> 19:05:00.0025 [eDVBServiceRecord] stop recording!
< 4600.0293> 19:05:00.0081 [eFilePushThreadRecorder] stopping thread: 100
< 4600.1297> 19:05:00.1084 [eFilePushThreadRecorder] stopping thread: 99
...
< 4602.5343> 19:05:02.5131 [eFilePushThreadRecorder] stopping thread: 75
< 4602.6345> 19:05:02.6133 [eFilePushThreadRecorder] stopping thread: 74
< 4602.7221> 19:05:02.7009 [gRC] main thread is non-idle! display spinner!
< 4602.7347> 19:05:02.7135 [eFilePushThreadRecorder] stopping thread: 73
< 4602.8350> 19:05:02.8138 [eFilePushThreadRecorder] stopping thread: 72
...
< 4609.8494> 19:05:09.8282 [eFilePushThreadRecorder] stopping thread: 2
< 4609.9496> 19:05:09.9284 [eFilePushThreadRecorder] stopping thread: 1
< 4610.0498> 19:05:10.0286 [eFilePushThreadRecorder] thread could not be stopped!
< 4610.0504> 19:05:10.0292 [eDVBTSTools] setSource loading streaminfo for /media/hdd/movie/Radio/20210205 1827 - BBC Radio 4 - The News Quiz.ts
< 4610.1027> 19:05:10.0815 [eThread] Destroyed thread without joining it, this usually means your thread is now running with a halfway destroyed objectand enigma2 is non-responsive....
EDIT: I suspect its not VPS related. I've had other recordings succeed with VPS in place, and this eFilePushThreadRecorder message reminds me of something else.
A quick check shows that for me.
Creating a manual timer shows no VPS option. Not surprising as the TimerEntry code knows nothing about VPS.
A timer set by an AutoTimer does know about VPS (which is odd, as by then it is just a timer so the point above should obtain, but doesn't).
Setting VPS to on in such an AutoTimer appears to work, but the value is never actually saved so if you look at it later it is unset again.
So, as far as I can tell, this is currently never going to do anything?
A quick check shows that for me.
Setting VPS to on in such an AutoTimer appears to work, but the value is never actually saved so if you look at it later it is unset again.
[/LIST]
So, as far as I can tell, this is currently never going to do anything?
I set up a few autotimers yesterday for the soap to keep the boss happy. They recorded perfectly yesterday and today. I have checked the timers created for the next few days and the "Enable VPS" is set to Yes (as expected)
Running 5.4.005 (release) with no mods. 28e epg downloaded with crossepg.
61422
No idea whether this is anything to do with the VPS plugin but I've just got this:
and enigma2 is non-responsive....
EDIT: I suspect its not VPS related. I've had other recordings succeed with VPS in place, and this eFilePushThreadRecorder message reminds me of something else.
Thats the Eric Slagter (OpenPli) FilepushThread fix that went on in January
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.