Advanced search needs fixing, especially for ExposureTime

[jkm]

Advanced Search (Ctrl-F) is not really adequate to the needs of a program like XnViewMP, but it is all we have. And since it is all we have it really needs to be fixed with regards to searching for certain things.

Specifically

1. When clicking ... in the QuickFilter entry field to bring up Search, it does not pickup the current directory as it does if you hit Ctrl-F. You have to browse for it within the search dialog or copy/paste. Waste of time.

2. Searching by Exif:ExposureTime is very impaired.

2a. Metadata is in 1/x format, search field is in decimal. So you need a calculator to convert what you want to search for, like 1/160 to decimal.

2b. The search field is only 4 digits after the decimal point. This is deficient. Example: 1/160=0.00625 which requires 5 digits. You simply cannot search for a value like ExposureTime=1/350 without ridiculously creating a compound search, that it is >.002 AND <.003

3. Because searching on ExposureTime is crippled and often requires the ALL option, some ExposureTime values simply cannot be incorporated into certain searches. It is impossible. Example: Search for any .CRW or JPEG with an ExposureTime of 1/4000.

4. Since the built in fields are extremely limited, the search should support calling ExifTool, just like Labels and ToolTips do.

5. Saved Presets in Advanced Search ALWAYS contain the directory to be searched. This severely limits the utility of saved searches. After defining a complicated search, saving it, and trying to use it later in a different directory, you must go through the steps of browsing for the current directory you were in when hitting Ctrl-F.

So, solutions:

A. Fix the way the ... button launches Search to default to Current Directory.

B. The ExposureTime filed MUST be in 1/x format, just like it is shown in the metadata. The application should do the math. That will fix 2a, 2b, and 3 above.

C. Support the {ExifTool:property} method

D. Allow search presets to be saved with the option "Use Current Directory". Loading such a preset with that option will not overwrite the directory already filled in in the Advanced Search dialog.


Please, this search as it is simply cannot do some basic things. These enhancements/fixes are needed.

[xnview]

1. When clicking ... in the QuickFilter entry field to bring up Search, it does not pickup the current directory as it does if you hit Ctrl-F. You have to browse for it within the search dialog or copy/paste. Waste of time.
2a. Metadata is in 1/x format, search field is in decimal. So you need a calculator to convert what you want to search for, like 1/160 to decimal.
2b. The search field is only 4 digits after the decimal point. This is deficient. Example: 1/160=0.00625 which requires 5 digits. You simply cannot search for a value like ExposureTime=1/350 without ridiculously creating a compound search, that it is >.002 AND <.003
3. Because searching on ExposureTime is crippled and often requires the ALL option, some ExposureTime values simply cannot be incorporated into certain searches. It is impossible. Example: Search for any .CRW or JPEG with an ExposureTime of 1/4000.

i'll change the format for 1/x .

4. Since the built in fields are extremely limited, the search should support calling ExifTool, just like Labels and ToolTips do.

which important fields are missing?

5. Saved Presets in Advanced Search ALWAYS contain the directory to be searched. This severely limits the utility of saved searches. After defining a complicated search, saving it, and trying to use it later in a different directory, you must go through the steps of browsing for the current directory you were in when hitting Ctrl-F.

Thanks to your detailed description I can reproduce the problem.

[jkm]

1. When clicking ... in the QuickFilter entry field to bring up Search, it does not pickup the current directory as it does if you hit Ctrl-F. You have to browse for it within the search dialog or copy/paste. Waste of time.
2a. Metadata is in 1/x format, search field is in decimal. So you need a calculator to convert what you want to search for, like 1/160 to decimal.
2b. The search field is only 4 digits after the decimal point. This is deficient. Example: 1/160=0.00625 which requires 5 digits. You simply cannot search for a value like ExposureTime=1/350 without ridiculously creating a compound search, that it is >.002 AND <.003
3. Because searching on ExposureTime is crippled and often requires the ALL option, some ExposureTime values simply cannot be incorporated into certain searches. It is impossible. Example: Search for any .CRW or JPEG with an ExposureTime of 1/4000.

i'll change the format for 1/x .

Great, thank you! What about the ... button? At least optionally, that should pick up the current directory.

4. Since the built in fields are extremely limited, the search should support calling ExifTool, just like Labels and ToolTips do.

