audio-bits-per-sample:24 audio-sample-rate:96000and similar
audio-sample-rate:44100or for dealing with whole other task e.g.
video-track-count:<1When chosen, such Bookmarks work very slowly, because Everything needs to check those specific Properties of all files, not just the multimedia ones. But this can me averted by going to
Tools > Options > Indexes > Properties
and adding [for those explanatory Bookmarks]
Audio Bits Per Sample
Audio Sample RateVideo Track Countwith selected option Include Files and then specifying in the field of Include only files only file formats of interest. By default Everything puts in this field very limited numbers of formats - and thus I expanded them to include all the multimedia formats that I use daily
But that got me wondering: why limit such lists to just frequently used formats and not expand them to all multimedia formats that are known to me?
Or going one step further: why not simply leave that field empty? I assume this would cause all files to be checked - and thus I would not have to bother in the feature with adding to those lists new / more file formats. So far this overkill makes sense, as long as it is merely few of Properties that are being indexed; I reckon
But what about taking the ultimate step: why not just add every possible Property there is and for every possible file and folder? If I will limit myself at previous step, then in the future when I will add indexation of some Property for also all files, then Everything will have to go again through all of my files, right? So why not order Everything to go through entirety of them once and for all? Or would that result with my database to swell from ~1.25 GB to possibly tens of GBs and also require as much RAM to be handled later on? Is the time required to process so thoroughly every item also a profound factor to be considered - or is that happening so fast, that popping into existence of new items on my volumes will not cause Everything to choke itself and / or Windows?