[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #29 from glenn --- ! I look forward to using digiKam :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #28 from Maik Qualmann --- Git commit a5f0380220cbebb7247d535302670e6374179412 by Maik Qualmann. Committed on 09/10/2019 at 21:34. Pushed by mqualmann into branch 'master'. add new Option to use compatible file name for sidecar files M +1-0core/libs/metadataengine/dmetadata/dmetadata.cpp M +10 -0core/libs/metadataengine/engine/metaengine.cpp M +10 -2core/libs/metadataengine/engine/metaengine.h M +2-2core/libs/metadataengine/engine/metaengine_fileio.cpp M +4-1core/libs/metadataengine/engine/metaengine_p.cpp M +1-0core/libs/metadataengine/engine/metaengine_p.h M +5-0core/libs/metadataengine/engine/metaenginesettingscontainer.cpp M +1-0core/libs/metadataengine/engine/metaenginesettingscontainer.h M +11 -0core/utilities/setup/metadata/setupmetadata.cpp https://invent.kde.org/kde/digikam/commit/a5f0380220cbebb7247d535302670e6374179412 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #27 from glenn --- I've just realised this issue was raised against Linux. Is there any difference in behaviour regards xmp file naming, between Linux and Windows? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #26 from glenn --- Thanks for your quick response Maik. So digiKam will default to reading and writing to $BASENAME.xmp if it finds one already existing. That's very helpful to know. This still presents a problem for a typical use case, where the user imports and manages new images through digiKam but processes the RAW files in (say) Capture One. In this case digiKam will create $BASENAME.EXT.xmp files, which Capture One will not be aware of. A common workflow would be rating newly imported images in digiKam, and sorting by these in Capture One for editing (and even changing the ratings or some other metadata in the RAW processor. eg to indicate editing complete and ready for printing). It remains the case that user control over xmp file naming would be very helpful and open digiKam to other users. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #25 from Maik Qualmann --- Digikam reads and writes $BASENAME.xmp if the file already exists. If the file does not exist, digiKam creates $BASENAME.EXT.xmp and uses it. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 glenn changed: What|Removed |Added CC||gl...@dazedowl.uk --- Comment #24 from glenn --- Could someone clarify Comment 22? What does it meant by 'used', does it simply mean read? Perhaps I am missing it but I cannot find a way to write to a sidecar named $BASENAME.xmp, which is the use case that most people are concerned about when discussing interoperability (ie read _and_ write). For better or worse many RAW processors use $BASENAME.xmp, including Capture One (which doesn't have DAM features!), and so writing to these files from digiKam is an essential aspect of interoperability. If writing to $BASENAME.xmp is provided as an option it will greatly increase the appeal of digiKam to new users. Think of the glory, and the donations! I would happily make a donation if digiKam suited this use case (sadly, without that option this powerful application is useless to me). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Version Fixed In||6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #23 from Sebastien --- My mistake, it does indeed works, sorry for the wrong message. Thank you for your reactivity! Sebastien. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 caulier.gil...@gmail.com changed: What|Removed |Added Version|2.0.0 |6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 caulier.gil...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |REOPENED Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #22 from caulier.gil...@gmail.com --- Re-openned -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #21 from Maik Qualmann --- DigiKam definitely supports $BASENAME.xmp files in digiKam-6.0.0 if they are present they will be used. Otherwise please upload XMP files from Capture One, XnViewMP or ON1. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 Sebastien changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |FIXED CC||sebg.ph...@gmail.com --- Comment #20 from Sebastien --- Hello, Is it planned to publish the patch by Maik Qualmann? If I'm not wrong, digiKam 6.0 doesn't support $BASENAME.xmp files under windows (at least those created by Capture One, XnViewMP or ON1). digiKam seems very nice indeed but I cannot use it without this support. Thanks, Sebastien. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #19 from Maik Qualmann --- Git commit 8f2d1d2df23df8540c47971d8f487122ce256ccd by Maik Qualmann. Committed on 14/09/2018 at 17:08. Pushed by mqualmann into branch 'master'. use sidecar in LR format if available M +10 -0core/libs/dmetadata/metaengine.cpp https://commits.kde.org/digikam/8f2d1d2df23df8540c47971d8f487122ce256ccd -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #18 from Maik Qualmann --- Ok, Gilles You were faster. I also wanted to write that it only served to get feedback and he did not have to compile anything by himself. https://files.kde.org/digikam/ Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #17 from caulier.gil...@gmail.com --- knick, It's not much difficult, but if you never experienced that, We will provide an AppImage linux bundle for you. Maik, As your code is really simple, there is no risk to introduce side effects. I recommend to patch git/master as well. While this week end i will rebuild all bundles. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #16 from knick --- You're saying patching the source code and compiling the whole app with all it's dependencies relative easy? No miracle why linux doesn't make it's way to desktop users. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 Maik Qualmann changed: What|Removed |Added Attachment #109721|0 |1 is obsolete|| CC||metzping...@gmail.com --- Comment #15 from Maik Qualmann --- Created attachment 114950 --> https://bugs.kde.org/attachment.cgi?id=114950=edit sidecarForLR.patch It is actually relatively simple to support LR users, if a sidecar exists in LR format, it will be used. If not, the digiKam format. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935
knick changed:
What|Removed |Added
CC||kn...@byom.de
--- Comment #14 from knick ---
As windows user for ages I wanted to give dk another try and found that it
would just read meta data from my tiffs but none from my raw files. What a
mess!
Browsing the web I found a few discussions on this problem and finally arrived
here.
I always felt dropping the extension and adding ".ext" to a file name was a bad
decision by adobe. I sometimes stumbled in this trap too with my ".cr2" and
".nef" files using the same base name. But it is widely accepted since many
years and I have more than 350,000 side car files following this rule.
I also love the idea to allow side cars for all file types, even ".jpg",
".tiff" or whatever. Using side cars is much smarter than writing meta data
into the image files. Makes backup much smaller and faster :-)
So here's my suggestion to allow all thinkable naming schemes and leave the
decision to the users. There already exists a dialogue to add other extensions
like ".pp3". But this only can give "{basename}{ext}.pp3".
Why not drill this procedure and allow to type full templates like
"{basename}{ext}.ext" (used by dk)
"{basename}.ext" (the standard from adobe and widely used outside the linux
world)
"{basename}{ext}.pp3" (the sample in the dialogue in dk)
or even
"{subfolder}/{basename}{ext}.ext" (for people who love to browse their file
base and down't want to see the side cars)
and also allow to type any other combination the users might want.
Templates like
"tiff:{basename}{ext}.ext"
"jpg:{basename}{ext}.ext"
"nef:{basename}.ext"
"cr2:{basename}.ext"
would even allow to have different naming schemes for different file types.
Then make the top most template the default for writing if no other side car
can be found and try the list top down to find a side car for reading.
Thanx for reading, knick
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Please make XMP Sidecar |Please make XMP Sidecar |filename configurable |filename configurable ||[patch] -- You are receiving this mail because: You are watching all bug changes.
