-
1. Re: Adobe Priemere Elements Quits Unexpectedly all the time (using Intel Core 2 Dou with 2.0 G of RAM)?
Bill Hunt Feb 11, 2010 7:11 AM (in response to TheGuyNamedCrisG)The "purple" tint is most often caused by an obsolete video driver. Have you installed the very latest?
This ARTICLE will also give you tips on setting up your computer for editing, and then even more for an editing session.
Good luck,
Hunt
-
2. Re: Adobe Priemere Elements Quits Unexpectedly all the time (using Intel Core 2 Dou with 2.0 G of RAM)?
Bill Hunt Feb 11, 2010 7:21 AM (in response to Bill Hunt)There are several links in the replies in this THREAD, that lead to other articles on similar playback display issues.
Hope that something helps,
Hunt
-
3. Re: Adobe Priemere Elements Quits Unexpectedly all the time (using Intel Core 2 Dou with 2.0 G of RAM)?
Steve Grisetti Feb 12, 2010 5:03 AM (in response to Bill Hunt)Cris, this is the second thread you've started.
Have you followed up on the responses to your first thread?
-
4. Re: Adobe Priemere Elements Quits Unexpectedly all the time (using Intel Core 2 Dou with 2.0 G of RAM)?
AdelaidePeter Feb 14, 2010 9:47 PM (in response to TheGuyNamedCrisG)Hi,
I was having massive stability problems myself until I followed some advice I received from the support team.
Even pop up processes like Norton's, McAfee's and Screen savers would kill my conformed audio & confuse things.
Now I too only have a 32 bit OS (Vista Premium Home) but have 3GB RAM - the most you can utilise in 32 bit OS - & two internal HD.
The advice was to save aside my raw media, then completely delete PRE 8 using Windows Add & Delete Programs.
Next too I deleted all the directories it was using & also cleaned up various system deitrous using CS3CLEAN SCRIPT (Google for it)
selecting Level 4 to clean the registry too - downloaded from the Adobe resource of course rather than anyone else.
I then did a DFRAG on both C: & D: drives and a general file cleanup making sure that there was 25GB of swap space on C drive.
This took a day and a bit.
I then reinstalled everything and, this time, when I started a New Project I first of all set up scratch disks for every sort of cache it needs on my D: drive.
It seems that this means its temporary files can be read and written efficiently without compteing with the processes competing for swap space.
I still have problems with sustaining conformed audio but I will make a separate post about that in a minute.
The good news is that the continual crashes and snail-paced user interface responsiveness is cured for now!
Hope others out there can benefit from this post. Perhaps a future edition of PRE could notice at installation that you have an internal D drive & use it.


