You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I changed to the recently updated sky.com script a couple of days ago (using a completely new install as in the readme) and have found an anomaly. This does not occur with an identical grab using my previous installation. The grabs are for about 60 UK FTA channels which I can list if it would be helpful.
A number of programmes have two identical blocks in the XML, including their start and finish times. This occurs only from around approximately 22:00 each day and up to about midnight GMT. During this period most channels are affected and it is consistent between successive grabs. In case of a timing issue I tested delays of 100, 1000, 3000 and 5000 msec but the XML was unchanged.
The text was updated successfully, but these errors were encountered:
Here is some additional information. I cannot see why this issue would be due to duplicate UK and IE channels.
This issue as described previously is consistent only at around 22:00 each day but does not occur with a 1 day grab nor on the final day of a multi-day grab. A 5 day XML is attached as an example. iptv-org-epg-sky-5.zip
And a 1 day XML also commencing today (20241219) iptv-org-epg-sky-1.zip
The duplicates around 22:00 today (19th) are present in the 5 day grab but not the 1 day grab.
Site
sky.com
Description
I changed to the recently updated sky.com script a couple of days ago (using a completely new install as in the readme) and have found an anomaly. This does not occur with an identical grab using my previous installation. The grabs are for about 60 UK FTA channels which I can list if it would be helpful.
A number of programmes have two identical blocks in the XML, including their start and finish times. This occurs only from around approximately 22:00 each day and up to about midnight GMT. During this period most channels are affected and it is consistent between successive grabs. In case of a timing issue I tested delays of 100, 1000, 3000 and 5000 msec but the XML was unchanged.
The text was updated successfully, but these errors were encountered: