Should editors work from camera originals or a house codec?
For teams making web content, I assess whether a consistent house codec can meet the editing and delivery requirements while reducing the media in active circulation. H.265 can be worth testing for that role. It needs to pass a real footage and workstation test before it becomes the team’s default.
A house codec is an agreed working format used across the team. It is not automatically a proxy, and it is not automatically suitable for finishing. Those decisions come from the picture requirements, edit performance and the jobs you deliver.
How is a house codec different from proxies?
Proxies are working copies intended to reconnect to higher-quality source media for finishing. A house codec is a standardized working format that may also be approved for delivery on suitable jobs. Camera originals preserve the captured source. Keep those roles explicit so editors know whether a conform is required.
| Question | Camera originals | Proxies | House codec |
|---|---|---|---|
| File size | Depends on the camera format | Usually designed to be smaller or easier to edit | Depends on the chosen working format and source |
| Picture information | Retains the recorded source information | Reduced to suit editorial needs | Transcoding may discard information; assess against the job |
| Finishing | Uses the recorded source | Normally reconnect to originals | May finish directly if approved; otherwise reconnect |
| Editor experience | Can vary across camera formats and hardware | Designed for responsive editorial work | Consistent format, with playback validated on team machines |
| Where I’d use it | Work needing source latitude or avoiding unnecessary conversion | Jobs needing light editorial files and source-based finishing | Repeatable workflows where the tested format meets the requirements |
Small files are not always easier to decode. A compact H.265 file can put different demands on a workstation from a larger editing codec. Test timeline behaviour as well as storage savings.
Where should you start with H.265 for LucidLink?
My recommended starting point is the built-in LucidLink preset in Parallel Media Encoder. Repeatable transcoding is part of why I built PME: the team should be able to start from a consistent preset, then validate it against their own footage and delivery requirements before adopting it across production.
Use Parallel Media Encoder to make a test batch, then put those files through a representative project. Check picture quality, scrubbing, multicam if you use it, audio, colour interpretation and final export on the workstations your editors actually have.
The preset is a starting point. A workflow for interviews and web explainers may need different decisions from one involving heavy grading, keying or detailed effects work.
What can a house codec save?
A smaller approved working format can reduce active storage, upload and download volume, and the amount of media each editor keeps locally. The saving depends on the source and output, so I measure a representative batch. I also account for transcode time and any additional finishing work before calling it a benefit.
For illustration, if 2 TB of source media produces 800 GB of approved working files, the working copy is 60% smaller. That is 1.2 TB less to transfer when someone needs the complete working set. It is an example calculation, not a claim about PME’s preset or your footage.
The originals still need storage and protection. If you keep both sets, total retained storage increases. The potential saving comes from limiting what needs expensive active or cloud storage, and what needs to move between people.
Cloud bills also depend on the plan. Fewer stored bytes do not necessarily reduce a per-user subscription or a minimum commitment. Compare the wider remote storage options.
When should you keep an originals-based finishing workflow?
Keep finishing tied to originals when the job needs source information the working format does not preserve, or when delivery and archive requirements demand it. RAW adjustments, substantial grading, VFX, keying and some broadcast or theatrical workflows warrant particular care. The client specification and a proper test should settle the choice.
Web delivery alone isn’t permission to discard picture information. Test demanding material: gradients, noise, motion, fine detail and the footage most likely to expose a problem.
If the working files fail the test, change the format or use proxies with a conform. The goal is a dependable workflow that meets the brief.
How do you introduce a house codec to a team?
Start with one representative project and document the result before changing the ingest process. A rollout needs more than an encoding preset: file identity, metadata, original storage, backup and any relinking procedure all need to work. Put someone in charge of that process so it stays consistent between shoots.
- Protect the originals. Verify ingest copies and backups before media is reused. Agree retention separately.
- Create a representative test batch. For LucidLink, start with PME’s built-in LucidLink preset.
- Check file identity. Verify timecode, audio channels, duration, frame rate and the naming or folder structure needed for matching sources.
- Run a real edit and export. Include normal handoffs, effects and finishing checks.
- Test a return to originals. Confirm that relinking works wherever the workflow may require it.
- Document the approved workflow. Record the preset version, exceptions, quality checks and who owns ingest.
- Roll it out in stages. Train the team and review the first projects before making it standard.