![digikam 6.0 hide original digikam 6.0 hide original](http://www.r-photoclass.com/wp-content/uploads/photoclass/23-04.jpg)
- #DIGIKAM 6.0 HIDE ORIGINAL HOW TO#
- #DIGIKAM 6.0 HIDE ORIGINAL INSTALL#
- #DIGIKAM 6.0 HIDE ORIGINAL FULL#
- #DIGIKAM 6.0 HIDE ORIGINAL CODE#
#DIGIKAM 6.0 HIDE ORIGINAL HOW TO#
So we need a high level interface to define how to read or write data in core application. Remember that Showfoto does not use a database,
![digikam 6.0 hide original digikam 6.0 hide original](https://images.pexels.com/photos/46394/pexels-photo-46394.jpeg)
So a new interface has been created, to access core application data, independently. This means one should be able to use these tools not only from album-view, but in Image Editor, in Light Table and in Showfoto. In fact, this is not only limited to export tools, but all main tools available in digiKam album view as the metadata and the geolocation editors, need to be available everywhere. With this new 6.0.0 release, we added the capability to use all export tools everywhere in digiKam graphical interfaces. The advanced search tool in digiKam has been patched to deal with all new metadata extracted from video media and stored in the database. The previous one, using QtAV API introduced a high time latency while icon-view is populated with video media. It’s fast and powerful enough to catch all major information about video media.Īfter three weeks of coding and testing, an FFmpeg wrapper for digiKam database interface has been finalizedĪnd is fully operational, without seeing any crash during collections scanning.Ī video thumbnailer based exclusively on FFmpeg was also written. FFmpeg provides a C API that we can use directly We started to use ffmpeg as metadata parser. So, after losing plenty of time with Exiv2 about video files, without any satisfying results, digiKam must work as simple way to deal with video, as for photo.
#DIGIKAM 6.0 HIDE ORIGINAL INSTALL#
We don’t want to force digiKam users to install extra programs for that. That end users need to install explicitly to obtain functional video support. In contrast, the QtMultimedia framework requires extra platform codecs We chose QtAV because this framework directly uses ffmpeg codecs which de facto supports all formats very well. In release 5.5.0 we started to use the QtAV framework to play video media in digiKam. So we have been forced to find an alternative to Exiv2 for video support. Which has never been finalized and the implementation is still unstable.Įnabling video metadata support with Exiv2 would crash digiKam quickly in production. The Exiv2 shared library used in background by digiKam has video support The challenge to deal with these video media is to extract all the main metadata and populate the database. Video support in all devices, with plenty of formats. Since a very long time, digiKam users would like to be able to manage videos just like photos. To simplify application compilation, packaging and maintenance for the next years.ĭue to new implementations are more than 350 files, but nothing is completed yet, as we plan a few more beta releases before publishing the final 6.0.0
#DIGIKAM 6.0 HIDE ORIGINAL CODE#
#DIGIKAM 6.0 HIDE ORIGINAL FULL#
Full support of video files management working as photos.The next major version 6.0.0 looks promising, and will introduce new features as: We are proud to announce the first beta of digiKam 6.0.0. Dear digiKam fans and users, following the long stage of integrating a lots of work from students during the Summer of Code