When using a COEditingPlugin is there a way to get access to the original file without edits for non raw files?
I am using the CO 20 api. I work for ON1 Software and we have a product called ON1 Photo Raw. Within that product we have support for creating HDR images. The CO Plugin that I am building will take a bracket of files the user has chosen, send them to ON1 Photo Raw, create a new TIF, JPEG, or PSD and return back to the CO Plugin and have it use that file as a result to be imported back into CO. We need the variants to not have any adjustments applied to them. This works fine for files that can be exported as DNG because there are no settings applied but is a problem for TIFF's and JPEG because the adjustment always seem to be applied. Currently I am using a COEditingPlugin because that seems to be the only way of telling CO that you have a new file as a result. I know that the COOpenWithPlugin can get the variants without adjustments applied but does not seem to have a import a resulting file back into CO.
I also have another problem. We are building plugins for both Mac and Windows. On mac, I am able to adjust the list of supported file formats by using the processSettingsForAction method. However, on windows, the GetProcessingSettingsForAction method results in that all of the file formats are shown. We do not support Jpeg softproof or Jpeg XR and would like them to not appear in the list of available variant formats.
Thanks for any help that you can give.
Tim Brown
ON1 Software.
-
Do you mean you managed to get access to the pixels on Capture One?
0 -
Camera raw files always contain the original, unprocessed pixels from the camera. alaskasworld Don't confuse Photoshop raw with camera raw file formats. users may not be able to access images stored in that format, and the images may in Camera Raw, watch How to make non-destructive edits in Camera Raw.
0
请先登录再写评论。
评论
2 条评论