Exiv2 bug reports

Gilles Caulier caulier.gilles at gmail.com
Fri Mar 10 21:52:43 GMT 2017

yes. The problem is that metadata abstraction use the same interface for
image and video. It's homogeneous. If we want to use another frameworks for
video only, this will increase the complexity of DK code, so the
probability of bugs.

We have an entry in QtAV framework to have an interface to handle metadata
with ffmpeg, but we don't receive a favorable response from QtAV team :


A digiKam user has proposed to use this tool :


But it support only few video formats (mp4 mostly).

Gilles Caulier

2017-03-10 22:42 GMT+01:00 Andrey Goreev <aegoreev at gmail.com>:

> Would it be a big deal to switch to something else for video metadata
> support ?
> Sent from my Samsung Galaxy smartphone.
> -------- Original message --------
> From: Gilles Caulier <caulier.gilles at gmail.com>
> Date: 2017-03-10 2:26 PM (GMT-07:00)
> To: digiKam - Home Manage your photographs as a professional with the
> power of open source <digikam-users at kde.org>
> Subject: Re: Exiv2 bug reports
> Hi,
> yes, i agree. this is not the first time that Exiv2 team drop as well the
> report.
> I responded on Exiv2 bugzilla where Robin Mills said that digiKam is badly
> designed. Technically the crash is in Exiv2 while parsing metadata. The
> architecture is the same in digiKam for image and video. We don't see any
> dysfunction about images. I use it everyday. For video support, Exiv2 has a
> not stabilized code yet. This is the problem.
> The ultimate solution is to disable video metadata IO with Exiv2 from
> digiKam. I don't see no better way....
> Gilles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170310/c5cb2bf5/attachment.html>

More information about the Digikam-users mailing list