https://bugs.kde.org/show_bug.cgi?id=420939

--- Comment #38 from Scott <shagooser...@gmail.com> ---
Quotes - The reply button only appears if you are logged in, thought I was
logged in because I could post.


> Thinking of the group who decides to trace the problem in the code. The aim
> would be to create something "minimal" that works with ffprobe and fails
> when being indexed (which I assume fails in ffmpegextractor...). They would
> need "small examples" of what's failing (small enough that can be uploaded
> as attachments).

I can understand the requirement for small, easy to manipulate data sets that
can be uploaded as an attachment and I can produce small files but the site
file size upload limit makes this unrealistic in this case. All of my UHD
movies, which you indicated an interest in, have much more data in them for 1
second of play time than 4000 KB. Even low quality HD files will blow past the
limit in a few seconds.

I can reduce the file size by cutting out a piece of a file which would
maintain it's characteristics, to reduce a file's size by reducing the quality
requires transcoding which will fundamentally alter the the file's
characteristics or properties.

Regarding your purge question, I looked at the first attachment, output of
running baloo purge, and that information appears there.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to