Reply to thread

Message

Yes, there is one case that I can think of.

One of the really-useful features that Windows Media Center implements is series recording with avoidance of recording the same episode twice. WMC uses unique programme ids to accomplish this. However, this still works when the user employs the record/watch/delete style of use, i.e. WMC remembers the information pertaining to episodes that have been deleted. This information is retained until the series-record request is deleted (at which point no future recordings are scheduled, and the information relating to deleted episodes is itself deleted).

MP does not currently support this. But the DVB-T/T2 system in the UK (and probably the DVB-S/S2 system in the UK) broadcast EPGs that do have unique programme ids, making it possible for MP to support this feature. I think that this is also true for some other sources of EPG (e.g. "Schedules Direct"), and for other countries in the world. There are no current plans to support this, but it might happen at some time in the future. However...

Support for this feature probably affects the recordings database, which I think is separate from the video database? If so, it does not directly affect the design or processing of the video database, unless you were anticipating using the same database structure for both databases.

-- from CyberSimian in the UK

<blockquote data-quote="CyberSimian" data-source="post: 1286643" data-attributes="member: 141969">Yes, there is one case that I can think of.&nbsp; <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite9" alt=":eek:" title="Eek!&nbsp; &nbsp; :eek:" loading="lazy" data-shortname=":eek:" />One of the really-useful features that Windows Media Center implements is series recording with avoidance of recording the same episode twice. WMC uses unique programme ids to accomplish this. However, this still works when the user employs the record/watch/delete style of use, i.e. WMC remembers the information pertaining to episodes that have been deleted. This information is retained until the series-record request is deleted (at which point no future recordings are scheduled, and the information relating to deleted episodes is itself deleted).MP does not currently support this. But the DVB-T/T2 system in the UK (and probably the DVB-S/S2 system in the UK) broadcast EPGs that do have unique programme ids, making it possible for MP to support this feature. I think that this is also true for some other sources of EPG (e.g. &quot;Schedules Direct&quot;), and for other countries in the world. There are no current plans to support this, but it might happen at some time in the future. However...Support for this feature probably affects the recordings database, which I think is separate from the video database? If so, it does not directly affect the design or processing of the video database, unless you were anticipating using the same database structure for both databases.-- from CyberSimian in the UK</blockquote>

[QUOTE="CyberSimian, post: 1286643, member: 141969"] Yes, there is one case that I can think of. :eek: One of the really-useful features that Windows Media Center implements is series recording with avoidance of recording the same episode twice. WMC uses unique programme ids to accomplish this. However, this still works when the user employs the record/watch/delete style of use, i.e. WMC remembers the information pertaining to episodes that have been deleted. This information is retained until the series-record request is deleted (at which point no future recordings are scheduled, and the information relating to deleted episodes is itself deleted). MP does not currently support this. But the DVB-T/T2 system in the UK (and probably the DVB-S/S2 system in the UK) broadcast EPGs that [b]do[/b] have unique programme ids, making it possible for MP to support this feature. I think that this is also true for some other sources of EPG (e.g. "Schedules Direct"), and for other countries in the world. There are no current plans to support this, but it might happen at some time in the future. However... Support for this feature probably affects the recordings database, which I think is separate from the video database? If so, it does not directly affect the design or processing of the video database, unless you were anticipating using the same database structure for both databases. -- from CyberSimian in the UK [/QUOTE]