https://bugs.kde.org/show_bug.cgi?id=385443
--- Comment #5 from Sebas ---
(In reply to caulier.gilles from comment #4)
> @sebas,
>
> digiKam 8.0.0 is out. This entry still valid with this release ?
>
> Best regards
>
> Gilles Caulier
Hey,
Yes this still applies.
--
Y
https://bugs.kde.org/show_bug.cgi?id=393313
--- Comment #8 from Sebas ---
Hello Gilles,
It's been a while...
Hope you are well.
It seems to still be there to a certain extent, but it feels a lot
faster/snappier than I remember. Good progress.
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=385443
--- Comment #2 from Sebas ---
This still applies. It is unnatural.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393313
--- Comment #4 from Sebas ---
This issue is about smart caching. Preloading the next x images from the
current one to eliminate loading time. Is Digikam changed on this aspect? It
feels a bit better now.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=399596
--- Comment #12 from Sebas ---
For me there is no easy way to test if this issue still applies.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406979
--- Comment #10 from Sebas ---
No crash in 7.0.0.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382706
--- Comment #10 from Sebas ---
Played around a bit: adding, editing, removing. No issue happened. We could
assume this issue is resolved, until it happens again. For me however, I am not
planning to use tags on NEF-files.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=382706
--- Comment #9 from Sebas ---
Hello, sorry for the time away. I will assign some time to play around with
this. Update soon.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=380876
--- Comment #19 from Sebas ---
Understood. So if I want to only write to sidecar for unsupported files I
should enable:
[X] Write to sidecar files: Write to XMP sidecar for read-only item only
And to later read from it, I guess also:
[X] Read from
https://bugs.kde.org/show_bug.cgi?id=406979
--- Comment #8 from Sebas ---
Hmm weird. Image displays well here in Windows Photo Viewer and is editable in
Paint.NET. Broken in IrfanView.
So this must be corruption...which is worrying...
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=406979
--- Comment #4 from Sebas ---
Done.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=380876
--- Comment #17 from Sebas ---
I removed tags from MOV-files in Digikam, then removed the tags from database.
Then, after starting with a new database due to the PNG-bug, the MOV-files came
back with the tags attached ánd enabled again.
--
You are
https://bugs.kde.org/show_bug.cgi?id=406981
--- Comment #3 from Sebas ---
By the way... this problem starts from around the filesize of the provided
sample. Smaller files do not suffer, and large files that have been trimmed
(causing a new file) by use of Quicktime on OSX also do not suffer
https://bugs.kde.org/show_bug.cgi?id=406981
--- Comment #2 from Sebas ---
Here is one: https://www.dropbox.com/s/8of0uzwmp8hh4v1/GOPR6539.MP4?dl=0
Will remove after a few days.
digikam version 6.1.0
CPU cores: 16
Eigen: 3.3.7
Exiv2: 0.27.0
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg
https://bugs.kde.org/show_bug.cgi?id=406979
--- Comment #2 from Sebas ---
I can mail it to you. Don't wish to put this one up in public.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398126
--- Comment #2 from Sebas ---
Kick. I would like to group all JPGs and NEFs in albums, but (correct me if I
am wrong) there is no easy way to do this except for doing it to every
individual album.
I suggest a global option to enable automatic grouping
https://bugs.kde.org/show_bug.cgi?id=406981
Bug ID: 406981
Summary: GoPro video thumbnails are just noise
Product: digikam
Version: 6.1.0
Platform: MS Windows
OS: MS Windows
Status: REPORTED
Severity: norm
https://bugs.kde.org/show_bug.cgi?id=406979
Bug ID: 406979
Summary: Specific PNG crashes Digikam
Product: digikam
Version: 6.1.0
Platform: MS Windows
OS: MS Windows
Status: REPORTED
Severity: crash
https://bugs.kde.org/show_bug.cgi?id=380876
Sebas changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=399596
--- Comment #7 from Sebas ---
Seems like I forgot to answer to Maik Qualmann's last reply.
I did fix the issue manually so it is a bit hard for me to recall the whole
thing, but let's try.
Digikam saves individually in image metadata (
https://bugs.kde.org/show_bug.cgi?id=382706
--- Comment #5 from Sebas ---
Is there a supposed fix?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399596
--- Comment #4 from Sebas ---
Using 6.x now.
I opened a photo in Notepad++ and found some interesting things.
Apparently Digikam saves tag trees in images apart from the tags themselves.
The latter ones can not be read by software like Windows
https://bugs.kde.org/show_bug.cgi?id=399596
--- Comment #3 from Sebas ---
Database maintenance on the tags with option 'sync metadata and database' ->
'from image metadata to database' actually made it worse. The wrong tag tree
was restored and probably all images with tho
https://bugs.kde.org/show_bug.cgi?id=399596
--- Comment #2 from Sebas ---
After clearing all tags from the wrong tag tree from the images and applying
tags from the right tree format it seems to go good with the images, but... the
tag tree format from the example keeps coming back. Empty of
https://bugs.kde.org/show_bug.cgi?id=399596
Bug ID: 399596
Summary: Tag tree keeps reverting back to incorrect format
after re-adding collection
Product: digikam
Version: 5.9.0
Platform: MS Windows
OS: MS Wi
https://bugs.kde.org/show_bug.cgi?id=399594
Bug ID: 399594
Summary: Collection being thrown away again and again
Product: digikam
Version: 5.9.0
Platform: MS Windows
OS: MS Windows
Status: REPORTED
Severit
https://bugs.kde.org/show_bug.cgi?id=398126
Bug ID: 398126
Summary: Group feature works across albums (undesired
behaviour?)
Product: digikam
Version: 5.9.0
Platform: MS Windows
OS: MS Windows
St
https://bugs.kde.org/show_bug.cgi?id=382706
--- Comment #3 from Sebas ---
I am not sure. With 5.9.0 I've been able to tag NEF's for months now without
problems...until...yesterday. After tagging a crash occurred and after
restarting a certain part of my tag tree had moved to some oth
https://bugs.kde.org/show_bug.cgi?id=393313
--- Comment #2 from Sebas ---
>From thumbnails select preview.
A bar shows up at top.
I make the bar as minimal as possible for more overview and bigger main
picture. Could this be made a preference?
Then start moving right on PNG's of 60-14
https://bugs.kde.org/show_bug.cgi?id=393313
Bug ID: 393313
Summary: Next-function sometimes goes next image, other times
it scrolls the bar
Product: digikam
Version: 5.9.0
Platform: MS Windows
OS: MS Windows
https://bugs.kde.org/show_bug.cgi?id=386910
Bug ID: 386910
Summary: Collection disappeared
Product: digikam
Version: 5.7.0
Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=385443
Bug ID: 385443
Summary: 'Auto toggle parents' unnatural behavior when removing
a tag
Product: digikam
Version: 5.7.0
Platform: MS Windows
OS: MS Windows
https://bugs.kde.org/show_bug.cgi?id=384182
Sebas changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=384182
--- Comment #2 from Sebas ---
That is what I was looking for. I had no idea it was behind that
menu/description.
Is there any way to turn this on by default for albums instead of having to
group manually?
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=384182
Bug ID: 384182
Summary: Combining JPEG and RAW in thumbs view
Product: digikam
Version: 5.7.0
Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
Severity: w
https://bugs.kde.org/show_bug.cgi?id=382706
--- Comment #1 from Sebas ---
I see the tags were saved to the NEF, despite the crash.
I removed half of the tags from the NEF's and again: crash. This time only the
gui specific preferences were lost. In a third try, when the last tag dat
https://bugs.kde.org/show_bug.cgi?id=382707
Bug ID: 382707
Summary: Order of albums different between tree view and
thumbnail view
Product: digikam
Version: 5.7.0
Platform: MS Windows
OS: MS Windows
https://bugs.kde.org/show_bug.cgi?id=382706
Bug ID: 382706
Summary: Assigning tag to NEF-file results in crash + config
disappearing
Product: digikam
Version: 5.7.0
Platform: MS Windows
OS: MS Windows
https://bugs.kde.org/show_bug.cgi?id=374356
--- Comment #5 from Sebas ---
In 5.7 (thanks for that) I see:
- Album -> Open in File Manager
- Item -> Open with Default Application
Two nice features but just not close enough.
What I am looking for (and I think wildcowboy too) is a feat
https://bugs.kde.org/show_bug.cgi?id=374356
Sebas changed:
What|Removed |Added
CC||djse...@home.nl
--- Comment #3 from Sebas ---
+1 for
https://bugs.kde.org/show_bug.cgi?id=368734
Sebas changed:
What|Removed |Added
CC||djse...@home.nl
--- Comment #16 from Sebas ---
I just
https://bugs.kde.org/show_bug.cgi?id=380876
--- Comment #2 from Sebas ---
Yes that's not the problem in this bug. The problem is that rescanning a
tagless file still keeps Digikam displaying the removed tags, so Digikam must
be loading them from database.
Please read description again.
--
https://bugs.kde.org/show_bug.cgi?id=380876
Bug ID: 380876
Summary: Tags in Digikam DB maintained after being removed from
file and file re-scanned
Product: digikam
Version: 5.6.0
Platform: MS Windows
OS: MS
https://bugs.kde.org/show_bug.cgi?id=379918
Sebas changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=379922
--- Comment #6 from Sebas ---
There is a default tag rule, this one:
Metadata Subspace: EXIF
Name: Exif.Image.XPKeywords
Special Options: NO_OPTS
Alternative name:
Alternative special options: NO_OPTS
Separator: ;
Set Tags Path: [V]
The rule is
https://bugs.kde.org/show_bug.cgi?id=379922
--- Comment #4 from Sebas ---
I did some deeper research. The field where Windows Explorer saves the tag has
the name "XPKeywords" according to IrfanView. DigiKam has a metadata tag entry
for this, but searching a bit further brought thi
https://bugs.kde.org/show_bug.cgi?id=379922
--- Comment #2 from Sebas ---
Thank you for the link. I tried 5.6.0 and it does not seem to be fixed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379922
Bug ID: 379922
Summary: Digikam won't remove tags set by Windows Explorer
Product: digikam
Version: 5.5.0
Platform: MS Windows
OS: unspecified
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=379918
Bug ID: 379918
Summary: Digikam writing tags in wrong order
Product: digikam
Version: 5.5.0
Platform: MS Windows
OS: unspecified
Status: UNCONFIRMED
Severity: no
49 matches
Mail list logo