ignore auxilliary AVCHD video container files when importing from filesystem
Submitted by Adam Dingle
Assigned to Lucas Beeler
Link to original bug (#718311)
Description
---- Reported by adam@yorba.org 2012-03-27 16:30:00 -0700 ----
Original Redmine bug id: 4943
Original URL: http://redmine.yorba.org/issues/4943
Searchable id: yorba-bug-4943
Original author: Adam Dingle
Original description:
From Martin Olsson on the mailing list:
If I record a single video recording with a Canon Legria HF200, then import everything that's on the memory card into shotwell; then the library shows 5 copies of a stock "movie tape" icon (if I click them totem opens and says "unable to determine stream type"), also I see one video thumbnail that is showed as a photo (not that strange since it's a JPG) and also the actual video clip I recorded. It would be nice if Shotwell didn't create all these other extra thumbnails that cannot be played anyway. I've compressed everything on the memory card after shooting a single recording and uploaded in a tgz here:
http://temp.minimum.se/shotwell_issues/straight_from_memcard_on_hdcamera_canon _legria_hf200.tgz
These kinds of AVCHD cameras (which is a standard btw, it's not just Canon cameras that use this) have a pretty extensive directory tree of video files, video thumbnails and other metadata and I think it's fair to say that the typical user might not even be able to determine which of these files are the actual movies and which ones a metadata. So I think it's pretty important that Shotwell learns about these directory structures so that A) it doesn't create those stock movie tape thumbnail entries that can't be clicked anyway, and so that B) it can couple the video thumbnail to the actual video like the RAW+JPG thing (or maybe just ignore the video thumbnails if shotwell generates thumbnails automatically from the video content itself). Note that during the import of the memcard contents, I see errors such as:
L 30416 2012-03-25 16:54:58 [DBG] VideoMetadata.vala:95: Error while testing for QuickTime file for
/home/molsson/fuzzing/bugs/hdcamera_import_all/PRIVATE/AVCHD/BDMV/PLAYLIST/000 00.MPL:
Unexpected early end-of-stream
L 30416 2012-03-25 16:54:58 [DBG] VideoMetadata.vala:95: Error while testing for QuickTime file for
/home/molsson/Pictures/2012/03/25/00000_1.CPI: Unexpected early end-of-stream
L 30416 2012-03-25 16:54:58 [WRN] VideoSupport.vala:122: Unable to read video metadata: File
/home/molsson/Pictures/2012/03/25/00000_1.CPI is not a supported video format
...and hence it might just be that you need to respond to such an error by not creating a thumbnail. The real video file in this case is the .MTS file.
Related issues:
- related to shotwell - Feature #2498 (closed): use GVFS rather than libgphoto2, allowing importing witho... (Open)
- related to shotwell - 6453: Ignore *.thm files in imports from mass storage cameras &... (Open)
- related to shotwell - 6454: Use paired .thm files for previews on ImportPage with mas... (Open)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:38:00 -0700 ----
History
Comment 1
Updated by Adam Dingle about 1 year ago
- Subject changed from ignore video thumbnail files when importing from AVCHD camera to ignore video thumbnail files when importing
- Priority changed from Normal to High
- Target version set to 0.14.0
When I record a video on my Canon S90, the camera stores both a .MOV video and a .THM thumbnail. If I then place the camera's SD card in my laptop and view its contents with Shotwell, I see both a generic movie icon (i.e. the .MOV) and also a broken image icon (i.e. the .THM). Shotwell should be smart enough to ignore the .THM file (or, perhaps, even use its contents as a thumbnail image before importing).
I'd love to see this for 0.14.
Comment 2
Updated by Jim Nelson 11 months ago
- Category set to import
Comment 3
Updated by Jim Nelson 9 months ago
- Assignee set to Lucas Beeler
Comment 4
Updated by Lucas Beeler 9 months ago
- Subject changed from ignore video thumbnail files when importing to ignore auxilliary AVCHD video container files when importing from filesystem
Comment 5
Updated by Lucas Beeler 8 months ago
- Status changed from Open to 5
Applied in changeset 121b952b.
Comment 6
Updated by Lucas Beeler 8 months ago
- Resolution set to fixed
Comment 7
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:56 UTC ---
This bug was previously known as bug 4943 at http://redmine.yorba.org/show_bug.cgi?id=4943
Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.14.0
Resolution: RESOLVED FIXED