I use Sony, but my experience is that Affinity Photo's Develop persona appears to handle color spaces differently to ACDSee's Develop mode and perhaps that might be contributing to what you are seeing. Do any other Fuji users have similar experience?I'm not a Fuji user. Clearly I can live with this by exporfting such images to Affinity, but I am wondering whether the algorithm (used by ACDSee to render Fuji raws) could be improved. Exposing to the right taken too far will obviously burn out highlights, but I have found that in some of my images ( particularly skies), highlights are not recoverable in ACDSee but are recoverable in Affinity.
The more automated treatments available today do pretty much everything I used to spend a lot of time on in pure editor tools, so I find myself using tools like Affinity less and less, and the less I use them the more I forget how to use them.For the most part I think that ACDSee renders Fuji Raw files as well as any other program except in one respect.
So, I have tried and own a few varieties of software in an attempt to streamline my workflow. Both ACDSee and Affinity handle the topaz and luminar plugins ok, but only one has a file manager. The best program so far for that is an older version of ACDSee that I have, the plugins transform it into a modern tool and I just ignore it’s editing features and mostly use it as a file manager. I have used affinity photo, but lately I find myself wanting to work more simply by starting out with a file manager, culling files, sometimes launching raw versions into tools like denoise-ai and sharpen-ai and then finishing them off in luminar (all via plugins, so no need to do time consuming save and re-open operations).
Thanks for taking the time to test fuji raw and dng files out. Can you make the previous verison installer available so we can go back to a working version of studio 2?
I should have stopped there, this new version is clearly flawed in many ways. Oh, by the way, the updater on my old version of studio 2 also told me it was uninstalling the beta version, which is just wrong. So, until this is fixed, Studio 2.2 is useless to me. In Studio 2.2 it’s an even uglier shade of pink than the raw conversion, no amount of fiddling with white balance controls can make it even acceptable. I used another commercial product to create an Adobe compatible DNG file, which opens just find in PSE. Right off the bat the blue sky was an ugly pink. I first went back to a Fuji Raw file (not an x-trans raw, but a bayer raw from an XA3) that I had been working with before. I then downloaded the installer and it installed without a hitch. By that, I mean I used a commercial uninstaller program to remove studio 2 and all it’s left over registry entries and files, over which there were many! (as an aside, when will software engineers on the windows platform create an uninstaller that actually uninstalls everything?) It gave a runtime exception… So I checked the forum and seeing a few other complaints but not this exact one, I decided to do a clean install. Studio 2.2 finally installed, but would not run.
Lot’s of errors with wrong versions of various components.
I finally acknowledged the update notice and it went into it’s auto update process. To start off, I was using Studio 2.1 or whatever the previous version was with no problems.