<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Hello Gilles</div><div><br></div><div>I just sent an email here but looks like it did not come through. Or maybe I forgot to press the send button. Typing it again anyways.</div><div><br></div><div>Thanks a lot for taking the time for this.</div><div><br></div><div>How about using ffmpeg for reading and writing video metadata? QtAV relies on it so it might in the appimage already.</div><div>Ffmpeg reads and writes QuickTime tags pretty well. We could use such tags as title, description, author, location (gps), keywords, rating (did I miss anything?) I did not have much luck writing keywords and rating but we could write keywords to the comment field and leave the rating in xmp sidecar for now.</div><div><br></div><div>Also looks like there is a way to do all this in C++ :</div><div><br></div><div>https://stackoverflow.com/questions/17024192/how-to-set-header-metadata-to-encoded-video</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"></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-06-10 5:06 AM (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>Hi all<br><br>Some news about the Video metadata support plan :<br><br>1/ I investigated the ExifTool way. The time latency introduced by<br>QProcess to run Perl script is too much important. It's acceptable for<br>some image, but for a large collection scan, it's inacceptable. Even<br>if metadata support is excellent, i will forget Exiftool...<br><br>2/ I take a look to MediaInfo. A lib is available de facto under<br>Linux. Even project management (source code, compilation rules,<br>compiler support) is not strong from my point of view, the code must<br>be compilable for all bundle. It sound like this project is maintained<br>under Windows, and other platform only provided as well. I'm not sure.<br>The interface is not to much complicated to wrap with digiKam core. So<br>i will study this way for the future.<br><br>3/ No news from Exiv2 since the 0.26 release. Only few bugzilla<br>entries have been created with some response, but no more. Sound like<br>Exiv2 switch progressively in frozen mode. I hope that a new<br>maintainer will be found quickly. We really need to see the video<br>supported completed, at least for read only request.<br>NOTE: do not ask me to do this job, in parallel of digiKam...<br><br>My plan : as we already do for unsupported RAW file by Exiv2, we use<br>libraw to get some metadata that library is able to parse. All are<br>stored in Exiv2 container, so all the rest of digiKam don't need to be<br>touch.<br>I want to do the same for MediaInfo, with a Cmake optional compilation rule.<br><br>This will provide a minimal support of video metadata, in read only,<br>until a solution will be found with Exiv2 project.<br><br>Important : i need a new entry in digiKam bugzilla to add video<br>support through MediaInfo. Thanks in advance.<br><br>Voilà. Constructive comments are welcome.<br><br>Best<br><br>Gilles Caulier<br><br><br>2017-04-28 16:24 GMT+02:00 Gilles Caulier <caulier.gilles@gmail.com>:<br>><br>><br>> 2017-04-28 15:31 GMT+02:00 NeiNei <neinei@gmx.net>:<br>>><br>>> Hi there,<br>>><br>>> the long awaited release of Exiv2 v0.26 should be released today according<br>>> to http://dev.exiv2.org/boards/3/topics/2830<br>>> However, I do not know wether or how it will change the situation for<br>>> DigiKam.<br>><br>><br>> Nothing news with Exiv2 0.26, as i already use current code from svn server<br>> in all bundle (so pre 0.26 release)<br>><br>><br>><br>>><br>>> As far as I understood Gilles thoroughly checks for alternatives in order<br>>> to ensure a working, evolving and reliable metadata editor for DigiKam.<br>>><br>><br>> yes. No code is done yet. I plan to make some demo code soon with Exiftool<br>> c++ interface, when time permit.<br>><br>> Gilles<br>><br></body></html>