https://bugs.kde.org/show_bug.cgi?id=420939
--- Comment #37 from tagwer...@innerjoin.org --- (In reply to Scott from comment #36) > ... The result of, 2:23:21.801467 is correct. I tested the remaining 3 > files in my test directory and they were also correct ... That's reassuring... > ... Every file is the result of me muxing the RAW data streams (video, > audio and subtitles) into one of the 3 containers. Every audio and subtitle > stream is broken down to its component parts and then rebuilt to the format > I want ... and ... > ... If I look at UHD files where the standards are > much tighter, eg all video files I have use the h.265 video codec the > situation is still the same, some indexed, some not ... It sounds as if you have complete control of how you build the files. 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). > Were you getting these messages when you were running "balooctl purge"? In > this case you wouldn't get the command prompt repeated after the message. > > It's over a year since I raised the issue, I cannot recall that level of > detail. Accepted :-) For me, sometimes last week is hard... > How are you quoting in your replies? There's a [reply] link in the top right of each of the comments. Click on that and the comment magically appears in the Additional Comments box as quoted text. It's just copied there, you can cut/paste/re-sort the text to weave in your replies as you see fit. I do check with the "Preview" tag to see whether what I've typed formats OK. -- You are receiving this mail because: You are watching all bug changes.
