gstreamer detects HDV video and can play but causes totem / pitivi problems

Bug #574050 reported by Chris Cheney
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
GStreamer
Expired
Medium
gstreamer0.10 (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: totem

In the past totem couldn't properly detect HDV video (prior to 9.10) but could play it fine if you manually installed gstreamer0.10-plugins-ugly, after installing the other codecs it recommended. Since 9.10 it appears it can properly detect HDV video but seems to have no clue the recommendations it gave were enough to play it and complains every time you try to play a file. You can then ignore the message and it will play, but it is annoying that it pops up for every file.

-----
8.04
Installs gstreamer0.10-ffmpeg, gstreamer0.10-fluendo-mpegdemux, gstreamer0.10-plugins-bad

Still does not work.

-

Manual install gstreamer0.10-plugins-ugly allows it to play.

-----
9.04
"MPEG-2 Transport Stream demuxer"

Installs gstreamer0.10-plugins-bad

Still does not work.

-

Manual install gstreamer0.10-plugins-ugly allows it to play.

-----
9.10
"MPEG-2 Transport Stream demuxer"

Installs gstreamer0.10-plugins-bad

-

"MPEG-2 Video decoder"
"HDV AUX-V decoder"
"HDV AUX-A decoder"
"MPEG-1 Audio decoder"

Installs gstreamer0.10-ffmpeg, gstreamer0.10-fluendo-mp3, gstreamer0.10-plugins-ugly

-

"HDV AUX-V decoder"
"HDV AUX-A decoder"

no plugins found

-

If you ignore the no plugins found on 9.10 it will then play ok.

-----
10.04
"MPEG-2 Transport Stream demuxer"

Installs gstreamer0.10-plugins-bad

-

"MPEG-2 Video decoder"
"HDV AUX-V decoder"
"HDV AUX-A decoder"
"MPEG-1 Audio decoder"

Installs gstreamer0.10-ffmpeg, gstreamer0.10-fluendo-mp3, gstreamer0.10-plugins-ugly

-

"HDV AUX-V decoder"
"HDV AUX-A decoder"

no plugins found

-

If you ignore the no plugins found on 10.04 it will then play ok, but seems a bit crashy.

-----

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: totem 2.30.0git20100413-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Sun May 2 17:33:16 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100128)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: totem

Revision history for this message
Chris Cheney (ccheney) wrote :
Chris Cheney (ccheney)
description: updated
Chris Cheney (ccheney)
Changed in totem (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Chris Cheney (ccheney) wrote :

This was originally reported on ubuntuforums at:

http://ubuntuforums.org/showthread.php?t=1464903

Revision history for this message
Chris Cheney (ccheney) wrote :

I just tested under PiTiVi like the original report on ubuntuforums and you actually can't work around the warning in it. It won't let you play in it.

Revision history for this message
Chris Cheney (ccheney) wrote :

I wonder if the reason it works in Totem but not in PiTiVi is that PiTiVi may not attempt to just play anyway after you can cancel the additional search for codecs which it doesn't need while Totem may attempt to play regardless.

Revision history for this message
Chris Cheney (ccheney) wrote :

14:49 < bilboed> yes, because those are private streams, not actual video
                 streams
14:49 < bilboed> those streams do *not* contain video (they contain metadata)
14:50 < bilboed> there are elements to read the metadata, but that's besides
                 the point
14:51 < bilboed> basically : not much can be done right now

affects: totem (Ubuntu) → gstreamer0.10 (Ubuntu)
Chris Cheney (ccheney)
summary: - totem detects HDV video but doesn't seem to know it can play it
+ gstreamer detects HDV video and can play but causes totem / pitivi
+ problems
Changed in gstreamer0.10 (Ubuntu):
status: Confirmed → Triaged
Changed in gstreamer:
status: Unknown → Confirmed
Changed in gstreamer:
importance: Unknown → Medium
Changed in gstreamer:
status: Confirmed → Expired
Revision history for this message
thom (tsk) wrote :

Expired ?
A bit of a shameful move to expire this bug because the problem still exists (ubuntu 12.04 LTS) and will continue to exist until fixed or until end-of-life of 12.04 (i.e. 2017)

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.