Bug 326997 - Some DNG files seem not to be recognized as such
Summary: Some DNG files seem not to be recognized as such
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Thumbs-RAW (show other bugs)
Version: 3.4.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-01 13:25 UTC by Romain Henriet
Modified: 2017-07-27 10:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.1.0


Attachments
Screenshots with different filters (589.45 KB, application/zip)
2013-11-01 13:25 UTC, Romain Henriet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Romain Henriet 2013-11-01 13:25:56 UTC
Created attachment 83268 [details]
Screenshots with different filters

When I try to filter using MIME type, some DNG photos are not considered to be raw files.
Examples (cf attachment): 
"No filter.jpg" : "130903_Camping!.dng" is shown if no filter is set
"No raw.jpg" : "130903_Camping!.dng" is shown too while "No raw" filter is active
"Dng only.jpg" : "130903_Camping!.dng" is hidden while other dng files are shown

A few files only are concerned by this bug, while most of dng photos are correctly recognized (all dngs come from the same camera : Pentax K-x).

Link to access to one dng file that is incorrectly filtered, and one that is correctly filtered :
http://dl.free.fr/edogGzFD1
Comment 1 caulier.gilles 2013-12-04 17:37:03 UTC
Which database you use ? SQLITE or MYSQL ?

Gilles Caulier
Comment 2 Romain Henriet 2013-12-04 19:57:58 UTC
I use SQLITE
Comment 3 caulier.gilles 2014-06-16 12:18:28 UTC
Not reproducible.

All DNG files from my huge collection are dropped on list when No RAW files filter is enabled...

I suspect a dysfunction from your Database file.

You you try to enable a new fresh collection with a new DB file to see if problem still reproducible ?

Gilles Caulier
Comment 4 Romain Henriet 2014-06-21 06:54:20 UTC
Well I can't reproduce this bug anymore, although I didn't create a new database...