Exiv2 bug reports
caulier.gilles at gmail.com
Fri Mar 10 22:36:26 GMT 2017
This report is clear also :
With video file, DK in unstable. There is no other solution to disable
video metadata support as it's specified here :
2017-03-10 23:20 GMT+01:00 Andrey Goreev <aegoreev at gmail.com>:
> It was me who proposed to use bento4. I tried it and it worked well to
> import metadata from a text file as an atom to mp4.
> I think treating images and videos the same way is why exiv2 isn't
> working. For example, images would store creation date as "Date created"
> while videos would have it as "Date Encoded". Just an example.
> Sent from my Samsung Galaxy smartphone.
> -------- Original message --------
> From: Gilles Caulier <caulier.gilles at gmail.com>
> Date: 2017-03-10 2:52 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
> 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
>> yes, i agree. this is not the first time that Exiv2 team drop as well the
>> 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....
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Digikam-users