https://bugs.kde.org/show_bug.cgi?id=415719
--- Comment #36 from caulier.gil...@gmail.com --- In fact the libheif API do not provide any progress info while encoding. Only the loop for pixels formatting to be encoded as x265 is handle in DK code and has progress info of course. This is what you see until 70% of the job. The 30% remaining is the real x265 encoding. So, if a improvement must be done, it's in libheif: https://github.com/strukturag/libheif/issues/161 ==> look like this bug is reported by... me few month ago (:=)))... So please comment on this files directly... About the performance, x265 is really a high computation stage. It's done by another library which is called in fact by the top-level library libheif : libx265 https://bitbucket.org/multicoreware/x265/wiki/Home Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
