![]() This unnecessarily complicates retouching as the stylus has to be lifted out of range to use zoom or jump to 100%. But if you have to do two OpenCL stacks with different methods to discover cross output retouching won't work for the stack, disable OpenCL, restart Helicon, and then restack with CPU only that's considerably slower than just doing the two stacks CPU only begin with.Īdditionally, Focus ignores two finger zooms and three finger touchpad presses for middle button clicks on one of my machines when the stylus is within range of the USB tablet I use. This is problematic since the purpose of OpenCL support is to allow faster stacking than with just the CPU. Since an additional workaround appears to be disabling OpenCL it would seem there are perhaps some issues with numerical stability on that codepath in addition to the issues around project design. Hi Catherine, any update? Been over a month since the issue was reported and I keep hitting more failures to link outputs for retouching even with rotation and brightness adjustment disabled. The purpose of cross-output retouching is, after all, to merge differences between outputs. However, it's unclear why this would affect retouching availability of outputs. It seems more natural that optimal brightness transforms might vary with stacking parameters since, for example, the contrast increase associated with pyramid stacking would favor increased highlight protection. My expectation is the alignment would be calculated once and then reused across different choices of stacking options but, given the large number of issues encountered in this space, perhaps this doesn't occur, perhaps numerical tolerances aren't considered, or perhaps there is an issue in creating a transform aligning the outputs to each other. Since the optimal alignment frames is presumably a property of only the frames, and therefore constant across different choices in stacking methods, it's unclear to me why rotational alignment would influence the availability of outputs as retouching sources. Keep the rotational alignment allowance at its default of zero even on images where it may be beneficial. ![]() Disable adjust brightness (Edit -> Preferences -> Autoadjustments).I've uploaded a second set of frames to the ftp server as well. Unfortunately this issue also reproduces on 7.6.4. Hit this same issue with cross-output retouching on a few more stacks, so tried ditching 7.6.6 and rolled back to 7.6.4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |