Forums

That is near correct, I found the files produced on the D: drive folder to be nearly the size of the imported asset, BUT this can only be confirmed if the asset is AVCHD. For my original AVCHD asset of just under 2Gb taken off my camera, after import one of the files (the .PEK or .CFA) was 1.47Gb, I think this is the so-called waveform file and I think one of the previous people explained that these are BOTH audio files. Now I ask again, for such a huge file should I not want it produced on the RAID0 drive?

Message du 22/04/09 02:28

De : "Bill Gehrke"

A : "JONES Peter"

Copie à :

Objet : Premiere Pro CS4 Premiere Pro CS4 eats my C: drive in Vista Ultimate 64-bit SP1 NxrpH-1HP9-80AA

 

Let me see if my understanding of this is correct.

 

If I capture with default settings in CS4 to my project disk in Vista 64 SP1 and import this to a project, I should see a correspond size increase my C: drive. Is this a correct statement of your sitution?

>

TRUE I am new to Premiere Pro and knew not about scratch files but now I have an idea.

FALSE I do know the video files are huge, that is my files, I never knew what files CS4 would then create during import, but I am learning by experience, apparently it does not change your original media files when you specify edits that therefore it produces some sort of copy and applies edits there, if this understanding is correct I am left with the next question that surely these copy files to which edits are applied should be placed also on the RAID0 drive or else everything will slow down later when CS4 presumeably switches to working off the modified copy????? Any answers please?

HOW SHOULD CS4 KNOW WHEN TO CLEAN-UP ITS PROJECT RELATED FILES? When you delete the project seems quite a logical answer to me. Even more important if it uses the one folder to intermix work files for several projects whereupon manual clean-up could become a scary exercise. With a database, it should be able to track which files it created of its own accord for which projects. Anyways, this is theoretical, we have to work with what we have.

HE will do just fine. 8-)

Message du 22/04/09 05:01

De : "Phil Griffith"

A : "JONES Peter"

Copie à :

Objet : Premiere Pro CS4 Premiere Pro CS4 eats my C: drive in Vista Ultimate 64-bit SP1 NxrpH-1HP9-80Ei

 

I have vista ultimate 64 bit with sp1. I don't have any shadow copy going on. If you mean the backup utility that's included with ultimate, then you have to set it up to run first of all. and then you tell it where to store the backup files. Doesn't make sense to put backup files on the same drive you are backing up. What happens when that drive fails? Your backup is on it too???

I think this all boils down to the original person not knowing how to set up scratch disk. He specifically states after he/she change it to d drive, it started getting "eaten up" This person in my opinion, doesn't realize that video files are quite large. second he/she thinks that premiere should delete them on its on. When should premiere delete them??? during the middle of your editing project. at the beginning? at the end? How does it know when you are finished??? No, the person has to delete them manually or else nothing gets accomplashed. Bill, your test run showed that 1 gig ~ of drive was used on c drive. Hardly, the 30 gigs or so that was stated by op. I don't have premiere cs4. I did download the trial, and actually used it to edit one 2 hr project. My c drive did not get eaten up and when I was thru I deleated files. As been stated before, ame does use the c drive to put temp files while writing to finished product. These are hardly hidden in my opinion, And I deleted them when I was thru. No worrys.

>

I am confident that it is the .PEK and .CFA files that do not get deleted when the project gets deleted and I will soon be able to prove it. Once I know whether these files are better off going onto the RAID0 drive then I intend restoring my computer to the point just after installation of PrPro so I can rebuild projects correctly with no bad hangovers from these experiments, just before such a restore I can delete the projects and see whether PrPro cleans up the .CFA and .PEK files and report the result.

Message du 22/04/09 16:39

De : "the_wine_snob"

A : "JONES Peter"

Copie à :

Objet : Premiere Pro CS4 Premiere Pro CS4 eats my C: drive in Vista Ultimate 64-bit SP1 Mk27j-1HP9-80TT

 

