Exiv2 bug reports

[Gilles Caulier]

In BQM, there is a tool to run external script for each file plug in a
queue.

Gilles Caulier

2017-03-11 0:12 GMT+01:00 Andrey Goreev <aegoreev at gmail.com>:

> Is there a way to add a launcher of external bash/python scripts to
> digiKam?
>
> Right now I am working on a bash script that compresses video files using
> ffmpeg and moving metadata atoms from the original to the output using
> bento4 (apparently some metadata gets lost during conversion even though
> there is an option in ffmpeg to preserve it).
>
> After that I want to write a script to read video file creation date
> (exiftool or mediainfo or both) and overwrite the wrong date that digiKam
> writes to XMP sidecar file.
>
> Next step will be reading tags (keywords) and people tags from XMP sidecar
> files and write them to video files using exiftool probably (this one
> should be easy to accomplish).
>
> Next step will be a script to read GPS location for video files from XMP
> sidecar and write it to video files using bento4.
>
> If I could call each script right from the context menu in digiKam that
> would help a lot.
> On 2017-03-10 03:36 PM, Gilles Caulier wrote:
>
> This report is clear also :
>
> https://bugs.kde.org/show_bug.cgi?id=376661
>
> With video file, DK in unstable. There is no other solution to disable
> video metadata support as it's specified here :
>
> https://bugs.kde.org/show_bug.cgi?id=375646
>
> Gilles Caulier
>
> 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 :
>>
>> https://github.com/wang-bin/QtAV/issues/820
>>
>> A digiKam user has proposed to use this tool :
>>
>> https://www.bento4.com/
>>
>> 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/20170311/08f482f7/attachment.html>