I have no idea if such an approach is viable or commercially realistic. Assuming, of course, that the way DxO do things for their own internal purposes within their own software is standardized, consistent and something they are prepared to share commercially. So to process a DxO "RAW" file C1 would need to be able to understand the internal "DxO RAW" profile used to create it. Thats' what 99.99% of phone users do anyway. Mobile phone files for example., but the potential is often somewhat limited almost to the point that one may as well use the phone's jpgs rather than waste its internal storage capacity. If that is not available, in much the same way as it would not be available for an unsupported camera, C1 has very limited scope for doing any successful processing.įor DNG files in some situations, a "generic" profile will give some results. Perhps you can try the same approach with DNG files, change the exif tags to make the file seem like it comes from a supported source.Ĭ1's editing of a DNG file, if it is to be accurate, requires the same information as an out-of-camera RAW file - data about the "camera". This command is of couese used in "Terminal" and calls Phil Harvey's exiftool application This will convert all your rw2 files in the current folder. The easiest way to use a DC-G9 raw file in PS to convert it (actually just rename the camera model in the raw file) with exiftool: Recently someone in DP review suggested this (haven't tried it) I started the when I edited GM1 files to be G5 using a hex editor like "010 editor" or "wxHe圎ditor", this OK to explore and do a small amount of images. I suspect a similar mechanism is at work here. PeI have noticed that when COP is asked to oipen RAW files, the success or failure is gated by Exif tags in the RAW file.Ĭurrently RAW files with exif tag "G9" cannot be opened (unsupported camera) but if you edit the file to change the tags to "GH5" (supported camera) then the file does open.
0 Comments
Leave a Reply. |