As to PrPro doing the cleanup, when a Project is deleted, I'll bet that it does - for its own files. However, it seems that what you are seeing might be files created by Vista. These would not be reported to, or known by, PrPro. This would be especially ture if these files were marked as "System," or "Hidden," which seems to be the case. I'd not want PrPro deleting any System file, even if it knew about them, and thought it safe to do so. That should be done manually, by the user. I've had programs that would delete files, and they "got it wrong" too many times.

 

Your post has made for some interesting discussion, and I've picked up some tips on the workings of Vista. Thanks for posting it in the first place.

 

Hunt

>

Lets us approach it the other way around, what is it going to use the really big 1.47Gb file (that it created when it imported the near 2Gb original AVCHD asset) for?

Message du 22/04/09 16:50

De : "Jim Simon"

A : "JONES Peter"

Copie à :

Objet : Premiere Pro CS4 Premiere Pro CS4 eats my C: drive in Vista Ultimate 64-bit SP1 Mk27j-1HP9-80Uj

 

I am learning by experience, apparently it does not change your original media files when you specify edits that therefore it produces some sort of copy and applies edits there

 

That is not actually what the created files are for. Premiere does use the original media for playback and export.

>

So you figure that the .CFA and .PEK files should be directed to the disk that is best suited for the video, in my case namely the RAID0 drive??? Yes?

Message du 22/04/09 20:00

De : "Kostas Arvanitidis"

A : "JONES Peter"

Copie à :

Objet : Premiere Pro CS4 Premiere Pro CS4 eats my C: drive in Vista Ultimate 64-bit SP1 Mk27j-1HP9-815h

 

Hi all these are snapshots of my Commons Folder. As you can see there are TWO Media Cache Folders. One with the database files and one with the .CFA and .PEK files. The second folder is a all-file-'******' duplicate from all projects i have on my Video Drive. Normally these files should be deleted automatically when i close the project (in my opinion they never should be created since they alredy exist on my project /MediaCache subfolder)

>

Disk eating happens by default after installation and when importing large AVCHD assets, I do not say here that it never happens under other conditions nor that it happens in all installations. The cause is that .PEK and .CFA files are being created on the C: drive as these assets are imported and they have an approximately similar size to the imported asset, BUT the creation is flawed in that the files are not visible to the user nor does CS4 clean them up itself. Whether the invisibility of the files created  is CS4's or Vista's fault we need not discuss, because there is a workaround. Go to Edit->Preferences->General and expressly reset CS4 workfiles therein to folders you create, then the files become visible as they are created. For full details follow the thread. Thanks for all those who contributed.

Well thanks for the suggestion, but no the problem was allocation of .PEK and .CFA files to the C: drive by default and that at least in my environment those were invisible and could not be reclaimed. I since restored from a backup to the point just after installation of PrPro, then went into Edit->Preferences->General->Media and set the two files therein to be on the RAID0 drive along with the imported AVCHD assets, now when I imported the assets C: drive remains normal and the .CFA and .PEK files appear in the same folder as the imported assets. And I think that each of the subsystems of PrPro have their own Media file settings to be set also, but those are not proving to be big consumers of space. Anyway having now completed a large part of project setup I am moving forward with other lessons from the Adobe 'classroom in a book'.

Message du 28/04/09 02:14

De : "tmsatterfeld"

A : "JONES Peter"

Copie à :

Objet : Premiere Pro CS4 Premiere Pro CS4 eats my C: drive in Vista Ultimate 64-bit SP1 PftUQ-1HP9-84cY

 

Greetings, it sounds to me like your space s being taken up by an ever increasing number of restore points being created. In Vista, unlike XP there is no simply GUI with which to adjust your max allowable space to be used to create restore points. Instead you must launch a command line and set a limit through the VSSAdmin as is is the Volume Shadow Copy which takes the snapshots, you can only find out as well has limit the amount of space allowed for these snapshots through the command line to the VSSAdmn. If your system is set to "Unbounded" there is no limit and it can eat your entire drive away until you get a drive low warning. Since you cannot "See" restore" points or there size, this may be your problem. TMS

>