- DXO FILMPACK 5 REVIEW UPDATE
- DXO FILMPACK 5 REVIEW SOFTWARE
- DXO FILMPACK 5 REVIEW PC
- DXO FILMPACK 5 REVIEW WINDOWS 7
it took 6 minutes and 30 seconds to convert 109 PEF files approximately 30MB each and I don't know is it good result. I also tested the speed of extracting files with deep prime and some other settings I liked almost by intuition. I‘ll check if it‘s hidden in a tag that preview may not read. I couldn't see any instances of this before PL4.Interesting! I also realised that my dxolab5 exported jpgs don‘t show the lens names in macos preview.
DXO FILMPACK 5 REVIEW SOFTWARE
My guess is that these are images in which, for some reason, I neglected to copy the lens name from Maker Notes to EXIF and somehow the software has put it in XMP. That is, there is the odd jpg where the lens name is in the XMP although not in EXIF. Mostly not, but occasionally it has, in PL 4.1, 4.2 or 5. So I have looked over other jpgs exported from PL to see whether this has happened. Looking at the details of the jpg in EXIFTool Gui, I notice that the lens name is not in the EXIF but has been written to XMP-aux - I can only surmise that Flickr read it from there. To my surprise the lens name showed in Flickr. I tried your test - processed a RAW file in which the lens name was only in Maker Notes (usually I copy it to EXIF using EXIFTool Gui, before processing, but not for this one), exported to jpg and uploaded to Flickr. I couldn't see any instances of this before PL4. Perhaps it's not saved to EXIF, but in a format that is readable by Flickr, while it was not done so before.I tried your test - processed a RAW file in which the lens name was only in Maker Notes (usually I copy it to EXIF using EXIFTool Gui, before processing, but not for this one), exported to jpg and uploaded to Flickr. Lens name shows up only in the second picture. See those two pictures, one the OOC jpg, the other the file as converted by DxO PL5. Actually the message mislead the user.I don't think it's a feature of the K-3 III. Return to the original post, I think DxO have to change something in the FP warning system. Win 7 is an emergency machine on my table, let me keep contact with the world.
DXO FILMPACK 5 REVIEW PC
My Win 10 PC is in the service station, because its power supply went wrong. The reason I did start my Win 7 version is simple. It means for me, the PL embedded FP is independent from FP standalone and did not updated by the latest FP version.
DXO FILMPACK 5 REVIEW WINDOWS 7
I went to the latest PL v3.3 Windows 7 compatible app and the built in FP part was perfectly functional. For test only start FP, which was not functional.
DXO FILMPACK 5 REVIEW UPDATE
After applied the effect, step out from PS -> update FP v5.5.27.605. Without update FP v5 it was working, because I intended to add frame to a layer image. It was a definitive request from DxO.īy the way I did open FP v5 from PS CS6 as a plugin only. HOWEVER, I wouldn’t update to the latest Filmpack version, without Filmpack pop up window: here is the latest version, please update.
0 kommentar(er)
