Hi,
Is there any option to limit the range of content search?
Currently content search searches every contents of a file but i want to limit the search within a certain range.
Say, i want to search within the first 80 kilobytes of data of every mkv files:
it can be something like:
ext:mkv utf8content:"authorName" contentrange:1-80000
or, if i want to search within 2048th byte to 8253th byte, it can be something like:
ext:mkv utf8content:"authorName" contentlimit:2048-8253
a use case:
It can be very useful to search metadata in large video files where most of the useful information remains within the first few kilobytes.
So, in such cases if content search is limited within some kilobytes, the results would come very fast and will save a lot of time.
And again, many thanks for this amazing software.
Content search with range limit
Re: Content search with range limit
Everything 1.5 has native support for mkv properties.
Everything 1.5 also has:
content-offset:
content-max-size:
For example:
ext:mkv content-max-size:80000 utf8content:"authorName"
ext:mkv content-offset:2048 content-max-size:6205 utf8content:"authorName"
Everything 1.5 also has:
content-offset:
content-max-size:
For example:
ext:mkv content-max-size:80000 utf8content:"authorName"
ext:mkv content-offset:2048 content-max-size:6205 utf8content:"authorName"
Re: Content search with range limit
void wrote: ↑Wed Dec 21, 2022 9:54 pm Everything 1.5 has native support for mkv properties.
Everything 1.5 also has:
content-offset:
content-max-size:
For example:
ext:mkv content-max-size:80000 utf8content:"authorName"
ext:mkv content-offset:2048 content-max-size:6205 utf8content:"authorName"
Hi void,
Lots of thanks, this worked perfectly.
I am using Everything 1.5.0.1331a and i checked all the items in the Help menu and did not find these functions, it seems a lot of very useful functions are implemented but not there in the Everything menu's Help files.
Also, there can be any custom text embedded in mkv as metadata, so mkv properties might not work in such cases but limiting with "content-offset" and "content-max-size" solves this particular problem well.
Many thanks!