Ok, I have had a bit more success proceeding VERY cautiously this afternoon.
Obviously as I get into editing, i forget to look at the History stack with Every Step i take, however I can definitely say I saw one instance of switching Filmic RGB on & 2 references immediately appearing in the history (I consolidated immediately to eliminate) & another instance where Colour Balance was behaving weirdly (excessive effect), so I looked at the history & 2 consecutive instances were there also, which i immediately consolidated, & that clarified the edit. I can't say with 100% certainty however that those 2 'history instances' were immediately instantiated on activating the module. So I do think there is some sort of issue, & the best i can narrow it down to is that, whatever the condition of its appearance, it involves the addition of activated modules to the history stack, & is occasional. Other weird behavoiur i have witnessed is probably cumulative from the instantiation in history error, resulting in logic errors with True / False toggle status or similar ? Perhaps whatever 'tests' are run on ensuring robustness on additions to the history stack on activation could at least be run to confirm desired behaviour? Or perhaps something specific to the OSX build has inadvertently regressed? (sounds like i know what i'm talking about, not really, but i've done a little bit of hobby coding in Python mainly. Engineering dropout ...) Whatever is happening, it certainly isn't screaming 'robust' at me ... whatever failings i may have as a user ... On Tue, May 26, 2020 at 6:53 PM Remco Viëtor <remco.vie...@wanadoo.fr> wrote: > On mardi 26 mai 2020 10:01:19 CEST Tim Mortimer wrote: > > Thanks Remco. > > > > I appreciate the points you are making, however i think there is more to > > the issue than this. > > > > I didn't experience these issues when i toyed with Darktable last year in > > V2, not did i experience the issues when i initially installed V3 & > played > > with the more 'familiar' editing strategy of using Tone Curve, Colour > Zones > > etc, & flicking back & forward in the history to assess the progress of > my > > edits. After all, what else would the history be designed to do? > > > > I'll certainly use 'snapshots' going forward, but i think there is an > issue > > here. Going 'back' in the history for example occasionally drops > everything > > subsequent / above in the stack simply by making the selection, without > > subsequent editing. > > > > Similarly, occasionally the effect of Filmic RGB seems to 'duplicate' or > > compound spontaneously on the image for no reason, & this happens > > concurrent with multiple instances appearing in the history. > > > > Often multiple instances of Filmic RGB spontaneously appear in the > history > > with no logical correlation to any history compression action, or > > associated module usage. > > > > I can only describe the overall effect as 'chaotic', whereas the scenario > > you describe is logical & predictable. > > > > So I do feel like there is a bona-fide issue here. I'll continue to play > > with it, & report additional symptoms or behaviour i see as problematic, > > but there appears to be no effective diagnosis tool i can export or > provide > > by way of 'history' that leads to the problem, as the 'history' itself > > appears to be either part of the problem, or disconnected from the > reality > > of the user intention or command sequence at some stage. > > > > Something else I noticed: sometimes when I start editing basecurve and > sharpen > are auto-applied, sometimes they aren't (there seems to be a pattern, but > I > haven't quite nailed it down). In such cases, using filmicRGB becomes > "strange". And I did specirfically set dt *not* to auto-apply the > basecurve. > And I also use version 3.0.2. > > Remco > > > > > > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to > darktable-user+unsubscr...@lists.darktable.org > > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
