Ram and media players

Hmm, I'm having trouble with my two hdd's, the larger one is the one I have to use for torrents and so on. Since that is the case I'm wondering if there is any media player that dumps 100-900mb chunks or thereabout of the video file into the ram for me?

That way I could reduce the number of hdd reads and get away without the slight stutter I sometimes get when the next part of the file is loading up and gets shuffled into the queue...

Ooh well it isn't that big a hassle, just curious if there is any media player where I could set a setting for it or one that does it by default. If it had a decent play list function that would be nice as well, but not needed.

As far as I know, no media player will do that. The stutter isn't due to harddisk reading, but slow cpu decoding compressed video formats. It should only happen when your cpu is below 1ghz. It can also happen when there is codec conflicts, and several different ones runs at the same time to decode the same pieces of information.

[vincent_10_27]

MPlayer is very same as MPC. It does not use much memory and much space plus it's about as big as 10mb or smaller, without the extra codecs. If you're planning to add more codecs it'll be like 40+mb. but still, Mplayer wont have the problem in codec prioritizing because it's also like VLC that has built in codecs.

If you do not know how to run a command line. I suggest you get the front-end for it. Some front ends offer a playlist thing. Dont get the gui's cause it's kinda hassle for Windows, gui for MPlayer will only be good for Linux. The difference between MPlayer and VLC is MPlayer offers all codecs available in the market while VLC offers only a few.

Originally Posted by dagger906

As far as I know, no media player will do that.

there are lots of Media Players that sucks up ram to get the decoding of own built-in codecs faster. You may not have encoutered it yet.

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)

If you don't turn off page file, then it will still run off the harddisk anyway. And since the page file runs off primary C drive instead of your storage drive, the extra load will just make things worse.

[vincent_10_27]

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.

Anyhow, I got my problem fixed. I went into services and msconfig and removed some stuff there, defragmented my hdd's and put in a fan to cool down my very hot hdd's...

Dunno which of the steps that did it, but it works as it ought to now anyhow, so was unrelated to codecs as I see it...