Offline Proxy editing for High Definition Video
When working with uncompressed YUV video files like we do at HomeDVD, we use a technique called proxy editing. Why do this? Uncompressed HD video files by nature are large and as such present a data handling problem on most computer platforms particularly when editing them. Did I mention slow as molasses in January.
It simply means that rather editing the large uncompressed files on the NLE timeline, use a lower resolution clone. Then an average powered computer platform can work in real-time to preview and help when editing and correcting your work. It is faster and less frustrating to the video editor.
Once the edit is done – this includes the regular raw edits, any compositing, special effects, transitions, titles, synchronizing audio tracks, etc., the chopped up and modified low resolution file is replaced by the higher quality “unedited” equivalent on the time line. All of the edit attributes (stored as meta tags and other functions) of the “edit”, is applied to the uncompressed file, which can then be rendered in its final form with all of the edits, or further tweaked with finer edits.
Of course you can’t escape the final render time for the HD file which can be many hours. A 400ft real of film for example, digitized in either 8bpp or 10bpp HD YUV 4:2:2 AVI form, rendered after edit can take up to 12 hours (Windows 7 64bit, multi-core 3GHZ, 12GB RAM) to complete. Hint, don’t use AVI, use Quicktime with the same 8bit or 10bit YUV 4:2:2 attributes and v210 flavour, goes two to three times faster. Same quality and same file size. Go figure.
The proxy technique will work in Adobe Premiere CS3, CS4 and CS5. I did not check if the other more main stream consumer NLE’s like Sony Vegas Pro, Pinnacle Studio etc., have this feature.
Here’s how its done, assuming the raw hi-res uncompressed file is created and ready for edit:
- create a working folder for the low res cloned video file(s)
- create the low res equivalent cloned file – use Adobe Media Encoder to do this. Import the original hi res file into the Media Encoder and set in low res values for export. It doesn’t matter the final frame size or the codec used, just choose one that allows frame size changes and variable bit rates. Quicktime will work. It would be a good idea to use a smaller resolution like a quarter size and a bit rate that gives reasonable video quality – 6Mb/s to 8Mb/s would do. You would like to see the color correction and compositing changes at least for the bit rate setting chosen.
- Export the low res clone file in the Media Encoder Queue.
- Save the the cloned file into its working folder just created. Use the same filename as the hi res file – just to keep things manageable for large projects
- Now lets edit. Create a new project for the HD project in Premiere – use the actual full frame preset. The smaller frame size of the cloned file will show up as a small window in the preview screens. That’s ok, just expand the video to fit if you wish.
- Import the low res HD file to edit and place in the project window
- Drag the file to the time line and do your “edits”
- When checked and done, we are ready for the magic,
- In the project window right click on the low res file and choose Select Clip > Replace Footage. Browse for the hi res uncompressed equivalent and click Select.
What will happen is that all of the associated edits done on the clone file will be inherited by the new uncompressed file. Now, just render the “edited” hi rez file using Adobe Media Encoder. Use the same compression codec/parameters as the original file to yield the final edited result. At which point the YUV file can be further transcoded to H.264, MPEG2 or AVCHD for Blu ray or DVD authoring respectively.
Thank you so much! I appreciate your work for explaining this problem that I had! Thank you very much once again!!!!
Teber,
Thanks for your comments. I am a full time user of Adobe products and will share what I’ve learned or discovered from others. New stuff coming. Stay in touch.
Bill
Thanks. I often and editing on my laptop with a client and don’t like to say “well, when its `rendered’ it won’t play that choppy” It also helps to go into preferences before you add any clips and set the default output folder (In CS5, it is under General -> Place output files in:) to the specific folder you want these files to be saved to.
Stuart,
A lot of the crap in CS4 is gone with CS5. Editing is so much faster, though render is still the gotcha. CS5 supports NVidia CUDA cards so render should be faster. I’m going to try this out soon.
nice idea, but the question is, what if you have hundred of footages to replace?
My trick is to rename all the proxy extension with original file extension, so if you got lot of footages to replace (like I always do) premiere will automatically recognize them all.
Here’s my workflow for MTS extension from panasonic camera
1. Create new folder for proxy files
2. Reencode all original MTS files using TMPGEnc Xpress,
with MPEG2 Transport as container, frame rate and size
are similiar to original files, but with lower bitrate,
I use 8 Mb/s.
(The reason I use TMPGEnc Xpress is it put all proxy
files at one folder that I choose, while with Adobe
Media Encoder, I have to manually change those folder
for every files)
3. Rename proxy files extension from MPG to MTS and Import
to premiere.
4. Before rendering, select files in project window and
make it offline
5. Rename the folder of proxy files (THIS IS IMPORTANT
STEP!!)
6. Select one files at premiere project window, rigth
click and select replace footage. Now premiere will
automatically replace all of your proxy files with the
original HQ files
It’s work for me, hope work for everyone to.
Hi
Looks like you have a clever way of handling more than a single file in one go. I’ll look into it and try it.
Thanks for the tip.
Bill
I wish they would include a proxy option into the interface like Adobe After Effects does. Would save so much time and it would only be a mouse click (keyboard short cut ; ) away!
Marco,
After Effects does a lot of neat things, but it is not an editing tool. I know some people use it as such, but its so clunky. However, for fast simple edits, coupled with the many super filters it supports it works great in a one go operation.
Bill