Reply to thread

Message

<blockquote data-quote="dvdfreak" data-source="post: 201125" data-attributes="member: 21313">Well, the truth is in the middle.&nbsp; DVB-EPG is perfectly possible, the API is there and the code is ready to run (I even added a setting to set either DVB-EPG or XMLTV as preferred source, so you could use both).&nbsp; But since TvScheduler is a separate sub-system it doesn't actually receive DVB-EPG information automatically.&nbsp; So what would be needed it a small modification (or possibly a plugin) to TVE3 to feed this data into TvScheduler.In the mean time you'll have to rely on XMLTV files.Copying the EPG info from the TVE3 database is not such a great idea if you look at the long-term.&nbsp; You'd have all EPG data twice on your machine in two different databases, which seems a bit silly <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="dvdfreak, post: 201125, member: 21313"] Well, the truth is in the middle. DVB-EPG is perfectly possible, the API is there and the code is ready to run (I even added a setting to set either DVB-EPG or XMLTV as preferred source, so you could use both). But since TvScheduler is a separate sub-system it doesn't actually receive DVB-EPG information automatically. So what would be needed it a small modification (or possibly a plugin) to TVE3 to feed this data into TvScheduler. In the mean time you'll have to rely on XMLTV files. Copying the EPG info from the TVE3 database is not such a great idea if you look at the long-term. You'd have all EPG data twice on your machine in two different databases, which seems a bit silly :) [/QUOTE]

Verification