Generate video thumbnails by looking for pixel variance
Submitted by Lucas Beeler
Link to original bug (#716838)
Description
---- Reported by lucas@yorba.org 2010-09-16 18:47:00 -0700 ----
Original Redmine bug id: 2568
Original URL: http://redmine.yorba.org/issues/2568
Searchable id: yorba-bug-2568
Original author: Lucas Beeler
Original description:
Many digital video files are processed to fade-in from black when they begin and fade-out to black when they end. Right now, we build the thumbnail from the first frame of the video. If the user imports 4 videos, all of which have fade-in effects, all of them will have unsightly pure black thumbnails. To rectify this, we should grab our thumbnail frame from, say, a timepoint that's 1/3 of video's duration.
---- Additional Comments From shotwell-maint@gnome.bugs 2010-12-27 01:43:00 -0800 ----
History
Comment 1
Updated by Marcel Stimberg about 3 years ago
The standard gnome thumbnailer (totem-video-thumbnailer) does something slightly more clever, it tests the frames at 33%, 66%, 10%, 90% and 50% (in that order) for being “interestingâ€, where interesting is defined as having a high enough variance in the b/w pixel distribution, i.e. discarding frames with mainly one colour.
See here: http://git.gnome.org/browse/totem/tree/src/totem-video- thumbnailer.c?id=a365d50c19b900911d7fe1bfdb24d22f8ab5bc98
Comment 2
Updated by Adam Dingle about 3 years ago
Fascinating. We should do something similar.
Comment 3
Updated by Adam Dingle about 3 years ago
- Tracker changed from Bug to Feature
Comment 4
Updated by Lucas Beeler almost 3 years ago
- Status changed from Open to 5
- Resolution set to fixed
- % Done changed from 0 to 100
r2399
Comment 5
Updated by Adam Dingle almost 3 years ago
- Status changed from 5 to 4
-
Resolution deleted (
<strike>
_fixed_</strike>
) - % Done changed from 100 to 0
-
Priority deleted (
<strike>
_High_</strike>
) - Subject changed from Many video thumbnails appear black because of fade effects to Generate video thumbnails by looking for pixel variance
Reopening at priority medium: the existing implementation is fine for 0.8, but at some point we should implement a smarter algorithm as described in Marcel's comment above.
Comment 6
Updated by Adam Dingle almost 3 years ago
- Status changed from 4 to Review
- Assignee changed from Lucas Beeler to Anonymous
--- Bug imported by chaz@yorba.org 2013-11-25 21:47 UTC ---
This bug was previously known as bug 2568 at http://redmine.yorba.org/show_bug.cgi?id=2568
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". 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. Resolution set on an open status. Dropping resolution