this is one of the areas of the spec that I never really understood, at least from the windows environment. with the number of devices that support this capability vs the number of non-twain solutions to doing this why do this in twain? I have similar views on multi-image tiff conversions (or really almost any sort of image filetype conversions) – do them outside of twain and avoid the vendor specific issues, leave the twain interaction to getting a valid image of high enough quality in low enough time..
but then maybe I just never ‘got’ the value of these capabilities.
Do you really need to do this in twain?
.