Re: [darktable-user] Keeping DT in sync between multiple computers
* Juha Lintula [04-09-19 15:37]: > Hi, > > I tested more and found an interesting detail. If I work only in Ubuntu, > everything works fine like Patrick described, but in Windows it doesn't > work. The additional xmp files are named differently in Windows and Linux. > In Windows it is image.raw_01.xmp and in Linux image_01.raw.xmp. Linux will > recognize the additional Linux style xmps, but not the Windows style. > Windows doesn't recognize either. > > -Juha > > On Tue, 9 Apr 2019 at 22:24, Juha Lintula wrote: > > > HI Patrick > > > > I tested to start darktable from command line with darktable --library > > :memory: and had the same result as when using database=:memory: in > > darktablerc. darktable shows only the primary edit image.raw.xmp, not the > > other version image.raw_01.xmp. I have tested darktablerc settings both > > in Windows 10 and Ubuntu and the command line in Windows. > > > > -Juha > > > > On Mon, 8 Apr 2019 at 11:05, Bernhard > > wrote: > > > >> > >> > >> Patrick Shanahan schrieb am 07.04.19 um 22:36: > >> > all three edits of the single image are there > >> > > >> > running dt master git901.e2188ea4b > >> > openSUSE Tumbleweed 20190403 > >> > images: > >> >181213_133958_aaa_2622.nef > >> >181213_122731_aaa_2621.nef.xmp > >> >181213_133958_aaa_2622_01.nef.xmp > >> >181213_133958_aaa_2622_02.nef.xmp > >> I wonder why the xmp has a different filename from the nef ... > >> (the duplicates seem to be correct) > >> > >> -- > >> > >> regards > >> Bernhard > >> > >> https://www.bilddateien.de > >> > >> > >> > >> darktable user mailing list > >> to unsubscribe send a mail to > >> darktable-user+unsubscr...@lists.darktable.org > >> > >> don't know about dt on windows. never ran it there so haven't shared files either. but I do know it is possible to share on linux as previously described. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/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+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
Hi, I tested more and found an interesting detail. If I work only in Ubuntu, everything works fine like Patrick described, but in Windows it doesn't work. The additional xmp files are named differently in Windows and Linux. In Windows it is image.raw_01.xmp and in Linux image_01.raw.xmp. Linux will recognize the additional Linux style xmps, but not the Windows style. Windows doesn't recognize either. -Juha On Tue, 9 Apr 2019 at 22:24, Juha Lintula wrote: > HI Patrick > > I tested to start darktable from command line with darktable --library > :memory: and had the same result as when using database=:memory: in > darktablerc. darktable shows only the primary edit image.raw.xmp, not the > other version image.raw_01.xmp. I have tested darktablerc settings both > in Windows 10 and Ubuntu and the command line in Windows. > > -Juha > > On Mon, 8 Apr 2019 at 11:05, Bernhard > wrote: > >> >> >> Patrick Shanahan schrieb am 07.04.19 um 22:36: >> > all three edits of the single image are there >> > >> > running dt master git901.e2188ea4b >> > openSUSE Tumbleweed 20190403 >> > images: >> >181213_133958_aaa_2622.nef >> >181213_122731_aaa_2621.nef.xmp >> >181213_133958_aaa_2622_01.nef.xmp >> >181213_133958_aaa_2622_02.nef.xmp >> I wonder why the xmp has a different filename from the nef ... >> (the duplicates seem to be correct) >> >> -- >> >> regards >> Bernhard >> >> https://www.bilddateien.de >> >> >> >> 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
Re: [darktable-user] Keeping DT in sync between multiple computers
HI Patrick I tested to start darktable from command line with darktable --library :memory: and had the same result as when using database=:memory: in darktablerc. darktable shows only the primary edit image.raw.xmp, not the other version image.raw_01.xmp. I have tested darktablerc settings both in Windows 10 and Ubuntu and the command line in Windows. -Juha On Mon, 8 Apr 2019 at 11:05, Bernhard wrote: > > > Patrick Shanahan schrieb am 07.04.19 um 22:36: > > all three edits of the single image are there > > > > running dt master git901.e2188ea4b > > openSUSE Tumbleweed 20190403 > > images: > >181213_133958_aaa_2622.nef > >181213_122731_aaa_2621.nef.xmp > >181213_133958_aaa_2622_01.nef.xmp > >181213_133958_aaa_2622_02.nef.xmp > I wonder why the xmp has a different filename from the nef ... > (the duplicates seem to be correct) > > -- > > regards > Bernhard > > https://www.bilddateien.de > > > > 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
Re: [darktable-user] Keeping DT in sync between multiple computers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Just another update on my situation, perhaps it's less than elegant, but when it comes to making money elegance doesn't matter too much. I've no got an alias set up in .bashrc: alias covdt='darktable . --library ./xmp/dtlibrary.db' (My workflow is to create the subfolders ./tiff ./jpg ./xmp when working on a folder of RAW files.) I'll use that to launch darktable, which will store a library file for each folder / project I work on directly in the project folder on the hard drive that I carry between computers. I've tested this, and it does handle the multiple versions I was having issues with perviously. Not the cleanest solution, having library files all over the place, but it will work and I don't need to worry about syncing or corrupting a database if I screw up and open it in two locations at once (if I were to store it on a server). Feel free to continue discussion, seeing what everyone's been coming up with has been interesting and enlightening. Thanks. -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhkixT3jIQEc/6oPNrPMsHVqrCxkFAlyrQ2AACgkQrPMsHVqr CxmdlwgAxsdd+NaM1x97pce7YE87/2aNZRiMvOmTcuggK2o4a3EoSxaRs+JmWudC OPXUVClHfJLZif2a4wjvEJXYph2tFi/c1lfgTMdKBKCHQnTWIbHrwdDqqscu61GM zjTQUSkRKBFjam/iIrgYjmUiV4UE/5aqUwpQfbnIgiwEVdOyj/UJUGcrvJ/QZWGO t8Q9GeGHPcH8QB2y/SBtfXlDUhFWVs00KWwHmTFUYlnZ+XyITXAtAsnItcGsRO7X wNEHg+a11DRpPrVxWF2wxPxjGZcoetrr+Z6B12OCX2UcNROVnfOxxCtmS15DtMAR hTeBcZmSetD/G4pZIAk6JJpxKvc1lQ== =M4oU -END PGP SIGNATURE- darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
Hi Benjamin, Jochen Keil, i use 2 scripts under Ubuntu 16.04 to keep 2 machines in sync - change my username to your username in pathnames: backup: #!/bin/bash # rsync all files form local disk with digital photos to backup-disk (USB or network) # set base path of the digi base dir directory DIGIDIR=/media/hb/spinning/digi DARKDIR=/home/hb/.config/darktable CACHEDIR=/home/hb/.cache/darktable # set base path of external USB disk BACKUPDIR=/media/hb/hbeasydock # set options SYNCOPTIONS="-aihP --delete --stats " # rsnc different folders # digi raws rsync $SYNCOPTIONS $DIGIDIR $BACKUPDIR/ # darktable database rsync $SYNCOPTIONS $DARKDIR $BACKUPDIR/darkdb # darktable cache rsync $SYNCOPTIONS $CACHEDIR $BACKUPDIR/darkcache read -p "press return" --- - save as backup.sh and set to permissions to 'allow executing file as executable' --- restore: --- #!/bin/bash # rsync all files form backup to local disk with digital photos # set base path of the digi base dir directory DIGIDIR=/media/hb/hbdock/digi DARKDIR=/home/hb/.config DARKBAK=/media/hb/hbdock/darkdb/darktable # set base path of local drive disk BACKUPDIR=/media/hb/spinning # set options SYNCOPTIONS="-aihP --delete --stats " # rsnc different folders # digi raws rsync $SYNCOPTIONS $DIGIDIR $BACKUPDIR # darktable database rsync $SYNCOPTIONS $DARKBAK $DARKDIR #darktable-generate-cache read -p "press return" --- - save as restore.sh and set to permissions to 'allow executing file as executable' --- Kinbd regards, __horst > Hi Benjamin, > > I just wanted to add another possibility: git annex. > > I use it (successfully) for keeping my RAWs, the XMPs and the db in > sync. Either over network or an external USB hard drive. Once it's set > up, it's a simple matter of `git annex sync --all` and / or the usual > git operations. And you can add additional backup locations easily. > > Cheers! > > On Tue, Apr 2, 2019 at 12:43 AM Benjamin Daines > wrote: >> In my workflow I find myself using multiple machines to work on the same >> images. My configuration right now on both machines is to have DT look for >> updated xmp files on start up and that seems to work pretty well. I usually >> just ignore the window that pops up to tell me about newer xmp files, unless >> the ones that I'm about to work on are listed, then I select those and let >> it update the database. >> >> However, there have been some situations where my previous work has been >> wiped out when opening a folder on another machine. Because of this, I now >> habitually copy all my xmp files to a subfolder after working on them in >> order to keep a back up, just in case. Occasionally I need to manually load >> these sidecar files. >> >> Would an option to disable darktable's database and use just the xmp files >> be a feasible option? How about using something like syncthing (Linux >> platform here) to keep the database synced between multiple machines? Would >> doing that cause any foreseeable issues? >> >> How are other people dealing with using multiple machines to work on >> projects, any tips? >> >> Thanks. > > darktable user mailing list > to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org > -- ec-logic GmbH h...@ec-logic.com www.ec-logic.com Theresienstraße 12 90762 Fürth, germany ++49 911 9711910 darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
* Bernhard [04-08-19 04:06]: > > > Patrick Shanahan schrieb am 07.04.19 um 22:36: > > all three edits of the single image are there > > > > running dt master git901.e2188ea4b > > openSUSE Tumbleweed 20190403 > > images: > >181213_133958_aaa_2622.nef > >181213_122731_aaa_2621.nef.xmp > >181213_133958_aaa_2622_01.nef.xmp > >181213_133958_aaa_2622_02.nef.xmp > I wonder why the xmp has a different filename from the nef ... > (the duplicates seem to be correct) undoubtedly I mis-copied. I definitely shouild not, 181213_133958_aaa_2622.nef 181213_122731_aaa_2622.nef.xmp 181213_133958_aaa_2622_01.nef.xmp 181213_133958_aaa_2622_02.nef.xmp is correct. blame it on brown bottles :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/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+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
Hi Benjamin, I just wanted to add another possibility: git annex. I use it (successfully) for keeping my RAWs, the XMPs and the db in sync. Either over network or an external USB hard drive. Once it's set up, it's a simple matter of `git annex sync --all` and / or the usual git operations. And you can add additional backup locations easily. Cheers! On Tue, Apr 2, 2019 at 12:43 AM Benjamin Daines wrote: > > In my workflow I find myself using multiple machines to work on the same > images. My configuration right now on both machines is to have DT look for > updated xmp files on start up and that seems to work pretty well. I usually > just ignore the window that pops up to tell me about newer xmp files, unless > the ones that I'm about to work on are listed, then I select those and let it > update the database. > > However, there have been some situations where my previous work has been > wiped out when opening a folder on another machine. Because of this, I now > habitually copy all my xmp files to a subfolder after working on them in > order to keep a back up, just in case. Occasionally I need to manually load > these sidecar files. > > Would an option to disable darktable's database and use just the xmp files be > a feasible option? How about using something like syncthing (Linux platform > here) to keep the database synced between multiple machines? Would doing that > cause any foreseeable issues? > > How are other people dealing with using multiple machines to work on > projects, any tips? > > Thanks. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
Patrick Shanahan schrieb am 07.04.19 um 22:36: all three edits of the single image are there running dt master git901.e2188ea4b openSUSE Tumbleweed 20190403 images: 181213_133958_aaa_2622.nef 181213_122731_aaa_2621.nef.xmp 181213_133958_aaa_2622_01.nef.xmp 181213_133958_aaa_2622_02.nef.xmp I wonder why the xmp has a different filename from the nef ... (the duplicates seem to be correct) -- regards Bernhard https://www.bilddateien.de darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
* Benjamin Daines [04-07-19 18:24]: > Try changing database=:memory: in your darktablerc file and see if that > changes the behavior? It seem that in theory launching with --library > :memory: should do the same thing, but perhaps it does not. > On Sun, 2019-04-07 at 16:36 -0400, Patrick Shanahan wrote: > > * Benjamin Daines [04-07-19 13:56]: > > > Don't get hung up on the example file names I used in the > > > email. Theissue that I'm having is with the database "disabled" > > > darktable doesnot recognize additional versions of images that are > > > created (viaclicking duplicate in darktable, which creates a second > > > xmp file forthe image). What's worse is when you open the folder > > > in darktableafter closing it, not only is the version you've > > > created gone, but ifyou create the second version again DT > > > immediately overwrites thesecond xmp file. Hopefully that makes > > > more sense. On Sun, 2019-04-07 at 11:50 -0400, Patrick Shanahan > > > wrote: > > > > * Benjamin Daines [04-07-19 11:04]: > > > > > Importing the folder doesn't recognize versions > > > > > eitherunfortunately. On Sat, 2019-04-06 at 13:54 -0400, Patrick > > > > > Shanahanwrote: > > > > > > * Benjamin Daines [04-06-19 > > > > > > 12:51]: > > > > > > > The issue I'm running into now, with database=:memory: is > > > > > > > thatifI'veduplicated an image so that I've got two xmp > > > > > > > files forthe sameimage(say IMG1.xmp and IMG1_01.xmp), when > > > > > > > I close thefolder andopen itagain, DT only reads the > > > > > > > initial image, notthe secondversion. If Ithen create a new > > > > > > > version, DTimmediately overwritesIMG1_01.xmp, sounless I've > > > > > > > copied all myxmp files to asubdirectory, that work > > > > > > > islost. It would be bestto have darktableautomatically > > > > > > > create these versionswhen seeingIMG_01.xmp.Hopefully that > > > > > > > makes sense. On Tue, 2019-04-02 at07:20 +0300, JuhaLintula > > > > > > > wrote: > > > > > > > > Hi!I also use darktable only for image processing and > > > > > > > > havethesamesetting as Robert; database=:memory: This > > > > > > > > settingwillalwaysautomatically read the .xmp files as you > > > > > > > > arealwaysstarting with afresh database.-JuhaOn Tue, 2 Apr > > > > > > > > 2019at 05:20, Patrick Shanahan wrote: > > > > > > > > > * I. Ivanov [04-01-19 20:03]: > > > > > > > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > > > > > > > > > * Benjamin Daines > > > > > > > > > > > [04-01-19 > > > > > > > > > 18:46]: > > > > > > > > > > > > In my workflow I find myself using multiple > > > > > > > > > > > > machinestowork > > > > > > > > > on the > > > > > > > > > > > > same images. My configuration right now on > > > > > > > > > > > > bothmachinesis > > > > > > > > > to have DT > > > > > > > > > > > > look for updated xmp files on start up and that > > > > > > > > > > > > seemstowork > > > > > > > > > pretty > > > > > > > > > > > > well. I usually just ignore the window that pops > > > > > > > > > > > > uptotell > > > > > > > > > me about > > > > > > > > > > > > newer xmp files, unless the ones that I'm about > > > > > > > > > > > > toworkon > > > > > > > > > are listed, > > > > > > > > > > > > then I select those and let it update > > > > > > > > > > > > thedatabase.However, there have been some > > > > > > > > > > > > situationswhere myprevious > > > > > > > > > work has > > > > > > > > > > > > been wiped out when opening a folder on > > > > > > > > > > > > anothermachine. > > > > > > > > > Because of > > > > > > > > > > > > this, I now habitually copy all my xmp files > > > > > > > > > > > > toasubfolder > > > > > > > > > after > > > > > > > > > > > > working on them in order to keep a back up, > > > > > > > > > > > > justincase. > > > > > > > > > Occasionally > > > > > > > > > > > > I need to manually load these sidecar files.Would > > > > > > > > > > > > anoption to disable darktable's database and > > > > > > > > > > > > usejust > > > > > > > > > the xmp > > > > > > > > > > > > files be a feasible option? How about > > > > > > > > > > > > usingsomethinglike > > > > > > > > > syncthing > > > > > > > > > > > > (Linux platform here) to keep the database > > > > > > > > > > > > syncedbetween > > > > > > > > > multiple > > > > > > > > > > > > machines? Would doing that cause any > > > > > > > > > > > > foreseeableissues?How are other people dealing > > > > > > > > > > > > with usingmultiple machinesto > > > > > > > > > work onprojects, any tips? > > > > > > > > > > > when I use any machine beside my main workstation > > > > > > > > > > > toedit > > > > > > > > > photos, I issue > > > > > > > > > > > darktable as: darktable --library > > > > > > > > > > > :memory: importthe photos to be edited finish > > > > > > > > > > > the edits closedtand back at my workstation, re- > > > > > > > > > > > import the editedphotoswith > > > > > > > > > their > > > > > > > > > > > accompanying xmp files.have not encountered > > > > >
Re: [darktable-user] Keeping DT in sync between multiple computers
Try changing database=:memory: in your darktablerc file and see if that changes the behavior? It seem that in theory launching with --library :memory: should do the same thing, but perhaps it does not. On Sun, 2019-04-07 at 16:36 -0400, Patrick Shanahan wrote: > * Benjamin Daines [04-07-19 13:56]: > > Don't get hung up on the example file names I used in the > > email. Theissue that I'm having is with the database "disabled" > > darktable doesnot recognize additional versions of images that are > > created (viaclicking duplicate in darktable, which creates a second > > xmp file forthe image). What's worse is when you open the folder > > in darktableafter closing it, not only is the version you've > > created gone, but ifyou create the second version again DT > > immediately overwrites thesecond xmp file. Hopefully that makes > > more sense. On Sun, 2019-04-07 at 11:50 -0400, Patrick Shanahan > > wrote: > > > * Benjamin Daines [04-07-19 11:04]: > > > > Importing the folder doesn't recognize versions > > > > eitherunfortunately. On Sat, 2019-04-06 at 13:54 -0400, Patrick > > > > Shanahanwrote: > > > > > * Benjamin Daines [04-06-19 > > > > > 12:51]: > > > > > > The issue I'm running into now, with database=:memory: is > > > > > > thatifI'veduplicated an image so that I've got two xmp > > > > > > files forthe sameimage(say IMG1.xmp and IMG1_01.xmp), when > > > > > > I close thefolder andopen itagain, DT only reads the > > > > > > initial image, notthe secondversion. If Ithen create a new > > > > > > version, DTimmediately overwritesIMG1_01.xmp, sounless I've > > > > > > copied all myxmp files to asubdirectory, that work > > > > > > islost. It would be bestto have darktableautomatically > > > > > > create these versionswhen seeingIMG_01.xmp.Hopefully that > > > > > > makes sense. On Tue, 2019-04-02 at07:20 +0300, JuhaLintula > > > > > > wrote: > > > > > > > Hi!I also use darktable only for image processing and > > > > > > > havethesamesetting as Robert; database=:memory: This > > > > > > > settingwillalwaysautomatically read the .xmp files as you > > > > > > > arealwaysstarting with afresh database.-JuhaOn Tue, 2 Apr > > > > > > > 2019at 05:20, Patrick Shanahan wrote: > > > > > > > > * I. Ivanov [04-01-19 20:03]: > > > > > > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > > > > > > > > * Benjamin Daines > > > > > > > > > > [04-01-19 > > > > > > > > 18:46]: > > > > > > > > > > > In my workflow I find myself using multiple > > > > > > > > > > > machinestowork > > > > > > > > on the > > > > > > > > > > > same images. My configuration right now on > > > > > > > > > > > bothmachinesis > > > > > > > > to have DT > > > > > > > > > > > look for updated xmp files on start up and that > > > > > > > > > > > seemstowork > > > > > > > > pretty > > > > > > > > > > > well. I usually just ignore the window that pops > > > > > > > > > > > uptotell > > > > > > > > me about > > > > > > > > > > > newer xmp files, unless the ones that I'm about > > > > > > > > > > > toworkon > > > > > > > > are listed, > > > > > > > > > > > then I select those and let it update > > > > > > > > > > > thedatabase.However, there have been some > > > > > > > > > > > situationswhere myprevious > > > > > > > > work has > > > > > > > > > > > been wiped out when opening a folder on > > > > > > > > > > > anothermachine. > > > > > > > > Because of > > > > > > > > > > > this, I now habitually copy all my xmp files > > > > > > > > > > > toasubfolder > > > > > > > > after > > > > > > > > > > > working on them in order to keep a back up, > > > > > > > > > > > justincase. > > > > > > > > Occasionally > > > > > > > > > > > I need to manually load these sidecar files.Would > > > > > > > > > > > anoption to disable darktable's database and > > > > > > > > > > > usejust > > > > > > > > the xmp > > > > > > > > > > > files be a feasible option? How about > > > > > > > > > > > usingsomethinglike > > > > > > > > syncthing > > > > > > > > > > > (Linux platform here) to keep the database > > > > > > > > > > > syncedbetween > > > > > > > > multiple > > > > > > > > > > > machines? Would doing that cause any > > > > > > > > > > > foreseeableissues?How are other people dealing > > > > > > > > > > > with usingmultiple machinesto > > > > > > > > work onprojects, any tips? > > > > > > > > > > when I use any machine beside my main workstation > > > > > > > > > > toedit > > > > > > > > photos, I issue > > > > > > > > > > darktable as: darktable --library > > > > > > > > > > :memory: importthe photos to be edited finish > > > > > > > > > > the edits closedtand back at my workstation, re- > > > > > > > > > > import the editedphotoswith > > > > > > > > their > > > > > > > > > > accompanying xmp files.have not encountered > > > > > > > > > > anyproblems with this work plan. > > > > > > > > > In theory... if you have 2 identical machines > > > > > > > > > (forexamplelinux)shared network location for DT > > > > > > > > > filessharednetwork location for
Re: [darktable-user] Keeping DT in sync between multiple computers
* Patrick Shanahan [04-07-19 16:42]: > * Benjamin Daines [04-07-19 13:56]: > > Don't get hung up on the example file names I used in the email. The > > issue that I'm having is with the database "disabled" darktable does > > not recognize additional versions of images that are created (via > > clicking duplicate in darktable, which creates a second xmp file for > > the image). What's worse is when you open the folder in darktable > > after closing it, not only is the version you've created gone, but if > > you create the second version again DT immediately overwrites the > > second xmp file. > > Hopefully that makes more sense. > > On Sun, 2019-04-07 at 11:50 -0400, Patrick Shanahan wrote: > > > * Benjamin Daines [04-07-19 11:04]: > > > > Importing the folder doesn't recognize versions either > > > > unfortunately. On Sat, 2019-04-06 at 13:54 -0400, Patrick Shanahan > > > > wrote: > > > > > * Benjamin Daines [04-06-19 12:51]: > > > > > > The issue I'm running into now, with database=:memory: is that > > > > > > ifI'veduplicated an image so that I've got two xmp files for > > > > > > the sameimage(say IMG1.xmp and IMG1_01.xmp), when I close the > > > > > > folder andopen itagain, DT only reads the initial image, not > > > > > > the secondversion. If Ithen create a new version, DT > > > > > > immediately overwritesIMG1_01.xmp, sounless I've copied all my > > > > > > xmp files to asubdirectory, that work islost. It would be best > > > > > > to have darktableautomatically create these versionswhen seeing > > > > > > IMG_01.xmp.Hopefully that makes sense. On Tue, 2019-04-02 at > > > > > > 07:20 +0300, JuhaLintula wrote: > > > > > > > Hi!I also use darktable only for image processing and have > > > > > > > thesamesetting as Robert; database=:memory: This setting > > > > > > > willalwaysautomatically read the .xmp files as you are > > > > > > > alwaysstarting with afresh database.-JuhaOn Tue, 2 Apr 2019 > > > > > > > at 05:20, Patrick Shanahan wrote: > > > > > > > > * I. Ivanov [04-01-19 20:03]: > > > > > > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > > > > > > > > * Benjamin Daines [04-01- > > > > > > > > > > 19 > > > > > > > > 18:46]: > > > > > > > > > > > In my workflow I find myself using multiple machines > > > > > > > > > > > towork > > > > > > > > on the > > > > > > > > > > > same images. My configuration right now on both > > > > > > > > > > > machinesis > > > > > > > > to have DT > > > > > > > > > > > look for updated xmp files on start up and that seems > > > > > > > > > > > towork > > > > > > > > pretty > > > > > > > > > > > well. I usually just ignore the window that pops up > > > > > > > > > > > totell > > > > > > > > me about > > > > > > > > > > > newer xmp files, unless the ones that I'm about to > > > > > > > > > > > workon > > > > > > > > are listed, > > > > > > > > > > > then I select those and let it update the > > > > > > > > > > > database.However, there have been some situations > > > > > > > > > > > where myprevious > > > > > > > > work has > > > > > > > > > > > been wiped out when opening a folder on another > > > > > > > > > > > machine. > > > > > > > > Because of > > > > > > > > > > > this, I now habitually copy all my xmp files to > > > > > > > > > > > asubfolder > > > > > > > > after > > > > > > > > > > > working on them in order to keep a back up, just > > > > > > > > > > > incase. > > > > > > > > Occasionally > > > > > > > > > > > I need to manually load these sidecar files.Would an > > > > > > > > > > > option to disable darktable's database and usejust > > > > > > > > the xmp > > > > > > > > > > > files be a feasible option? How about using > > > > > > > > > > > somethinglike > > > > > > > > syncthing > > > > > > > > > > > (Linux platform here) to keep the database synced > > > > > > > > > > > between > > > > > > > > multiple > > > > > > > > > > > machines? Would doing that cause any foreseeable > > > > > > > > > > > issues?How are other people dealing with using > > > > > > > > > > > multiple machinesto > > > > > > > > work onprojects, any tips? > > > > > > > > > > when I use any machine beside my main workstation to > > > > > > > > > > edit > > > > > > > > photos, I issue > > > > > > > > > > darktable as: darktable --library :memory: import > > > > > > > > > > the photos to be edited finish the edits close > > > > > > > > > > dtand back at my workstation, re-import the edited > > > > > > > > > > photoswith > > > > > > > > their > > > > > > > > > > accompanying xmp files.have not encountered any > > > > > > > > > > problems with this work plan. > > > > > > > > > In theory... if you have 2 identical machines (for > > > > > > > > > examplelinux)shared network location for DT filesshared > > > > > > > > > network location for the DB, configuration files > > > > > > > > > andcachesame mounting point for the 2 machinesyou could > > > > > > > > > use DT on one or the other (one at a time) and the > > > > > > > > changes should > > > > > > > > > be
Re: [darktable-user] Keeping DT in sync between multiple computers
* Juha Lintula [04-07-19 15:06]: > Hi! > > Yes, I've noticed the same thing. It would be nice, that when you import a > folder, darktable would recognize also the additional xmp files. > > -Juha > > On Sun, 7 Apr 2019 at 20:52, Benjamin Daines > wrote: > > > Don't get hung up on the example file names I used in the email. The issue > > that I'm having is with the database "disabled" darktable does not > > recognize additional versions of images that are created (via clicking > > duplicate in darktable, which creates a second xmp file for the image). > > What's worse is when you open the folder in darktable after closing it, not > > only is the version you've created gone, but if you create the second > > version again DT immediately overwrites the second xmp file. > > > > Hopefully that makes more sense. > > > > On Sun, 2019-04-07 at 11:50 -0400, Patrick Shanahan wrote: > > > > * Benjamin Daines < > > > > ben@digitalsand.photography > > > > > [04-07-19 11:04]: > > > > Importing the folder doesn't recognize versions either unfortunately. > > > > On Sat, 2019-04-06 at 13:54 -0400, Patrick Shanahan wrote: > > > > * Benjamin Daines < > > > > ben@digitalsand.photography > > > > > [04-06-19 12:51]: > > > > The issue I'm running into now, with database=:memory: is that if > > > > I'veduplicated an image so that I've got two xmp files for the same > > > > image(say IMG1.xmp and IMG1_01.xmp), when I close the folder and > > > > open itagain, DT only reads the initial image, not the second > > > > version. If Ithen create a new version, DT immediately overwrites > > > > IMG1_01.xmp, sounless I've copied all my xmp files to a > > > > subdirectory, that work islost. It would be best to have darktable > > > > automatically create these versionswhen seeing IMG_01.xmp. > > > > Hopefully that makes sense. On Tue, 2019-04-02 at 07:20 +0300, Juha > > > > Lintula wrote: > > > > Hi!I also use darktable only for image processing and have the > > > > samesetting as Robert; database=:memory: This setting will > > > > alwaysautomatically read the .xmp files as you are always > > > > starting with afresh database. > > > > -Juha > > > > On Tue, 2 Apr 2019 at 05:20, Patrick Shanahan < > > > > p...@opensuse.org > > > > > > > > > wrote: > > > > * I. Ivanov < > > > > iv3...@gmail.com > > > > > [04-01-19 20:03]: > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > > * Benjamin Daines < > > > > ben@digitalsand.photography > > > > > [04-01-19 > > > > 18:46]: > > > > In my workflow I find myself using multiple machines to > > > > work > > > > on the > > > > same images. My configuration right now on both machines > > > > is > > > > to have DT > > > > look for updated xmp files on start up and that seems to > > > > work > > > > pretty > > > > well. I usually just ignore the window that pops up to > > > > tell > > > > me about > > > > newer xmp files, unless the ones that I'm about to work > > > > on > > > > are listed, > > > > then I select those and let it update the database. > > > > However, there have been some situations where my > > > > previous > > > > work has > > > > been wiped out when opening a folder on another machine. > > > > Because of > > > > this, I now habitually copy all my xmp files to a > > > > subfolder > > > > after > > > > working on them in order to keep a back up, just in > > > > case. > > > > Occasionally > > > > I need to manually load these sidecar files. > > > > Would an option to disable darktable's database and use > > > > just > > > > the xmp > > > > files be a feasible option? How about using something > > > > like > > > > syncthing > > > > (Linux platform here) to keep the database synced between > > > > multiple > > > > machines? Would doing that cause any foreseeable issues? > > > > How are other people dealing with using multiple machines > > > > to > > > > work onprojects, any tips? > > > > when I use any machine beside my main workstation to edit > > > > photos, I issue > > > > darktable as: > > > >darktable --library :memory: > > > >import the photos to be edited > > > >finish the edits > > > >close dt > > > > and back at my workstation, re-import the edited photos > > > > with > > > > their > > > > accompanying xmp files. > > > > have not encountered any problems with this work plan. > > > > In theory... if you have 2 identical machines (for example > > > > linux) > > > > shared network location for DT files > > > > shared network location for the DB, configuration files and > > > > cache > > > > same mounting point for the 2 machines > > > > you could use DT on one or the other (one at a time) and the > > > > changes should > > > > be on the 2 machines. > > > > BUT... I haven't tested the scenario please back up if you > > > > want > > > > to try it. > > > > On the other hand - what Patrick is pointing to is based on > > > > experience. > > > > > > > > IF, IF, IF you NEVER run dt at the same time on different > > > > machines,one > > > > could share the db placing
Re: [darktable-user] Keeping DT in sync between multiple computers
* Benjamin Daines [04-07-19 13:56]: > Don't get hung up on the example file names I used in the email. The > issue that I'm having is with the database "disabled" darktable does > not recognize additional versions of images that are created (via > clicking duplicate in darktable, which creates a second xmp file for > the image). What's worse is when you open the folder in darktable > after closing it, not only is the version you've created gone, but if > you create the second version again DT immediately overwrites the > second xmp file. > Hopefully that makes more sense. > On Sun, 2019-04-07 at 11:50 -0400, Patrick Shanahan wrote: > > * Benjamin Daines [04-07-19 11:04]: > > > Importing the folder doesn't recognize versions either > > > unfortunately. On Sat, 2019-04-06 at 13:54 -0400, Patrick Shanahan > > > wrote: > > > > * Benjamin Daines [04-06-19 12:51]: > > > > > The issue I'm running into now, with database=:memory: is that > > > > > ifI'veduplicated an image so that I've got two xmp files for > > > > > the sameimage(say IMG1.xmp and IMG1_01.xmp), when I close the > > > > > folder andopen itagain, DT only reads the initial image, not > > > > > the secondversion. If Ithen create a new version, DT > > > > > immediately overwritesIMG1_01.xmp, sounless I've copied all my > > > > > xmp files to asubdirectory, that work islost. It would be best > > > > > to have darktableautomatically create these versionswhen seeing > > > > > IMG_01.xmp.Hopefully that makes sense. On Tue, 2019-04-02 at > > > > > 07:20 +0300, JuhaLintula wrote: > > > > > > Hi!I also use darktable only for image processing and have > > > > > > thesamesetting as Robert; database=:memory: This setting > > > > > > willalwaysautomatically read the .xmp files as you are > > > > > > alwaysstarting with afresh database.-JuhaOn Tue, 2 Apr 2019 > > > > > > at 05:20, Patrick Shanahan wrote: > > > > > > > * I. Ivanov [04-01-19 20:03]: > > > > > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > > > > > > > * Benjamin Daines [04-01- > > > > > > > > > 19 > > > > > > > 18:46]: > > > > > > > > > > In my workflow I find myself using multiple machines > > > > > > > > > > towork > > > > > > > on the > > > > > > > > > > same images. My configuration right now on both > > > > > > > > > > machinesis > > > > > > > to have DT > > > > > > > > > > look for updated xmp files on start up and that seems > > > > > > > > > > towork > > > > > > > pretty > > > > > > > > > > well. I usually just ignore the window that pops up > > > > > > > > > > totell > > > > > > > me about > > > > > > > > > > newer xmp files, unless the ones that I'm about to > > > > > > > > > > workon > > > > > > > are listed, > > > > > > > > > > then I select those and let it update the > > > > > > > > > > database.However, there have been some situations > > > > > > > > > > where myprevious > > > > > > > work has > > > > > > > > > > been wiped out when opening a folder on another > > > > > > > > > > machine. > > > > > > > Because of > > > > > > > > > > this, I now habitually copy all my xmp files to > > > > > > > > > > asubfolder > > > > > > > after > > > > > > > > > > working on them in order to keep a back up, just > > > > > > > > > > incase. > > > > > > > Occasionally > > > > > > > > > > I need to manually load these sidecar files.Would an > > > > > > > > > > option to disable darktable's database and usejust > > > > > > > the xmp > > > > > > > > > > files be a feasible option? How about using > > > > > > > > > > somethinglike > > > > > > > syncthing > > > > > > > > > > (Linux platform here) to keep the database synced > > > > > > > > > > between > > > > > > > multiple > > > > > > > > > > machines? Would doing that cause any foreseeable > > > > > > > > > > issues?How are other people dealing with using > > > > > > > > > > multiple machinesto > > > > > > > work onprojects, any tips? > > > > > > > > > when I use any machine beside my main workstation to > > > > > > > > > edit > > > > > > > photos, I issue > > > > > > > > > darktable as: darktable --library :memory: import > > > > > > > > > the photos to be edited finish the edits close > > > > > > > > > dtand back at my workstation, re-import the edited > > > > > > > > > photoswith > > > > > > > their > > > > > > > > > accompanying xmp files.have not encountered any > > > > > > > > > problems with this work plan. > > > > > > > > In theory... if you have 2 identical machines (for > > > > > > > > examplelinux)shared network location for DT filesshared > > > > > > > > network location for the DB, configuration files > > > > > > > > andcachesame mounting point for the 2 machinesyou could > > > > > > > > use DT on one or the other (one at a time) and the > > > > > > > changes should > > > > > > > > be on the 2 machines.BUT... I haven't tested the scenario > > > > > > > > please back up if youwant > > > > > > > to try it. > > > > > > > > On the other hand - what Patrick is pointing to is based > > > > > > > > on > > > > > >
Re: [darktable-user] Keeping DT in sync between multiple computers
Hi! Yes, I've noticed the same thing. It would be nice, that when you import a folder, darktable would recognize also the additional xmp files. -Juha On Sun, 7 Apr 2019 at 20:52, Benjamin Daines wrote: > Don't get hung up on the example file names I used in the email. The issue > that I'm having is with the database "disabled" darktable does not > recognize additional versions of images that are created (via clicking > duplicate in darktable, which creates a second xmp file for the image). > What's worse is when you open the folder in darktable after closing it, not > only is the version you've created gone, but if you create the second > version again DT immediately overwrites the second xmp file. > > Hopefully that makes more sense. > > On Sun, 2019-04-07 at 11:50 -0400, Patrick Shanahan wrote: > > * Benjamin Daines < > > ben@digitalsand.photography > > > [04-07-19 11:04]: > > Importing the folder doesn't recognize versions either unfortunately. > > On Sat, 2019-04-06 at 13:54 -0400, Patrick Shanahan wrote: > > * Benjamin Daines < > > ben@digitalsand.photography > > > [04-06-19 12:51]: > > The issue I'm running into now, with database=:memory: is that if > > I'veduplicated an image so that I've got two xmp files for the same > > image(say IMG1.xmp and IMG1_01.xmp), when I close the folder and > > open itagain, DT only reads the initial image, not the second > > version. If Ithen create a new version, DT immediately overwrites > > IMG1_01.xmp, sounless I've copied all my xmp files to a > > subdirectory, that work islost. It would be best to have darktable > > automatically create these versionswhen seeing IMG_01.xmp. > > Hopefully that makes sense. On Tue, 2019-04-02 at 07:20 +0300, Juha > > Lintula wrote: > > Hi!I also use darktable only for image processing and have the > > samesetting as Robert; database=:memory: This setting will > > alwaysautomatically read the .xmp files as you are always > > starting with afresh database. > > -Juha > > On Tue, 2 Apr 2019 at 05:20, Patrick Shanahan < > > p...@opensuse.org > > > > > wrote: > > * I. Ivanov < > > iv3...@gmail.com > > > [04-01-19 20:03]: > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > * Benjamin Daines < > > ben@digitalsand.photography > > > [04-01-19 > > 18:46]: > > In my workflow I find myself using multiple machines to > > work > > on the > > same images. My configuration right now on both machines > > is > > to have DT > > look for updated xmp files on start up and that seems to > > work > > pretty > > well. I usually just ignore the window that pops up to > > tell > > me about > > newer xmp files, unless the ones that I'm about to work > > on > > are listed, > > then I select those and let it update the database. > > However, there have been some situations where my > > previous > > work has > > been wiped out when opening a folder on another machine. > > Because of > > this, I now habitually copy all my xmp files to a > > subfolder > > after > > working on them in order to keep a back up, just in > > case. > > Occasionally > > I need to manually load these sidecar files. > > Would an option to disable darktable's database and use > > just > > the xmp > > files be a feasible option? How about using something > > like > > syncthing > > (Linux platform here) to keep the database synced between > > multiple > > machines? Would doing that cause any foreseeable issues? > > How are other people dealing with using multiple machines > > to > > work onprojects, any tips? > > when I use any machine beside my main workstation to edit > > photos, I issue > > darktable as: > >darktable --library :memory: > >import the photos to be edited > >finish the edits > >close dt > > and back at my workstation, re-import the edited photos > > with > > their > > accompanying xmp files. > > have not encountered any problems with this work plan. > > In theory... if you have 2 identical machines (for example > > linux) > > shared network location for DT files > > shared network location for the DB, configuration files and > > cache > > same mounting point for the 2 machines > > you could use DT on one or the other (one at a time) and the > > changes should > > be on the 2 machines. > > BUT... I haven't tested the scenario please back up if you > > want > > to try it. > > On the other hand - what Patrick is pointing to is based on > > experience. > > > > IF, IF, IF you NEVER run dt at the same time on different > > machines,one > > could share the db placing it on networked storage. BUT NEVER > > RUNDT ON > > TWO MACHINES AT THE SAME TIME. > > > > > Thanks. > > > try instead, to import the image instead of just reading the xmp > > file. Ihave not seen that happen to me and I do have duplicate > > images withdifferent crops. it appears your dup images are not being > > created withthe same filenames reflected by your oddly number xmp > > files. but ... > > > > > versions of what? > > > importing an image not in dt's db will utilize the acompa
Re: [darktable-user] Keeping DT in sync between multiple computers
Don't get hung up on the example file names I used in the email. The issue that I'm having is with the database "disabled" darktable does not recognize additional versions of images that are created (via clicking duplicate in darktable, which creates a second xmp file for the image). What's worse is when you open the folder in darktable after closing it, not only is the version you've created gone, but if you create the second version again DT immediately overwrites the second xmp file. Hopefully that makes more sense. On Sun, 2019-04-07 at 11:50 -0400, Patrick Shanahan wrote: > * Benjamin Daines [04-07-19 11:04]: > > Importing the folder doesn't recognize versions either > > unfortunately. On Sat, 2019-04-06 at 13:54 -0400, Patrick Shanahan > > wrote: > > > * Benjamin Daines [04-06-19 12:51]: > > > > The issue I'm running into now, with database=:memory: is that > > > > ifI'veduplicated an image so that I've got two xmp files for > > > > the sameimage(say IMG1.xmp and IMG1_01.xmp), when I close the > > > > folder andopen itagain, DT only reads the initial image, not > > > > the secondversion. If Ithen create a new version, DT > > > > immediately overwritesIMG1_01.xmp, sounless I've copied all my > > > > xmp files to asubdirectory, that work islost. It would be best > > > > to have darktableautomatically create these versionswhen seeing > > > > IMG_01.xmp.Hopefully that makes sense. On Tue, 2019-04-02 at > > > > 07:20 +0300, JuhaLintula wrote: > > > > > Hi!I also use darktable only for image processing and have > > > > > thesamesetting as Robert; database=:memory: This setting > > > > > willalwaysautomatically read the .xmp files as you are > > > > > alwaysstarting with afresh database.-JuhaOn Tue, 2 Apr 2019 > > > > > at 05:20, Patrick Shanahan wrote: > > > > > > * I. Ivanov [04-01-19 20:03]: > > > > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > > > > > > * Benjamin Daines [04-01- > > > > > > > > 19 > > > > > > 18:46]: > > > > > > > > > In my workflow I find myself using multiple machines > > > > > > > > > towork > > > > > > on the > > > > > > > > > same images. My configuration right now on both > > > > > > > > > machinesis > > > > > > to have DT > > > > > > > > > look for updated xmp files on start up and that seems > > > > > > > > > towork > > > > > > pretty > > > > > > > > > well. I usually just ignore the window that pops up > > > > > > > > > totell > > > > > > me about > > > > > > > > > newer xmp files, unless the ones that I'm about to > > > > > > > > > workon > > > > > > are listed, > > > > > > > > > then I select those and let it update the > > > > > > > > > database.However, there have been some situations > > > > > > > > > where myprevious > > > > > > work has > > > > > > > > > been wiped out when opening a folder on another > > > > > > > > > machine. > > > > > > Because of > > > > > > > > > this, I now habitually copy all my xmp files to > > > > > > > > > asubfolder > > > > > > after > > > > > > > > > working on them in order to keep a back up, just > > > > > > > > > incase. > > > > > > Occasionally > > > > > > > > > I need to manually load these sidecar files.Would an > > > > > > > > > option to disable darktable's database and usejust > > > > > > the xmp > > > > > > > > > files be a feasible option? How about using > > > > > > > > > somethinglike > > > > > > syncthing > > > > > > > > > (Linux platform here) to keep the database synced > > > > > > > > > between > > > > > > multiple > > > > > > > > > machines? Would doing that cause any foreseeable > > > > > > > > > issues?How are other people dealing with using > > > > > > > > > multiple machinesto > > > > > > work onprojects, any tips? > > > > > > > > when I use any machine beside my main workstation to > > > > > > > > edit > > > > > > photos, I issue > > > > > > > > darktable as: darktable --library :memory: import > > > > > > > > the photos to be edited finish the edits close > > > > > > > > dtand back at my workstation, re-import the edited > > > > > > > > photoswith > > > > > > their > > > > > > > > accompanying xmp files.have not encountered any > > > > > > > > problems with this work plan. > > > > > > > In theory... if you have 2 identical machines (for > > > > > > > examplelinux)shared network location for DT filesshared > > > > > > > network location for the DB, configuration files > > > > > > > andcachesame mounting point for the 2 machinesyou could > > > > > > > use DT on one or the other (one at a time) and the > > > > > > changes should > > > > > > > be on the 2 machines.BUT... I haven't tested the scenario > > > > > > > please back up if youwant > > > > > > to try it. > > > > > > > On the other hand - what Patrick is pointing to is based > > > > > > > on > > > > > > experience. > > > > > > > > > > > > IF, IF, IF you NEVER run dt at the same time on > > > > > > differentmachines,onecould share the db placing it on > > > > > > networked storage. BUT NEVERRUNDT ONTWO MACHINES AT THE > > > > > >
Re: [darktable-user] Keeping DT in sync between multiple computers
* Benjamin Daines [04-07-19 11:04]: > Importing the folder doesn't recognize versions either unfortunately. > On Sat, 2019-04-06 at 13:54 -0400, Patrick Shanahan wrote: > > * Benjamin Daines [04-06-19 12:51]: > > > The issue I'm running into now, with database=:memory: is that if > > > I'veduplicated an image so that I've got two xmp files for the same > > > image(say IMG1.xmp and IMG1_01.xmp), when I close the folder and > > > open itagain, DT only reads the initial image, not the second > > > version. If Ithen create a new version, DT immediately overwrites > > > IMG1_01.xmp, sounless I've copied all my xmp files to a > > > subdirectory, that work islost. It would be best to have darktable > > > automatically create these versionswhen seeing IMG_01.xmp. > > > Hopefully that makes sense. On Tue, 2019-04-02 at 07:20 +0300, Juha > > > Lintula wrote: > > > > Hi!I also use darktable only for image processing and have the > > > > samesetting as Robert; database=:memory: This setting will > > > > alwaysautomatically read the .xmp files as you are always > > > > starting with afresh database. > > > > -Juha > > > > On Tue, 2 Apr 2019 at 05:20, Patrick Shanahan > > > > wrote: > > > > > * I. Ivanov [04-01-19 20:03]: > > > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > > > > > * Benjamin Daines [04-01-19 > > > > > 18:46]: > > > > > > > > In my workflow I find myself using multiple machines to > > > > > > > > work > > > > > on the > > > > > > > > same images. My configuration right now on both machines > > > > > > > > is > > > > > to have DT > > > > > > > > look for updated xmp files on start up and that seems to > > > > > > > > work > > > > > pretty > > > > > > > > well. I usually just ignore the window that pops up to > > > > > > > > tell > > > > > me about > > > > > > > > newer xmp files, unless the ones that I'm about to work > > > > > > > > on > > > > > are listed, > > > > > > > > then I select those and let it update the database. > > > > > > > > However, there have been some situations where my > > > > > > > > previous > > > > > work has > > > > > > > > been wiped out when opening a folder on another machine. > > > > > Because of > > > > > > > > this, I now habitually copy all my xmp files to a > > > > > > > > subfolder > > > > > after > > > > > > > > working on them in order to keep a back up, just in > > > > > > > > case. > > > > > Occasionally > > > > > > > > I need to manually load these sidecar files. > > > > > > > > Would an option to disable darktable's database and use > > > > > > > > just > > > > > the xmp > > > > > > > > files be a feasible option? How about using something > > > > > > > > like > > > > > syncthing > > > > > > > > (Linux platform here) to keep the database synced between > > > > > multiple > > > > > > > > machines? Would doing that cause any foreseeable issues? > > > > > > > > How are other people dealing with using multiple machines > > > > > > > > to > > > > > work onprojects, any tips? > > > > > > > when I use any machine beside my main workstation to edit > > > > > photos, I issue > > > > > > > darktable as: > > > > > > >darktable --library :memory: > > > > > > >import the photos to be edited > > > > > > >finish the edits > > > > > > >close dt > > > > > > > and back at my workstation, re-import the edited photos > > > > > > > with > > > > > their > > > > > > > accompanying xmp files. > > > > > > > have not encountered any problems with this work plan. > > > > > > In theory... if you have 2 identical machines (for example > > > > > > linux) > > > > > > shared network location for DT files > > > > > > shared network location for the DB, configuration files and > > > > > > cache > > > > > > same mounting point for the 2 machines > > > > > > you could use DT on one or the other (one at a time) and the > > > > > changes should > > > > > > be on the 2 machines. > > > > > > BUT... I haven't tested the scenario please back up if you > > > > > > want > > > > > to try it. > > > > > > On the other hand - what Patrick is pointing to is based on > > > > > experience. > > > > > > > > > > > > > > > IF, IF, IF you NEVER run dt at the same time on different > > > > > machines,one > > > > > could share the db placing it on networked storage. BUT NEVER > > > > > RUNDT ON > > > > > TWO MACHINES AT THE SAME TIME. > > > > > > > > > > > > > > > > Thanks. > > > > try instead, to import the image instead of just reading the xmp > > file. Ihave not seen that happen to me and I do have duplicate > > images withdifferent crops. it appears your dup images are not being > > created withthe same filenames reflected by your oddly number xmp > > files. but ... > > > versions of what? importing an image not in dt's db will utilize the acompanying xmp. you have something irregular wrt your filename and accompanying xmp files. if the filenames to the xmp files do not match, iiuc, the xmp is not relevant, ie: not utilized. you appear to be defeating the very
Re: [darktable-user] Keeping DT in sync between multiple computers
Importing the folder doesn't recognize versions either unfortunately. On Sat, 2019-04-06 at 13:54 -0400, Patrick Shanahan wrote: > * Benjamin Daines [04-06-19 12:51]: > > The issue I'm running into now, with database=:memory: is that if > > I'veduplicated an image so that I've got two xmp files for the same > > image(say IMG1.xmp and IMG1_01.xmp), when I close the folder and > > open itagain, DT only reads the initial image, not the second > > version. If Ithen create a new version, DT immediately overwrites > > IMG1_01.xmp, sounless I've copied all my xmp files to a > > subdirectory, that work islost. It would be best to have darktable > > automatically create these versionswhen seeing IMG_01.xmp. > > Hopefully that makes sense. On Tue, 2019-04-02 at 07:20 +0300, Juha > > Lintula wrote: > > > Hi!I also use darktable only for image processing and have the > > > samesetting as Robert; database=:memory: This setting will > > > alwaysautomatically read the .xmp files as you are always > > > starting with afresh database. > > > -Juha > > > On Tue, 2 Apr 2019 at 05:20, Patrick Shanahan > > > wrote: > > > > * I. Ivanov [04-01-19 20:03]: > > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > > > > * Benjamin Daines [04-01-19 > > > > 18:46]: > > > > > > > In my workflow I find myself using multiple machines to > > > > > > > work > > > > on the > > > > > > > same images. My configuration right now on both machines > > > > > > > is > > > > to have DT > > > > > > > look for updated xmp files on start up and that seems to > > > > > > > work > > > > pretty > > > > > > > well. I usually just ignore the window that pops up to > > > > > > > tell > > > > me about > > > > > > > newer xmp files, unless the ones that I'm about to work > > > > > > > on > > > > are listed, > > > > > > > then I select those and let it update the database. > > > > > > > However, there have been some situations where my > > > > > > > previous > > > > work has > > > > > > > been wiped out when opening a folder on another machine. > > > > Because of > > > > > > > this, I now habitually copy all my xmp files to a > > > > > > > subfolder > > > > after > > > > > > > working on them in order to keep a back up, just in > > > > > > > case. > > > > Occasionally > > > > > > > I need to manually load these sidecar files. > > > > > > > Would an option to disable darktable's database and use > > > > > > > just > > > > the xmp > > > > > > > files be a feasible option? How about using something > > > > > > > like > > > > syncthing > > > > > > > (Linux platform here) to keep the database synced between > > > > multiple > > > > > > > machines? Would doing that cause any foreseeable issues? > > > > > > > How are other people dealing with using multiple machines > > > > > > > to > > > > work onprojects, any tips? > > > > > > when I use any machine beside my main workstation to edit > > > > photos, I issue > > > > > > darktable as: > > > > > >darktable --library :memory: > > > > > >import the photos to be edited > > > > > >finish the edits > > > > > >close dt > > > > > > and back at my workstation, re-import the edited photos > > > > > > with > > > > their > > > > > > accompanying xmp files. > > > > > > have not encountered any problems with this work plan. > > > > > In theory... if you have 2 identical machines (for example > > > > > linux) > > > > > shared network location for DT files > > > > > shared network location for the DB, configuration files and > > > > > cache > > > > > same mounting point for the 2 machines > > > > > you could use DT on one or the other (one at a time) and the > > > > changes should > > > > > be on the 2 machines. > > > > > BUT... I haven't tested the scenario please back up if you > > > > > want > > > > to try it. > > > > > On the other hand - what Patrick is pointing to is based on > > > > experience. > > > > > > > > > > > > IF, IF, IF you NEVER run dt at the same time on different > > > > machines,one > > > > could share the db placing it on networked storage. BUT NEVER > > > > RUNDT ON > > > > TWO MACHINES AT THE SAME TIME. > > > > > > > > > > > > Thanks. > > try instead, to import the image instead of just reading the xmp > file. Ihave not seen that happen to me and I do have duplicate > images withdifferent crops. it appears your dup images are not being > created withthe same filenames reflected by your oddly number xmp > files. but ... > signature.asc Description: This is a digitally signed message part
Re: [darktable-user] Keeping DT in sync between multiple computers
Importing might be the answer, however I much prefer to open darktable from a terminal window with '$ darktable .' On Sat, 2019-04-06 at 13:54 -0400, Patrick Shanahan wrote: > * Benjamin Daines [04-06-19 12:51]: > > The issue I'm running into now, with database=:memory: is that if > > I'veduplicated an image so that I've got two xmp files for the same > > image(say IMG1.xmp and IMG1_01.xmp), when I close the folder and > > open itagain, DT only reads the initial image, not the second > > version. If Ithen create a new version, DT immediately overwrites > > IMG1_01.xmp, sounless I've copied all my xmp files to a > > subdirectory, that work islost. It would be best to have darktable > > automatically create these versionswhen seeing IMG_01.xmp. > > Hopefully that makes sense. On Tue, 2019-04-02 at 07:20 +0300, Juha > > Lintula wrote: > > > Hi!I also use darktable only for image processing and have the > > > samesetting as Robert; database=:memory: This setting will > > > alwaysautomatically read the .xmp files as you are always > > > starting with afresh database. > > > -Juha > > > On Tue, 2 Apr 2019 at 05:20, Patrick Shanahan > > > wrote: > > > > * I. Ivanov [04-01-19 20:03]: > > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > > > > * Benjamin Daines [04-01-19 > > > > 18:46]: > > > > > > > In my workflow I find myself using multiple machines to > > > > > > > work > > > > on the > > > > > > > same images. My configuration right now on both machines > > > > > > > is > > > > to have DT > > > > > > > look for updated xmp files on start up and that seems to > > > > > > > work > > > > pretty > > > > > > > well. I usually just ignore the window that pops up to > > > > > > > tell > > > > me about > > > > > > > newer xmp files, unless the ones that I'm about to work > > > > > > > on > > > > are listed, > > > > > > > then I select those and let it update the database. > > > > > > > However, there have been some situations where my > > > > > > > previous > > > > work has > > > > > > > been wiped out when opening a folder on another machine. > > > > Because of > > > > > > > this, I now habitually copy all my xmp files to a > > > > > > > subfolder > > > > after > > > > > > > working on them in order to keep a back up, just in > > > > > > > case. > > > > Occasionally > > > > > > > I need to manually load these sidecar files. > > > > > > > Would an option to disable darktable's database and use > > > > > > > just > > > > the xmp > > > > > > > files be a feasible option? How about using something > > > > > > > like > > > > syncthing > > > > > > > (Linux platform here) to keep the database synced between > > > > multiple > > > > > > > machines? Would doing that cause any foreseeable issues? > > > > > > > How are other people dealing with using multiple machines > > > > > > > to > > > > work onprojects, any tips? > > > > > > when I use any machine beside my main workstation to edit > > > > photos, I issue > > > > > > darktable as: > > > > > >darktable --library :memory: > > > > > >import the photos to be edited > > > > > >finish the edits > > > > > >close dt > > > > > > and back at my workstation, re-import the edited photos > > > > > > with > > > > their > > > > > > accompanying xmp files. > > > > > > have not encountered any problems with this work plan. > > > > > In theory... if you have 2 identical machines (for example > > > > > linux) > > > > > shared network location for DT files > > > > > shared network location for the DB, configuration files and > > > > > cache > > > > > same mounting point for the 2 machines > > > > > you could use DT on one or the other (one at a time) and the > > > > changes should > > > > > be on the 2 machines. > > > > > BUT... I haven't tested the scenario please back up if you > > > > > want > > > > to try it. > > > > > On the other hand - what Patrick is pointing to is based on > > > > experience. > > > > > > > > > > > > IF, IF, IF you NEVER run dt at the same time on different > > > > machines,one > > > > could share the db placing it on networked storage. BUT NEVER > > > > RUNDT ON > > > > TWO MACHINES AT THE SAME TIME. > > > > > > > > > > > > Thanks. > > try instead, to import the image instead of just reading the xmp > file. Ihave not seen that happen to me and I do have duplicate > images withdifferent crops. it appears your dup images are not being > created withthe same filenames reflected by your oddly number xmp > files. but ... > signature.asc Description: This is a digitally signed message part
Re: [darktable-user] Keeping DT in sync between multiple computers
* Benjamin Daines [04-06-19 12:51]: > The issue I'm running into now, with database=:memory: is that if I've > duplicated an image so that I've got two xmp files for the same image > (say IMG1.xmp and IMG1_01.xmp), when I close the folder and open it > again, DT only reads the initial image, not the second version. If I > then create a new version, DT immediately overwrites IMG1_01.xmp, so > unless I've copied all my xmp files to a subdirectory, that work is > lost. > It would be best to have darktable automatically create these versions > when seeing IMG_01.xmp. > Hopefully that makes sense. > On Tue, 2019-04-02 at 07:20 +0300, Juha Lintula wrote: > > Hi! > > I also use darktable only for image processing and have the same > > setting as Robert; database=:memory: This setting will always > > automatically read the .xmp files as you are always starting with a > > fresh database. > > > > -Juha > > > > On Tue, 2 Apr 2019 at 05:20, Patrick Shanahan > > wrote: > > > * I. Ivanov [04-01-19 20:03]: > > > > > > > > > > > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > > > > > > * Benjamin Daines [04-01-19 > > > 18:46]: > > > > > > > > > In my workflow I find myself using multiple machines to work > > > on the > > > > > > > > > same images. My configuration right now on both machines is > > > to have DT > > > > > > > > > look for updated xmp files on start up and that seems to work > > > pretty > > > > > > > > > well. I usually just ignore the window that pops up to tell > > > me about > > > > > > > > > newer xmp files, unless the ones that I'm about to work on > > > are listed, > > > > > > > > > then I select those and let it update the database. > > > > > > > > > > > > > > > > > > However, there have been some situations where my previous > > > work has > > > > > > > > > been wiped out when opening a folder on another machine. > > > Because of > > > > > > > > > this, I now habitually copy all my xmp files to a subfolder > > > after > > > > > > > > > working on them in order to keep a back up, just in case. > > > Occasionally > > > > > > > > > I need to manually load these sidecar files. > > > > > > > > > > > > > > > > > > Would an option to disable darktable's database and use just > > > the xmp > > > > > > > > > files be a feasible option? How about using something like > > > syncthing > > > > > > > > > (Linux platform here) to keep the database synced between > > > multiple > > > > > > > > > machines? Would doing that cause any foreseeable issues? > > > > > > > > > > > > > > > > > > How are other people dealing with using multiple machines to > > > work onprojects, any tips? > > > > > > > > when I use any machine beside my main workstation to edit > > > photos, I issue > > > > > > > > darktable as: > > > > > > > >darktable --library :memory: > > > > > > > >import the photos to be edited > > > > > > > >finish the edits > > > > > > > >close dt > > > > > > > > and back at my workstation, re-import the edited photos with > > > their > > > > > > > > accompanying xmp files. > > > > > > > > > > > > > > > > have not encountered any problems with this work plan. > > > > > > > > > > > > > > > In theory... if you have 2 identical machines (for example linux) > > > > > > > shared network location for DT files > > > > > > > shared network location for the DB, configuration files and cache > > > > > > > same mounting point for the 2 machines > > > > > > > > > > > > > > you could use DT on one or the other (one at a time) and the > > > changes should > > > > > > > be on the 2 machines. > > > > > > > > > > > > > > BUT... I haven't tested the scenario please back up if you want > > > to try it. > > > > > > > > > > > > > > On the other hand - what Patrick is pointing to is based on > > > experience. > > > > > > > > > > > > IF, IF, IF you NEVER run dt at the same time on different machines, > > > one > > > > > > could share the db placing it on networked storage. BUT NEVER RUN > > > DT ON > > > > > > TWO MACHINES AT THE SAME TIME. > > > > > > > > > > > Thanks. try instead, to import the image instead of just reading the xmp file. I have not seen that happen to me and I do have duplicate images with different crops. it appears your dup images are not being created with the same filenames reflected by your oddly number xmp files. but ... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/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+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
The issue I'm running into now, with database=:memory: is that if I've duplicated an image so that I've got two xmp files for the same image (say IMG1.xmp and IMG1_01.xmp), when I close the folder and open it again, DT only reads the initial image, not the second version. If I then create a new version, DT immediately overwrites IMG1_01.xmp, so unless I've copied all my xmp files to a subdirectory, that work is lost. It would be best to have darktable automatically create these versions when seeing IMG_01.xmp. Hopefully that makes sense. On Tue, 2019-04-02 at 07:20 +0300, Juha Lintula wrote: > Hi! > I also use darktable only for image processing and have the same > setting as Robert; database=:memory: This setting will always > automatically read the .xmp files as you are always starting with a > fresh database. > > -Juha > > On Tue, 2 Apr 2019 at 05:20, Patrick Shanahan > wrote: > > * I. Ivanov [04-01-19 20:03]: > > > > > > > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > > > > * Benjamin Daines [04-01-19 > > 18:46]: > > > > > > > In my workflow I find myself using multiple machines to work > > on the > > > > > > > same images. My configuration right now on both machines is > > to have DT > > > > > > > look for updated xmp files on start up and that seems to work > > pretty > > > > > > > well. I usually just ignore the window that pops up to tell > > me about > > > > > > > newer xmp files, unless the ones that I'm about to work on > > are listed, > > > > > > > then I select those and let it update the database. > > > > > > > > > > > > > > However, there have been some situations where my previous > > work has > > > > > > > been wiped out when opening a folder on another machine. > > Because of > > > > > > > this, I now habitually copy all my xmp files to a subfolder > > after > > > > > > > working on them in order to keep a back up, just in case. > > Occasionally > > > > > > > I need to manually load these sidecar files. > > > > > > > > > > > > > > Would an option to disable darktable's database and use just > > the xmp > > > > > > > files be a feasible option? How about using something like > > syncthing > > > > > > > (Linux platform here) to keep the database synced between > > multiple > > > > > > > machines? Would doing that cause any foreseeable issues? > > > > > > > > > > > > > > How are other people dealing with using multiple machines to > > work onprojects, any tips? > > > > > > when I use any machine beside my main workstation to edit > > photos, I issue > > > > > > darktable as: > > > > > >darktable --library :memory: > > > > > >import the photos to be edited > > > > > >finish the edits > > > > > >close dt > > > > > > and back at my workstation, re-import the edited photos with > > their > > > > > > accompanying xmp files. > > > > > > > > > > > > have not encountered any problems with this work plan. > > > > > > > > > > > In theory... if you have 2 identical machines (for example linux) > > > > > shared network location for DT files > > > > > shared network location for the DB, configuration files and cache > > > > > same mounting point for the 2 machines > > > > > > > > > > you could use DT on one or the other (one at a time) and the > > changes should > > > > > be on the 2 machines. > > > > > > > > > > BUT... I haven't tested the scenario please back up if you want > > to try it. > > > > > > > > > > On the other hand - what Patrick is pointing to is based on > > experience. > > > > > > > > IF, IF, IF you NEVER run dt at the same time on different machines, > > one > > > > could share the db placing it on networked storage. BUT NEVER RUN > > DT ON > > > > TWO MACHINES AT THE SAME TIME. > > > > > > Thanks. signature.asc Description: This is a digitally signed message part
Re: [darktable-user] Keeping DT in sync between multiple computers
Sounds like disabling the library within the config file is the best way to go. Thanks for all the responses! On Tue, 2019-04-02 at 07:20 +0300, Juha Lintula wrote: > Hi! > I also use darktable only for image processing and have the same > setting as Robert; database=:memory: This setting will always > automatically read the .xmp files as you are always starting with a > fresh database. > > -Juha > > On Tue, 2 Apr 2019 at 05:20, Patrick Shanahan > wrote: > > * I. Ivanov [04-01-19 20:03]: > > > > > > > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > > > > * Benjamin Daines [04-01-19 > > 18:46]: > > > > > > > In my workflow I find myself using multiple machines to work > > on the > > > > > > > same images. My configuration right now on both machines is > > to have DT > > > > > > > look for updated xmp files on start up and that seems to work > > pretty > > > > > > > well. I usually just ignore the window that pops up to tell > > me about > > > > > > > newer xmp files, unless the ones that I'm about to work on > > are listed, > > > > > > > then I select those and let it update the database. > > > > > > > > > > > > > > However, there have been some situations where my previous > > work has > > > > > > > been wiped out when opening a folder on another machine. > > Because of > > > > > > > this, I now habitually copy all my xmp files to a subfolder > > after > > > > > > > working on them in order to keep a back up, just in case. > > Occasionally > > > > > > > I need to manually load these sidecar files. > > > > > > > > > > > > > > Would an option to disable darktable's database and use just > > the xmp > > > > > > > files be a feasible option? How about using something like > > syncthing > > > > > > > (Linux platform here) to keep the database synced between > > multiple > > > > > > > machines? Would doing that cause any foreseeable issues? > > > > > > > > > > > > > > How are other people dealing with using multiple machines to > > work onprojects, any tips? > > > > > > when I use any machine beside my main workstation to edit > > photos, I issue > > > > > > darktable as: > > > > > >darktable --library :memory: > > > > > >import the photos to be edited > > > > > >finish the edits > > > > > >close dt > > > > > > and back at my workstation, re-import the edited photos with > > their > > > > > > accompanying xmp files. > > > > > > > > > > > > have not encountered any problems with this work plan. > > > > > > > > > > > In theory... if you have 2 identical machines (for example linux) > > > > > shared network location for DT files > > > > > shared network location for the DB, configuration files and cache > > > > > same mounting point for the 2 machines > > > > > > > > > > you could use DT on one or the other (one at a time) and the > > changes should > > > > > be on the 2 machines. > > > > > > > > > > BUT... I haven't tested the scenario please back up if you want > > to try it. > > > > > > > > > > On the other hand - what Patrick is pointing to is based on > > experience. > > > > > > > > IF, IF, IF you NEVER run dt at the same time on different machines, > > one > > > > could share the db placing it on networked storage. BUT NEVER RUN > > DT ON > > > > TWO MACHINES AT THE SAME TIME. > > > > > > signature.asc Description: This is a digitally signed message part
Re: [darktable-user] Keeping DT in sync between multiple computers
I use FreeFileSync (https://freefilesync.org/) to keep files on three laptops (2- Win 10; 1 - Ubuntu Linux) in sync. When I open DT, I get a window that recognizes the updated xmp files (if any) and asks whether I want to overwrite older xmp files, just as you noted. The difference is that I usually let DT update. I might consider using FreeFileSync update the db, but I'm not willing to mix Windows and Linux machines' db files until I know more about their compatibility and the chance of inducing major mal-boo-boos. Willy * On 4/1/2019 at 18:38, Benjamin Daines wrote: In my workflow I find myself using multiple machines to work on the same images. My configuration right now on both machines is to have DT look for updated xmp files on start up and that seems to work pretty well. I usually just ignore the window that pops up to tell me about newer xmp files, unless the ones that I'm about to work on are listed, then I select those and let it update the database. However, there have been some situations where my previous work has been wiped out when opening a folder on another machine. Because of this, I now habitually copy all my xmp files to a subfolder after working on them in order to keep a back up, just in case. Occasionally I need to manually load these sidecar files. Would an option to disable darktable's database and use just the xmp files be a feasible option? How about using something like syncthing (Linux platform here) to keep the database synced between multiple machines? Would doing that cause any foreseeable issues? How are other people dealing with using multiple machines to work on projects, any tips? Thanks. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
Hi! I also use darktable only for image processing and have the same setting as Robert; database=:memory: This setting will always automatically read the .xmp files as you are always starting with a fresh database. -Juha On Tue, 2 Apr 2019 at 05:20, Patrick Shanahan wrote: > * I. Ivanov [04-01-19 20:03]: > > > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > > * Benjamin Daines [04-01-19 18:46]: > > > > In my workflow I find myself using multiple machines to work on the > > > > same images. My configuration right now on both machines is to have > DT > > > > look for updated xmp files on start up and that seems to work pretty > > > > well. I usually just ignore the window that pops up to tell me about > > > > newer xmp files, unless the ones that I'm about to work on are > listed, > > > > then I select those and let it update the database. > > > > > > > > However, there have been some situations where my previous work has > > > > been wiped out when opening a folder on another machine. Because of > > > > this, I now habitually copy all my xmp files to a subfolder after > > > > working on them in order to keep a back up, just in case. > Occasionally > > > > I need to manually load these sidecar files. > > > > > > > > Would an option to disable darktable's database and use just the xmp > > > > files be a feasible option? How about using something like syncthing > > > > (Linux platform here) to keep the database synced between multiple > > > > machines? Would doing that cause any foreseeable issues? > > > > > > > > How are other people dealing with using multiple machines to work > onprojects, any tips? > > > when I use any machine beside my main workstation to edit photos, I > issue > > > darktable as: > > >darktable --library :memory: > > >import the photos to be edited > > >finish the edits > > >close dt > > > and back at my workstation, re-import the edited photos with their > > > accompanying xmp files. > > > > > > have not encountered any problems with this work plan. > > > > > In theory... if you have 2 identical machines (for example linux) > > shared network location for DT files > > shared network location for the DB, configuration files and cache > > same mounting point for the 2 machines > > > > you could use DT on one or the other (one at a time) and the changes > should > > be on the 2 machines. > > > > BUT... I haven't tested the scenario please back up if you want to try > it. > > > > On the other hand - what Patrick is pointing to is based on experience. > > IF, IF, IF you NEVER run dt at the same time on different machines, one > could share the db placing it on networked storage. BUT NEVER RUN DT ON > TWO MACHINES AT THE SAME TIME. > > -- > (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri > http://en.opensuse.orgopenSUSE Community Memberfacebook/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+unsubscr...@lists.darktable.org > > darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
* I. Ivanov [04-01-19 20:03]: > > On 2019-04-01 16:34, Patrick Shanahan wrote: > > * Benjamin Daines [04-01-19 18:46]: > > > In my workflow I find myself using multiple machines to work on the > > > same images. My configuration right now on both machines is to have DT > > > look for updated xmp files on start up and that seems to work pretty > > > well. I usually just ignore the window that pops up to tell me about > > > newer xmp files, unless the ones that I'm about to work on are listed, > > > then I select those and let it update the database. > > > > > > However, there have been some situations where my previous work has > > > been wiped out when opening a folder on another machine. Because of > > > this, I now habitually copy all my xmp files to a subfolder after > > > working on them in order to keep a back up, just in case. Occasionally > > > I need to manually load these sidecar files. > > > > > > Would an option to disable darktable's database and use just the xmp > > > files be a feasible option? How about using something like syncthing > > > (Linux platform here) to keep the database synced between multiple > > > machines? Would doing that cause any foreseeable issues? > > > > > > How are other people dealing with using multiple machines to work > > > onprojects, any tips? > > when I use any machine beside my main workstation to edit photos, I issue > > darktable as: > >darktable --library :memory: > >import the photos to be edited > >finish the edits > >close dt > > and back at my workstation, re-import the edited photos with their > > accompanying xmp files. > > > > have not encountered any problems with this work plan. > > > In theory... if you have 2 identical machines (for example linux) > shared network location for DT files > shared network location for the DB, configuration files and cache > same mounting point for the 2 machines > > you could use DT on one or the other (one at a time) and the changes should > be on the 2 machines. > > BUT... I haven't tested the scenario please back up if you want to try it. > > On the other hand - what Patrick is pointing to is based on experience. IF, IF, IF you NEVER run dt at the same time on different machines, one could share the db placing it on networked storage. BUT NEVER RUN DT ON TWO MACHINES AT THE SAME TIME. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/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+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
> In theory... if you have 2 identical machines (for example linux) > shared network location for DT files > shared network location for the DB, configuration files and cache > same mounting point for the 2 machines > > you could use DT on one or the other (one at a time) and the changes > should be on the 2 machines. There are two points you should be careful of: - no concurrent use of the database (DT doesn't lock its access to it) - database format can change, so all machines should run exactly the same versions of DT (or at least the same major versions) On practice, probably the best idea is to treat one installation as the master and use memory database on the others, or use no database at all if it brings you no added benefit. Regards, Guillermo darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
On 2019-04-01 16:34, Patrick Shanahan wrote: * Benjamin Daines [04-01-19 18:46]: In my workflow I find myself using multiple machines to work on the same images. My configuration right now on both machines is to have DT look for updated xmp files on start up and that seems to work pretty well. I usually just ignore the window that pops up to tell me about newer xmp files, unless the ones that I'm about to work on are listed, then I select those and let it update the database. However, there have been some situations where my previous work has been wiped out when opening a folder on another machine. Because of this, I now habitually copy all my xmp files to a subfolder after working on them in order to keep a back up, just in case. Occasionally I need to manually load these sidecar files. Would an option to disable darktable's database and use just the xmp files be a feasible option? How about using something like syncthing (Linux platform here) to keep the database synced between multiple machines? Would doing that cause any foreseeable issues? How are other people dealing with using multiple machines to work onprojects, any tips? when I use any machine beside my main workstation to edit photos, I issue darktable as: darktable --library :memory: import the photos to be edited finish the edits close dt and back at my workstation, re-import the edited photos with their accompanying xmp files. have not encountered any problems with this work plan. In theory... if you have 2 identical machines (for example linux) shared network location for DT files shared network location for the DB, configuration files and cache same mounting point for the 2 machines you could use DT on one or the other (one at a time) and the changes should be on the 2 machines. BUT... I haven't tested the scenario please back up if you want to try it. On the other hand - what Patrick is pointing to is based on experience. Regards, B darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
On Mon, 1 Apr 2019 19:34:15 -0400, Patrick Shanahan wrote: > * Benjamin Daines [04-01-19 18:46]: >> In my workflow I find myself using multiple machines to work on the >> same images. My configuration right now on both machines is to have DT >> look for updated xmp files on start up and that seems to work pretty >> well. I usually just ignore the window that pops up to tell me about >> newer xmp files, unless the ones that I'm about to work on are listed, >> then I select those and let it update the database. >> >> However, there have been some situations where my previous work has >> been wiped out when opening a folder on another machine. Because of >> this, I now habitually copy all my xmp files to a subfolder after >> working on them in order to keep a back up, just in case. Occasionally >> I need to manually load these sidecar files. >> >> Would an option to disable darktable's database and use just the xmp >> files be a feasible option? How about using something like syncthing >> (Linux platform here) to keep the database synced between multiple >> machines? Would doing that cause any foreseeable issues? >> >> How are other people dealing with using multiple machines to work >> onprojects, any tips? > > when I use any machine beside my main workstation to edit photos, I issue > darktable as: darktable --library :memory: > import the photos to be edited > finish the edits > close dt > and back at my workstation, re-import the edited photos with their > accompanying xmp files. > > have not encountered any problems with this work plan. I do the same thing, except that I have database=:memory: in my ~/.config/darktable/darktablerc. I use darktable strictly for image processing. I use kphotoalbum to manage my photos, and stick the .xmp files in the tree alongside the photos. -- Robert Krawitz *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint --http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] Keeping DT in sync between multiple computers
* Benjamin Daines [04-01-19 18:46]: > In my workflow I find myself using multiple machines to work on the > same images. My configuration right now on both machines is to have DT > look for updated xmp files on start up and that seems to work pretty > well. I usually just ignore the window that pops up to tell me about > newer xmp files, unless the ones that I'm about to work on are listed, > then I select those and let it update the database. > > However, there have been some situations where my previous work has > been wiped out when opening a folder on another machine. Because of > this, I now habitually copy all my xmp files to a subfolder after > working on them in order to keep a back up, just in case. Occasionally > I need to manually load these sidecar files. > > Would an option to disable darktable's database and use just the xmp > files be a feasible option? How about using something like syncthing > (Linux platform here) to keep the database synced between multiple > machines? Would doing that cause any foreseeable issues? > > How are other people dealing with using multiple machines to work onprojects, > any tips? when I use any machine beside my main workstation to edit photos, I issue darktable as: darktable --library :memory: import the photos to be edited finish the edits close dt and back at my workstation, re-import the edited photos with their accompanying xmp files. have not encountered any problems with this work plan. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/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+unsubscr...@lists.darktable.org
