Proxy
Proxy Settings
Sklic
- Podokno
- Storage
Defines whether the proxies are for individual strips or the entire sequence.
- Per Strip
Proxies are stored in the directory of the input.
- Project
All proxies are stored in one directory.
- Proxy Directory
The location to store the proxies for the project.
- Set Selected Strip Proxies
Set proxy size and overwrite flag for all selected strips.
- Rebuild Proxy and Timecode Indices
Generates Proxies and Timecodes for all selected strips, same as doing .
Strip Proxy & Timecode
Sklic
- Podokno
Once you have chosen the Proxy/Timecode options, you need to select all strips for which you want proxies to be built. Then use , or button in Proxy Settings panel. Once all proxies are built, they will be ready to use.
In order to use proxies, you have to select matching Proxy Render Size in the Sequencer preview Sidebar panel.
- Custom Proxy
- Directory
By default, all generated proxy images are storing to the
<path of original footage>/BL_proxy/<clip name>folder, but this location can be set by hand using this option.- File
Allows you to use pre-existing proxies.
- Resolutions
Buttons to control how big the proxies are. The available options are 25%, 50%, 75%, 100 percent of original strip size.
- Overwrite
Saves over any existing proxies in the proxy storage directory.
- Quality
Defines the quality of the images used for proxies.
- Timecode Index
When you are working with footage directly copied from a camera without pre-processing it, there might be bunch of artifacts, mostly due to seeking a given frame in sequence. This happens because such footage usually does not have correct frame rate values in their headers. This issue can still arise when the source clip has the same frame rate as the scene settings. In order for Blender to correctly calculate frames and frame rate there are two possible solutions:
Preprocess your video with e.g. MEncoder to repair the file header and insert the correct keyframes.
Use Proxy/Timecode option in Blender.
- None
Do not use any timecode.
- Record Run
Use images in the order they are recorded.
- Free Run
Use global timestamp written by recording device.
- Free Run (Rec Date)
Interpolate a global timestamp using the record date and time written by recording device.
- Record Run No Gaps
Record run, but ignore timecode, changes in frame rate or dropouts.
Opomba
Record Run is the timecode which usually is best to use, but if the source file is totally damaged, Record Run No Gaps will be the only chance of getting acceptable result.