-
Premiere Pro 1.5.1 HDV – render problems & crashes
Hi,
I’m working on my first larger HDV Production (aprox. 60 min., aprox. 20 hours HDV footage and 2 hours dv footage) with PPro 1.5.1 (all updates and windows sp2 fixes). The performance is really good, but a lot of things need to be rendered without additional hardware support. Unfortunately PPro crashes more and more while rendering and working.
A few infos about my system:
Dual Xeon 3,2 GHz
2 GB RAM
Internal HD: 160 GB IDE 7200
External HD: 4 x 250 GB SATA 7200 (RAID0)
RAID Conroller: HighPoint RocketRaid 1640Problem:
PPro often gives a Error message while or while staring the rendering process:
“Error occured while creating clip” -> ok (free translation from german)
or
“premiere has discovered an error and has to be stopped. It is tryed to save the project.” -> ok (also translated).The 2nd error also happens while working in the timeline. This is very frustrating, because PPro doesn’t manage to save the project every time it crashes.
Can anybody figure out a reason for the crashes? Could it have something to do with my scratch disk setup or the raid controller?
Normann
-
8 Replies
-
Hi Normann,
ich habe auch so einn
-
Thanks for your answer Claus-Peter (Ich werd’ hier mal auf englisch schreiben, wegen der kompatibilit
-
Hi again,
i
-
Sure, could be SATA, but I won’t bet. My suspicion is, that it is a PPro thing… however – I would be glad if you could give me some feedback after your test (noermli(at)web.de, >next week< is a long time for a threat). Regards from Berlin.
-
Try this (from Adobe)
Try this;
Solution 2: Change the affinity setting for the Adobe Premiere Elements.exe or Adobe Premiere Pro.exe process to use only one CPU.
To change the affinity setting:
1. Start Premiere Elements or Premiere Pro.
2. Press Ctrl + Alt + Delete and then click Task Manager.
3. Click the Processes tab.
4. Right-click the process Adobe Premiere Elements.exe (or Adobe Premiere Pro.exe), and then choose Set Affinity.
5. Deselect all CPUs except the first CPU listed (CPU 0), and then click OK.
6. Quit the Task Manager.
-
Hi mike, thanks.
Actually PPro only uses max. 55% of both CPU-power. So it wouldn’t slow it down a lot. What about hyperthreating? Does this should be disabled, because it simulates more CPUs?
I also noticed, that everytime a render-problem occures, the PPro memory usage in the task manager is somewhere around 1GB (975.000 – 1.020.000 KB). Could this mean something?
normann
-
The 1.51 update was supposed to take care of the memory issue…it does for most. Disabling HT works for most of the rest.
-
Well, actually HT is disabled. I did this a few weeks ago. But it did not change any thing.
It looks like I have to finish my project with these crashes and errors. But I am not quite sure how to export my work for PAL (PPro always returns an error after 1 – 2 min. of the movie). Unfortunatelly I need to insert serveral PAL clips and they come out better, when the aren’t blown up and down again. Further the downconverted titles look very “stairy” so I have to do them in PAL aswell… Very frustrating.
Reply to this Discussion! Login or Sign Up