Seeing as how Vegas and OFX is mentioned quite a lot here I thought it worth trying to get a better understanding of what it is and what it isn't.
From my research I believe it provides a standard way for a plugin to be called from a host, an image supplied to the plugin and an image to be returned, on a frame by frame basis. There's a bit more functionality that permits no frame to be supplied but one returned to support things such as noise generators. Two frames can be supplied so that transitions are supported. Also a frame of alpha channel data can be supplied.
Obviously there's more complexity to it than that, most of which goes over my head. Still by my very basic understanding the interface is limited to what are non temporal image manipulations. That would exclude plugins such as image stabilisation and motion tracking.
Of course I could be completely and utterly wrong, my hope is someone will set me straight if so and all of us will get a better understanding of what all the fuss is about.
Bob.
From my research I believe it provides a standard way for a plugin to be called from a host, an image supplied to the plugin and an image to be returned, on a frame by frame basis. There's a bit more functionality that permits no frame to be supplied but one returned to support things such as noise generators. Two frames can be supplied so that transitions are supported. Also a frame of alpha channel data can be supplied.
Obviously there's more complexity to it than that, most of which goes over my head. Still by my very basic understanding the interface is limited to what are non temporal image manipulations. That would exclude plugins such as image stabilisation and motion tracking.
Of course I could be completely and utterly wrong, my hope is someone will set me straight if so and all of us will get a better understanding of what all the fuss is about.
Bob.