(3) Proxy Editing
« BACK Method 4: Proxy EditingNEXT »

"...can you tell what is Real? and what is just Proxy?"

Proxy Editing

The whole purpose of Proxy Editing is to provide a way for your computer to perform difficult editing tasks on dummy/fake footage (known as Proxies) when it would otherwise be too strenuous to perform on the Real footage. This may be useful if you are dealing with massive Lossless Files (possibly HD) that simply don't read fast enough in your timeline (probably bottlenecked by Hard Drive Read Speeds), or if you try the FrameServing method, and find it to be too slow.

So the whole idea is to make two files (with different quality resolutions and/or codecs),  then trick your editor into using whatever file it see's in the file location of your footage. As long as they look the same frame-by-frame, and have the same name and file extension (like .avi), your editor cannot distinguish between the two files. So, just like in the diagram, you can switch between the two as needed.

The Old Switcheroo... (aka 'Bait-and-Switch' with Proxies)

A. To make your "Real" File(s), simply make Lossless Files, or doing FrameServing.
B. To make your "Proxy" File(s), install the Midvid Codec, and use it in VirtualDub's Compression dialogue.
(alternatively you can use the MJPEG option offered by ffdshow (which comes with CCCP)

Now, you could switch files the long way by swapping clips directly in your timeline, or...
    1. Close your editor.
    2. Switch the file location of your footage with the Real/Proxy file. (my moving or renaming files)
    3. Re-open your editor, and hope it uses the swapped file in your timeline instead.
    4. Then just Edit with the Proxy file; Render with the Real file.

Suggestions for Success

a. Make sure your Proxy file has the same framerate as your Real file.
b. Repeat this process as you edit, so you know it is working, ensuring all your frames line up.
    (You really don't want to botch your whole project...)
c. You may need to change your project framesize to match the new file.
d. Play with resolution/quality of your proxy file using Spline36Resize(width, height).
    I've gone as low as 320x180, and it was lightning fast (quality was iffy but good enough for me...)

I find the nicest thing about proxy editing is: you can use the slowest computer ever, and it will still be fast in your timeline; assuming you aren't applying any effects that require processing power.
(until it comes to rendering... but I usually render on a different computer at home anyway... )

  • Experiment with different Resolutions/Codecs.
  • Test the whole process thoroughly before starting a project. (It could save you some pain)
  • If you know a bit of Batch, you can write a script to automate the whole process.

« BACK (DONE: Method 4:
Proxy Editing)

1 comment:

AMVGuide said...

Questions/Comments? Typos/Errors? Tips? Related Links?
Feel free to post a comment below. Your feedback is valuable.

Post a Comment