Video metadata and GPS information.

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Video metadata and GPS information.

Gilles Caulier-4
Hi all, 

I can reproduce this file here with 6.0.0:


From my video collection, few items are taken with Iphone and GPS info are present in metadata.

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.

To reproduce, try to import this file in your collection for ex :


This is the result on icon-view :


The question is why... As you can see, GPS info are properly populated in Exif :

[gilles@localhost METADATA]$ ./loadfromfile_exif Apple-Iphone5s.mov  
digikam.metaengine: Cannot load metadata from file   (Error # 11 :  Apple-Iphone5s.mov : Le fichier contient des données de type inconnu
digikam.metaengine: Parse metadada with FFMpeg: "Apple-Iphone5s.mov"
digikam.metaengine: -- FFMpeg video stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("encoder", "H.264")("handler_name", "Core Media Data Handler")("language", "und")("rotate", "90"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: Exif.Image.Orientation tag set to:  6
digikam.metaengine: -- FFMpeg audio stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("handler_name", "Core Media Data Handler")("language", "und"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: -- FFMpeg root container metadata entries :
digikam.metaengine: QMap(("com.apple.quicktime.creationdate", "2014-07-05T13:02:04+0200")("com.apple.quicktime.location.ISO6709", "+43.6521+003.3638+148.202/")("com.apple.quicktime.make", "Apple")("com.apple.qui
cktime.model", "iPhone 5s")("com.apple.quicktime.software", "7.1.2")("compatible_brands", "qt  ")("creation_time", "2014-07-05T11:02:04.000000Z")("date", "2014-07-05T13:02:04+0200")("date-fra", "2014-07-05T13:02
:04+0200")("encoder", "7.1.2")("encoder-fra", "7.1.2")("location", "+43.6521+003.3638+148.202/")("location-fra", "+43.6521+003.3638+148.202/")("major_brand", "qt  ")("make", "Apple")("make-fra", "Apple")("minor_
version", "0")("model", "iPhone 5s")("model-fra", "iPhone 5s"))
digikam.metaengine: ------------------------------------------
"Exif.GPSInfo.GPSAltitude" :: "148.2 m"
"Exif.GPSInfo.GPSAltitudeRef" :: "Au dessus du niveau de la mer"
"Exif.GPSInfo.GPSLatitude" :: "43deg 39.12600' "
"Exif.GPSInfo.GPSLatitudeRef" :: "Nord"
"Exif.GPSInfo.GPSLongitude" :: "3deg 21.82800' "
"Exif.GPSInfo.GPSLongitudeRef" :: "Est"
"Exif.GPSInfo.GPSMapDatum" :: "WGS-84"
"Exif.GPSInfo.GPSVersionID" :: "2.0.0.0"
"Exif.Image.DateTime" :: "2014:07:05 11:02:04"
"Exif.Image.ImageLength" :: "1080"
"Exif.Image.ImageWidth" :: "1920"
"Exif.Image.Orientation" :: "droit, haut"
"Exif.Photo.DateTimeDigitized" :: "2014:07:05 11:02:04"
"Exif.Photo.DateTimeOriginal" :: "2014:07:05 11:02:04"
"Exif.Photo.PixelXDimension" :: "1920"
"Exif.Photo.PixelYDimension" :: "1080"

... and file scanner must be able to import this info in DB...

Gilles

Reply | Threaded
Open this post in threaded view
|

Re: Video metadata and GPS information.

Gilles Caulier-4
Another file probably relevant of this dysfunction :


Gilles Caulier

2018-03-04 19:07 GMT+01:00 Gilles Caulier <[hidden email]>:
Hi all, 

I can reproduce this file here with 6.0.0:


From my video collection, few items are taken with Iphone and GPS info are present in metadata.

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.

To reproduce, try to import this file in your collection for ex :


This is the result on icon-view :


The question is why... As you can see, GPS info are properly populated in Exif :

[gilles@localhost METADATA]$ ./loadfromfile_exif Apple-Iphone5s.mov  
digikam.metaengine: Cannot load metadata from file   (Error # 11 :  Apple-Iphone5s.mov : Le fichier contient des données de type inconnu
digikam.metaengine: Parse metadada with FFMpeg: "Apple-Iphone5s.mov"
digikam.metaengine: -- FFMpeg video stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("encoder", "H.264")("handler_name", "Core Media Data Handler")("language", "und")("rotate", "90"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: Exif.Image.Orientation tag set to:  6
digikam.metaengine: -- FFMpeg audio stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("handler_name", "Core Media Data Handler")("language", "und"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: -- FFMpeg root container metadata entries :
digikam.metaengine: QMap(("com.apple.quicktime.creationdate", "2014-07-05T13:02:04+0200")("com.apple.quicktime.location.ISO6709", "+43.6521+003.3638+148.202/")("com.apple.quicktime.make", "Apple")("com.apple.qui
cktime.model", "iPhone 5s")("com.apple.quicktime.software", "7.1.2")("compatible_brands", "qt  ")("creation_time", "2014-07-05T11:02:04.000000Z")("date", "2014-07-05T13:02:04+0200")("date-fra", "2014-07-05T13:02
:04+0200")("encoder", "7.1.2")("encoder-fra", "7.1.2")("location", "+43.6521+003.3638+148.202/")("location-fra", "+43.6521+003.3638+148.202/")("major_brand", "qt  ")("make", "Apple")("make-fra", "Apple")("minor_
version", "0")("model", "iPhone 5s")("model-fra", "iPhone 5s"))
digikam.metaengine: ------------------------------------------
"Exif.GPSInfo.GPSAltitude" :: "148.2 m"
"Exif.GPSInfo.GPSAltitudeRef" :: "Au dessus du niveau de la mer"
"Exif.GPSInfo.GPSLatitude" :: "43deg 39.12600' "
"Exif.GPSInfo.GPSLatitudeRef" :: "Nord"
"Exif.GPSInfo.GPSLongitude" :: "3deg 21.82800' "
"Exif.GPSInfo.GPSLongitudeRef" :: "Est"
"Exif.GPSInfo.GPSMapDatum" :: "WGS-84"
"Exif.GPSInfo.GPSVersionID" :: "2.0.0.0"
"Exif.Image.DateTime" :: "2014:07:05 11:02:04"
"Exif.Image.ImageLength" :: "1080"
"Exif.Image.ImageWidth" :: "1920"
"Exif.Image.Orientation" :: "droit, haut"
"Exif.Photo.DateTimeDigitized" :: "2014:07:05 11:02:04"
"Exif.Photo.DateTimeOriginal" :: "2014:07:05 11:02:04"
"Exif.Photo.PixelXDimension" :: "1920"
"Exif.Photo.PixelYDimension" :: "1080"

... and file scanner must be able to import this info in DB...

Gilles


Reply | Threaded
Open this post in threaded view
|

Re: Video metadata and GPS information.

AndriusWild
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 ?

https://bugs.kde.org/show_bug.cgi?id=375570

Sent from my Samsung Galaxy smartphone.

-------- Original message --------
From: Gilles Caulier <[hidden email]>
Date: 2018-03-04 11:10 AM (GMT-07:00)
To: "digiKam developers room - digiKam: Manage your photographs as a professional with the power of open source" <[hidden email]>
Subject: Re: Video metadata and GPS information.

Another file probably relevant of this dysfunction :


Gilles Caulier

2018-03-04 19:07 GMT+01:00 Gilles Caulier <[hidden email]>:
Hi all, 

I can reproduce this file here with 6.0.0:


From my video collection, few items are taken with Iphone and GPS info are present in metadata.

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.

To reproduce, try to import this file in your collection for ex :


This is the result on icon-view :


The question is why... As you can see, GPS info are properly populated in Exif :

[gilles@localhost METADATA]$ ./loadfromfile_exif Apple-Iphone5s.mov  
digikam.metaengine: Cannot load metadata from file   (Error # 11 :  Apple-Iphone5s.mov : Le fichier contient des données de type inconnu
digikam.metaengine: Parse metadada with FFMpeg: "Apple-Iphone5s.mov"
digikam.metaengine: -- FFMpeg video stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("encoder", "H.264")("handler_name", "Core Media Data Handler")("language", "und")("rotate", "90"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: Exif.Image.Orientation tag set to:  6
digikam.metaengine: -- FFMpeg audio stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("handler_name", "Core Media Data Handler")("language", "und"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: -- FFMpeg root container metadata entries :
digikam.metaengine: QMap(("com.apple.quicktime.creationdate", "2014-07-05T13:02:04+0200")("com.apple.quicktime.location.ISO6709", "+43.6521+003.3638+148.202/")("com.apple.quicktime.make", "Apple")("com.apple.qui
cktime.model", "iPhone 5s")("com.apple.quicktime.software", "7.1.2")("compatible_brands", "qt  ")("creation_time", "2014-07-05T11:02:04.000000Z")("date", "2014-07-05T13:02:04+0200")("date-fra", "2014-07-05T13:02
:04+0200")("encoder", "7.1.2")("encoder-fra", "7.1.2")("location", "+43.6521+003.3638+148.202/")("location-fra", "+43.6521+003.3638+148.202/")("major_brand", "qt  ")("make", "Apple")("make-fra", "Apple")("minor_
version", "0")("model", "iPhone 5s")("model-fra", "iPhone 5s"))
digikam.metaengine: ------------------------------------------
"Exif.GPSInfo.GPSAltitude" :: "148.2 m"
"Exif.GPSInfo.GPSAltitudeRef" :: "Au dessus du niveau de la mer"
"Exif.GPSInfo.GPSLatitude" :: "43deg 39.12600' "
"Exif.GPSInfo.GPSLatitudeRef" :: "Nord"
"Exif.GPSInfo.GPSLongitude" :: "3deg 21.82800' "
"Exif.GPSInfo.GPSLongitudeRef" :: "Est"
"Exif.GPSInfo.GPSMapDatum" :: "WGS-84"
"Exif.GPSInfo.GPSVersionID" :: "2.0.0.0"
"Exif.Image.DateTime" :: "2014:07:05 11:02:04"
"Exif.Image.ImageLength" :: "1080"
"Exif.Image.ImageWidth" :: "1920"
"Exif.Image.Orientation" :: "droit, haut"
"Exif.Photo.DateTimeDigitized" :: "2014:07:05 11:02:04"
"Exif.Photo.DateTimeOriginal" :: "2014:07:05 11:02:04"
"Exif.Photo.PixelXDimension" :: "1920"
"Exif.Photo.PixelYDimension" :: "1080"

... and file scanner must be able to import this info in DB...

Gilles


Reply | Threaded
Open this post in threaded view
|

Re: Video metadata and GPS information.

Gilles Caulier-4
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.

If i'm right, fixing this problem will fix XMP sidecar too...

Gilles

2018-03-04 21:48 GMT+01:00 Andrey Goreev <[hidden email]>:
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 ?


Sent from my Samsung Galaxy smartphone.

-------- Original message --------
From: Gilles Caulier <[hidden email]>
Date: 2018-03-04 11:10 AM (GMT-07:00)
To: "digiKam developers room - digiKam: Manage your photographs as a professional with the power of open source" <[hidden email]>
Subject: Re: Video metadata and GPS information.

Another file probably relevant of this dysfunction :


Gilles Caulier

2018-03-04 19:07 GMT+01:00 Gilles Caulier <[hidden email]>:
Hi all, 

I can reproduce this file here with 6.0.0:


From my video collection, few items are taken with Iphone and GPS info are present in metadata.

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.

To reproduce, try to import this file in your collection for ex :


This is the result on icon-view :


The question is why... As you can see, GPS info are properly populated in Exif :

[gilles@localhost METADATA]$ ./loadfromfile_exif Apple-Iphone5s.mov  
digikam.metaengine: Cannot load metadata from file   (Error # 11 :  Apple-Iphone5s.mov : Le fichier contient des données de type inconnu
digikam.metaengine: Parse metadada with FFMpeg: "Apple-Iphone5s.mov"
digikam.metaengine: -- FFMpeg video stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("encoder", "H.264")("handler_name", "Core Media Data Handler")("language", "und")("rotate", "90"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: Exif.Image.Orientation tag set to:  6
digikam.metaengine: -- FFMpeg audio stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("handler_name", "Core Media Data Handler")("language", "und"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: -- FFMpeg root container metadata entries :
digikam.metaengine: QMap(("com.apple.quicktime.creationdate", "2014-07-05T13:02:04+0200")("com.apple.quicktime.location.ISO6709", "+43.6521+003.3638+148.202/")("com.apple.quicktime.make", "Apple")("com.apple.qui
cktime.model", "iPhone 5s")("com.apple.quicktime.software", "7.1.2")("compatible_brands", "qt  ")("creation_time", "2014-07-05T11:02:04.000000Z")("date", "2014-07-05T13:02:04+0200")("date-fra", "2014-07-05T13:02
:04+0200")("encoder", "7.1.2")("encoder-fra", "7.1.2")("location", "+43.6521+003.3638+148.202/")("location-fra", "+43.6521+003.3638+148.202/")("major_brand", "qt  ")("make", "Apple")("make-fra", "Apple")("minor_
version", "0")("model", "iPhone 5s")("model-fra", "iPhone 5s"))
digikam.metaengine: ------------------------------------------
"Exif.GPSInfo.GPSAltitude" :: "148.2 m"
"Exif.GPSInfo.GPSAltitudeRef" :: "Au dessus du niveau de la mer"
"Exif.GPSInfo.GPSLatitude" :: "43deg 39.12600' "
"Exif.GPSInfo.GPSLatitudeRef" :: "Nord"
"Exif.GPSInfo.GPSLongitude" :: "3deg 21.82800' "
"Exif.GPSInfo.GPSLongitudeRef" :: "Est"
"Exif.GPSInfo.GPSMapDatum" :: "WGS-84"
"Exif.GPSInfo.GPSVersionID" :: "2.0.0.0"
"Exif.Image.DateTime" :: "2014:07:05 11:02:04"
"Exif.Image.ImageLength" :: "1080"
"Exif.Image.ImageWidth" :: "1920"
"Exif.Image.Orientation" :: "droit, haut"
"Exif.Photo.DateTimeDigitized" :: "2014:07:05 11:02:04"
"Exif.Photo.DateTimeOriginal" :: "2014:07:05 11:02:04"
"Exif.Photo.PixelXDimension" :: "1920"
"Exif.Photo.PixelYDimension" :: "1080"

... and file scanner must be able to import this info in DB...

Gilles



Reply | Threaded
Open this post in threaded view
|

Re: Video metadata and GPS information.

Gilles Caulier-4
Hi all,

I think i found the problem, and in fact, the video file are not scanned by the same way than image.

Look well in ImageScanner::scanFile()


The condition (item == video) do not backport anything about camera shot information. This include GPS info but not only, as image size. 

The scanVideoInformation need to be improved, i think :


Gilles Caulier

2018-03-04 23:02 GMT+01:00 Gilles Caulier <[hidden email]>:
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.

If i'm right, fixing this problem will fix XMP sidecar too...

Gilles

2018-03-04 21:48 GMT+01:00 Andrey Goreev <[hidden email]>:
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 ?


Sent from my Samsung Galaxy smartphone.

-------- Original message --------
From: Gilles Caulier <[hidden email]>
Date: 2018-03-04 11:10 AM (GMT-07:00)
To: "digiKam developers room - digiKam: Manage your photographs as a professional with the power of open source" <[hidden email]>
Subject: Re: Video metadata and GPS information.

Another file probably relevant of this dysfunction :


Gilles Caulier

2018-03-04 19:07 GMT+01:00 Gilles Caulier <[hidden email]>:
Hi all, 

I can reproduce this file here with 6.0.0:


From my video collection, few items are taken with Iphone and GPS info are present in metadata.

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.

To reproduce, try to import this file in your collection for ex :


This is the result on icon-view :


The question is why... As you can see, GPS info are properly populated in Exif :

[gilles@localhost METADATA]$ ./loadfromfile_exif Apple-Iphone5s.mov  
digikam.metaengine: Cannot load metadata from file   (Error # 11 :  Apple-Iphone5s.mov : Le fichier contient des données de type inconnu
digikam.metaengine: Parse metadada with FFMpeg: "Apple-Iphone5s.mov"
digikam.metaengine: -- FFMpeg video stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("encoder", "H.264")("handler_name", "Core Media Data Handler")("language", "und")("rotate", "90"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: Exif.Image.Orientation tag set to:  6
digikam.metaengine: -- FFMpeg audio stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("handler_name", "Core Media Data Handler")("language", "und"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: -- FFMpeg root container metadata entries :
digikam.metaengine: QMap(("com.apple.quicktime.creationdate", "2014-07-05T13:02:04+0200")("com.apple.quicktime.location.ISO6709", "+43.6521+003.3638+148.202/")("com.apple.quicktime.make", "Apple")("com.apple.qui
cktime.model", "iPhone 5s")("com.apple.quicktime.software", "7.1.2")("compatible_brands", "qt  ")("creation_time", "2014-07-05T11:02:04.000000Z")("date", "2014-07-05T13:02:04+0200")("date-fra", "2014-07-05T13:02
:04+0200")("encoder", "7.1.2")("encoder-fra", "7.1.2")("location", "+43.6521+003.3638+148.202/")("location-fra", "+43.6521+003.3638+148.202/")("major_brand", "qt  ")("make", "Apple")("make-fra", "Apple")("minor_
version", "0")("model", "iPhone 5s")("model-fra", "iPhone 5s"))
digikam.metaengine: ------------------------------------------
"Exif.GPSInfo.GPSAltitude" :: "148.2 m"
"Exif.GPSInfo.GPSAltitudeRef" :: "Au dessus du niveau de la mer"
"Exif.GPSInfo.GPSLatitude" :: "43deg 39.12600' "
"Exif.GPSInfo.GPSLatitudeRef" :: "Nord"
"Exif.GPSInfo.GPSLongitude" :: "3deg 21.82800' "
"Exif.GPSInfo.GPSLongitudeRef" :: "Est"
"Exif.GPSInfo.GPSMapDatum" :: "WGS-84"
"Exif.GPSInfo.GPSVersionID" :: "2.0.0.0"
"Exif.Image.DateTime" :: "2014:07:05 11:02:04"
"Exif.Image.ImageLength" :: "1080"
"Exif.Image.ImageWidth" :: "1920"
"Exif.Image.Orientation" :: "droit, haut"
"Exif.Photo.DateTimeDigitized" :: "2014:07:05 11:02:04"
"Exif.Photo.DateTimeOriginal" :: "2014:07:05 11:02:04"
"Exif.Photo.PixelXDimension" :: "1920"
"Exif.Photo.PixelYDimension" :: "1080"

... and file scanner must be able to import this info in DB...

Gilles




Reply | Threaded
Open this post in threaded view
|

Re: Video metadata and GPS information.

Gilles Caulier-4
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.

Gilles

2018-03-05 7:14 GMT+01:00 Gilles Caulier <[hidden email]>:
Hi all,

I think i found the problem, and in fact, the video file are not scanned by the same way than image.

Look well in ImageScanner::scanFile()


The condition (item == video) do not backport anything about camera shot information. This include GPS info but not only, as image size. 

The scanVideoInformation need to be improved, i think :


Gilles Caulier

2018-03-04 23:02 GMT+01:00 Gilles Caulier <[hidden email]>:
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.

If i'm right, fixing this problem will fix XMP sidecar too...

Gilles

2018-03-04 21:48 GMT+01:00 Andrey Goreev <[hidden email]>:
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 ?


Sent from my Samsung Galaxy smartphone.

-------- Original message --------
From: Gilles Caulier <[hidden email]>
Date: 2018-03-04 11:10 AM (GMT-07:00)
To: "digiKam developers room - digiKam: Manage your photographs as a professional with the power of open source" <[hidden email]>
Subject: Re: Video metadata and GPS information.

Another file probably relevant of this dysfunction :


Gilles Caulier

2018-03-04 19:07 GMT+01:00 Gilles Caulier <[hidden email]>:
Hi all, 

I can reproduce this file here with 6.0.0:


From my video collection, few items are taken with Iphone and GPS info are present in metadata.

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.

To reproduce, try to import this file in your collection for ex :


This is the result on icon-view :


The question is why... As you can see, GPS info are properly populated in Exif :

[gilles@localhost METADATA]$ ./loadfromfile_exif Apple-Iphone5s.mov  
digikam.metaengine: Cannot load metadata from file   (Error # 11 :  Apple-Iphone5s.mov : Le fichier contient des données de type inconnu
digikam.metaengine: Parse metadada with FFMpeg: "Apple-Iphone5s.mov"
digikam.metaengine: -- FFMpeg video stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("encoder", "H.264")("handler_name", "Core Media Data Handler")("language", "und")("rotate", "90"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: Exif.Image.Orientation tag set to:  6
digikam.metaengine: -- FFMpeg audio stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("handler_name", "Core Media Data Handler")("language", "und"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: -- FFMpeg root container metadata entries :
digikam.metaengine: QMap(("com.apple.quicktime.creationdate", "2014-07-05T13:02:04+0200")("com.apple.quicktime.location.ISO6709", "+43.6521+003.3638+148.202/")("com.apple.quicktime.make", "Apple")("com.apple.qui
cktime.model", "iPhone 5s")("com.apple.quicktime.software", "7.1.2")("compatible_brands", "qt  ")("creation_time", "2014-07-05T11:02:04.000000Z")("date", "2014-07-05T13:02:04+0200")("date-fra", "2014-07-05T13:02
:04+0200")("encoder", "7.1.2")("encoder-fra", "7.1.2")("location", "+43.6521+003.3638+148.202/")("location-fra", "+43.6521+003.3638+148.202/")("major_brand", "qt  ")("make", "Apple")("make-fra", "Apple")("minor_
version", "0")("model", "iPhone 5s")("model-fra", "iPhone 5s"))
digikam.metaengine: ------------------------------------------
"Exif.GPSInfo.GPSAltitude" :: "148.2 m"
"Exif.GPSInfo.GPSAltitudeRef" :: "Au dessus du niveau de la mer"
"Exif.GPSInfo.GPSLatitude" :: "43deg 39.12600' "
"Exif.GPSInfo.GPSLatitudeRef" :: "Nord"
"Exif.GPSInfo.GPSLongitude" :: "3deg 21.82800' "
"Exif.GPSInfo.GPSLongitudeRef" :: "Est"
"Exif.GPSInfo.GPSMapDatum" :: "WGS-84"
"Exif.GPSInfo.GPSVersionID" :: "2.0.0.0"
"Exif.Image.DateTime" :: "2014:07:05 11:02:04"
"Exif.Image.ImageLength" :: "1080"
"Exif.Image.ImageWidth" :: "1920"
"Exif.Image.Orientation" :: "droit, haut"
"Exif.Photo.DateTimeDigitized" :: "2014:07:05 11:02:04"
"Exif.Photo.DateTimeOriginal" :: "2014:07:05 11:02:04"
"Exif.Photo.PixelXDimension" :: "1920"
"Exif.Photo.PixelYDimension" :: "1080"

... and file scanner must be able to import this info in DB...

Gilles






videometadatatodb.patch (906 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Video metadata and GPS information.

Gilles Caulier-4
Andrey,

Confirmed, my patch fix https://bugs.kde.org/show_bug.cgi?id=375570 too...

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.
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 :


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...

Can you reproduce on your computer ?

Gilles

2018-03-05 8:20 GMT+01:00 Gilles Caulier <[hidden email]>:
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.

Gilles

2018-03-05 7:14 GMT+01:00 Gilles Caulier <[hidden email]>:
Hi all,

I think i found the problem, and in fact, the video file are not scanned by the same way than image.

Look well in ImageScanner::scanFile()


The condition (item == video) do not backport anything about camera shot information. This include GPS info but not only, as image size. 

The scanVideoInformation need to be improved, i think :


Gilles Caulier

2018-03-04 23:02 GMT+01:00 Gilles Caulier <[hidden email]>:
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.

If i'm right, fixing this problem will fix XMP sidecar too...

Gilles

2018-03-04 21:48 GMT+01:00 Andrey Goreev <[hidden email]>:
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 ?


Sent from my Samsung Galaxy smartphone.

-------- Original message --------
From: Gilles Caulier <[hidden email]>
Date: 2018-03-04 11:10 AM (GMT-07:00)
To: "digiKam developers room - digiKam: Manage your photographs as a professional with the power of open source" <[hidden email]>
Subject: Re: Video metadata and GPS information.

Another file probably relevant of this dysfunction :


Gilles Caulier

2018-03-04 19:07 GMT+01:00 Gilles Caulier <[hidden email]>:
Hi all, 

I can reproduce this file here with 6.0.0:


From my video collection, few items are taken with Iphone and GPS info are present in metadata.

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.

To reproduce, try to import this file in your collection for ex :


This is the result on icon-view :


The question is why... As you can see, GPS info are properly populated in Exif :

[gilles@localhost METADATA]$ ./loadfromfile_exif Apple-Iphone5s.mov  
digikam.metaengine: Cannot load metadata from file   (Error # 11 :  Apple-Iphone5s.mov : Le fichier contient des données de type inconnu
digikam.metaengine: Parse metadada with FFMpeg: "Apple-Iphone5s.mov"
digikam.metaengine: -- FFMpeg video stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("encoder", "H.264")("handler_name", "Core Media Data Handler")("language", "und")("rotate", "90"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: Exif.Image.Orientation tag set to:  6
digikam.metaengine: -- FFMpeg audio stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("handler_name", "Core Media Data Handler")("language", "und"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: -- FFMpeg root container metadata entries :
digikam.metaengine: QMap(("com.apple.quicktime.creationdate", "2014-07-05T13:02:04+0200")("com.apple.quicktime.location.ISO6709", "+43.6521+003.3638+148.202/")("com.apple.quicktime.make", "Apple")("com.apple.qui
cktime.model", "iPhone 5s")("com.apple.quicktime.software", "7.1.2")("compatible_brands", "qt  ")("creation_time", "2014-07-05T11:02:04.000000Z")("date", "2014-07-05T13:02:04+0200")("date-fra", "2014-07-05T13:02
:04+0200")("encoder", "7.1.2")("encoder-fra", "7.1.2")("location", "+43.6521+003.3638+148.202/")("location-fra", "+43.6521+003.3638+148.202/")("major_brand", "qt  ")("make", "Apple")("make-fra", "Apple")("minor_
version", "0")("model", "iPhone 5s")("model-fra", "iPhone 5s"))
digikam.metaengine: ------------------------------------------
"Exif.GPSInfo.GPSAltitude" :: "148.2 m"
"Exif.GPSInfo.GPSAltitudeRef" :: "Au dessus du niveau de la mer"
"Exif.GPSInfo.GPSLatitude" :: "43deg 39.12600' "
"Exif.GPSInfo.GPSLatitudeRef" :: "Nord"
"Exif.GPSInfo.GPSLongitude" :: "3deg 21.82800' "
"Exif.GPSInfo.GPSLongitudeRef" :: "Est"
"Exif.GPSInfo.GPSMapDatum" :: "WGS-84"
"Exif.GPSInfo.GPSVersionID" :: "2.0.0.0"
"Exif.Image.DateTime" :: "2014:07:05 11:02:04"
"Exif.Image.ImageLength" :: "1080"
"Exif.Image.ImageWidth" :: "1920"
"Exif.Image.Orientation" :: "droit, haut"
"Exif.Photo.DateTimeDigitized" :: "2014:07:05 11:02:04"
"Exif.Photo.DateTimeOriginal" :: "2014:07:05 11:02:04"
"Exif.Photo.PixelXDimension" :: "1920"
"Exif.Photo.PixelYDimension" :: "1080"

... and file scanner must be able to import this info in DB...

Gilles






Reply | Threaded
Open this post in threaded view
|

Re: Video metadata and GPS information.

Maik Qualmann
Gilles,

I could not reproduce an error message with a small test collection. Did the
error message appear as a dialog or in the console as a debug message? What
was the error message about?

Maik

Am Montag, 5. März 2018, 12:51:41 CET schrieb Gilles Caulier:

> Andrey,
>
> Confirmed, my patch fix https://bugs.kde.org/show_bug.cgi?id=375570 too...
>
> 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.
> 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 :
>
> https://youtu.be/67pcOJj_3RM
>
> 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...
>
> Can you reproduce on your computer ?
>
> Gilles
>
> 2018-03-05 8:20 GMT+01:00 Gilles Caulier <[hidden email]>:
> > 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.
> >
> > Gilles
> >
> > 2018-03-05 7:14 GMT+01:00 Gilles Caulier <[hidden email]>:
> >> Hi all,
> >>
> >> I think i found the problem, and in fact, the video file are not scanned
> >> by the same way than image.
> >>
> >> Look well in ImageScanner::scanFile()
> >>
> >> https://cgit.kde.org/digikam.git/tree/libs/database/item/ima
> >> gescanner.cpp?h=development/6.0.0#n467
> >>
> >> The condition (item == video) do not backport anything about camera shot
> >> information. This include GPS info but not only, as image size.
> >>
> >> The scanVideoInformation need to be improved, i think :
> >>
> >> https://cgit.kde.org/digikam.git/tree/libs/database/item/ima
> >> gescanner.cpp?h=development/6.0.0#n1480
> >>
> >> Gilles Caulier
> >>
> >> 2018-03-04 23:02 GMT+01:00 Gilles Caulier <[hidden email]>:
> >>> 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.
> >>>
> >>> If i'm right, fixing this problem will fix XMP sidecar too...
> >>>
> >>> Gilles
> >>>
> >>> 2018-03-04 21:48 GMT+01:00 Andrey Goreev <[hidden email]>:
> >>>> 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 ?
> >>>>
> >>>> https://bugs.kde.org/show_bug.cgi?id=375570
> >>>>
> >>>> Sent from my Samsung Galaxy smartphone.
> >>>>
> >>>> -------- Original message --------
> >>>> From: Gilles Caulier <[hidden email]>
> >>>> Date: 2018-03-04 11:10 AM (GMT-07:00)
> >>>> To: "digiKam developers room - digiKam: Manage your photographs as a
> >>>> professional with the power of open source" <[hidden email]>
> >>>> Subject: Re: Video metadata and GPS information.
> >>>>
> >>>> Another file probably relevant of this dysfunction :
> >>>>
> >>>> https://bugs.kde.org/show_bug.cgi?id=373682
> >>>>
> >>>> Gilles Caulier
> >>>>
> >>>> 2018-03-04 19:07 GMT+01:00 Gilles Caulier <[hidden email]>:
> >>>>> Hi all,
> >>>>>
> >>>>> I can reproduce this file here with 6.0.0:
> >>>>>
> >>>>> https://bugs.kde.org/show_bug.cgi?id=377177
> >>>>>
> >>>>> From my video collection, few items are taken with Iphone and GPS info
> >>>>> are present in metadata.
> >>>>>
> >>>>> 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.
> >>>>>
> >>>>> To reproduce, try to import this file in your collection for ex :
> >>>>>
> >>>>> https://drive.google.com/open?id=1qn5k2zwIg-jihb6i4LwG1CVdUQ-AChMW
> >>>>>
> >>>>> This is the result on icon-view :
> >>>>>
> >>>>> https://www.flickr.com/photos/digikam/26745652098/in/pool-di
> >>>>> gikam-labs/
> >>>>>
> >>>>> The question is why... As you can see, GPS info are properly populated
> >>>>> in Exif :
> >>>>>
> >>>>> [gilles@localhost METADATA]$ ./loadfromfile_exif Apple-Iphone5s.mov
> >>>>>
> >>>>> digikam.metaengine: Cannot load metadata from file   (Error # 11 :
> >>>>>  Apple-Iphone5s.mov : Le fichier contient des données de type inconnu
> >>>>>
> >>>>> digikam.metaengine: Parse metadada with FFMpeg: "Apple-Iphone5s.mov"
> >>>>> digikam.metaengine: -- FFMpeg video stream metadata entries :
> >>>>> digikam.metaengine: QMap(("creation_time",
> >>>>> "2014-07-05T11:02:04.000000Z")("encoder", "H.264")("handler_name",
> >>>>> "Core Media Data Handler")("language", "und")("rotate", "90"))
> >>>>> digikam.metaengine: -----------------------------------------
> >>>>> digikam.metaengine: Exif.Image.Orientation tag set to:  6
> >>>>> digikam.metaengine: -- FFMpeg audio stream metadata entries :
> >>>>> digikam.metaengine: QMap(("creation_time",
> >>>>> "2014-07-05T11:02:04.000000Z")("handler_name", "Core Media Data
> >>>>> Handler")("language", "und"))
> >>>>> digikam.metaengine: -----------------------------------------
> >>>>> digikam.metaengine: -- FFMpeg root container metadata entries :
> >>>>> digikam.metaengine: QMap(("com.apple.quicktime.creationdate",
> >>>>> "2014-07-05T13:02:04+0200")("com.apple.quicktime.location.ISO6709",
> >>>>> "+43.6521+003.3638+148.202/")("com.apple.quicktime.make",
> >>>>> "Apple")("com.apple.qui
> >>>>> cktime.model", "iPhone 5s")("com.apple.quicktime.software",
> >>>>> "7.1.2")("compatible_brands", "qt  ")("creation_time",
> >>>>> "2014-07-05T11:02:04.000000Z")("date",
> >>>>> "2014-07-05T13:02:04+0200")("date-fra", "2014-07-05T13:02
> >>>>>
> >>>>> :04+0200")("encoder", "7.1.2")("encoder-fra", "7.1.2")("location",
> >>>>>
> >>>>> "+43.6521+003.3638+148.202/")("location-fra",
> >>>>> "+43.6521+003.3638+148.202/")("major_brand", "qt  ")("make",
> >>>>> "Apple")("make-fra", "Apple")("minor_
> >>>>> version", "0")("model", "iPhone 5s")("model-fra", "iPhone 5s"))
> >>>>> digikam.metaengine: ------------------------------------------
> >>>>> "Exif.GPSInfo.GPSAltitude" :: "148.2 m"
> >>>>> "Exif.GPSInfo.GPSAltitudeRef" :: "Au dessus du niveau de la mer"
> >>>>> "Exif.GPSInfo.GPSLatitude" :: "43deg 39.12600' "
> >>>>> "Exif.GPSInfo.GPSLatitudeRef" :: "Nord"
> >>>>> "Exif.GPSInfo.GPSLongitude" :: "3deg 21.82800' "
> >>>>> "Exif.GPSInfo.GPSLongitudeRef" :: "Est"
> >>>>> "Exif.GPSInfo.GPSMapDatum" :: "WGS-84"
> >>>>> "Exif.GPSInfo.GPSVersionID" :: "2.0.0.0"
> >>>>> "Exif.Image.DateTime" :: "2014:07:05 11:02:04"
> >>>>> "Exif.Image.ImageLength" :: "1080"
> >>>>> "Exif.Image.ImageWidth" :: "1920"
> >>>>> "Exif.Image.Orientation" :: "droit, haut"
> >>>>> "Exif.Photo.DateTimeDigitized" :: "2014:07:05 11:02:04"
> >>>>> "Exif.Photo.DateTimeOriginal" :: "2014:07:05 11:02:04"
> >>>>> "Exif.Photo.PixelXDimension" :: "1920"
> >>>>> "Exif.Photo.PixelYDimension" :: "1080"
> >>>>>
> >>>>> ... and file scanner must be able to import this info in DB...
> >>>>>
> >>>>> Gilles




Reply | Threaded
Open this post in threaded view
|

Re: Video metadata and GPS information.

Gilles Caulier-4


2018-03-05 19:33 GMT+01:00 Maik Qualmann <[hidden email]>:
Gilles,

I could not reproduce an error message with a small test collection. Did the
error message appear as a dialog or in the console as a debug message?

There are 2 dialogs : One about the DB files already existing at storage location (where files have been removed in fact) and another dialog about to said that DB file cannot created at this place.

The RC file is unchanged and have been created by DK 5.x previously. Only DB have been removed.

At startup Setup collection page appear as expected. You set the root collection place. Nothing ask to set the DB files place. The path is taken from RC file if i remember and DB files will be recreated at this place. But after to close setup collection page, DK said that DB file already exists and ask to use files as well or to remplace. I choose to remplace and scan albums start. At end, DK open a new warning message box to indicate that DB file have not be created (false alarm in fact). I close the dialog and Album view appear and items scan continue in background. 

Gilles

Reply | Threaded
Open this post in threaded view
|

Re: Video metadata and GPS information.

AndriusWild
In reply to this post by Gilles Caulier-4
Thanks Gilles, I will test it when the updated appimage bundle available.

Best regards,

On Mon, Mar 5, 2018 at 4:51 AM, Gilles Caulier <[hidden email]> wrote:
Andrey,

Confirmed, my patch fix https://bugs.kde.org/show_bug.cgi?id=375570 too...

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.
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 :


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...

Can you reproduce on your computer ?

Gilles

2018-03-05 8:20 GMT+01:00 Gilles Caulier <[hidden email]>:
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.

Gilles

2018-03-05 7:14 GMT+01:00 Gilles Caulier <[hidden email]>:
Hi all,

I think i found the problem, and in fact, the video file are not scanned by the same way than image.

Look well in ImageScanner::scanFile()


The condition (item == video) do not backport anything about camera shot information. This include GPS info but not only, as image size. 

The scanVideoInformation need to be improved, i think :


Gilles Caulier

2018-03-04 23:02 GMT+01:00 Gilles Caulier <[hidden email]>:
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.

If i'm right, fixing this problem will fix XMP sidecar too...

Gilles

2018-03-04 21:48 GMT+01:00 Andrey Goreev <[hidden email]>:
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 ?


Sent from my Samsung Galaxy smartphone.

-------- Original message --------
From: Gilles Caulier <[hidden email]>
Date: 2018-03-04 11:10 AM (GMT-07:00)
To: "digiKam developers room - digiKam: Manage your photographs as a professional with the power of open source" <[hidden email]>
Subject: Re: Video metadata and GPS information.

Another file probably relevant of this dysfunction :


Gilles Caulier

2018-03-04 19:07 GMT+01:00 Gilles Caulier <[hidden email]>:
Hi all, 

I can reproduce this file here with 6.0.0:


From my video collection, few items are taken with Iphone and GPS info are present in metadata.

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.

To reproduce, try to import this file in your collection for ex :


This is the result on icon-view :


The question is why... As you can see, GPS info are properly populated in Exif :

[gilles@localhost METADATA]$ ./loadfromfile_exif Apple-Iphone5s.mov  
digikam.metaengine: Cannot load metadata from file   (Error # 11 :  Apple-Iphone5s.mov : Le fichier contient des données de type inconnu
digikam.metaengine: Parse metadada with FFMpeg: "Apple-Iphone5s.mov"
digikam.metaengine: -- FFMpeg video stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("encoder", "H.264")("handler_name", "Core Media Data Handler")("language", "und")("rotate", "90"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: Exif.Image.Orientation tag set to:  6
digikam.metaengine: -- FFMpeg audio stream metadata entries :
digikam.metaengine: QMap(("creation_time", "2014-07-05T11:02:04.000000Z")("handler_name", "Core Media Data Handler")("language", "und"))
digikam.metaengine: -----------------------------------------
digikam.metaengine: -- FFMpeg root container metadata entries :
digikam.metaengine: QMap(("com.apple.quicktime.creationdate", "2014-07-05T13:02:04+0200")("com.apple.quicktime.location.ISO6709", "+43.6521+003.3638+148.202/")("com.apple.quicktime.make", "Apple")("com.apple.qui
cktime.model", "iPhone 5s")("com.apple.quicktime.software", "7.1.2")("compatible_brands", "qt  ")("creation_time", "2014-07-05T11:02:04.000000Z")("date", "2014-07-05T13:02:04+0200")("date-fra", "2014-07-05T13:02
:04+0200")("encoder", "7.1.2")("encoder-fra", "7.1.2")("location", "+43.6521+003.3638+148.202/")("location-fra", "+43.6521+003.3638+148.202/")("major_brand", "qt  ")("make", "Apple")("make-fra", "Apple")("minor_
version", "0")("model", "iPhone 5s")("model-fra", "iPhone 5s"))
digikam.metaengine: ------------------------------------------
"Exif.GPSInfo.GPSAltitude" :: "148.2 m"
"Exif.GPSInfo.GPSAltitudeRef" :: "Au dessus du niveau de la mer"
"Exif.GPSInfo.GPSLatitude" :: "43deg 39.12600' "
"Exif.GPSInfo.GPSLatitudeRef" :: "Nord"
"Exif.GPSInfo.GPSLongitude" :: "3deg 21.82800' "
"Exif.GPSInfo.GPSLongitudeRef" :: "Est"
"Exif.GPSInfo.GPSMapDatum" :: "WGS-84"
"Exif.GPSInfo.GPSVersionID" :: "2.0.0.0"
"Exif.Image.DateTime" :: "2014:07:05 11:02:04"
"Exif.Image.ImageLength" :: "1080"
"Exif.Image.ImageWidth" :: "1920"
"Exif.Image.Orientation" :: "droit, haut"
"Exif.Photo.DateTimeDigitized" :: "2014:07:05 11:02:04"
"Exif.Photo.DateTimeOriginal" :: "2014:07:05 11:02:04"
"Exif.Photo.PixelXDimension" :: "1920"
"Exif.Photo.PixelYDimension" :: "1080"

... and file scanner must be able to import this info in DB...

Gilles







Reply | Threaded
Open this post in threaded view
|

Re: Video metadata and GPS information.

Gilles Caulier-4
In reply to this post by Gilles Caulier-4
Maik,

the problem with the database error dialog is easy to reproduce.

Today i would to turn on the filename over icon view setup page. I go to the setup change the option and close the dialog. The famous DB question dialog box appear.

In fact when you option the setup dialog and you close, i suspect a check in DB setup page which is called at end of dialog session which ask confirmation all the time.

In fact you don't need to change anything. Just close the setup dialog with OK button...

Gilles



2018-03-05 23:00 GMT+01:00 Gilles Caulier <[hidden email]>:


2018-03-05 19:33 GMT+01:00 Maik Qualmann <[hidden email]>:
Gilles,

I could not reproduce an error message with a small test collection. Did the
error message appear as a dialog or in the console as a debug message?

There are 2 dialogs : One about the DB files already existing at storage location (where files have been removed in fact) and another dialog about to said that DB file cannot created at this place.

The RC file is unchanged and have been created by DK 5.x previously. Only DB have been removed.

At startup Setup collection page appear as expected. You set the root collection place. Nothing ask to set the DB files place. The path is taken from RC file if i remember and DB files will be recreated at this place. But after to close setup collection page, DK said that DB file already exists and ask to use files as well or to remplace. I choose to remplace and scan albums start. At end, DK open a new warning message box to indicate that DB file have not be created (false alarm in fact). I close the dialog and Album view appear and items scan continue in background. 

Gilles


Reply | Threaded
Open this post in threaded view
|

Re: Video metadata and GPS information.

Maik Qualmann
I can reproduce a double dialog to set the collection. I believe that this
problem exists since the ignore folders setting was added.

Maik

Am Samstag, 10. März 2018, 22:06:12 CET schrieb Gilles Caulier:

> Maik,
>
> the problem with the database error dialog is easy to reproduce.
>
> Today i would to turn on the filename over icon view setup page. I go to
> the setup change the option and close the dialog. The famous DB question
> dialog box appear.
>
> In fact when you option the setup dialog and you close, i suspect a check
> in DB setup page which is called at end of dialog session which ask
> confirmation all the time.
>
> In fact you don't need to change anything. Just close the setup dialog with
> OK button...
>
> Gilles
>
> 2018-03-05 23:00 GMT+01:00 Gilles Caulier <[hidden email]>:
> > 2018-03-05 19:33 GMT+01:00 Maik Qualmann <[hidden email]>:
> >> Gilles,
> >>
> >> I could not reproduce an error message with a small test collection. Did
> >> the
> >> error message appear as a dialog or in the console as a debug message?
> >
> > There are 2 dialogs : One about the DB files already existing at storage
> > location (where files have been removed in fact) and another dialog about
> > to said that DB file cannot created at this place.
> >
> > The RC file is unchanged and have been created by DK 5.x previously. Only
> > DB have been removed.
> >
> > At startup Setup collection page appear as expected. You set the root
> > collection place. Nothing ask to set the DB files place. The path is taken
> > from RC file if i remember and DB files will be recreated at this place.
> > But after to close setup collection page, DK said that DB file already
> > exists and ask to use files as well or to remplace. I choose to remplace
> > and scan albums start. At end, DK open a new warning message box to
> > indicate that DB file have not be created (false alarm in fact). I close
> > the dialog and Album view appear and items scan continue in background.
> >
> > Gilles