Discussion:
[Xmltv-devel] tv_sort and clumpidx usage
h***@gmail.com
2014-12-24 12:28:41 UTC
Permalink
Hi All,

Please can anyone help with a question I have.

My understanding from the DTD is that "clumpidx" relates to 2 (or more) programmes in the same timeslot.

DTD:
+++++++++++
TV listings sometimes have the problem of listing two or more
programmes in the same timeslot, such as 'News; Weather'. We call
this a 'clump' of programmes, and the 'clumpidx' attribute
differentiates between two programmes sharing the same timeslot and
channel. In this case News would have clumpidx="0/2" and Weather
would have clumpidx="1/2".
+++++++++++

I've interpreted that as being, for example:
18:00 - 18:30 News
18:25 - 18:30 Weather

In this scenario News gets clumpidx="0/2" and Weather gets clumpidx="1/2"

However, tv_sort has a different interpretation of "clumpidx". Sub overlap() (lines 405-429) treats all programmes as being overlaps (i.e. ignores the clumpidx) unless they both (or 'all'!) start at the *same time*.

tv_sort is rejecting my clumps as being overlapping because it is not using the clumpidx I have set.

Is tv_sort wrong, or have I misunderstood?

Thanks,
Geoff
Robert Eden
2014-12-24 16:06:15 UTC
Permalink
Post by h***@gmail.com
Hi All,
Please can anyone help with a question I have.
My understanding from the DTD is that "clumpidx" relates to 2 (or more) programmes in the same timeslot.
+++++++++++
TV listings sometimes have the problem of listing two or more
programmes in the same timeslot, such as 'News; Weather'. We call
this a 'clump' of programmes, and the 'clumpidx' attribute
differentiates between two programmes sharing the same timeslot and
channel. In this case News would have clumpidx="0/2" and Weather
would have clumpidx="1/2".
+++++++++++
18:00 - 18:30 News
18:25 - 18:30 Weather
In this scenario News gets clumpidx="0/2" and Weather gets clumpidx="1/2"
However, tv_sort has a different interpretation of "clumpidx". Sub overlap() (lines 405-429) treats all programmes as being overlaps (i.e. ignores the clumpidx) unless they both (or 'all'!) start at the *same time*.
tv_sort is rejecting my clumps as being overlapping because it is not using the clumpidx I have set.
Is tv_sort wrong, or have I misunderstood?
Your interpretation sounds reasonable to me.... tv_sort could be wrong.
What does it want to do (if anything) with clumps? I've never actually
seen a clump :).
h***@gmail.com
2014-12-24 16:50:23 UTC
Permalink
Post by Robert Eden
Your interpretation sounds reasonable to me.... tv_sort could be wrong.
What does it want to do (if anything) with clumps? I've never actually
seen a clump :).
It seems many grabbers silently drop the offending overlapper so they don't have to do anything with it ;)

tv_sort is currently rejecting programmes as being "overlapping" despite them having a clump index (c.f. the 'nightly' report for uk_atlas)

I think it should allow 2 programmes to have overlapping times providing they have clump indexes.

So it would be like: "if 2 or more programmes have overlapping times, then this is ok providing they have valid (consecutive) clumpidx attributes; otherwise report error".

At the moment it's: "if 2 or more programmes have overlapping times AND start at the same time, then ...".
Loading...