Premiere Pro, Lag and Lag everywhere, WHY ! Please aid me in optimizing my System.

[Ht Davis]

to be clear about my earlier post…
I work 4 projects a week. The longer ones I usually use a proxy\prores, this gives a slight boost in quality over most originals, but when I actually output, I use a prores rendered from a separate machine.

When I said to keep audio and video previews on the same drive, it doesn’t matter which drive, as long as it is big enough for the whole thing, and connected to a fast enough interface.

Finally, my own spec:
I work mostly on a 2008 Macbook pro with 256mb gfx card and intel core2duo 2.16 with 4gbram. I have a 5400rpm internal 1tb, and another 7200rpm spare drive internal (replaced cd\dvd drive). I use 2 esata raid 3 and 4 drives with 5400’s in them to hold my decompressed files (proxies and prores full) and my disk images for the projects ( i keep all my projects organized on sparse images limited to 50-100gb for archival, it keeps them all organized and I can burn the image at my leisure); I use 3 firewire raid attached to a hub, for backups and for initial renders (preview files). Using these interfaces, I edit 4 projects a week, and output at least 2 with more than 4 hours total footage, and at least 1 other with more than an hour. This is on average for the past 90 days.
I render out my rips for encore (cddvd) on other machines, but render my output from premiere to ProresLT or prores full 422, then pass it out to another computer for render (using one of the firewire drives to transport it between the two or by using compressor to render across a network for smaller project clips).

Use RAID drives to guarantee fuller drive speed, and use your fastest interface (plug). This will enable you to work faster.

Tips:
1. leave the cache internal on a drive that matches your OS for permissions capability (ntfs for windows, HFS+ for mac).
2. Put previews on their own drive but together.
3. Dedicate a Drive for output from premiere (output to a large format then drop down to a compress for best quality)
4. render your effects regularly throughout the work (every few effects), and render the work area when you leave the office (so it will be ready in the morning), then reboot when you come back and the render is done).
5. Find your own method for containing your main project files and smaller image\graphic files for your project, I use disk images because I can archive them quickly, or just RAR split and burn to dvd (I’ve had a near miss on that “Oh sh*T!” moment and it saved my butt). I also use an incremental image backup of my files to an external (only the work files, and any renders, including proxies, I ignore the full formats, as I can remake them on another machine while I work; I do borrow that machine though, it’s not mine).

[Sibel Zivy]

Mr Davis your workflow is Amazing, But my bottleneck is my HDD drive, So hopefully I’ll get mine shipped within the week and I’ll report back to you!

[Ht Davis]

So you believe you’ve Identified your problem… …If you have, WONDERFUL!

I used to do IT for a small office, where there were only 2 computers when I started. As more computers were wired in, I was relied on more an more for support, even to the point of HDD recovery. I was also a consult on Server technology.

Don’t forget, a single drive is great, and cheap. The faster the spin, the faster the drive, typically.
However, when reading, the drive is slower than it’s RPM rating (which is usually a measure of the single random write speed), sometimes a lot slower. With RAID drives, you can nearly double the read speed with two drive enclosures and with more drives, you multiply your reads even more, and you can get closer to the speed of your port (plug\wire\connection to the enclosure). That’s why most servers use the SAS SATA RAID, especially when designed specifically for database or document use\storage.

Storage space\speed, ram, system drives, and output were all a part of my consideration at each change I made to my system. I chose HDD internals because I could get 1tb HDD’s cheap, and I needed the space for other suites I use besides adobe. I do maintain internals with major repair\defrags twice a year. I back up to Time machine, regularly (once a week), and to a differential IMAGE once every two weeks (I do the same with my main work files, excluding the Full Format transcodes to pro res). I can continue work after a day’s recovery, and have another machine do the transcode to full res and uncompressed prores while I finish edits with the proxies and previews recovered. I’ve had one drive fail, and recovered it quickly. It kept me on time for my deadline. Ultimately, such considerations allow me to offer an archival to my clients. I can revisit a project at any time. I charge them at the front end a standard fee, if they want, or double that later. Considering your workflow carefully can help your bottom line, especially when your job market isn’t exactly booming.

[Sibel Zivy]

Mr. Davis please send me an email at qwasiz-ex@hotmail.com.

Thank you so much you’ve very elaborate and helpful, I appreciate the stuff you’ve shared.