MP-TV Series not automatically updating my shows (1 Viewer)

[seco]

Yes, you have the same problem and error than I have.

I think the problem is that with some motherboards the specific wake up event is not dispatched in automatic (or manual, not sure) wake up. TVSeries listens to this event and since it's never dispatched the importer is not initialized after wake up -> error.

I don't know if there is any easy solution to this, I've learned to live with it...

 

[Mark Stephenson]

I'm having this same problem as well. My machine wakes from sleep but never finds any new episodes until I restart MP.

I can understand why the importer might not be re-initialized properly on wake up, but I'm struggling to see why running the importer manually from within MP does nothing (no bar, nothing).

Would it not be simple enough for the manual import to re-initialise/re-start the importer when run? It would seem the ability to run a manual import would be for exactly this situation - where it fails to run automatically. Why else would you need it really?

 

[ltfearme]

I can understand why the importer might not be re-initialized properly on wake up, but I'm struggling to see why running the importer manually from within MP does nothing (no bar, nothing).

because it uses the same timer object when doing a manual import (it just schedules the import immediately). Since the timer has been disposed it craps itself.

Would it not be simple enough for the manual import to re-initialise/re-start the importer when run? It would seem the ability to run a manual import would be for exactly this situation - where it fails to run automatically. Why else would you need it really?

That will be the only solution currently for motherboards that experience this issue...I wonder how many there are. Have you tried updating your BIOS and chipset drivers?

 

[ltfearme]

Hey Guys,

Can you please test the following dll to see if a manual import works after 'Resume From Standby'. I added a check to see if the timer is disposed and re-initialize if we need too.

Note: this does not support automatic updates after resume, for that you will need to get a supported system. I think this is a good workaround for now though.

 

[Mark Stephenson]

Thanks very much for the dll. I shall try a manual import next time the automatic one fails and let you know if it works. Unfortunately my system is a fairly aging laptop which hasn't seen much in the way of bios or driver updates for quite some time. I'll be more than happy if the manual import works.

 

[Mark Stephenson]

Of course it's the time of year when all the TV series stop for a break so I've not really been able to test whether it is working properly or not, but I can say that whenever I try the manual import I do now see the white bar at the top of the screen, even if it doesn't pick up any episodes (as there are no new ones to pick up).

 

[Mark Stephenson]

Happy to report that the manual import option is now working perfectly for me with the new .dll. Any time MP doesn't pick up new episodes automatically (which is most of the time), when I run the manual import they all get picked up fine.

Thanks very much for the fix - much appreciated.

 

[Chubler]

Hey ltfearme

I recently updated to Scythe42's 1.4.0 fixes and this issue now occurs whenever I power down my amp (no standby involved here).

I suspect that the new changes scythe42 is working on are very similar to the recovery for standby. He has offered to look into this issue if you could supply more info on what MP may be doing to cause the "disposed timer" issue you mentioned as the root cause.

Post #364 in this thread https://forum.team-mediaportal.com/threads/scythe42s-fixes-for-1-4-0.118345

 

[ltfearme]

Are you sure Scythe42 changes are what is causing your issue?

The root cause was more hardware related iirc ie. we did not receive a resume event from windows so we dont initialize the timer (after we disposed of it on standby). Just speaking off the top of my head as I dont have the code in front of me now.

 

[Chubler]

Of course it could be hardware and Scythe42's fixes are hilighting it. I never use standby mode so I wouldn't have been aware if is ahve the same issue as other posters here. Things have been updating fine until I started using the new 1.4.0 fixes testing version.

Could you check the logs for me in post #363 to see if the issue is the same as those here?