* Scott <[email protected]> [09-05-20 14:01]: > Thanks for the input. This is the exact reason that I've never used a > development version either. I've only ever used DT from the > repositories. Honestly, I don't even know how to use a development > version and I've never tried to compile DT. I can compress the > history before the profiled denoise instances and it seems to work > fine, but it obviously removes the profiled denoise instances in that > case. All of my edits from before DT 3 are affected (at least all of > those with 2 profiled denoise instances). > > On Sat, Sep 5, 2020 at 10:38 AM Remco Viëtor <[email protected]> wrote: > > > > On samedi 5 septembre 2020 18:15:53 CEST Scott wrote: > > > Hello. I've recently updated to DT 3.2.1 and I've found that many > > > (most?) of my old edits are now ruined when I open them in darkroom. > > > I think it consistently occurs when I have two instances of profiled > > > denoise in versions before DT 3. For years I edited my pictures with > > > the 2 profiled denoise instances as I found recommended a few times > > > (one for luma and one for chroma), which makes me surprised that there > > > are not many others with this issue. I did not use DT 3 before 3.0.2 > > > since I knew there were issues with iop order in 3.0.0 and I didn't > > > want to risk being in the situation that I'm now in. The vast > > > majority of my edits are in DT 2, mostly 2.6 series. The link below > > > contains some screenshots and additional information, so I won't > > > repeat it all here. A few devs have indicated that I've lost my work > > > in this issue report, but I figured I'd ask here for any additional > > > tips or ideas before throwing away hundreds of hours of edits. > > > > > > https://github.com/darktable-org/darktable/issues/6207 > > > > > > Thanks for any ideas! > > > ____________________________________________________________________________ > > > darktable user mailing list > > > to unsubscribe send a mail to > > > [email protected] > > > > It seems that this was an issue present in some *development* versions > > *only*. > > As I never use those for serious work, it's not surprising I haven't had any > > of those problems. > > > > And this kind of problems is the *reason* I don't use development versions > > for > > anything I consider serious work... > > > > That said, would the following work? > > - disable both profiled denoise instances > > - click "compress history stack" (that should remove the old active > > instances from the history stack) > > - in the history stack, move to the line just below those two now disabled > > modules (you should now be on the third line in the history stack) > > - click again on "compress history stack". > > You should now have no instances of profiled denoise in your stack. > > > > And, are all your old edits affected, or only those you edited with the > > faulty > > dt version? > > > > Remco > > > > > > ____________________________________________________________________________ > > darktable user mailing list > > to unsubscribe send a mail to [email protected] > >
then you now have discerned a method to identify which photos you need to attend, those with two profiled denoise entries in the xmp, and by the module order iirc your previous comments which oddly I do not see quoted. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
