Possible topics of discussions - Calls for topics of interest
PierreJasmin_REVisionEffects
Call for Ideas.
Would like to organize sometime before end of this summer an online session to
continue/resolve the GPU issue and also at same time add some
educational value elements to this and now we will be adding "github
sponsor" buttons hopefully to find ways to beef up funding for
support code / examples etc and having a more "academic / dev
learning" component would allow us to attract a larger variety of
developers I think and expand where OpenFX can be used. The main
part about the github sponsor is to energize external
contributions as examples etc is really a big inertial force in adapting the
API over time.
Just providing examples of short presentations that would be of
interest, exploring options, did not ask people I list here. If
anyone has ideas please chime in.
1. Michel Elie who is on this list and doing his PhD for next few
years, did an experimental ofxMeshEffect suite for Blender - same
level as ofxImageEffects and also uses ofx core (his test case
was to support Houdini SOP type operators in Blender), that would be a
nice presentation I think.
2. Alexandre Bizeau discussed his own use of SYCL on this list.
It could be nice to have a short presentation of what it implies
to develop OpenFX plugins using that programming platform. That
would ghost nicely shipping OCL suite.
3. There is a few Resolve developers on this list, it would be
nice to get a demo of their SDK cross API "pixel shader" sort of
macros over different API working on buffers. Maybe there is
someone familiar with that on this list that would like to do
that, or someone who supports Resolve and has or would like to play with
that...
4. Aaron Boxer recently posted his open source library with OpenFX
plugin. There appears to be support for FPGA/OpenFX/OpenCL. A short
presentation of what it means to support FPGA would be nice.
5. Is there anyone that knows anything about Windows Display
Driver thing... one issue we have with abstracting GPU API is not
being to index GPU across API the same. Since 2017 Windows provide
a unique Index for each GPU whatever the API used - see the
performance monitor GPU if you have more than one (including an
integrated graphics) - not clear how we map GPU in an API to that
so we have a common reference. On Windows drivers are written
over Windows Display Driver.
6. Any other ideas? I know TuttleOFX has a Reader and Writer
Context, and Dennis recently mentioned they do similar. Maybe to
understand what a plugin could do in that context would be useful?
And should that become supported officially?
7. Mike had issue with a plugin controlling the output to an external monitor I guess. This reminded me of Combustion back then, they did a FrameBuffer API (not unlike the AE one now used for example to interface Character Animator to AE I think). Combustion had 5 companies supporting it back then, including Blackmagic. MotivaCG back then (not sure if he is on this list) did a nice demo of sending images across ethernet to different computers running different OFX hosts - he removed his experiment out of youtube now... that could maybe be a useful suite.
If we are successful with that, we can repeat 4 months later with next set of topics. It's premature for now to talks about Apple Silicon (at least OpenGL and OpenCL is not dead in MacOS 11) as no one has a dev kit yet...