Hi Jean-Jacques,

I realized after I made the changes to gimp.lua that you could run any
external executable with it.  I see that you figured it out too  :-D.

The way the exporter works is to take the raw, apply any changes you made,
convert it to the file format you requested, and then store it wherever
darktable.configuration.tmp_dir points to.  That's where the exporter
scripts like gimp.lua pick up the files for processing and store their
results.  The results are then picked up and imported back into the film
roll.

This is another reason I'm working on DTPlugin.  Sometimes you need to pass
files without exporting them.

Having said all this, I know an ugly but effective way to accomplish this.
The exporter supplies an image table that contains the raw filename and the
exported filename as pairs.  We could delete the exported image, so we
don't clutter up the file system, and use the raw filename to build the
image list.  After the program exits, a dt.database.import(<name of
directory>) should show the result grouped with the raw.  If you're
importing jpegs as the result, make sure you didn't check "Ignore JPEG
images when importing film rolls" in the darktable configuration.  There
are other, cleaner, ways to do this such as using a shortcut, but the
problem is specifying the executable without having to edit the darktablerc
file by hand.

Another option for denoising would be to send a 16 bit tiff to dfine 2,
then edit the resulting tiff.

I'll see what I can do....    :-D


Bill


On Thu, Mar 8, 2018 at 11:48 AM, Jean-Jacques MONOT <
[email protected]> wrote:

> What I would like to have  :
>
> - use DT for cataloguing
> - "export" to PL in a raw format : PL will not care of the xml sidecar
> files (it has its own .dop sidecar files)
> - process in PM the raw file
> - generate a finalized jpg image with PL in the same folder as the original
> - tell DT to resynchronize the folder to see that new Dxo generated jpg
> file
>
>
>
>
> Le 8 mars 2018 17:19, "Patrick Shanahan" <[email protected]> a écrit :
>
> * Jean-Jacques MONOT <[email protected]> [03-08-18 10:47]:
> > Hello William
> >
> > I have just realized that you have made a major and great evolution to
> the
> > gimp.lua script.
>
>  [...]
>
> > The trouble that I see :
> > - the new file can not be a raw file (.NEF as Nikon), as I want the
> process
> > in PL done on raw files ...
> > - if I choose .jpg : OK PL can open it
> > - if I choose .png : PL can not open it
> > plus :
> > - if, in PL, I record a new copy of the image after processing : for
> > example, I got a .nef and I want to produce the final .jpg image, how
> can I
> > tell DT to refresh or resynchronize the folder to see the new file
> > generated by PL.
>
> the raw file, in your case, .NEF, is not altered by dt, only the sidecar
> file contains the changes, .xmp.  dt *never* alters your original raw
> file.  I believe you are wanting a scenario that is not possible, unless
> all involved software can read, write and utilize the same xmp files.  at
> present, iiuc, you can only pass exported files which will not be raw.
>
>  [...]
>
> --
> (paka)Patrick Shanahan       Plainfield, Indiana, USA          @ptilopteri
> http://en.opensuse.org    openSUSE Community Member    facebook/ptilopteri
> Registered Linux User #207535                    @ http://linuxcounter.net
> Photos: http://wahoo.no-ip.org/piwigo               paka @ IRCnet freenode
> ____________________________________________________________
> ________________
> darktable user mailing list
> to unsubscribe send a mail to darktable-user+unsubscribe@lis
> ts.darktable.org
>
>
>
> ____________________________________________________________________________
> darktable user mailing list to unsubscribe send a mail to
> [email protected]
>

____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]

Reply via email to