| Summary: | Video with geo tags is filtered as non-geotagged: Mysql float value are encoded with comma or dot depending on the locale. | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | bugskdeorg.20.dimon3000 |
| Component: | Database-Mysql | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 6.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Appimage | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/documentation/digikam-doc/-/commit/13ad6467af8a6189b541882307d9e94357b02a8e | Version Fixed/Implemented In: | 8.2.0 |
| Sentry Crash Report: | |||
| Attachments: |
Metadata sidecar
ffprobe (ffmpeg) metadata |
||
|
Description
bugskdeorg.20.dimon3000
2019-04-27 09:55:46 UTC
Created attachment 119665 [details]
ffprobe (ffmpeg) metadata
Now you have to perform a re-read the metadata of the video files, so that the database entries are updated. This is a country specific problem and only arises with the AppImage. We should try to set LC_NUMERIC on the basis of the system locale in the AppImage start script. Maik Maik, appending "export LC_NUMERIC=c" in AppRun bash script for AppImage is of course possible, but i fear that it do not cover all possible cases, depending of host locale settings. But, in fact the question is why we need to set LC_NUMERIC=c before to run digiKam ? I suspect something around Exiv2 which use a specific locale to decode float data from tags before to register information in database. Right ? Because All digiKam Qt code has rules to deal with float values encoding depending of the locale. Right ? If yes, perhaps i build Exiv2 with a non turned on option ? Gilles No it is not dependent on Exiv2 because the problem with SQLite does not occur. The cause is the external MySQL server that is set up with the locale of the system. Maik The double values in the tables of a MySQL server are saved with comma or dot, depending on the locale. Maik Hi, Can you check if this problem still exist with last weekly bundle build of digiKam 7.0.0 available here: https://files.kde.org/digikam/ Thanks in advance Gilles Caulier digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier With next digiKam 7.4.0 release, AppImage bundle is compiled using a more recent Linux Mageia 7.1 host. Last stable Qt 5.15.2 and KF5 5.84 are used. ImageMagick codec 7 and libav 58 (ffmpeg) are used to supports extra image and video formats. https://i.imgur.com/XV1tZkL.png Please check if problem still reproducible with this version available as pre-release here: https://files.kde.org/digikam/ Gilles Caulier @dimon, digiKam 8.0.0 is out. This entry still valid with this release ? Best regards Gilles Caulier To Maik Comment #4, If the problem is the remote Mysql server locale, well this is not a bug but a settings problem which must be solved by end users. Typically, local from the Mysql server and local from the client computer running digiKam must be the same. I will patch the documentation accordingly. Gilles Caulier Git commit 13ad6467af8a6189b541882307d9e94357b02a8e by Gilles Caulier. Committed on 10/10/2023 at 07:55. Pushed by cgilles into branch 'master'. add warning about remote database encoding which must be the same in client computer. FIXED-IN: 8.2.0 M +4 -0 setup_application/database_settings.rst https://invent.kde.org/documentation/digikam-doc/-/commit/13ad6467af8a6189b541882307d9e94357b02a8e |
