Tvheadend

K Shea wrote:

Under the Digital Video Recorders Profiles tab there is a setting in the Parameters section called "EPG Update Window" which lets you pick any of a number of times from a dropdown, however when you click on Help for that screen, nothing at all is mentioned about this setting, and I for one am mystified as to its purpose in this context. Please update the help file to include an explanation of this setting.

I believe it checks the EPG data to see whether the time has changed for the recordings, so say for example the broadcaster is running late and adds 5 minutes to the start time of upcoming programmes, if this occurs within the time frame window the start times will be updated.

It's quite clever and really needed (here in the UK at least).

Hopefully I've got this right, if not I'm sure someone who does know will correct me!

Mark Clarkstone wrote:

I believe it checks the EPG data to see whether the time has changed for the recordings, so say for example the broadcaster is running late and adds 5 minutes to the start time of upcoming programmes, if this occurs within the time frame window the start times will be updated.

It's quite clever and really needed (here in the UK at least).

Hopefully I've got this right, if not I'm sure someone who does know will correct me!

I don't know if you are right or wrong but your explanation doesn't completely make sense to me because those profiles can be used for all kinds of recordings, including strictly time-based recordings added in the Digital Video Recorders | Time Schedules tab. I would logically think that if that's what that setting if for, you would want it applied on a per-tuner or per-channel basis, not in the recording profile. I don't know anything about the internal design of TVHeadEnd so maybe there is some good reason for placing a setting like that in these profiles, and just ignoring the setting in cases where it's not applicable, but to me that just doesn't seem like the logical place to put the "EPG Update Window" setting if it operates as you've described.

I'm in North America using TVHeadEnd to receive channels that do not include EPG data, so there would be no way to detect real-time changes like that here (I wish there were!). So I wonder what the proper setting would be to disable real time EPG update attempts?

K Shea wrote:

Mark Clarkstone wrote:

I believe it checks the EPG data to see whether the time has changed for the recordings, so say for example the broadcaster is running late and adds 5 minutes to the start time of upcoming programmes, if this occurs within the time frame window the start times will be updated.

It's quite clever and really needed (here in the UK at least).

Hopefully I've got this right, if not I'm sure someone who does know will correct me!

I don't know if you are right or wrong but your explanation doesn't completely make sense to me because those profiles can be used for all kinds of recordings, including strictly time-based recordings added in the Digital Video Recorders | Time Schedules tab. I would logically think that if that's what that setting if for, you would want it applied on a per-tuner or per-channel basis, not in the recording profile. I don't know anything about the internal design of TVHeadEnd so maybe there is some good reason for placing a setting like that in these profiles, and just ignoring the setting in cases where it's not applicable, but to me that just doesn't seem like the logical place to put the "EPG Update Window" setting if it operates as you've described.

I'm in North America using TVHeadEnd to receive channels that do not include EPG data, so there would be no way to detect real-time changes like that here (I wish there were!). So I wonder what the proper setting would be to disable real time EPG update attempts?

I believe the data is supplied within the SI table of a DVB Stream, according to this document: http://www.etsi.org/deliver/etsi_en/300400_300499/300468/01.11.01_60/en_300468v011101p.pdf

5.2.7 Running Status Table (RST)
The RST (see table 10) allows accurate and rapid updating of the timing status of one or more events. This may be
necessary when an event starts early or late due to scheduling changes. The use of a separate table enables fast updating
mechanism to be achieved.
The RST shall be segmented into running_status_sections using the syntax of table 10. Any sections forming part of an
RST shall be transmitted in TS packets with a PID value of 0x0013, and the table_id shall take the value 0x71. 

Again I could be totally wrong here but this is the only thing I can think of that would make sense for this option, it could even be something totally different.