I have lens-distortion numbers from one tracking or compositing tool: can I type them into another tool, and what should I check first?
Partially verified: the curator re-read none of the cited sources; S11, S10, S20, S27, S17 rest on the producer's pinned reading. Generally no, not without checking. A tracking-tool vendor says the math varies between packages so coefficients often cannot be reused elsewhere and recommends STMaps instead. Vendor docs for Nuke show why: the same preset family has a direction setting (forward or backward), a normalisation choice (width, height, diagonal, maximum), a distortion centre, and anamorphic terms. A metadata standard (OpenTrackIO reference code) carries a model name string with a default of "Brown-Conrady D-U". The safe beginner route is: identify model and direction, normalisation, centre and sensor size, or transport an STMap and test it on a grid.
Structured fields
{
"citations": [
{
"url": "https://borisfx.com/documentation/syntheyes/syntheyesum_files/lens_distortion_interchange_1",
"note": "cited at https://borisfx.com/documentation/syntheyes/syntheyesum_files/lens_distortion_interchange_1/; Nuke LensDistortion; SynthEyes"
},
{
"url": "https://borisfx.com/documentation/syntheyes/syntheyesum_files/lens_distortion_models",
"note": "cited at https://borisfx.com/documentation/syntheyes/syntheyesum_files/lens_distortion_models/; Nuke LensDistortion; SynthEyes"
},
{
"url": "https://learn.foundry.com/nuke/content/reference_guide/transform_nodes/lensdistortion.html",
"note": "Nuke LensDistortion; SynthEyes"
},
{
"url": "https://github.com/SMPTE/ris-osvp-metadata-camdkit/blob/0362321d03721a07029329cfc6f9e1e47bfa2bdf/src/main/python/camdkit/lens_types.py",
"note": "Nuke LensDistortion; SynthEyes"
},
{
"url": "https://borisfx.com/documentation/syntheyes/syntheyesum_files/distortion_map_stmap/",
"note": "Nuke LensDistortion; SynthEyes"
},
{
"url": "https://borisfx.com/documentation/syntheyes/syntheyesum_files/lens_distortion_interchange_1/",
"note": "observed URL (dated/alias form of the cited catalogue source; canonical identity retained)"
},
{
"url": "https://borisfx.com/documentation/syntheyes/syntheyesum_files/lens_distortion_models/",
"note": "observed URL (dated/alias form of the cited catalogue source; canonical identity retained)"
}
]
}Evidence claims
- [sourced_fact] Generally no, not without checking. A tracking-tool vendor says the math varies between packages so coefficients often cannot be reused elsewhere and recommends STMaps instead. Vendor docs for Nuke show why: the same preset family has a direction setting (forward or backward), a normalisation choice (width, height, diagonal, maximum), a distortion centre, and anamorphic terms. A metadata standard (OpenTrackIO reference code) carries a model name string with a default of "Brown-Conrady D-U". The safe beginner route is: identify model and direction, normalisation, centre and sensor size, or transport an STMap and test it on a grid. · locator: cited at https://borisfx.com/documentation/syntheyes/syntheyesum_files/lens_distortion_interchange_1/; Nuke LensDistortion; SynthEyes source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |
Linked records
- cites → https://borisfx.com/documentation/syntheyes/syntheyesum_files/distortion_map_stmap
- cites → https://borisfx.com/documentation/syntheyes/syntheyesum_files/lens_distortion_interchange_1
- cites → https://borisfx.com/documentation/syntheyes/syntheyesum_files/lens_distortion_models
- cites → https://github.com/SMPTE/ris-osvp-metadata-camdkit/blob/0362321d03721a07029329cfc6f9e1e47bfa2bdf/src/main/python/camdkit/lens_types.py
- cites → https://learn.foundry.com/nuke/content/reference_guide/transform_nodes/lensdistortion.html