Thank Stefan, William, If I found the time, I'll work on Stefan script to be able to manage variables in destination path (like in the William's script) and this, by images (if all exported images don't have the same values regarded variables used). For sure, I'll inform you in this case.
Regards, Fabrice. On 28/01/2020 19:12, dt-l...@stefan-klinger.de 'dt-l...@stefan-klinger.de' wrote: > This email was sent to darktable...@ebaf.me from dt-l...@stefan-klinger.de > and has been forwarded by AnonAddy. > To deactivate this alias copy and paste the url below into your web browser. > > https://app.anonaddy.com/deactivate/30ba5977-f685-4c92-80ef-e2501b81990f?signature=8f457fd9649237ba928cb63d44097f0afdea1d00bf6b9c91b49f43bc2d108bf4 > > ----- > > > darktable...@ebaf.me (2020-Jan-27, excerpt): >> Maybe it's possible by creating a new storage. In this case, what is >> the widget object to be able to use variables (like in directory and >> filename field in the "file on disk" storage). > That's exactly what I did [1] in order to post-process some images. > >> My first use case is to include an exiftool in my workflow. Exiftool is an >> image to image command. > We, I've used `exiv2` the other EXIF tool, but for no particular > reason. > > I've put a lot of comments and links to documentation in there... > > HTH > Stefan > > ____________________ > [1]: https://github.com/s5k6/dtscripts/ > > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
