https://bugs.kde.org/show_bug.cgi?id=420939
--- Comment #31 from tagwer...@innerjoin.org ---
(In reply to Scott from comment #30)
> ... just to confirm, what is the correct config setting/syntax to
> enable content indexing:
> 1/ Remove the line, only basic indexing=true, or,
> 2/ Include the line, only basic indexing=false
Yes. Or go through "System Settings > Search > File Search" and you'll see an
"Also index file content" checkbox.
> It is clear that baloo should index duration (the play time of a music
> piece) as is evidenced by the selectable field in Dolphin, Audio>Duration.
The question is, where has the "duration" information got lost.
>From your screenshot (with balooshow), baloo hasn't extracted it. On to the
next step...
If you run 'exiftool' on the file, you should see if the information is there
in the file. If it is, then there's a bug in the extractor. If exiftool does
not show the info, then maybe there's an issue with the file.
A useful comparative test is to download and try a different MP3 file...
In general I see the "Duration" listed for the MP3's I've checked (in Dolphin
and listed by "balooshow -x" and exiftool). I don't see much info for videos (a
little and maybe not sufficient) even with exiftool.
I think yes, it's good that baloo tries to extract embedded metadata from the
files. However, it's clearly a horrible, messy job to have to do.
As far as I remember I installed exiftool on Neon with:
sudo apt install libimage-exiftool-perl
It is handy, solid and straightforward
--
You are receiving this mail because:
You are watching all bug changes.
