hi, these parameters are unfortunately not very easy to interface with. these are straight binary dumps of the history params structs you'll find in the source code of the respective modules (see for instance for exposure: https://github.com/darktable-org/darktable/blob/master/src/iop/exposure.c#L65). there is, however, an introspection api that allows you to walk these parameters if you prefer that: https://github.com/darktable-org/darktable/blob/master/src/common/introspection.h
for simple cases in the past i used to store a full history stack as xmp/dtstyle file and just inserted the extra parameters where needed, see https://github.com/darktable-org/darktable/blob/master/src/chart/main.c#L556 of course that would depend on your use case. and yes, as patrick said.. you might have a chance finding me or tobias (author of the introspection system) on irc. cheers, jo On Mon, May 6, 2019 at 12:22 AM Gunther Wegner <gwegner...@gmail.com> wrote: > > Hi Jochen, > yes, I've also found out that some (longer) parameters are compressed via > gzip, and before encoded via base64. After decoding we end up with a hex > string. But what's inside the hex string should be documented somewhere. I > hope to get some insights from the developers here. > > Greetings, > Gunther > > ___________________________________________________________________________ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
