2008/1/29, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > You should note though that the individual render node *must not* hold > any time varying data because of thread safety. Any data will be passed > in as "frames" (video, audio, control data) with the individual "pull" > calls for rendering. The render network is shared, and the backend needs > complete freedom for pulling rendered frames as it sees fit.
Problems to keep in Mind: * Requiring Plugins to provide random access to frames is nice in theory, but in practice, many iterative Video Filters exist and produce nice Visuals. * Complete Separation of UI and Plugins is nice in theory, but in practice, you might want to attach additional UI relevant data to an Effect. * FreeJ does funky javascript video compositing stuff. * LiViDO was drafted in great Detail, and was never really used? * It lives on in the Weed Filter API in Lives. http://lives.cvs.sourceforge.net/lives/lives-plugins/weed-plugins/ * Apps such as the Blender Compositor would be perfect to create as well as use such plugins. http://wiki.blender.org/uploads/8/8e/Green_screen_03.jpg * You want to reuse filters from MathMap, Gimp and Krita with little Effort. http://www.complang.tuwien.ac.at/schani/mathmap/ http://www.krita-plugins.org/ * You want to be able to eventually accommodate concepts such as fancy Transitions from http://gvfx.blogspot.com and from http://www.kde-files.org/index.php?xcontentmode=683 * You don't want to fall prey to the Architecture Astronauts http://www.joelonsoftware.com/articles/fog0000000018.html _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
