http://www.openeffects.org/dokuwiki/ 2010-05-26T00:21:56-04:00 http://www.openeffects.org/dokuwiki/ http://www.openeffects.org/dokuwiki/lib/images/favicon.ico text/html 2010-05-24T22:53:23-04:00 Pierre Jasmin http://www.openeffects.org/dokuwiki/doku.php?id=standards:draft:ofx_image_processing_api_2&rev=1274756003&do=diff Back to main contents The OFX 2.0 Image processing API is a rationalisation and extension of OFX 1.0. Committee Members * Bruno Nicoletti, on behalf of The Foundry (chair) * Piere Jasmin, on behalf of RE:Vision Effects * Gary Oberbrunner on behalf of GenArts Inc * Shin Kurokawa on behalf of Digieffects LLC * Jean-Luc Dery on behalf of Autodesk Inc * Phil Barrett on behalf of Filmlight Ltd. text/html 2010-05-17T19:10:12-04:00 Pierre Jasmin http://www.openeffects.org/dokuwiki/doku.php?id=standards:draft:ofx_image_processing_api_2:major:threading&rev=1274137812&do=diff Back to OFX 2.0 Draft Status For discussion. Overview It has been suggested that the threading API needs to be extended radically or deprecated entirely and replaced with host OS threading. There are pros and cons to each option. In case of deprecation, the plug-in should be informed of the maximum number of threads it should be using by the host application. text/html 2010-05-17T18:10:57-04:00 Pierre Jasmin http://www.openeffects.org/dokuwiki/doku.php?id=standards:draft:ofx_image_processing_api_2:enhancements:data_caching&rev=1274134257&do=diff Back to OFX 2.0 Draft Status For discussion Overview There is a need for a suite that allows a plug-in to cache internal data during render calls for retrieval in a subsequent render call, e.g. retimer caching motion vectors. This is especially important if we split off separate render object from the persistent instance.