shotwell does not categorize MTS files into events

Bug #1804541 reported by Steve Chadsey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntuone-shotwell-plugin
Unknown
Unknown
shotwell (Ubuntu)
Triaged
Low
Unassigned

Bug Description

I have a Sony HDR-CX675 which produces MTS video files. When I add them to shotwell (version 0.28.2), the video files are added to the "No Event" category (if that is the right term). Other video file types such as MOV files are categorized into the correct event based on the media creation time. If I play any of my MTS videos with parole, the date and time are displayed on the video (I don't know why parole does this, but that's a separate issue. The point is that parole is able to figure out the date/time of the video, so shotwell should, too).

$ ffprobe 00012.MTS
ffprobe version 3.4.4-0ubuntu0.18.04.1 Copyright (c) 2007-2018 the FFmpeg developers
  built with gcc 7 (Ubuntu 7.3.0-16ubuntu3)
  configuration: --prefix=/usr --extra-version=0ubuntu0.18.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared
  WARNING: library configuration mismatch
  avcodec configuration: --prefix=/usr --extra-version=0ubuntu0.18.04.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared --enable-version3 --disable-doc --disable-programs --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libtesseract --enable-libvo_amrwbenc
  libavutil 55. 78.100 / 55. 78.100
  libavcodec 57.107.100 / 57.107.100
  libavformat 57. 83.100 / 57. 83.100
  libavdevice 57. 10.100 / 57. 10.100
  libavfilter 6.107.100 / 6.107.100
  libavresample 3. 7. 0 / 3. 7. 0
  libswscale 4. 8.100 / 4. 8.100
  libswresample 2. 9.100 / 2. 9.100
  libpostproc 54. 7.100 / 54. 7.100
Input #0, mpegts, from '00012.MTS':
  Duration: 00:00:19.04, start: 1.033367, bitrate: 22304 kb/s
  Program 1
    Stream #0:0[0x1011]: Video: h264 (High) (HDMV / 0x564D4448), yuv420p(top first), 1920x1080 [SAR 1:1 DAR 16:9], 29.97 fps, 59.94 tbr, 90k tbn, 59.94 tbc
    Stream #0:1[0x1100]: Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 5.1(side), fltp, 448 kb/s
    Stream #0:2[0x1200]: Subtitle: hdmv_pgs_subtitle ([144][0][0][0] / 0x0090), 1920x1080

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: shotwell 0.28.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 21 18:00:21 2018
InstallationDate: Installed on 2016-01-05 (1050 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: shotwell
UpgradeStatus: Upgraded to bionic on 2018-10-08 (44 days ago)

Revision history for this message
Steve Chadsey (schadsey) wrote :
Revision history for this message
Jens Georg (yg-jensge) wrote :
Revision history for this message
Jens Georg (yg-jensge) wrote :
Revision history for this message
Steve Chadsey (schadsey) wrote :

From https://bugzilla.gnome.org/show_bug.cgi?id=717468:

> If the files are being imported from a USB harddrive you can create a folder
> called DCIM on the root and put all the videos into it. Start Shotwell and
> import them as if they were coming from a camera. Shotwell will now
> successfully save them into the library with the correct creation date/time.

I don't consider this to be a very viable workaround. The videos are on the camera memory card and so one would have to either copy them onto another USB drive with the suggested DCIM folder, or copy/move them from their native location on the camera filesystem to another location on the same filesystem. Either way, it's inconvenient, and not something that someone who regularly imports videos would want to suffer through more than a couple times.

Changed in shotwell (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Steve Chadsey (schadsey) wrote :

This is still an issue in 20.04.4, shotwell 0.30.10-0ubuntu0.1

The workaround of adding the MTS file to a mounted drive under /DCIM fails to import it to an event date corresponding to the recorded date of the video. Instead, it is imported for the current date.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.