Roadmap

FIRST TUESDAY, 08.00 AM (West Coast US time, e.g. Hollywood)
https://lists.aswf.io/g/openfx-discussion/calendar to register ahead (subscribe) if not on list already.
You will get a response email and it will ask for you to create an LF login if you don't have an account yet.
Then you can at the bottom of the calendar page set the calendar to notify you (reminder)

1, General: Association Business (website)
2, Continue Discussions

Color:		Follow-up - discussion started Dec 6 Meeting

OCIO	Issue #102 PR #103	BorisFX JP Smith to describe their OFX-OCIO mapping, intiially developed so Silhouette and Mocha look at same color. Objective is to have something. Comments from Assimilate, Silhouette, BMD and Filmlight who don't internally work with OCIO model, how is this used by plug-ins and host to communicate?

			Deprecated - Issue Removed

GPU		Status: Ready to be continued
Action Item	Issue #98	3 properties were removed from original BMD SDK file - they would like to make sure old BMD flavor EXT will still work.	Gary has pushed new file Did BMD has modified their SDK (I think 18,5)?
		list is growing: Metal, Cuda, Vulkan (GLSL, SPIR-V), OneAPI, DirectX. OpenCL etc - Note SPIR-V is only driver simplification, the API remains different even if SPIR-V, we cannot use OpenCL for compute in a Vulkan context	As per last survey, everyone supports at least OpenCL, can add to OpenCL list Digital Anarchy.
gpu utils	#issue 64	remember we also have the GPU utils thread (its own PR) for any API like error code to be the same...	Pierre: Edited some typos, added dynamic opt-out option (documented but not a property in OGL suite)
		Would be a good thing to carry over the gain example for Cuda, Metal and OpenCL

Spatial Format
Spatial Format	TO be resubmitted	#Issue 77 and #PR 61	* This was the initial PR from Pierre and BrunoN	purpose was to address generators format (i.e. versus project dimensions) and multi-format in some hosts as domain of definition can change every frame and some hosts can return a small video in a black sea of pixels without reference to actual image dimension and also some hosts just cannot expand the image pass the source buffer received... Sure some host can pad themselves with a sort of static crop node before the effect (for these should be trivial to support).
Additional Info:	ASC FDL		RE:VIsion has been involved in the development of this model for framing. This is about maintaining framing decisions and intent across a whole production (from previz to conform). The initial Spatial Format should be modified to support this form of meta-data I think.	ASC Framing Decision List - The American Society of Cinematographers (en-US) (theasc.com)
Preliminary Research	OpenFX related		Pierre did a while back a listing of all spatial format related properties in OpenFX - link beside here. This clearly established that temporal and color properties are completely orthogonal to spatial properties.	SpaceTimePixels
Additional Info	Other API		A mention here is there are other standard discussions including SMPTE RIS project (which was somehow led by Unreal / Epic for virtual camera, real camera matching) and also a more in incubation stage USD camera discussion. Both would reference an FDL to reference physical dimension (e.g. to match lens data) and the matching image pixel window (same rectangle in different units).	Extra Notes: Note also side discussion with EXR, one thing FDL addresses is being richer description versus the limited data and image window of EXR, that for example many use to store less pixels, making a rectangle using the alpha bounds...

Parameters and Meta-Data
Parameter Interpolation		#Issue 116	* Open Issue of Parameter Interpolation

	Open Question		Format for storage for interchange	We had a first discussion about saving effects... April 2023
	Open question		Dynamic Parameters

Temporal format, timeline
Timeline Suite V2		* Would like to list all related properties in OpenFX already
	Open Question	OTIO	Pierre comments: I looked at OTIO a bit more carefully and I think we will have similar issues as with OCIO, as it's designed for pipeline conversion not as timeline model.

////////////////

Interaction - Overlays	over V1 released		As of December 6, Meeting - in hibernation for now
Overlay Draw Suite	Resolved	#PR 97	* remove typdef of a struct - we assume it's a C API inside a C++ compiler actually define as type is suggested	(PTM) Issue#99 (#100 on github), pull requested
	Resolved		* either document this suite must be handshaked before Overlay suite or add a V2 kOfxImageEffectPluginPropOverlayInteractV2 conclusion: V2 is DrawSuite only	(PJ) - Overlay Interact V2 in kOfxImageEffectPluginPropOverlayInteractV2
				Documentation for InteractV2 needs to be updated in header files.
	Open question		Phil asks about custom UI support... as next in this bucket. Custom UI parameter have the same issue.	Looking for host that actually implements this. Right now the Overlay suite would work - no image display though.

Page tree

Roadmap