Properties - Include only, excludes all else

[therube]

Properties - Include only, excludes all else


i have Length Property indexed for video: files,
Length column is displayed

if i switch to Audio filter, Length column is still there,
but lazy-load does not occur, nor can i Read Extened Information

- must be me, also - why?


> (Property) Include only
> also Excludes all that are NOT Include only,
> such that neither lazy-load, nor Read Extended Information,
> will gather any NOT Include only files (file types)

is that expected?
or should a 'Read Extended Information' gather it regardless ?


Or is there a way to gather this data for non-indexed file types?

Code: Select all

COMMAND 41064
db_query_read_extended_info_on_selection(): 0.000040 seconds
ready
DB_WAIT: _db_ready_proc waiting for _db_read_extended_info_thread_proc...
DB_WAIT: _db_ready_proc waited 0.003316 seconds
new results 390948

(but nothing is actually gathered
- oh, & was not looking to gather 390K, but since i knew nothing would happen, i was OK in attempting it )

[therube]

(on a related note - perhaps)

so once again, had a need to see non-indexed Length of audio: - in a Profile where video: is indexed

& that was for not, as i couldn't load the Lengths of audio files

so i tried Read Extended Information - to no avail*
it was about 10,000 audio files, i believe, that i wanted to pull Length on
(actually i wanted to, at the onset, lazy-load it)

anyhow, on realizing i wasn't going to get wanted Lengths that way,
i simply (hard) deleted those 10K files


*somewhere along the line, i realized the Everything is re-indexing my video: files

something triggered that re-index, but i'm not sure what?
did my attempt at Read Extended Information do it?
pretty sure my Filter had been set to Everything,
but my REI want was with the particular set of filtered files that i was looking at
(which were audio: types, even though the Filter was Everything)


so as it's re-indexing, i'm thinking... what to do (cause it will take a long time)?
Quit & throw in the backup.db (thinking that it would then only need to pick up on "changes")

backup.db itself was almost 2 months old (last time i Quit Everything, i gather)
but i did have a current backup of the (current) .db - from the morning
(& as it was, the .db hadn't written to disk in the interim either - IOW, my backup & .db on disk were identical)

so with that, figured i'd Quit Everything & throw in the back up copy of .db
(& i changed one of the .ini settings relating to indexing to =0)

but when i restarted Everything, to my surprise it again was wanting to reindex (Length Property)?
i could understand where it might need to go out get the most recent files, but this was more then that,
& by looking at Length (or lack thereof) i could see that it not just more recent files, but also older files
that hadn't changed in any way, that it was going after

now, i'm pretty certain that this indexing, while relatively prolonged, while not a "just pick up on a few things missed",
it also was not a "start over from the beginning" kind of thing
(if i remember, maybe it had ~14K files that it had in its queue)


that was all kind of, unexpected.