Adobe Premiere Pro Error

Pas · Post by **Pas** » Wed Oct 03, 2007 5:06 am

Whenever I try to save my file, this error message keeps coming up:

Adobe Premiere Pro has encountered an error.

[\dev\stingray\Beckend\Src\FileCache\CileCache.cpp-879]

Then it will close without saving anything.

What the heck does that mean??

Bauzi · Post by **Bauzi** » Wed Oct 03, 2007 6:15 am

Uhm I know that Premiere Pro has problems when you try to export in something that it can´t handle. Such as XviD.

I guess you tried to export uncompressed, Lagarith or HuffYUV? Do you try to overwrite a damaged file? Does it throw the message at you just right after you hit the button or does it work a bit?

If you already tried to export in proper looseless I think that the DebugMode Frameserver can help you. However let´s try to fix it without first.

What the heck does that mean??

Maybe you´re out of RAM? Tell us how much MB and % you have free when you try to export. Tell me your free diskspace in % please...

I try to save my file

Project file? I guess you´re out of RAM or something... You work with Pro CS3 right?

Pas · Post by **Pas** » Wed Oct 03, 2007 7:42 am

It happens after I render the file then hit ctrl+s to save, then that line comes up.

My total amount of HD space is 320gb, though that gets rounded down to 300gb.

Free space 32.4gb, which should be enough to do at least that.

I think I'm running CS2.

Bauzi · Post by **Bauzi** » Wed Oct 03, 2007 8:15 am

Pas1990 wrote: I think I'm running CS2.

You better find out

It happens after I render the file then hit ctrl+s to save, then that line comes up.

Yeah I think it´s a memory problem after render process. How many minutes do you render?

--> Save before you render. Sounds dumb, but I don´t think that you can avoid the error .-. Maybe someone else has an idea.

BasharOfTheAges · Post by **BasharOfTheAges** » Wed Oct 03, 2007 8:16 am

Pas1990 wrote:It happens after I render the file then hit ctrl+s to save, then that line comes up.

Either the project file is corrupted (what compression types are your files?) or you're getting a program error from something else. You still haven't answered the question on RAM though, so I can't be sure at all.

My total amount of HD space is 320gb, though that gets rounded down to 300gb.

That's a combination of partition table loss and the fact that HDD manufacturers are allowed to lie on their packaging as to the total size of a disc - they advertise in a metric system between byte tpes (1000 = next level) instead of a binary one (1024 = next level) and the diference becomes more pronounced the bigger your drive is. Your total free space is all that matters when anyone asks you how much drive space you have left though.

Pas · Post by **Pas** » Wed Oct 03, 2007 8:27 am

BasharOfTheAges wrote:
My total amount of HD space is 320gb, though that gets rounded down to 300gb.
That's a combination of partition table loss and the fact that HDD manufacturers are allowed to lie on their packaging as to the total size of a disc - they advertise in a metric system between byte tpes (1000 = next level) instead of a binary one (1024 = next level) and the diference becomes more pronounced the bigger your drive is. Your total free space is all that matters when anyone asks you how much drive space you have left though.

Yeah, my friend once explained that to me.

Anyway, problem has seemingly dissapeared O.o

I can render fine now, but I wonder what the heck happened... It was failing for like an hour then suddenly it reverts.

Gepetto · Post by **Gepetto** » Wed Oct 03, 2007 8:50 am

Pas1990 wrote:I can render fine now, but I wonder what the heck happened... It was failing for like an hour then suddenly it reverts.

Welcome to Windows.

Bauzi · Post by **Bauzi** » Wed Oct 03, 2007 9:12 am

Gepetto wrote:
Pas1990 wrote:I can render fine now, but I wonder what the heck happened... It was failing for like an hour then suddenly it reverts.
Welcome to Windows.

and to Premiere Pro

Editing is about fixing problems too...

Mr Pilkington · Post by **Mr Pilkington** » Wed Oct 03, 2007 10:27 am

This is why I dumped Premiere.

That and Pro's random corruption of save files. Those same files that IRONICALLY open up in CS3 and all versions of AfterEffects with no errors.

Pas · Post by **Pas** » Thu Oct 04, 2007 6:48 am

Ohh goodie, moar errors.

This time I got a screenie of the little bastard.

That's what it gives me when I hit enter to render.

Now, the reason I know this is f_cked up is because I have already rendered some scenes from the footage.

In fact, it happened around an hour before too, but somehow magically dissapeared. This time, its not.

I've tried closing premiere, shutting my computer etc to no avail. Why the hell won't it let me render scenes from footage I have rendered just hours before?