Posts: 1,736
Joined: Oct 2008
Reputation:
14
Yeah its weird. All 264 mkvs play fine. If I play the the same iso from a local drive it plays fine. This is on a wireless N network but it should be fine since all other file types play fine but isos. Which is why I was guessing earlier that it was some sort of buffer issue. It cant be bandwidth since I can drop to the older one and its fine.
Posts: 11,582
Joined: Feb 2008
Reputation:
84
davilla
Retired-Team-XBMC Developer
Posts: 11,582
Also can you pastebin another xbmc.log, this time let it play longer and don't do any chapter jumps or seeks.
Posts: 11,582
Joined: Feb 2008
Reputation:
84
davilla
Retired-Team-XBMC Developer
Posts: 11,582
ahh, I thought you were already compiling your own versions. Sorry, I know nothing about windows build, only osx and linux.
Posts: 69
Joined: May 2009
Reputation:
1
Hi, i haven't read the all the posts so i hope this isn't a repeat. I had a similar problem with xbmc, which I have fixed by running on one processor only. My system : amd x2 2.05 ghz, 2gb ram , win xp. I only had problems playing from the hard drive. build from sometime in may
Posts: 2,752
Joined: Dec 2008
Reputation:
23
bobo1on1
cheapass Team-XBMC Developer
Posts: 2,752
Try disabling any sort of cpu frequency scaling your system has.
Posts: 1,736
Joined: Oct 2008
Reputation:
14
2009-06-13, 18:20
(This post was last modified: 2009-06-13, 19:25 by SlaveUnit.)
I disabled upscaling, deinterlacing, and sync playback to display. Are those the features you are speaking of? If so am I missing any?
Other than those Im not sure what you are referring to. The system is a very basic build of XP. Its a dedicated HTPC so there are very few software pieces installed. Its an Intel e6750 cpu that isnt overclocked.
Also with everything disabled the CPU never goes above 8%. With the upscaling running etc it hits about 25%.
Posts: 2,752
Joined: Dec 2008
Reputation:
23
bobo1on1
cheapass Team-XBMC Developer
Posts: 2,752
I'm talking about the feature that lets your cpu run at a lower frequency to lower the power usage, it can cause QueryPerformanceCounter to do strange things.