GPU - extention to pass buffers with different API about openfx HOT 9 OPEN

Stub

from openfx.

Summary

BMD's extension header file ofxImageEffectExt.h defines a set of properties which enable hosts to pass images to plugins as Cuda, Metal or OpenCL buffers, with associated stream and queue objects.

This mechanism has seen widespread adoption across plugins and hosts but is not officially part of the standard.

This issue is to get these extensions into ofxImageEffect.h or possibly a separate header, with community review largely of the comments/documentation since we cannot really change functionality.

For example there is no documentation about specific error codes (compare kOfxStatGLOutOfMemory, kOfxStatGLRenderFailed) nor of whether kOfxImagePropRowBytes has any meaning and/or should be respected.

from openfx.

Anyone know how to rename an issue? The title is wrong because there is no GPU suite and we're not proposing one.

from openfx.

Anyone know how to rename an issue? The title is wrong because there is no GPU suite and we're not proposing one.

There is Edit button beside the title, tested as you can see

Also there is an FR from Autodesk to add Vulkan to that list

from openfx.

As mentioned in meeting, PR #64 already defines error messages without GL in name...

from openfx.

Also there is an FR from Autodesk to add Vulkan to that list

As discussed in the TSC we'll make that (and any others) a separate issue/PR to prevent it holding up this one

from openfx.

Should we add runOn OpenGL to be complete?
I don't see a pull request for this item

from openfx.

Should we add runOn OpenGL to be complete?

Unclear what you mean, we have the OpenGL Render Suite for that.

I don't see a pull request for this item

I made one but it wasn't great. Gary took my commits and pushed them, see above.

from openfx.

I know we have a suite, I think you are saying host can decide to runOn OpenGL suite also?
My note is for Image/Texture, if you run on OpenGL you can use OpenCL and Cuda interop as a plugin so it already works, distinction here is in some tools we use or not OpenGL depending on user settings, I am not clear if for some hosts to send direct OpenCL or Cuda buffers makes a difference for host... (e.g. saves something). If so, we could dynamically say NO to runOn OpenCL or Cuda (then host can decide to runOn OpenGL)... or switch to request CPU and use GPU from that if faster to internally rasterize pushing back to CPU and back to GPU...

from openfx.