Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - NiallG

#1
Hi -

I've been noticing a lot of issues with the xmltv listings with invalid start/stop times etc over past week on various channels. I thought it might have just been a screw up with your DST calculations - but the problem has not gone away now that DST has kicked in.

One particular example is next Friday Night on Channel 9 + 9HD..

For example :

<programme start="20100409135000 +0000" stop="20100409155000 +0000" channel="7">
      <title lang="en">Rugby League: NRL Championship Season</title>
...
</programme>

and then

<programme start="20100409140000 +0000" stop="20100409160000 +0000" channel="7">
      <title lang="en">Movie: Striking Distance</title>
...
</programme>


Note that second start time is prior to first entry stop time. Most of the listings for friday night are then all over the place. (ie. shows which are not showing at all). Same thing happens for 9HD ..


Also - you guys keep publishing invalid xmltv data and then publishing different (or fixed) xmltv data a few hours later. This is a real pitb - can you please get it right the first time.


thanks
Niall






#2
Hi -

Your XMLTV Feed has been incorrectly marking 'Underbelly 2' (Nine) as a repeat for it's 8:30pm Monday Night Showing (which is supposed to always be a new episode) - and incorrectly includes the <previously-shown /> element.  (but doesn't include a 'previously shown' date)

My Location : Melbourne
Guide Source : XMLTV feed

I think the other Underbelly listings seem to be incorrect as well - ie.

For next week - there is a repeat screening on Sunday Night (10:30pm) - where no proper episode id has been provided (and one of the entries is not marked as repeat) - and then on Monday night it's marked as a repeat (on both 9 and 9HD).

This same problem existed with feed for last night (where Underbelly was listed as a repeat by inclusion of the <previously-shown/> element).

Can you please fix this.

Thanks
Niall