Re: Exiv2 bug reports
Locked
 
|
Hello Gilles 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. Thanks a lot for taking the time for this. How about using ffmpeg for reading and writing video metadata? QtAV relies on it so it might in the appimage already. 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. Also looks like there is a way to do all this in C++ : https://stackoverflow.com/questions/17024192/how-to-set-header-metadata-to-encoded-video Sent from my Samsung Galaxy smartphone. -------- Original message -------- From: Gilles Caulier <[hidden email]> Date: 2017-06-10 5:06 AM (GMT-07:00) To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: Exiv2 bug reports Some news about the Video metadata support plan : 1/ I investigated the ExifTool way. The time latency introduced by QProcess to run Perl script is too much important. It's acceptable for some image, but for a large collection scan, it's inacceptable. Even if metadata support is excellent, i will forget Exiftool... 2/ I take a look to MediaInfo. A lib is available de facto under Linux. Even project management (source code, compilation rules, compiler support) is not strong from my point of view, the code must be compilable for all bundle. It sound like this project is maintained under Windows, and other platform only provided as well. I'm not sure. The interface is not to much complicated to wrap with digiKam core. So i will study this way for the future. 3/ No news from Exiv2 since the 0.26 release. Only few bugzilla entries have been created with some response, but no more. Sound like Exiv2 switch progressively in frozen mode. I hope that a new maintainer will be found quickly. We really need to see the video supported completed, at least for read only request. NOTE: do not ask me to do this job, in parallel of digiKam... My plan : as we already do for unsupported RAW file by Exiv2, we use libraw to get some metadata that library is able to parse. All are stored in Exiv2 container, so all the rest of digiKam don't need to be touch. I want to do the same for MediaInfo, with a Cmake optional compilation rule. This will provide a minimal support of video metadata, in read only, until a solution will be found with Exiv2 project. Important : i need a new entry in digiKam bugzilla to add video support through MediaInfo. Thanks in advance. Voilà. Constructive comments are welcome. Best Gilles Caulier 2017-04-28 16:24 GMT+02:00 Gilles Caulier <[hidden email]>: > > > 2017-04-28 15:31 GMT+02:00 NeiNei <[hidden email]>: >> >> Hi there, >> >> the long awaited release of Exiv2 v0.26 should be released today according >> to http://dev.exiv2.org/boards/3/topics/2830 >> However, I do not know wether or how it will change the situation for >> DigiKam. > > > Nothing news with Exiv2 0.26, as i already use current code from svn server > in all bundle (so pre 0.26 release) > > > >> >> As far as I understood Gilles thoroughly checks for alternatives in order >> to ensure a working, evolving and reliable metadata editor for DigiKam. >> > > yes. No code is done yet. I plan to make some demo code soon with Exiftool > c++ interface, when time permit. > > Gilles > |
|
|
Here is my initial email. :) Hello Gilles, Thank you for taking the time for this.How about ffmpeg? QtAV relies on it so it is probably already a part of the appimage. What do you think? Best regards, Andrey On Sat, Jun 10, 2017 at 5:06 AM, Gilles Caulier <[hidden email]> wrote: Hi all |
|
|
Hi Andrey,
Yes, QtAV use ffmpeg, and ffmpeg is an indirect dependency to digiKam. I like the link to stackoverflow. This can mean that writting metadta to video files can be done easily with ffmpeg. I think reading must be true also... Look this report done to QtAV bugzilla : https://github.com/wang-bin/QtAV/issues/820 This entry must be implemented in QtAV. It's really important. Comment in this entry to promote the feature to QtAV developers. Gilles Caulier 2017-07-06 22:48 GMT+02:00 Andrey Goreev <[hidden email]>: > Here is my initial email. :) > > Hello Gilles, > > Thank you for taking the time for this. > > How about ffmpeg? QtAV relies on it so it is probably already a part of the > appimage. > ffmpeg can read and write QuickTime tags ( > https://developer.apple.com/library/content/documentation/QuickTime/QTFF/Metadata/Metadata.html#//apple_ref/doc/uid/TP40000939-CH1-SW43 > ) very well. > I think all we need is to read/write: > 1. Creation date > 2. Title > 3. Description > 4. Keywords (tags) > 5. Location (GPS) > 6. Rating > 7. Author > > I could not figure out how to write keywords and rating using ffmpeg but all > the rest it can do. > We could write keywords to the field "comments" instead. > Rating..we can leave without it > What do you think? > > Best regards, > Andrey > > On Sat, Jun 10, 2017 at 5:06 AM, Gilles Caulier <[hidden email]> > wrote: >> >> Hi all >> >> Some news about the Video metadata support plan : >> >> 1/ I investigated the ExifTool way. The time latency introduced by >> QProcess to run Perl script is too much important. It's acceptable for >> some image, but for a large collection scan, it's inacceptable. Even >> if metadata support is excellent, i will forget Exiftool... >> >> 2/ I take a look to MediaInfo. A lib is available de facto under >> Linux. Even project management (source code, compilation rules, >> compiler support) is not strong from my point of view, the code must >> be compilable for all bundle. It sound like this project is maintained >> under Windows, and other platform only provided as well. I'm not sure. >> The interface is not to much complicated to wrap with digiKam core. So >> i will study this way for the future. >> >> 3/ No news from Exiv2 since the 0.26 release. Only few bugzilla >> entries have been created with some response, but no more. Sound like >> Exiv2 switch progressively in frozen mode. I hope that a new >> maintainer will be found quickly. We really need to see the video >> supported completed, at least for read only request. >> NOTE: do not ask me to do this job, in parallel of digiKam... >> >> My plan : as we already do for unsupported RAW file by Exiv2, we use >> libraw to get some metadata that library is able to parse. All are >> stored in Exiv2 container, so all the rest of digiKam don't need to be >> touch. >> I want to do the same for MediaInfo, with a Cmake optional compilation >> rule. >> >> This will provide a minimal support of video metadata, in read only, >> until a solution will be found with Exiv2 project. >> >> Important : i need a new entry in digiKam bugzilla to add video >> support through MediaInfo. Thanks in advance. >> >> Voilà. Constructive comments are welcome. >> >> Best >> >> Gilles Caulier >> >> >> 2017-04-28 16:24 GMT+02:00 Gilles Caulier <[hidden email]>: >> > >> > >> > 2017-04-28 15:31 GMT+02:00 NeiNei <[hidden email]>: >> >> >> >> Hi there, >> >> >> >> the long awaited release of Exiv2 v0.26 should be released today >> >> according >> >> to http://dev.exiv2.org/boards/3/topics/2830 >> >> However, I do not know wether or how it will change the situation for >> >> DigiKam. >> > >> > >> > Nothing news with Exiv2 0.26, as i already use current code from svn >> > server >> > in all bundle (so pre 0.26 release) >> > >> > >> > >> >> >> >> As far as I understood Gilles thoroughly checks for alternatives in >> >> order >> >> to ensure a working, evolving and reliable metadata editor for DigiKam. >> >> >> > >> > yes. No code is done yet. I plan to make some demo code soon with >> > Exiftool >> > c++ interface, when time permit. >> > >> > Gilles >> > > > |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |