[digiKam-users] Date taken tag for video files
Gilles Caulier
caulier.gilles at gmail.com
Wed Feb 27 17:09:58 GMT 2019
Hi,
The video file metadata are extracted, with... ffmpeg libraries.
So, the difference can be relevant of codec implementation in ffmpeg. In
fact we ask to fmmpeg to extract all metadata and pass the result that we
parse to populate the database.
If you want to compare yourself, open a console, go to your video file and
run ffmpeg -i file. Exemple :
[gilles at localhost Video]$ ffmpeg -i small.mp4
ffmpeg version 3.3.9 Copyright (c) 2000-2018 the FFmpeg developers
built with gcc 5.5.0 (Mageia 5.5.0-1.mga6)
configuration: --prefix=/usr --enable-shared --libdir=/usr/lib64
--shlibdir=/usr/lib64 --incdir=/usr/include --disable-stripping
--enable-postproc --enable-gpl --enable-pthreads --enable-libtheora
--enable-libvorbis --disable-encoder=vorbis --enable-libvpx
--enable-runtime-cpudetect --enable-libdc1394 --enable-libschroedinger
--enable-librtmp --enable-libspeex --enable-libfreetype --enable-libnut
--enable-libgsm --enable-libcelt --enable-libopus --enable-libopencv
--enable-libopenjpeg --enable-libtwolame --enable-libxavs --enable-frei0r
--enable-libmodplug --enable-libass --enable-gnutls --enable-libcdio
--enable-libpulse --enable-libv4l2 --enable-avresample --enable-opencl
--enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb
--enable-version3 --enable-libx264 --enable-libx265 --enable-libvo-amrwbenc
--enable-libxvid
libavutil 55. 58.100 / 55. 58.100
libavcodec 57. 89.100 / 57. 89.100
libavformat 57. 71.100 / 57. 71.100
libavdevice 57. 6.100 / 57. 6.100
libavfilter 6. 82.100 / 6. 82.100
libavresample 3. 5. 0 / 3. 5. 0
libswscale 4. 6.100 / 4. 6.100
libswresample 2. 7.100 / 2. 7.100
libpostproc 54. 5.100 / 54. 5.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'small.mp4':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: mp42isomavc1
creation_time : 2010-03-20T21:29:11.000000Z
encoder : HandBrake 0.9.4 2009112300
Duration: 00:00:05.57, start: 0.000000, bitrate: 551 kb/s
Stream #0:0(und): Video: h264 (Constrained Baseline) (avc1 /
0x31637661), yuv420p(tv, bt709), 560x320, 465 kb/s, 30 fps, 30 tbr, 90k
tbn, 60 tbc (default)
Metadata:
creation_time : 2010-03-20T21:29:11.000000Z
encoder : JVT/AVC Coding
Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono,
fltp, 83 kb/s (default)
Metadata:
creation_time : 2010-03-20T21:29:11.000000Z
At least one output file must be specified
Look the "creation_time" tags.
Gilles Caulier
Le mer. 27 févr. 2019 à 15:39, nonobio <nonobio at gmail.com> a écrit :
> Hi :)
>
> Since my last message i didn't tried anything new : i just use the file
> name
> as it is the best "taken date" info i have.
>
> I just updated Digikam to version 6.0.0 and as it have a new video files
> management, i make a new try.
>
> After analyse a video file metadata with Digikam 6.0.0, it find a new field
> displayed in file view : "dititalized date". It seems to display the same
> date that "created date".
>
> Anyway, this is what i see and understand about differents date fields in
> list view :
>
> <http://digikam.1695700.n4.nabble.com/file/t376394/gfH5Sh1.png>
>
> 1- File name : file is named with the actual date as soon as i start video
> capture. It isn't a metadata but it is the real "taken date".
> 2- Last modified. File date attribute is writed at the end of the capture.
> It isn't the good "date taken" because it is the "end" of the video, not
> the
> "start". I think it have more sense to use "beginning date".
> 3- Created date : it is the end of the video but not the good : it has an
> error of "one hour". I think it is about "GMT" ?
> 4- Digitalized date : new field sinc Digikam 6.0.0 but same problem that
> created date (one hour less).
>
> Because the "file name" is the only good "taken time", i only use it and
> not
> the others fields. For that i just rename it to match my others file names
> preferences (yyyymmddhhmmss). It is ok but when i explore my videos, i have
> to sort them by "name", not by "date"...
>
> Am i wrong about what i understand for the different dates ?
> Why is there a delta of one hour for created and digitalized date, and how
> to correct it ?
> Do you have any recommandations ?
>
> Thanks
>
>
>
>
>
>
> --
> Sent from:
> http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20190227/7911a6c5/attachment.html>
More information about the Digikam-users
mailing list