home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
XMLTV import gives 2 hours offset
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="milagroso" data-source="post: 182893" data-attributes="member: 51371"><p>Hello furetto,</p><p></p><p>in fact, I tried this option, too. It was my former default, but now the import behaves differently.</p><p></p><p>Thanks for Your suggestion.</p><p></p><p>edit:</p><p></p><p>I think I have found a solution now - however no explanation for the root cause.</p><p></p><p>I tried out the xmltv2 plugin. Among other nice features this plugin contains a checkbox 'delete program table before import'. I checked it, triggered the import and observed im MySQL that the program table was reduced from ~2MB to ~700kB. And I also found correct timestamps finally.</p><p></p><p>Comparing the new table with the previous one (wisely I made a backup...) I found that in the old table there were many, partially contradicting entries. In the example of my original post: I found as well one entry saying 22:00 and another saying 20:00. I assume that only the first of them 'won' and was displayed.</p><p></p><p>So, if anyone has a similar behaviour, he should try to empty (not delete) the table 'program' and then issue a reimport.</p><p></p><p>Have a nice day <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p></blockquote><p></p>
[QUOTE="milagroso, post: 182893, member: 51371"] Hello furetto, in fact, I tried this option, too. It was my former default, but now the import behaves differently. Thanks for Your suggestion. edit: I think I have found a solution now - however no explanation for the root cause. I tried out the xmltv2 plugin. Among other nice features this plugin contains a checkbox 'delete program table before import'. I checked it, triggered the import and observed im MySQL that the program table was reduced from ~2MB to ~700kB. And I also found correct timestamps finally. Comparing the new table with the previous one (wisely I made a backup...) I found that in the old table there were many, partially contradicting entries. In the example of my original post: I found as well one entry saying 22:00 and another saying 20:00. I assume that only the first of them 'won' and was displayed. So, if anyone has a similar behaviour, he should try to empty (not delete) the table 'program' and then issue a reimport. Have a nice day :) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Watch / Listen Media
Television (MyTV frontend and TV-Server)
XMLTV import gives 2 hours offset
Contact us
RSS
Top
Bottom