2014-05-25, 16:37
Turn on OSD debug and look at memory usage. I bet there is a leak somewhere.
(2013-02-13, 14:27)vexation Wrote: If you're really clutching at straws, it's a long shot but you could try the advice at http://experts.windows.com/frms/windows_...spx#521405 - there's an issue with Windows and certain combinations of hardware that causes timing problems, it's happened in XBMC and MCE before now (to be honest it normally happens when resuming from sleep tho)
"Start, type cmd, right click, Run as Administrator.
Type bcdedit /set useplatformclock true and press enter.
Type bcdedit /enum and press enter.
Verify that useplatformclock is on/true.
Restart the computer then test playback behavior."
I think what you're experiencing is a 'bug' that has been around for a few years now but no-ones ever determined whether it's GPU / Windows / XBMC that's at fault.. this subject has popped up in one name or another several times before http://forum.xbmc.org/showthread.php?tid=116224
If nothing else seems to fix it, you can always cheese it by creating a scheduled task to kill and restart XBMC at 0300 every morning or something? (I know I'd love to get to the bottom of why this happens too but as it's been around for so long I haven't got particularly high hopes) - if I remember correctly the debug logs have never shown anything valid but if someone really wants to get the attention of the dev's, you're best enabling debug logging until the problem arises and then submit a bug with the log.
(2014-05-26, 08:34)torcar Wrote: @pjakesson:
Did you have problems with lip sync in addition to fps before switching to OpenELEC?
If so... do you still have lip sync issues or did OpenELEC solve that also?
Thanks
(2013-02-13, 14:27)vexation Wrote: "Start, type cmd, right click, Run as Administrator.
Type bcdedit /set useplatformclock true and press enter.
Type bcdedit /enum and press enter.
Verify that useplatformclock is on/true.
Restart the computer then test playback behavior."
(2014-08-12, 13:51)blossom24 Wrote: Any reason the developers aren't participating in this thread? As well as other threads on the same topic that I have searched?I'm assuming because they have no idea what's causing it and/or don't care. I was told before that there is only 1 Windows dev on the team. Doesn't exactly inspire confidence that this will ever get fixed does it? If people keep posting here and 5 starring it, maybe they will be forced to at least look at it.