Tried it standalone – and yes, the pre-sharpener opened it …īut I couldn’t save anything (Nikon D750) Where the adjustments from the pre-sharpener were finally saved Tried it from PL5 – and PL developed & opened an intermediate TIFF – and of course, to work on raw-files it has to be able to handle them! Outdated or not, the RAW pre-sharpener, that is advertised in the most recent DxO Nik collection that also is available for license-for-fee at this time, claims to work on a RAW file as a PS plugin.īeing familiar w/ Nik Collection since it was NIK, I think I never really used the pre-sharpener With PL5E DeepPRIME, some output images “improved” using the Topaz suite as further processing (with more time investment) my preliminary tests indicate that with PL6E DeepPRIME XD the Topaz step for image “improvement” is not needed. Note that the use of presets in PL requires less photographer time in post compared to plugins and adjustments, although in both the Adobe suite and Affinity I have had to use plugins to get the results I wanted (typically, for clients). ![]() On a separate question, as I have not experimented with Affinity plus Nik RAW pre-sharpener on any images since I switched to PL from the Adobe suite, does the current PL5E DeepPRIME XD provide a “better” result than the current Nik RAW pre-sharpener? Does the RAW pre-sharpener actually work on a RAW image as a plug-in? A TIFF or other de-mosaiced format is NOT raw. ![]() Assuming that RAW means raw (un-de-mosaiced), whatever internal representation for a RAW file is used in the PS-compatible internal workflow image data pipeline should thus have been transmitted to the Nik raw-presharpener and then returned to Affinity for further workflow. NO export to a TIFF or other file was required to use the plugin in Affinity. The Nik pre-sharpener result – after the pre-sharpener pops-up and adjustments are made – does appear in the workflow image display of Affinity with a visibly changed (improved) result. Serif Affinity accepts PS plugins, and does accept and activate the Nik RAW pre-sharpener plug-in the current Affinity update does accept Nikon Z9 lossless compressed NEF files (raw) as do both PL5 and PL6. (Wolfgang, I am glad you are not laughing at this thread and falling out of your chair – if that was not your comment, please accept my apologies for the mention.) Outdated or not, the RAW pre-sharpener, that is advertised in the most recent DxO Nik collection that also is available for license-for-fee at this time, claims to work on a RAW file as a PS plugin. What am I failing to understand? If DxO products would not integrate into the Adobe-style workflow, then the problem would be more difficult as the “pipeline” (not mass storage file export and import) would need to be solved. The output could then be analyzed as to whatever changes should be incorporated into the parameters of the “adjusted” image, the same as if, say, a modified TIFF were re-imported into PL. Hence, PL (whether or not it “creates on the fly” the image shown to the photographer during image “adjustment”) could export the image as displayed by PL to an Adobe compatible plugin and accept the output from such a plugin without an actual creation of a TIFF, etc, file on the mass storage device. Clearly, DxO software engineers are able to import and return that format as the Nik plugins work with Adobe workflow (or has that changed? – the current DxO Nik web page still shows that integration as direct Adobe plugins). There is a “destructive layered” internal format used by workflow applications compatible with Adobe plugins (including the DxO Nik plugins). ![]() This should be no more computationally intensive than converting to TIFF and then converting TIFF back to the internal PL format and would allow PL to use the wide range of Adobe-compatible plugins. In any event, instead of outputting to a TIFF or DNG that holds (most of) the (raw) image information, and then creating an actual file on the harddrive to co-applications that accept TIFF, etc, as an input file, converting to the Adobe or Affinity format used for Adobe compatible plugins, transmitting this to the plugin (buffered either in RAM or in a pool on a drive, but NOT an actual output file such as a TIFF), then converting back to the PL form should be possible. ![]() At some point, PL must convert to “pixels”. Is any of this information published or described in public literature, or are you under NDA? As PL will also work on JPEGs, etc, for those raw formats that are not supported by PL (eg, NEF High Efficiency TICO), PL clearly is not strictly a raw editor. Clearly, you have some knowledge of the design and internals (possibly algorithms or even actual “code fragments”) of PL.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |