paka
a simple solution to your needs w/o requiring any development work on darktable would be to run darktable as: darktable --library :memory: this way no entries in your ~/.config/darktable/library.db (or...
> While the comments remove the library management on the darktable side but still leaves export and import into photos. > using "--library :memory:" there is no "import into photos"...
* Paolo Benvenuto ***@***.***> [09-23-24 20:30]: > ### Describe the bug > > In filmic RGB module, when I click the dropper for auto tune levels, an area is presente...
* Jakub T. Jankiewicz ***@***.***> [09-22-25 12:22]: > jcubic left a comment (darktable-org/darktable#19398) > > Let me be clear, becausae it seems to be misunderstanding. > > The duplication happens...
* Jakub T. Jankiewicz ***@***.***> [09-22-25 13:25]: > jcubic left a comment (darktable-org/darktable#19398) > > @wpferguson Exactly. > > @ptilopteri I'm not talking about deleting by clicking the history item,...
* Jakub T. Jankiewicz ***@***.***> [09-22-25 14:27]: > jcubic left a comment (darktable-org/darktable#19398) > > Oh, didn't know there is a CTRL+Z shortcut. But it doesn't work, maybe because I'm...
* nicor2012 ***@***.***> [10-05-25 12:43]: > nicor2012 left a comment (darktable-org/darktable#19398) > > Finally found a perfect answer : > - click the history step you want > - take...
or you could make sure your "NAS" has the same address on all your work stations, then each of your photos would have the same latest, unique xmp
if you have configured xmp updates while working photo and your photos are on a "NAS", the xmp files on the "NAS" are *current*. if you locally copy the files...
put the db on the "NAS"