- Defragmented the HD
- Checked SMART and other self tests on the hard drive. The drive is in perfect shape.
Those terms sound suspiciously like singular, instead of plural. You need at least three different 7200 RPM SATA disks or faster for a practical editing station.
Those transfer rates you mention seem quite OK for a single 5400 disk on a lousy CPU with very limited memory, especially if the system is not tuned, contains a lot of supplier installed crap, runs any anti-something software. Unfortunately you left out all the details to say whether you are lucky with that kind of transfer times or not.
I appreciate the reply Harm but unfortunately it's not helping me much. As I mentioned, I'm still in school and I can not really afford a dedicated editing station, especially when I'm not headed in this direction of media development Of course you made a fair point and I apologize for forgetting the basics of a post like this.
I'm running a Windows7 64- i7 2500K overclocked to 4.5GHz with 8GB of DDR3. My main disk is a Vertex2 SSD and my storage HD (Media Cache, applications) is a Samsung 2TB 7.2K RPM SATA2 disk Perhaps you are mixing up Mb and MB because 7MB is not OK at all for a hard drive like this. It should be getting atleast 100MB in read (140MB average as confirmed on other tests.)
My other projects are working fine, so the hardware is excluded from the source of the problem.
I would like to add that I have just updated my CS5.5 to its latest versions, renamed my source files folder and the problem persists. Extremely slow reading speeds of footage after I have re-located the file in the popup window that came up after it couldn't find the clip in the original location. I believe this is what causing AE to crash: it can't read the linked sequence fast enough and AE times out.
I apologize for my bad writing skills, English is not my main tongue
Message was edited by: Pieterjan - KL I forgot to mention that both times this happened, this was after I nearly finished my project and I was rendering the project in Media Encoder. I don't risk to experiment anymore but I believe this happened when I canceled a render in ME. Perhaps I have found a bug? In the meanwhile, it has suddenly decided to work again. So I'm finishing and rendering the project so I will not have to touch it ever again.
Sorry, that disk is an 'Eco green' model and not suitable for editing. If you have any form of power saving, hibernation, indexing, compression, anti-something, screen saving and similar stuff running, this is to be expected. If you have your pagefile on the Vertex2 and it is dynamically managed, your problems will only increase.
My investigation has proven otherwise. I agree there are better hard drives (performance wise) but this one will suffice for what I'm doing.