Open Effects Proposal for Standard Change
Please read the contribution guidelines first.
Standard Change Workflow
Requirements for accepting a standard change:
Summary
Some hosts have the concept of a 3D camera, lights, nulls, etc. There is currently no standard method
by an OFX plugin for querying that information.
Motivation
Plugin vendors want to get access to the host Camera and possibly lights and 3D nulls.
Problem
The problem is there is currently no standard way to query this information. Some hosts have
private suites but they are inconsistent.
Impact
This would require a new set of 3D-related properties and and a suite which would not affect
existing suites or properties.
Host support for 3D would be determined by the presence of a new suite.
Documentation Impact
A new section on 3D support would be required in the documentation.
Stakeholders
Hosts and plugins would benefit from this.
Discussion
The following hosts have private suites:
Nuke
Nuke has a NukeOfxCameraSuiteV1 with functions for defining a camera input (during the Describe) action that can be connected to via the graph, like an image input. Cameras are described as a PropertySetHandle with properties:
- Projection Mode
- Focal Length
- H/V Aperture
- Near/Far planes
- window translation/scale/roll
- Focal Point
- position matrix (a 4x4 matrix but its nature is not described)
Scratch
Scratch has a OfxAssimilateCameraSuite with a call to get a single global camera. The camera information is described by a PropertySetHandle with properties:
- Pose (a 4x4 OpenGL-style matrix),
- Field of View
- Near/Far planes.
HitFilm
HitFilm has comprehensive 3D support for Cameras, Lights, and arbitrary per-clip Transforms.
The Camera API is similar to Nuke's, where Cameras are treated like inputs. Properties are:
- Matrix (row-major 4x4 double)
- Zoom
- FOV
- Focus Distance
- Blur Level
- Aperture
Additionally, the suite allows querying the available lights which have numerous light-related properties.
Transformation matrices for clips that are "3D" can also be queried.
Open Effects Proposal for Standard Change
Please read the contribution guidelines first.
Standard Change Workflow
standard changetagfeature/PROPOSAL-NAMEbranch)maintainer merges PR to master which closes PR and issue
Requirements for accepting a standard change:
Summary
Some hosts have the concept of a 3D camera, lights, nulls, etc. There is currently no standard method
by an OFX plugin for querying that information.
Motivation
Plugin vendors want to get access to the host Camera and possibly lights and 3D nulls.
Problem
The problem is there is currently no standard way to query this information. Some hosts have
private suites but they are inconsistent.
Impact
This would require a new set of 3D-related properties and and a suite which would not affect
existing suites or properties.
Host support for 3D would be determined by the presence of a new suite.
Documentation Impact
A new section on 3D support would be required in the documentation.
Stakeholders
Hosts and plugins would benefit from this.
Discussion
The following hosts have private suites:
Nuke
Nuke has a NukeOfxCameraSuiteV1 with functions for defining a camera input (during the Describe) action that can be connected to via the graph, like an image input. Cameras are described as a PropertySetHandle with properties:
Scratch
Scratch has a OfxAssimilateCameraSuite with a call to get a single global camera. The camera information is described by a PropertySetHandle with properties:
HitFilm
HitFilm has comprehensive 3D support for Cameras, Lights, and arbitrary per-clip Transforms.
The Camera API is similar to Nuke's, where Cameras are treated like inputs. Properties are:
Additionally, the suite allows querying the available lights which have numerous light-related properties.
Transformation matrices for clips that are "3D" can also be queried.