foxyshadis
9th April 2006, 13:00
I was arguing with someone over the relative merits of the mac or the lack thereof, and he raised a very interesting point. More advanced video systems have SDKs, so what would keep avisynth filters from being ported over? He's right that the basic idea is (get a frame) -> perform magic -> (hand frame back), and the bookkeeping details, while not trivial, aren't nearly as complex as the actual filter. A few avisynth filters would be incredibly useful for some projects (although AE/Motion have their own sets of advanced filters replacing ), plus, well, they're free and fast.
Unfortunately, some of the most useful are scripts, which would be a pain to convert into some kind of self-contained plugin, or morph the scripts into scripts or actions for other software.
For 3.0 avisynth will actually be able to work on other OSes, apparently without the restrictions of avi and color imposed now, but this is a way to branch out without waiting for the upgrade. I think virtualdub is the only other framework avisynth stuff has been ported to so far.
Any thoughts on the topic? Anyone feel a burning need for this?
AE SDK (http://partners.adobe.com/public/developer/aftereffects/devcenter.html)
FCP SDK (http://connect.apple.com/), I think.
Combustion & Shake use the AE plugin format.
Unfortunately, some of the most useful are scripts, which would be a pain to convert into some kind of self-contained plugin, or morph the scripts into scripts or actions for other software.
For 3.0 avisynth will actually be able to work on other OSes, apparently without the restrictions of avi and color imposed now, but this is a way to branch out without waiting for the upgrade. I think virtualdub is the only other framework avisynth stuff has been ported to so far.
Any thoughts on the topic? Anyone feel a burning need for this?
AE SDK (http://partners.adobe.com/public/developer/aftereffects/devcenter.html)
FCP SDK (http://connect.apple.com/), I think.
Combustion & Shake use the AE plugin format.