After introducing the DxO ColorWheel, which offers users a brand-new approach to colour, DxO PhotoLab 3.2 has made local adjustment mask management even more flexible, optimized its Repair Tool, and improved PhotoLibrary keyword support. It also now supports the Canon EOS-1D X Mark III, Nikon D780, Olympus E-M1 Mark III, Leica D-Lux 7 and Leica Q2 cameras.ĭxO PhotoLab 3 users can download this update for free.ĭxO PhotoLab 3.2 Is Expanding Its Set Of Local Adjustment Tools And Improving Its PhotoLibraryĭxO PhotoLab 3, the market’s leading photo-editing software in terms of image quality developed by DxO, has now become even better with its latest 3.2 update. So the need for seamless integration of editors is important (which Serif should have resolved before they released Affinity 2 or provided a fully documented workaround at the time of the release - but they have been particularly pro-active responding to users concerns and that is too their credit).DxO PhotoLab 3.2 has made local adjustment mask management even more flexible, optimized its Repair Tool, and improved PhotoLibrary keyword support. Photo Editing appears to be one area, in particular, where users have favourite programs for specific elements of their workflow and will “jump” from program to program (and back again). BAT workaround)!Ĭurrently DxO has more than enough issues with respect to DxPL that need fixing and I would prefer that they show their concern for their users by fixing those first, and actively participating in this forum, and if Serif does the same with Affinity (they appear to be active in their forum) then the problem will go away! Hamish I agree but DxO fixing the problem means that DxPL users could then access Affinity but not users of other packages! None of the ones I mentioned can access Affinity 2 (except via the. When I use “Export to App” to send images to the the newly linked Affinity 2…It just fails with “Affinity Photo could not be opened” message. SECOND ISSUE: EXPORT TO AFFINITY V.2 FAILS EVEN WHEN AFFINITY V2 EXECUTABLE IS LOCATED. The correct location for my Affinity executable was:Ĭ:\Program Files\WindowsApps\SerifEuropeLtd.AffinityPhoto2_2._圆4_3cqzy0nppv2rt\AppĬan you add the ability to browse hidden folders in Photolab? I didn’t find it in any documentation, but it might be worth adding it somewhere for others who might have the same issue. I could NOT see the WindowsApps folder at all in the browsing window of Photolab6. Unfortunately, it seems the “WindowsApps” folder within the Program File’s folder is hidden to Photolab. You’d think this would solve the problem… but alas it isn’t so. I ultimately found version two of Affinity by using the desktop shortcut path, then copying and pasting the complete file path to the Affinity2 executable into Photolabs external app folder browsing window. Browsing through the Program Files directory could find my old Version 1 of the Affinity App, but had NO chance of finding the location for Version 2. Serif has changed the installation of Affinity V.2 in such a way, that using the “export to app” function can’t find it. In short, it’s impossible to find the executable using Photolabs folder browser. ISSUES WITH LINKING PHOTOLAB 6 TO AFFINITY V.2: The original version of Serifs Affinity (V.1) works flawlessly with all versions of Photolab but the recently released version 2 does not work with Photolabs “export to app” function. Except when trying to export to the new version of Affinity. I recently installed Photolab 6 Elite on my WIndows 10 system, everything is going really well. Please direct this to your software development team. Photolab 6 Elite and Affinity 2 don’t play nicely with each other (through export to app function) in Windows 10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |