Quote:
|
Originally Posted by Sosseres So my problem is with codecs or corrupted files? (since I have a athlon 64 3.2ghz) Ooh well not much to do then since I have a clean system of codecs if one exlcudes cccp and players built in ones...
Ooh well, maybe I ought to learn programming to see if I can create a player that uses ram more instead of hdd as much, for future high quality stuff  (j/k I won't learn programing for something this silly) |
There's no problem with a 64bit processor if you are using a 32bit OS. However if you are using a 64bit OS, I dont think there'll be a problem either cause Athlon 64 has a set of built in 32bit executables. If you are using Windows 64XP, your app(CCCP + media player) will go through an emulation(WOW64) to run the necessary lib. But since the kernel access done by the WOW64 will just switch the command to 32bit not exactly emulate it, it will flow just like you are using a 32bit OS. So it's not in your processor, whether or not you're using other kinds of OS.
It could be that prioritizing. You must've misproperly configured your codecs to which is first to be decoded. Let's say you have XviD, FFDSHOW, and MPC. These three can decode mp4 in their own manner. Usually all media players will prioritize their built-in codecs.
So let's say you prioritize external codecs over the built-in from MPC's. Now the player will have trouble in deciding which decoder should it use, XviD or FFDSHOW. If you did not configure one to be prioritized over the other, then MPC will load both decoders during playback. Hence, conflict in priority, and will end up the player in crashing.
And one note, since you are using CCCP, you must know(or if you dont, read the documentation), that it has an XviD decoder and FFDSHOW as well, you must disable one or configure the pack to use one first before the other.