I tried using the Unity Lens File search for *.*
and filtering by Last Modified=All, Type=Videos, and Size=All, but found nothing, although I know there are some .3gp
files in my Pictures
folder. I know that I have numerous video files on another drive mounted on the file system as well.
I compiled a list of likely extensions and I tried numerous iterations of the find
command, utilizing these with:
find ./ -name "*.ext" -o (etc, etc, ad nauseum)
with no luck whatsoever.
What is the solution?
Alternative: search on file:
or if you only want the filenames ...
-N, --no-pad
: Don't pad filenames-i, --mime
: Causes the file command to output mime type strings rather than the more traditional human readable ones. Thus it may say 'text/plain; charset=us-ascii' rather than 'ASCII text'. In order for this option to work, file changes the way it handles files recognized by the command itself (such as many of the text file types, directories etc), and makes use of an alternative 'magic' file. (See the FILES section, below).The FILES section points to:
file
is slowwwwwwwwwwwwwwwww though (it will open all the files find finds) but has the advantage you do not need to add all those extentions.Using locate:
I imagine this could be done as a 1-liner but it seemed a bit cumbersome so I created a script for ease of launching and editing and called it
findvids.sh
This is what worked for me.Note: I may not have covered ALL the video file types, but I'm sure I have most of them. One notable exception is .mkv as that is the target format for the project and I don''t need to find the files that have already been processed. It should be very simple to add additional formats (extensions) to the script to suit your needs by examining the pattern and adjusting accordingly while maintaining the quotes at the beginning and end of the expression. Note that files you don't have permission to read will not be found.
Edit based on comment: The
$
at the end of the extension signifies that the search term must be found at end of line. if we wanted to match the beginning of the line instead we'd use^
before the term we intend to match. You can find these anchors explained in more detail here.I did a speed comparison to using locate and the results were:
vs.
Unexpectedly find is faster. I'll be using this approach.
Edit: further testing indicates that locate was faster on a different machine. I think my initial speed test results were bunk due to caching.
Sources:
man find
man grep
https://stackoverflow.com/questions/7190565/unix-find-multiple-file-types
In the
find
command in Elder Geek's answer, case sensitivity caught me out. My devices seem to have used capitals quite often when taking videos etc. Just need to add-i
option to grep to fix this:Here is a reliable and simple answer composed of
find
,file
andgrep
:Note that it would not work for path name which contains
: image/
.