Replace totem-video-indexer and use hachoir-metadata

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Dmedia
High
Unassigned

Bug Description

I know it sounds to be a duplicate of bug #680886
It's better to keep the bugs separate.

If you check dmedialib/extractor.py and look at line 162 in function extract_video_info
http://bazaar.launchpad.net/~dmedia/dmedia/trunk/annotate/head:/dmedialib/extractor.py#L162

You can see that it uses popen to communicate to totem-video-indexer to get the video metadata. This needs to go away and replaced with hachoir-metadata

Changed in dmedia:
milestone: none → 0.3
importance: Undecided → High
status: New → Triaged
Jason Gerard DeRose (jderose) wrote :

We may not be able to extract everything we need with hachoir-metadata, but it's worth a shot.

However, we *can* extract everything with gstreamer. Although we aren't currently extracting all this information, for editing purposes we need to know:

 * Number of frames in video
 * Exact rational video framerate (e.g., 29.97 fps = 30000/1001)
 * Number of samples in audio
 * Number of audio channels
 * Audio sample rate
 * Audio sample depth

Changed in dmedia:
milestone: 0.3 → 0.4
Jason Gerard DeRose (jderose) wrote :

I'm trying to keep the 0.4 cycle more focused, so I'm re-targeted this for 0.5 as it doesn't fit the 0.4 theme. Which is not to say someone can't take this on during 0.4 - if you completed it, I will land it!

Changed in dmedia:
milestone: 0.4 → 0.5
Changed in dmedia:
milestone: 0.5 → 0.6
Changed in dmedia:
milestone: 0.6 → 0.7
Changed in dmedia:
milestone: 0.7 → 0.8
Jason Gerard DeRose (jderose) wrote :

I'm merging this with lp:687962 as both will be solved by a gstreamer pipeline.

https://bugs.launchpad.net/dmedia/+bug/687962

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

Other bug subscribers