<div dir="ltr">Thanks Gilles, I will test it when the updated appimage bundle available.<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Best regards, <br></div></div></div></div>
<br><div class="gmail_quote">On Mon, Mar 5, 2018 at 4:51 AM, Gilles Caulier <span dir="ltr"><<a href="mailto:caulier.gilles@gmail.com" target="_blank">caulier.gilles@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Andrey,<br><div><br></div><div>Confirmed, my patch fix <a href="https://bugs.kde.org/show_bug.cgi?id=375570" style="color:rgb(17,85,204);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)" target="_blank">https://bugs.kde.org/show_<wbr>bug.cgi?id=375570</a> too...</div><div><br></div><div>But removing and creating new DB from scratch report unwanted errors (without any side-effects). I think it's relevant only on 6.0.0 and probably to new similarity DB rules.</div><div>Maik, did you try to run digiKam from scratch whithout any DB (but a valid RC). Typically, i do exactly what's Andrey done in this video :</div><div><br></div><div><a href="https://youtu.be/67pcOJj_3RM" target="_blank">https://youtu.be/67pcOJj_3RM</a><br></div><div><br></div><div>I moved all DB files hosted in my main root collection path to a temp directory, and restart digiKam. It ask my to setup collection as usual, but it ask me to use current DB file in this path, where all DB file was bee removed previously. I confirm to create new DB, but finally it said an error while creating DB files at end of scanning. By change all have been processed fine: files have been parsed and DB populated...</div><div><br></div><div>Can you reproduce on your computer ?</div><div><br></div><div>Gilles</div></div><div class="gmail_extra"><br><div class="gmail_quote">2018-03-05 8:20 GMT+01:00 Gilles Caulier <span dir="ltr"><<a href="mailto:caulier.gilles@gmail.com" target="_blank">caulier.gilles@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Confirmed. The patch follow fix definitively the GPS info problem, and certainly more about video info stored in DB. This small patch can also be applied to git master.<span class="m_6513215447464662693HOEnZb"><font color="#888888"><div><br></div><div>Gilles</div></font></span></div><div class="m_6513215447464662693HOEnZb"><div class="m_6513215447464662693h5"><div class="gmail_extra"><br><div class="gmail_quote">2018-03-05 7:14 GMT+01:00 Gilles Caulier <span dir="ltr"><<a href="mailto:caulier.gilles@gmail.com" target="_blank">caulier.gilles@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi all,</div><div><br></div>I think i found the problem, and in fact, the video file are not scanned by the same way than image.<div><br></div><div>Look well in ImageScanner::scanFile()</div><div><br></div><div><a href="https://cgit.kde.org/digikam.git/tree/libs/database/item/imagescanner.cpp?h=development/6.0.0#n467" target="_blank">https://cgit.kde.org/digikam.g<wbr>it/tree/libs/database/item/ima<wbr>gescanner.cpp?h=development/6.<wbr>0.0#n467</a><br></div><div><br></div><div>The condition (item == video) do not backport anything about camera shot information. This include GPS info but not only, as image size. </div><div><br></div><div>The scanVideoInformation need to be improved, i think :</div><div><br></div><div><a href="https://cgit.kde.org/digikam.git/tree/libs/database/item/imagescanner.cpp?h=development/6.0.0#n1480" target="_blank">https://cgit.kde.org/digikam.g<wbr>it/tree/libs/database/item/ima<wbr>gescanner.cpp?h=development/6.<wbr>0.0#n1480</a><span class="m_6513215447464662693m_-3632407337044375824HOEnZb"><font color="#888888"><br></font></span></div><span class="m_6513215447464662693m_-3632407337044375824HOEnZb"><font color="#888888"><div><br></div><div>Gilles Caulier</div></font></span></div><div class="m_6513215447464662693m_-3632407337044375824HOEnZb"><div class="m_6513215447464662693m_-3632407337044375824h5"><div class="gmail_extra"><br><div class="gmail_quote">2018-03-04 23:02 GMT+01:00 Gilles Caulier <span dir="ltr"><<a href="mailto:caulier.gilles@gmail.com" target="_blank">caulier.gilles@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I don't yet tested XMP sidecar file, but if GPS info inside video file, backported properly by ffmpeg parser, is not able to populate the database with this information, well the problem is more in-deed, somewhere in file parser or DB interface.<div><br></div><div>If i'm right, fixing this problem will fix XMP sidecar too...</div><span class="m_6513215447464662693m_-3632407337044375824m_-8105934979602202657HOEnZb"><font color="#888888"><div><br></div><div>Gilles</div></font></span></div><div class="m_6513215447464662693m_-3632407337044375824m_-8105934979602202657HOEnZb"><div class="m_6513215447464662693m_-3632407337044375824m_-8105934979602202657h5"><div class="gmail_extra"><br><div class="gmail_quote">2018-03-04 21:48 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>How about this one? Can you reproduce it on files without Geolocation embedded (e.g. videos taken on a camera) but with geolocation added to a sidecar file ?</div><div><br></div><div><a href="https://bugs.kde.org/show_bug.cgi?id=375570" target="_blank">https://bugs.kde.org/show_bug.<wbr>cgi?id=375570</a></div><div><br></div><div id="m_6513215447464662693m_-3632407337044375824m_-8105934979602202657m_2002718026190651708m_2924254657959817765composer_signature"><div style="font-size:85%;color:#575757" dir="auto">Sent from my Samsung Galaxy smartphone.</div></div><div><div class="m_6513215447464662693m_-3632407337044375824m_-8105934979602202657m_2002718026190651708h5"><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: 2018-03-04 11:10 AM (GMT-07:00) </div><div>To: "digiKam developers room - digiKam: Manage your photographs as a professional with the power of open source" <<a href="mailto:digikam-devel@kde.org" target="_blank">digikam-devel@kde.org</a>> </div><div>Subject: Re: Video metadata and GPS information. </div><div><br></div></div><div dir="ltr">Another file probably relevant of this dysfunction :<div><br></div><div><a href="https://bugs.kde.org/show_bug.cgi?id=373682" target="_blank">https://bugs.kde.org/show_bug.<wbr>cgi?id=373682</a><br></div><div><br></div><div>Gilles Caulier</div></div><div class="gmail_extra"><br><div class="gmail_quote">2018-03-04 19:07 GMT+01:00 Gilles Caulier <span dir="ltr"><<a href="mailto:caulier.gilles@gmail.com" target="_blank">caulier.gilles@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi all, <div><br></div><div>I can reproduce this file here with 6.0.0:</div><div><br></div><div><a href="https://bugs.kde.org/show_bug.cgi?id=377177" target="_blank">https://bugs.kde.org/show_bug.<wbr>cgi?id=377177</a></div><div><br></div><div>From my video collection, few items are taken with Iphone and GPS info are present in metadata.</div><div><br></div><div>Even if the FFMPEG metadata extractor get GPS info and populate Exif with right values, the GPS icon view overlay is off and now GPS position are linked with the video on DB.</div><div><br></div><div>To reproduce, try to import this file in your collection for ex :</div><div><br></div><div><a href="https://drive.google.com/open?id=1qn5k2zwIg-jihb6i4LwG1CVdUQ-AChMW" target="_blank">https://drive.google.com/open?<wbr>id=1qn5k2zwIg-jihb6i4LwG1CVdUQ<wbr>-AChMW</a><br></div><div><br></div><div>This is the result on icon-view :</div><div><br></div><div><a href="https://www.flickr.com/photos/digikam/26745652098/in/pool-digikam-labs/" target="_blank">https://www.flickr.com/photos/<wbr>digikam/26745652098/in/pool-di<wbr>gikam-labs/</a><br></div><div><br></div><div>The question is why... As you can see, GPS info are properly populated in Exif :</div><div><br></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">[gilles@localhost METADATA]$ ./loadfromfile_exif Apple-Iphone5s.mov </span><br>digikam.metaengine: Cannot load metadata from file (Error # 11 : Apple-Iphone5s.mov : Le fichier contient des données de type inconnu
<br>digikam.metaengine: Parse metadada with FFMpeg: "Apple-Iphone5s.mov"
<br>digikam.metaengine: -- FFMpeg video stream metadata entries :
<br>digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")<wbr>("encoder", "H.264")("handler_name", "Core Media Data Handler")("language", "und")("rotate", "90"))
<br>digikam.metaengine: ------------------------------<wbr>-----------
<br>digikam.metaengine: Exif.Image.Orientation tag set to: 6
<br>digikam.metaengine: -- FFMpeg audio stream metadata entries :
<br>digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")<wbr>("handler_name", "Core Media Data Handler")("language", "und"))
<br>digikam.metaengine: ------------------------------<wbr>-----------
<br>digikam.metaengine: -- FFMpeg root container metadata entries :
<br>digikam.metaengine: QMap(("com.apple.quicktime.cre<wbr>ationdate", "2014-07-05T13:02:04+0200")("c<a href="http://om.apple.quicktime.location.IS" target="_blank"><wbr>om.apple.quicktime.location.IS</a><wbr>O6709", "+43.6521+003.3638+148.202/")(<wbr>"com.apple.quicktime.make", "Apple")("com.apple.qui<br>cktime.model", "iPhone 5s")("com.apple.quicktime.soft<wbr>ware", "7.1.2")("compatible_brands", "qt ")("creation_time", "2014-07-05T11:02:04.000000Z")<wbr>("date", "2014-07-05T13:02:04+0200")("d<wbr>ate-fra", "2014-07-05T13:02<br>:04+0200")("encoder", "7.1.2")("encoder-fra", "7.1.2")("location", "+43.6521+003.3638+148.202/")(<wbr>"location-fra", "+43.6521+003.3638+148.202/")(<wbr>"major_brand", "qt ")("make", "Apple")("make-fra", "Apple")("minor_<br>version", "0")("model", "iPhone 5s")("model-fra", "iPhone 5s"))
<br>digikam.metaengine: ------------------------------<wbr>------------
<br>"Exif.GPSInfo.GPSAltitude" :: "148.2 m"
<br>"Exif.GPSInfo.GPSAltitudeRef" :: "Au dessus du niveau de la mer"
<br>"Exif.GPSInfo.GPSLatitude" :: "43deg 39.12600' "
<br>"Exif.GPSInfo.GPSLatitudeRef" :: "Nord"
<br>"Exif.GPSInfo.GPSLongitude" :: "3deg 21.82800' "
<br>"Exif.GPSInfo.GPSLongitudeRef" :: "Est"
<br>"Exif.GPSInfo.GPSMapDatum" :: "WGS-84"
<br>"Exif.GPSInfo.GPSVersionID" :: "2.0.0.0"
<br>"Exif.Image.DateTime" :: "2014:07:05 11:02:04"
<br>"Exif.Image.ImageLength" :: "1080"
<br>"Exif.Image.ImageWidth" :: "1920"
<br>"Exif.Image.Orientation" :: "droit, haut"
<br>"Exif.Photo.DateTimeDigitized" :: "2014:07:05 11:02:04"
<br>"Exif.Photo.DateTimeOriginal" :: "2014:07:05 11:02:04"
<br>"Exif.Photo.PixelXDimension" :: "1920"
<br>"Exif.Photo.PixelYDimension" :: "1080"<br>
<br></span>... and file scanner must be able to import this info in DB...</div><span class="m_6513215447464662693m_-3632407337044375824m_-8105934979602202657m_2002718026190651708m_2924254657959817765HOEnZb"><font color="#888888"><div><br></div><div>Gilles</div><div><br></div></font></span></div>
</blockquote></div><br></div>
</div></div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</blockquote></div><br></div>