<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>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.</div><div><br></div><div>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.</div><div><br></div><div id="composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Gilles Caulier <caulier.gilles@gmail.com> </div><div>Date: 2017-03-10 2:52 PM (GMT-07:00) </div><div>To: digiKam - Home Manage your photographs as a professional with the power of open source <digikam-users@kde.org> </div><div>Subject: Re: Exiv2 bug reports </div><div><br></div></div><div dir="ltr">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.<div><br></div><div>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 :</div><div><br></div><div><a href="https://github.com/wang-bin/QtAV/issues/820">https://github.com/wang-bin/QtAV/issues/820</a><br></div><div><br></div><div>A digiKam user has proposed to use this tool :</div><div><br></div><div><a href="https://www.bento4.com/" rel="noreferrer" target="_blank" style="font-size:16px">https://www.bento4.com/</a><br></div><div><br></div><div>But it support only few video formats (mp4 mostly).</div><div><br></div><div>Gilles Caulier</div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-03-10 22:42 GMT+01:00 Andrey Goreev <span dir="ltr"><<a href="mailto:aegoreev@gmail.com" target="_blank">aegoreev@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Would it be a big deal to switch to something else for video metadata support ?</div><div><br></div><div><br></div><div><br></div><div id="m_-7189239998302453729composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><div class="h5"><div><br></div><div style="font-size:100%;color:#000000"><div>-------- Original message --------</div><div>From: Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com" target="_blank">caulier.gilles@gmail.com</a>> </div><div>Date: 2017-03-10 2:26 PM (GMT-07:00) </div><div>To: digiKam - Home Manage your photographs as a professional with the power of open source <<a href="mailto:digikam-users@kde.org" target="_blank">digikam-users@kde.org</a>> </div><div>Subject: Re: Exiv2 bug reports </div><div><br></div></div><div dir="ltr">Hi,<div><br></div><div>yes, i agree. this is not the first time that Exiv2 team drop as well the report. </div><div><br></div><div>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.</div><div><br></div><div>The ultimate solution is to disable video metadata IO with Exiv2 from digiKam. I don't see no better way....</div><div><br></div><div>Gilles</div></div>
</div></div></div></blockquote></div><br></div>
</body></html>