Wrong epg source

[WKleeven]

I disabled booting, enabled mc2xml task again (but didn't run because of no booting), set updatetime to "none". Still no problems. Thankfully.
However, I don't know what went wrong. Maybe a difference between 2.5.9 and 2.6.2? I don't know.
I'm thinking of putting back an old image so I can find out the root of the problem, but what would be the point if the problem's gone?

Could it be that mc2xml "claims" the epg-data, so that no new dvb-c data can be imported?
I'm going to enable booting, see if that makes a difference.

[Zeb]

Could it be that mc2xml "claims" the epg-data, so that no new dvb-c data can be imported? I'm going to enable booting, see if that makes a difference.

Perhaps something like that, or perhaps XMLTV data extends further in time than DVB data. Keep in mind that the usual way of getting automatic updates with mc2xml (which I also use) is with an UpdateEPG.bat file along lines described in the Wiki. You are circumventing regular EPG updates by using a Windows task to run mc2xml. You can use either DVB or XMLTV for all channels, or you can use one for some channels and one for other channels; but using both for all channels is something that I wouldn't care to try myself.

[sub]

It still just sounds like the problem was that you had the update set to 'none', which effectively disables the overnight EPG update, and eventually you'll run out of EPG data. As Zeb said, it may be soon or later for xmltv vs dvb sourced epg data.