Lightroom to DigiKam: reading xmp files
Locked
12
12
 
|
Hi all,
i'm trying to migrate my lightroom catalog to DigiKam, but i have a big problem in reading keywords. I would like to be able to search my photo through keywords/tags that i had previously added in Lightroom. I created from LR sidecar files (xmp) for every photo and i notice that files have the following naming convention: - *original photo: abcdefg.orf* - *xmp file generated: abcdefg.xmp* With that naming convention DigiKam is not able to read xmp files! I tried to rename manually the xmp files as abcdefg*.org*.xmp ( the .orf extension added ) and all seems works correctly. I have thousands of photo and i wouldn't rename every files manually.... is there a solution? Thansk in advance! Ale -- Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html |
Re: Lightroom to DigiKam: reading xmp files
|
|
On dimanche 31 décembre 2017 15:39:59 CET salinaale wrote:
> Hi all, > i'm trying to migrate my lightroom catalog to DigiKam, but i have a big > problem in reading keywords. > I would like to be able to search my photo through keywords/tags that i had > previously added in Lightroom. > I created from LR sidecar files (xmp) for every photo and i notice that > files have the following naming convention: > - *original photo: abcdefg.orf* > - *xmp file generated: abcdefg.xmp* > > With that naming convention DigiKam is not able to read xmp files! > I tried to rename manually the xmp files as abcdefg*.org*.xmp ( the .orf > extension added ) and all seems works correctly. > > I have thousands of photo and i wouldn't rename every files manually.... is > there a solution? Or, at least under Linux, a shell script can do the job quite easily. No idea how to attack it under MS-Windows, though, unless you can do a bulk rename where you replace one extension by another (in your case: ".xmp" => ".orf.xmp"). Remco |
Re: Lightroom to DigiKam: reading xmp files
|
|
Either Ubuntu or openSUSE terminals can be installed in Windows 10 so a file renaming script should work there too. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Remco Viëtor <[hidden email]> Date: 2018-01-01 6:44 AM (GMT-07:00) To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: Lightroom to DigiKam: reading xmp files > Hi all, > i'm trying to migrate my lightroom catalog to DigiKam, but i have a big > problem in reading keywords. > I would like to be able to search my photo through keywords/tags that i had > previously added in Lightroom. > I created from LR sidecar files (xmp) for every photo and i notice that > files have the following naming convention: > - *original photo: abcdefg.orf* > - *xmp file generated: abcdefg.xmp* > > With that naming convention DigiKam is not able to read xmp files! > I tried to rename manually the xmp files as abcdefg*.org*.xmp ( the .orf > extension added ) and all seems works correctly. > > I have thousands of photo and i wouldn't rename every files manually.... is > there a solution? Or, at least under Linux, a shell script can do the job quite easily. No idea how to attack it under MS-Windows, though, unless you can do a bulk rename where you replace one extension by another (in your case: ".xmp" => ".orf.xmp"). Remco |
|
|
Ok... if there isn't a real solution, i will opt for renaming with a script
every xmp files. I am really surprised because this can be an obstacle for everyone who wants to abandon lightroom in favor of digikam. Thanks to all. Ale -- Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html |
|
|
Hello to all,
I tried to solve the problem of the xmp file format but without success. I'm trying to replace Lightroom with DigiKam but it's not possible because DigiKam is not able to read xmp files generated by Lightroom. I tried to rename xmp file ( from filename.xmp -> filename.ext.xmp) and everythings seemed to be ok in DK; i was able to search every photo by tag, title etc etc... wow... But... this cannot be the solution.. if i rename every xmp files in filename.ext.xmp, those files are not read by external editors... for example by Dxo Photolab. It's a shame that I can not use DigiKam ... I'll have to look for a new replacement for Lightroom.... -- Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html |
Re: Lightroom to DigiKam: reading xmp files
|
|
One solution might by symlinking file.xmp to file.ext.xmp.
You could also try darktable for editing, which also uses file.ext.xmp for sidecar files. IMO, the xmp spec is silly for allowing multiple files per sidecar and for not including the native file extension. -m On January 6, 2018 2:37:33 PM PST, salinaale <[hidden email]> wrote:
Hello to all, |
Re: Lightroom to DigiKam: reading xmp files
|
|
I use both darktable and digikam and they share same xmps. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Mica Semrick <[hidden email]> Date: 2018-01-06 6:21 PM (GMT-07:00) To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: Lightroom to DigiKam: reading xmp files You could also try darktable for editing, which also uses file.ext.xmp for sidecar files. IMO, the xmp spec is silly for allowing multiple files per sidecar and for not including the native file extension. -m On January 6, 2018 2:37:33 PM PST, salinaale <[hidden email]> wrote:
Hello to all, |
|
|
I think that xmp files porpose is to facilitate interoperability between
different sw...maybe the standard is silly ( i can't find the iso standard now ), but using different naming convention for xmp files, you are limiting the spread of this great product. i don't have a great experience, but i know that Lightroom and dxo ( i think are very widespread ) are using the filename.xmp naming convention. I can't create symlinks because i'm on win and not on linux, and i don't want to fill my disk with thousand of links. Maybe it could be possible to give the possibility to configure the name of xmp files? Just my 2 cents... It is a pity that an excellent software like digikam can not be used as a Lightroom alternative for a matter of standard-not standard. sorry for my english.. :) -- Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html |
Re: Lightroom to DigiKam: reading xmp files
|
|
Note : a report have already open about this topic : Gilles Caulier 2018-01-07 10:40 GMT+01:00 salinaale <[hidden email]>: I think that xmp files porpose is to facilitate interoperability between |
Re: Lightroom to DigiKam: reading xmp files
|
|
In bug 278935 i proposed a simple proof of concept patch to use LR sidecar naming scheme. It must work to test an import of LR files in DK, but it's so far not enough, because it will break backward compatibility with current sidecar naming scheme : typically with this patch, all current XMP sidecar previously generated by DK will be ignored. Gilles Caulier 2018-01-07 10:46 GMT+01:00 Gilles Caulier <[hidden email]>:
|
Re: Lightroom to DigiKam: reading xmp files
|
|
On dimanche 7 janvier 2018 11:21:07 CET Gilles Caulier wrote:
> In bug 278935 <https://bugs.kde.org/show_bug.cgi?id=278935> i proposed a > simple proof of concept patch to use LR sidecar naming scheme. It must work > to test an import of LR files in DK, but it's so far not enough, because it > will break backward compatibility with current sidecar naming scheme : > typically with this patch, all current XMP sidecar previously generated by > DK will be ignored. > > Gilles Caulier > > 2018-01-07 10:46 GMT+01:00 Gilles Caulier <[hidden email]>: > > Note : a report have already open about this topic : > > > > https://bugs.kde.org/show_bug.cgi?id=278935 > > > > Gilles Caulier > > > > 2018-01-07 10:40 GMT+01:00 salinaale <[hidden email]>: > >> I think that xmp files porpose is to facilitate interoperability between > >> different sw...maybe the standard is silly ( i can't find the iso > >> standard > >> now ), but using different naming convention for xmp files, you are > >> limiting > >> the spread of this great product. > >> i don't have a great experience, but i know that Lightroom and dxo ( i > >> think > >> are very widespread ) are using the filename.xmp naming convention. > >> I can't create symlinks because i'm on win and not on linux, and i don't > >> want to fill my disk with thousand of links. > >> Maybe it could be possible to give the possibility to configure the name > >> of > >> xmp files? > >> Just my 2 cents... It is a pity that an excellent software like digikam > >> can > >> not be used as a Lightroom alternative for a matter of standard-not > >> standard. > >> > >> > >> sorry for my english.. :) > >> > >> > >> > >> -- > >> Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189. > >> html Going to a naming scheme of "<basename>.xmp" instead of "<basename>.<orig- ext>.xmp" could break compatibility with Darktable, a raw convertor/editor that's used by several users active here. But can't you have a system where "<basename>.xmp" is used when there is no eligible sidecar with the other possible name present? (i.e. first check for presence of a sidecar with current naming, if not found try "<basename>.xmp") Remco |
Re: Lightroom to DigiKam: reading xmp files
|
|
yes, this can be done for reading, with a priority : 1/ old naming scheme. 2/ new naming scheme (LR) ... or vis versa. But the problem is not here. Look well my comment #11 Gilles Caulier 2018-01-07 13:52 GMT+01:00 Remco Viëtor <[hidden email]>: On dimanche 7 janvier 2018 11:21:07 CET Gilles Caulier wrote: |
Re: Lightroom to DigiKam: reading xmp files
|
|
On dimanche 7 janvier 2018 13:56:19 CET Gilles Caulier wrote:
> yes, this can be done for reading, with a priority : > > 1/ old naming scheme. > 2/ new naming scheme (LR) > > ... or vis versa. > > But the problem is not here. Look well my comment #11 > > https://bugs.kde.org/show_bug.cgi?id=278935#c11 > > Gilles Caulier > Oh, I realise that in the case of multiple existing sidecars with the same basenam you have a problem. Solvable in theory (XMP allows combining sidecar data for several image files/formats in one sidecar), but complicated to implement. But, why do you have sidecar files in the first place? In Digikam, as I see it, the main use is as an external place to save metadata linked to raw files (which are in principle unwritable safely). If you decide that you don't need to use a sidecar for jpeg, tiff, png, the problem would basically go away in a large part. So you could decide to have the <basename>.xmp scheme refer to raw files only. The more so as any information about editing operations is inherently non-portable to other programs anyway. Basically, the problem seems to be adapting Digikam to play nice with other programs. While that's always a good thing, how many users are in that position, other than e.g. a one-time import from lightroom to Digikam? And some other points: - https://discuss.pixls.us/t/linux-applications-and-their-non-standard-xmp-sidecar-naming-convention/2688 gives rules about the naming of sidecar files, but those are specified for /each/ base format, /not/ in a general rule. That document deals principally with /embedding/ XMP data in other files, and sidecars are mentioned more or less in passing; when you have no other option (e.g. MP2 files which don't provide for embedding XMP metadata). I cannot conclude /from that document/ that the scheme "<basename>.XMP" is the *official* standard way of naming sidecar files (I don't have access to the ISO standard documents). - LR seems to use sidecars for raw files *only*, not for .jpg, .dng and other writable formats. Both seem to indicate that sidecars are considered a last option when the metadata cannot be embedded/added/modified, and in that case "<basename>.XMP" works (as most derived formats *can* embed the XML data) Remco > 2018-01-07 13:52 GMT+01:00 Remco Viëtor <[hidden email]>: <...> > > > > Going to a naming scheme of "<basename>.xmp" instead of "<basename>.<orig- > > ext>.xmp" could break compatibility with Darktable, a raw convertor/editor > > that's used by several users active here. > > > > But can't you have a system where "<basename>.xmp" is used when there is > > no > > eligible sidecar with the other possible name present? (i.e. first check > > for > > presence of a sidecar with current naming, if not found try > > "<basename>.xmp") > > > > Remco |
Re: Lightroom to DigiKam: reading xmp files
|
|
In reply to this post by Remco Viëtor
Please don't break the compability with darktable. :) Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Remco Viëtor <[hidden email]> Date: 2018-01-07 5:52 AM (GMT-07:00) To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: Lightroom to DigiKam: reading xmp files > In bug 278935 <https://bugs.kde.org/show_bug.cgi?id=278935> i proposed a > simple proof of concept patch to use LR sidecar naming scheme. It must work > to test an import of LR files in DK, but it's so far not enough, because it > will break backward compatibility with current sidecar naming scheme : > typically with this patch, all current XMP sidecar previously generated by > DK will be ignored. > > Gilles Caulier > > 2018-01-07 10:46 GMT+01:00 Gilles Caulier <[hidden email]>: > > Note : a report have already open about this topic : > > > > https://bugs.kde.org/show_bug.cgi?id=278935 > > > > Gilles Caulier > > > > 2018-01-07 10:40 GMT+01:00 salinaale <[hidden email]>: > >> I think that xmp files porpose is to facilitate interoperability between > >> different sw...maybe the standard is silly ( i can't find the iso > >> standard > >> now ), but using different naming convention for xmp files, you are > >> limiting > >> the spread of this great product. > >> i don't have a great experience, but i know that Lightroom and dxo ( i > >> think > >> are very widespread ) are using the filename.xmp naming convention. > >> I can't create symlinks because i'm on win and not on linux, and i don't > >> want to fill my disk with thousand of links. > >> Maybe it could be possible to give the possibility to configure the name > >> of > >> xmp files? > >> Just my 2 cents... It is a pity that an excellent software like digikam > >> can > >> not be used as a Lightroom alternative for a matter of standard-not > >> standard. > >> > >> > >> sorry for my english.. :) > >> > >> > >> > >> -- > >> Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189. > >> html Going to a naming scheme of "<basename>.xmp" instead of "<basename>.<orig- ext>.xmp" could break compatibility with Darktable, a raw convertor/editor that's used by several users active here. But can't you have a system where "<basename>.xmp" is used when there is no eligible sidecar with the other possible name present? (i.e. first check for presence of a sidecar with current naming, if not found try "<basename>.xmp") Remco |
Re: Lightroom to DigiKam: reading xmp files
|
|
In reply to this post by Remco Viëtor
On 07/01/18 14:49, Remco Viëtor wrote:
> > But, why do you have sidecar files in the first place? Because users want them, that's why it is configurable. Reason range from possible file corruption to easier backup (the latter is huge if you use incremental but not deduplicating backup programs) and probably there is more. > I cannot conclude /from that document/ that the scheme "<basename>.XMP" is the > *official* standard way of naming sidecar files (I don't have access to the ISO > standard documents). The ISO standards excludes these issues: The composition of a resource and the precise association of an XMP packet with a resource is beyond the scope of this International Standard. Where feasible, an XMP packet should be physically associated with the resource that it describes. Adobe publishes an extension standard that mandates "basename.xmp" but as they are a player in this temselves this is basically just saying "our solution is right". Read only support for basename.xmp should be fairly easy to do. Write support is hard as you either need to resolve conflicts (as metadata in db is per file, xmp will be per "basename") or implement this scheme where one xmp file has data for many pictures (haven't seen any spec yet standardizing this). This should either be done right (who has time and interest? I'd guess nobody) or just read only. |
Re: Lightroom to DigiKam: reading xmp files
|
|
In reply to this post by AndriusWild
This is why this thread exists (:=)))... Gilles Caulier 2018-01-07 15:01 GMT+01:00 Andrey Goreev <[hidden email]>:
|
Re: Lightroom to DigiKam: reading xmp files
|
|
In reply to this post by Remco Viëtor
I use sidecars for raw image files incl. DNG and video files e.g. MP4 'cause exiv2 isn't capable of writing into them. To be honestly I am not sure if digikam reads xmp on startup. I did not see any setting in digikam to set priorities for 1. Database 2. Sidecars 3. Embedded metadata. I might be wrong on this one but I think as long as you don't click "read metadata from sidecars" digikam won't see any changes. Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Remco Viëtor <[hidden email]> Date: 2018-01-07 6:49 AM (GMT-07:00) To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: Lightroom to DigiKam: reading xmp files > yes, this can be done for reading, with a priority : > > 1/ old naming scheme. > 2/ new naming scheme (LR) > > ... or vis versa. > > But the problem is not here. Look well my comment #11 > > https://bugs.kde.org/show_bug.cgi?id=278935#c11 > > Gilles Caulier > Oh, I realise that in the case of multiple existing sidecars with the same basenam you have a problem. Solvable in theory (XMP allows combining sidecar data for several image files/formats in one sidecar), but complicated to implement. But, why do you have sidecar files in the first place? In Digikam, as I see it, the main use is as an external place to save metadata linked to raw files (which are in principle unwritable safely). If you decide that you don't need to use a sidecar for jpeg, tiff, png, the problem would basically go away in a large part. So you could decide to have the <basename>.xmp scheme refer to raw files only. The more so as any information about editing operations is inherently non-portable to other programs anyway. Basically, the problem seems to be adapting Digikam to play nice with other programs. While that's always a good thing, how many users are in that position, other than e.g. a one-time import from lightroom to Digikam? And some other points: - https://discuss.pixls.us/t/linux-applications-and-their-non-standard-xmp-sidecar-naming-convention/2688 gives rules about the naming of sidecar files, but those are specified for /each/ base format, /not/ in a general rule. That document deals principally with /embedding/ XMP data in other files, and sidecars are mentioned more or less in passing; when you have no other option (e.g. MP2 files which don't provide for embedding XMP metadata). I cannot conclude /from that document/ that the scheme "<basename>.XMP" is the *official* standard way of naming sidecar files (I don't have access to the ISO standard documents). - LR seems to use sidecars for raw files *only*, not for .jpg, .dng and other writable formats. Both seem to indicate that sidecars are considered a last option when the metadata cannot be embedded/added/modified, and in that case "<basename>.XMP" works (as most derived formats *can* embed the XML data) Remco > 2018-01-07 13:52 GMT+01:00 Remco Viëtor <[hidden email]>: <...> > > > > Going to a naming scheme of "<basename>.xmp" instead of "<basename>.<orig- > > ext>.xmp" could break compatibility with Darktable, a raw convertor/editor > > that's used by several users active here. > > > > But can't you have a system where "<basename>.xmp" is used when there is > > no > > eligible sidecar with the other possible name present? (i.e. first check > > for > > presence of a sidecar with current naming, if not found try > > "<basename>.xmp") > > > > Remco |
|
|
In reply to this post by Gilles Caulier-4
Hello,
I saw that this patch was under review for v5.9.0. Is there any windows build that includes this? I'm trying to migrate from lightroom and all my xmp are ignored... If I understood correctly the description of the patch, an option to make dikiKam read the meta from filename.xmp instead of filename.nef.xmp should perfectly solve my issue. -- Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html |
Re: Lightroom to DigiKam: reading xmp files
|
|
Hi Ene, The patch from bug is not yet applied to any code. In fact this code is a proof of concept, far to be deployed in production, for the reason that i list in bug report. Note that bug is not closed, so no patch is applied to source code Gilles Caulier 2018-07-23 15:59 GMT+02:00 ene <[hidden email]>: Hello, |
|
|
Hello Gilles,
Thank you for your reply. I hope that it will make past the stage of proof of concept soon than :) Enea -- Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |