XnView Software

JohnFredC wrote:I think camera make and model should be indexed.

Yes, they are. Any lookup field is indexed (case insensitively) in the lookup table as well as its FK values, hence the query engine will use it. See closely my post about the lookup fields.

Thanks for the hint tough.

The table metatadata1 is more or less finished :

https://docs.google.com/spreadsheet/pub?key=0AnQycoc5pnW6dGhpc0RNVV80TzdwMEJnM1loNWdYR0E&output=html

Perhaps someone can give us an opinion?

About the Lookup fields which are present in the table above:

'Lookup' field type for the field ' foo ...

Let the user to choice which fields he want to store in the DB.

There are some headaches tied to this approach - some of them which I remember now:

- in which form one should store the fields (for ex. lookup fields like the EXIF:CameraModel or the Paths field which already exists in DB ...

While trying to move some big files (high resolution, gifs with many frames, etc...) looks like xnviewmp is done quite fast and tries to delete the original file while it's still trying to render in the preview. This causes a failed dialog to appear, clicking "retry" opens another one prompting you ...

...
Do you know how to calculate it using only EXIF data? ...


... From exiftool I had this (~/.ExifTool_config):
...
ScaleFactor35efl => {
Description => 'Scale Factor To 35mm Equivalent',
Notes => 'this value and any derived values may be incorrect if image has been resized',
Groups ...

... 1. Do you have the formulae? ...
Hello,
Some are already here (a link into the previous exiftool link- ~/.ExifTool_config ) ;-) :
http://owl.phy.queensu.ca/~phil/exiftool/config.html

...But about composite data/fields ... it will be IMHO for the future (After the v1.0 MP release) ;-)

I ...

Approx. one year ago on my Zenbook UX31A, I first had Windows 7 Home.
I installes XnViewMP and used the file association tool.
And it worked!

Windows 7 Enterprise SP 1 here. And it works. Istm that it has something to do either with rights either with other programs which put "somewhere else" in ...

Glad that you succeeded!

As an aside, the file association tool needs to be updated (at least) with most common raw formats:

Adobe (.DNG)
Canon (.CRW, .CR2)
Casio (.RAW)
Fuji (.RAF)
Hasselblad (.3FR) - supported? (the Hasselblad H4D's .fff format has problems)
Kodak (.DCR, .KDC) - supported ...

This post is RFC (Request For Comments) - Questions. (please comment my thoughts bellow)


Foreword:

I think that we'll have two+one tables:
- metadata1 for most used and most often - high-performance table - mainly the EXIF info
- metadata2 which will act like a L2 cache, mainly for big texts ...

It's typical during a software lifecylce that database modifications are needed. Typical handling for this is:
- Introduce a database version.


There is already (AFAIS) in DBInfo table.


- Newer XnView versions can update from any old database version to the current version. This is performed ...

...I think that we must introduce the concept of Unified Metadata Space which will hold only once each property of the image. The Unified Metadata Space is an in-database representation of the metadata regardless of the storage scheme (EXIF, IPTC, XMP et al.)...
+1 ... Interesting ...

... It ...

Fair enough for me. Use XnView as reader and not as viewer.

xnview wrote:

m.Th. wrote: Question: Which are the most important metadata fields for you for displaying and filter / search?

For displaying, all

LOL! nice one!

About 'Flash fired' field:
The idea is than the flash is usually used to highlight the foreground (less than ~ 5 meters), so usually the faces, so combined with IPTC keywords for a particular person it can be useful (search on rare cases)


Yeah, sure. The 'Flash' field has very low selectivity ...

If a shortcut has been assigned for a command (default or custom) and then you assign the same shortcut for another command, how XnViewMP should behave?

In the worst mode possible: Neither the first neither the second command will work anymore.

In order to make things work again, you must:
1 ...