I searched around the forum to find what settings you guys might use if you had only two drives to work with and wanted to save the main drive from doing a lot of thrashing round. I got a little confused with the various selections in the scratch disc preferences window. I know you guys are using several drives, but a lot of people only have the main drive in which case everything could be left alone as in the screenshot with Adobe default selections.
I am importing AVI from VHS through Pyro AV Link. Can you walk through the settings in the window screenshot and where would you save what? Which in main drive and which in external drive (1TB 7200 rpm esata). Thanks
I forgot to add that I am using PrE9
With an eSATA external, you have an external that is very close to being the same as a SATA internal.
I use IEEE-1394b (FireWire 800) externals, as I migrate my Projects between computers, so I have everything, Projects, Assets, all Scratch Disks and Exports/Shares on my externals. That works very well, and your eSATA should be about 1.5 - 2x faster than my FW-800's.
Separating the OS, the program and your Windows Virtual Memory (if on Windows) on your internal C:\, and your Projects with EVERYTHING else on the eSATA will be the best that you can get.
Also, when setting up your Projects on that eSATA external, this article might be useful: http://forums.adobe.com/message/4028199#4028199
Little bit confused. Are you suggesting moving PrE9 to the external and storing everything there? Only the operating system and VMem on internal? I'm sure you're not telling me to partition the main drive. I was thinking in terms of which files in the scratch disc screenshot to move the the external, but never thought of installing the program there. I read your link but that's way above my head for now. I know you do capured video on one drive, captured audio on another, etc. But most people don't haved that many drives so I was hoping to keep it simple.
No. Sorry for any confusion. Leave PrE, the OS, all other programs, and the Windows Virtual Memory Page File, on C:\.
Just locate your Projects, the Assets and the PrE Scratch Disks (various folders), onto your eSATA external.
And zero partitons, as they slow things down, and are basically a holdover from when OS's could not access larger HDD's.
I know you do capured video on one drive, captured audio on another, etc. But most people don't haved that many drives so I was hoping to keep it simple.
The multiple HDD (and RAID arrays for some), is the realm of a video workstation, and the majority of PrE users will not be building a special computer, just for video editing.
While I have multiple HDD's, on both the laptop and the workstation, that was basically from when I was doing commercial video editing. Still, they come in handy, but one can manage nicely with your setup. My new laptop will also have 3 physical HDD's, but I am set in my ways, and pay extra for such. Still, to migrate Projects, I will do about what I am recommending to you - Projects, Copies of Assets, and Premiere Scratch Disks on the external.
Thank you. I think I get the picture. When I set up a new project I would direct the project to be saved in my external drive. All 6 of the locations as shown in the screenshot would be set to "Same as Project". I see Adobe saves the "Media Cache" folder to App Data Roaming by default? Change that to "Same as Project"?
Also of interest is Virtual Memory. You had mentioned in several posts that you set the virtual memory "on the edge of the platter?". Being as i have fooled around with various sizes of memory (System Managed, Custom, etc.) I was wondering if the VM changes location on the C Drive every time a persono would change it. This is hypothetical, but my thought is that each time a person would change the memory, it would move further in on the drive as the drive fills. It would have to relocate to a new location especially if the VM was being increased? I didn't think this warranted a new post or maybe someone else has asked this question.
I would also set the Media Cache files to Same As Project, to keep those all together, and to not use the C:\ more often, than necessary.
As for the Windows Page File, if one has a 64-bit OS, and plenty of installed RAM, it gets used less, than when all OS's were 32-bit, and the ~ 3.5GB RAM was all that one could have. I create a statically managed Page File, as soon as the OS has been installed, before any programs have been installed. Back in the 32-bit OS days, I would create that at ~ 2.5x the installed RAM, so ~ 10GB in size. Two reasons for doing the Page File as static, and as my first operation is that HDD location, that you mention, and a dynamically managed Page File requires CPU cycles, and OS work, to expand/contract it. With video editing, I know that I will be using some Page File, so just set it up (~ 1.5x the installed RAM is probably more than enough with a 64-bit OS) to be there for me.
If one is changing the management, the location or the size of the Page File, with a bunch of programs installed, then it will be moved further into the interior of the HDD. With a 64-bit OS and plenty of installed RAM, I doubt that one could ever tell that the performance was down a bit.
Also, there is now another consideration - Win7 & Win8 are both more efficient at managing the Page File, than was XP or Vista. They could probably be set to be dynamically managed, and with a fast CPU, one would never notice. Still, as I have plenty HDD space, and want my Page File to be in the same spot always, I still use static management. If one has Win7, or Win8 in 64-bit w/ an SSD boot drive w/ plenty of space, I'd expect that they would never even notice the OS's accessing the Page File - it would be virtually transparent in its operation.