If a native implementation is present it is, by default, the preferred implementation. But if the nature of the sources and parameters of the operation are incompatible with the native operation then processing will revert to Java code. In general the following minimum requirements must be adhered to for the mediaLib native implementation of an operation to be executed: * All sources must be RenderedImages. * All sources and destination must have a SampleModel which is a ComponentSampleModel and a ColorModel which is a ComponentColorModel or no ColorModel (i.e., it is null). * All sources and the destination must have at most 4 bands of pixel data. * If Interpolation type is one of the arguments to the operator, then native acceleration is available only for Nearest, Bilinear, Bicubic and Bicubic2 cases. Additionally for byte images InterpolationTable is also supported for native acceleration.
I'm not really that familiar with the detailed guts of image processing, and would like to use some basic functions that would be nice if they were natively accelerated. If somebody could better expound/expand/explain "at most 4 bands of pixel data" I'd appreciate it! [ June 03, 2002: Message edited by: Gerry Giese ]
CJP (Certifiable Java Programmer), AMSE (Anti-Microsoft Software Engineer)
Author of Posts in the Saloon