which important fields are missing?

For example, the following cannot be searched:
Metering Mode,Light Source,Color Space,White Balance,Contrast,Saturation,Sharpness,Lens Info,Lens Model,Digital Zoom Ratio

or ANY important MakerNotes properties, like:

Extender,Exposure Shift,Focus Mode,AI Subject Tracking Mode,White Balance 2,White Balance,Temperature,Noise Filter,Gradation,Picture Mode,Tone Level,Drive Mode,Roll Angle,Pitch Angle

5. Saved Presets in Advanced Search ALWAYS contain the directory to be searched. This severely limits the utility of saved searches. After defining a complicated search, saving it, and trying to use it later in a different directory, you must go through the steps of browsing for the current directory you were in when hitting Ctrl-F.

Thanks to your detailed description I can reproduce the problem.

I can understand why people might want to save the directory on a search, but I think it should be optional.

My suggestion on the EXIF and MakerNotes is this:

When a directory is first scanned, in a separate thread while the thumbnail is being generated, probe each file with ExifTool. The entire output can be cached in the database. In the case of MakerNotes, if you want to keep the parsing minimal (since the MakerNotes differs from one manufacturer to another), simply store all MakerNotes entries as <key>,<value> pairs. XnViewMP doesn't need to understand the MakerNotes, just have the data available for fast searching.

If the probe is done in the background when the folder is first scanned, the performance hit will not be noticeable to the user. If the user has the "create from original image" thumbnail option turned on, the ExifTool probe will be completed before the thumbnail is, so there will be no apparent delay.

When users want to search the MakerNotes, (against the <key>,<value> pairs you have stored) there are two easy options:
1. Make them type the name of the field (key) to match. Easy. A bit tedious for the user, but MUCH better than what we have now.
2. Auto-populate a drop-down list of keys based on the cached data; simple to do. But since this could conceivably cover the entire db with multiple camera manufactures, it could be a long list of available keys.

So much critical data about images is in the MakerNotes nowadays, this would be a huge improvement for XnViewMP.

Thank you very much for your work on this!

[xnview]

This problem is supposed to be fixed in XnView MP 1.9.3. Please check and confirm the bug fix here.

[jkm]

Current Folder from ... button: FIXED Thank you!

Exposure time 1/x format: FIXED Thank you!

Advanced Search presets saving folder: FIXED (no longer saves folder) Thank you!

Important fields missing: No improvement

Fields listed in earlier post:

For example, the following standard EXIF fields cannot be searched:
Metering Mode,Light Source,Color Space,White Balance,Contrast,Saturation,Sharpness,Lens Info,Lens Model,Digital Zoom Ratio

or ANY important MakerNotes properties, like:

Extender,Exposure Shift,Focus Mode,AI Subject Tracking Mode,White Balance 2,White Balance,Temperature,Noise Filter,Gradation,Picture Mode,Tone Level,Drive Mode,Roll Angle,Pitch Angle

It would be helpful to get things like White Balance and Lens Model on the pick list. A much longer list of fields is available for Labels, why not Search?

And it is incredibly important that a way is found to integrate searching MakerNotes. So much critical information is in those fields on modern cameras.

XnViewMP does not need to understand anything about MakerNotes, it does not need to decode them, and it does not need to be updated when manufactures put out new cameras or change MakerNotes formats. ExifTool will handle all that. XnViewMP just needs to store ExifTool's output in simple text-based <key>,<value> format.

I think comprehensive EXIF searching can be added with no performance impact visible to the user if the files are scanned when thumbnails are built and the EXIF data is stored in the database. The db can be used for more than just categories and ratings. This would be a tremendous improvement to XnViewMP.

[xnview]

Important fields missing: No improvement

Fields listed in earlier post:

For example, the following standard EXIF fields cannot be searched:
Metering Mode,Light Source,Color Space,White Balance,Contrast,Saturation,Sharpness,Lens Info,Lens Model,Digital Zoom Ratio

or ANY important MakerNotes properties, like:

Extender,Exposure Shift,Focus Mode,AI Subject Tracking Mode,White Balance 2,White Balance,Temperature,Noise Filter,Gradation,Picture Mode,Tone Level,Drive Mode,Roll Angle,Pitch Angle

Please make a new post for the suggestions