Important HitFilm Notes

< Previous | Contents | Manuals Home | Boris FX | Next >

Important HitFilm Notes

- Image sequences must be placed into a folder WITH NOTHING ELSE IN IT, except those images. Really, it can't have ANYTHING else in it, no IFLs, no SNI files, no text file of what it is, etc. To deal with that, you must turn OFF the "Write .IFL files" preference in the Image Input section of the SynthEyes preferences.

- You must be sure that your image sequences always have fully-padded frame numbers from whatever application is generating them. YES: img0001.jpg, NO: img1.jpg

- You must always be sure to select the first frame of the sequence when opening the sequence in SynthEyes, not a later frame.

- Only the currently active shot and its related objects are exported.

- You may want to use the Exportable checkbox on the 3D Panel in SynthEyes to intelligently control which trackers are exported to HitFilm, to reduce clutter.

- Windows : HitFilm will not automatically open a file newly exported by SynthEyes if HitFilm is already open. So you need to either turn off that checkbox, so that SynthEyes doesn't ask for the file to be opened, or you must close HitFilm first before exporting.

- When lens distortion is present (a Lens Workflow must be used), generating the distortion maps may take tens of seconds. Future SynthEyes versions may do that in SynthEyes itself, instead of in the export script, which would make it more efficient and able to use multiple cores.

- The Displacement Effect used to implement lens undistortion and redistortion in HitFilm is not very accurate; in particular when using Lens Distortion Workflow #2 the redistorted image typically exhibits several pixels of error compared to the original version. Hopefully future HitFilm and exporter developments will make it possible to avoid this.

- Tracker Layers must be selected in HitFilm to be visible in the camera view. (We've suggested that can be inconvenient.)

- Large meshes require substantial storage in HitFilm's project file format, so they may take some time to export and import.

- We're aware of the HitFilm's Alembic animation capability, and SynthEyes's Alembic export capability. Unfortunately they can't yet talk, as HitFilm requires the mesh and vertices to be in a special simplified (unrolled) format. That will require a special future HitFilm option for SynthEyes's Alembic exporter, or HitFilm to support the MDD or PC2 animated mesh formats.

©2024 Boris FX, Inc. — UNOFFICIAL — Converted from original PDF.