4/1/2023 0 Comments Uninstall topaz photofxlab![]() Given my choice I do not particularly want Elements on my system as it takes up an enormous amount of space and does not do 10% of what AP does. I will try what you suggested - using Edit -> Matte. That is, Elements must remove the alpha channel(s). One more thing - if I call Photoshop Elements instead of APB when re-saving the modified image I do not have this problem. That requires that I make the complete round trip between CaptureOne and the plugin for each call rather than being able to apply each plugin's adjustments in a single call, but the result is visible in CaptureOne. ![]() If I use Topaz's Fusion Express 2 instead of photoFXlab this problem does not seem to occur. There are some interesting variations to this CaptureOne -> Topaz -> CaptureOne -> APB -> scenario. Specifically Adjust was used and the adaptive exposure and adaptive color settings were modified before the image was returned to CaptureOne. The image was made by Topaz software called from CaptureOne through Topaz's photoFXlab. I can now remove Elements from my system. Thanks for the speed that you addressed this issue. If so, should APB not release the lock when the file is closed? Or am I on the wrong track here? That makes me ask if APB has a lock of some kind on the image and is not releasing it until it exits. My question (and I think this may be important) - If I go through this process and get an unreadable file in CaptureOne and then call Elements to fix the problem CaptureOne updates the thumbnail as soon as the image is saved back to CaptureOne but when I do the same with APB, fixing the problem with the Edit -> Matte command, the thumbnail does not get updated when the image is saved back, nor when the file is closed in APB, but only when APB exits. I guess that makes sense as jpgs do not support layers. In any case Edit -> Matte does indeed take care of the issue so I am good.Īs an aside the problem does not appear if I use a jpg instead of a tif when I send the image to photoFXlab. Given that Topaz does not seem very interested in updating that I assume I will have to live with it or change to Fusion Express 2. I have verified that Fusion Express does not cause this problem, even if the same changes are made to the image in the Topaz plugin, so the problem must originate in photoFXlab. Given the great job that Serif has done with everything I have seen I am really looking forward to any HDR functionality they create. Like a lot of such dedicated small operations he did a great job at a reasonable cost, but the tool only works on Windows so, when I moved to the Mac, I had to abandon it. The tool that I was the happiest with was a Windows based tool named SNS-HDR created by some guy in Poland. I have been using the HDR tool built into Lightroom 6 and that does a decent job. In addition it also has built-in gradient controls so it does a good job. The tool has a complete set of adjustments, beyond what I have seen available on other tools, as well as a large number of presets, and allows each preset adjustment to be further adjusted by controlling the intensity of the change. I have seen a new HDR tool named Aurora HDR which actually seems very complete. ![]() I do not always want those intense changes but assume that is what the opacity layers setting is for. On the other hand I have tried a lot of HDR tools and, as with you, I prefer those capable of making intense changes. ![]() Oh, I can make some assumptions involving luminosity masks and selective merging, but it is all guesswork on my part. I know very little of how HDR is actually implemented. > The HDR thing using stacks and Median Mode is somehow very limited. I was offline for some time because I had no photos to process and thus no reason to be using APB. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |