Find All Images

[famadorian]

Does this application have a nice way to find all images in a directory?

I know I can do an extension search, like *.png, *jpg *jpeg and so on, but does it have some smart filter to find all image extensions or all files containing images, even files without extensions?

Any other program I can use if not?

[Kilmatead]

There is a default filter for images called {pictures}. If you either type that (including the {-braces-}) into the addressbar it will filter all images in the current folder. If you press <Ctrl+F> and enter {pictures} into the "Named:" field, then it will return all image files in the current folder and all subfolders thereof.

You can also just hit <Ctrl+H> or <Alt+H> and enter {pictures} to apply the dedicated filter.

The {pictures} filter is defined under Tools -> Advanced Options -> Global (tab) -> File Types (it's all the way at the bottom), alongside filters for {documents}, {audio files}, {video files}, etc. This allows you to add any extra filetypes to the filter which you may need, such as .DDS images, etc which may not be included by default.

There is no way to search for images within files that don't have extensions as that would require binary deconstruction of every single file - such a search would probably only be possible using dedicated 3rd-party image software, though I don't know of any which offer that very specialised function.

[famadorian]

Ok, great; I will try thanks.

Btw, in GNU/Linux, you could do:

find . -type f -exec file {} \; | grep -o -P '^.+: \w+ image'

And it will find all image files, no matter what the extension is;)

[nikos]

the easiest way to do this would be to use the AUTOFILTER button on the toolbar, one of the categories is for images

[Kilmatead]

Windows has no built-in equivalent of Linux's 'file' utility - Windows was built from the ground-up on the extension-based paradigm of filetype identification and rather staunchly sticks to it as an integral part of the shell.

You can, however, find equivalent ports of 'file' for Win32 via projects like Cygwin, TrID, and File for Windows. Cygwin being the most widely-known function set, but I can't speak to the efficacy of any of them.

[Enternal]

Just to note but TrID does not count. That tool is simply a file type identification tool and basically it just finds certain characteristics of file types (rar, iso, jpg, png, lzh, and so on) to help you identify files. It's very useful though! Have encountered various files without any extensions and used it to help me identify what file it is. Here is a sample output for a recent file that I used it on that had no extension:

Code: Select all

Collecting data from file: D:\Downloads\TaskScheduler
 81.0% (.DLL) Generic .NET DLL/Assembly (238132/4/30)
  9.4% (.EXE) Win64 Executable (generic) (27653/43/4)
  4.4% (.SCR) Windows Screen Saver (13102/52/3)
  2.2% (.DLL) Win32 Dynamic Link Library (generic) (6578/25/2)
  1.5% (.EXE) Win32 Executable (generic) (4508/7/1)

It's so useful that I made a little script that integrates it with another *cough* software that I can use to update its database or run it on a currently selected files and stuff.
.
.
.
Yeah, I'm getting off topic. Back on topic... yeah Cygwin and File for Windows should do.

[Kilmatead]

Just to note but TrID does not count. That tool is simply a file type identification tool and basically it just finds certain characteristics of file types

Umm... how does that "not count"? That's the whole point, isn't it... if you (for some devious reason) have a file without an extension, a tool that claims to "find characteristics" to identify that type would seem like a kosher thing to me. Or does TrID require you to already know the filetype before telling you what it is? Which would seem more than a little weird... but par for the course with computers...

[Enternal]

Oh! Yes that was my mistake haha. What I was thinking is a bit different. What I thought famadorian was trying to say was that "file", the Linux tool, is able to find and list all image files regardless of the actual file extension. In that case, TrID is not the same since it can't find and list files as it's only purpose is to state what the file that is being inputted is. Now that I look a closer look at the actual script that famadorian, he/she is actually using several tools to do all that (find, file, and grep) and in this case, "file" was specifically used to find what the type of file being inputted is.

Either way, the fact remains that TrID is cool! ... at least to me it is...