GNOME Bugzilla – Bug 675924
Totem can't play some FLV videos encoded by H.264 codec
Last modified: 2012-08-05 15:56:58 UTC
Created attachment 213905 [details] screenshot Ubuntu 12.04 after upgrading from 11.10 totem can't play some FLV file encoded by H.264 codec. After opening we got zero resolution (0x0 pixels). Other players Parole, VLC plays it normaly. Some times we got a crash exiting totem. Sometimes we can drag scroller and see that audio is working. In ubuntu 11.10 all file are working normaly.
Hi Nikolay, Thanks for taking the time to report this bug. However, you are using version 3.0.x which is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes by GNOME developers for the version that you use. Please feel free to reopen this bug if the problem still occurs with a newer version (3.4). As Ubuntu still supports and ships this version the place to report and discuss this problem is https://launchpad.net/bugs/993937 .
Adding Ubuntu GNOME TEAM PPA https://launchpad.net/~gnome3-team/+archive/gnome3 thus upgrade gnome, totem will become to 3.4.1 problem still exist
Thanks for retesting with 3.4. Please see http://projects.gnome.org/totem/index.html , section "Reporting bugs" for how to provide more debug information. As you wrote "some FLV file" a testcase is also welcome, in case that it is a small file and that you can attach it in public (license of the file).
Created attachment 214812 [details] Extra debug info
Created attachment 214818 [details] Extra debug info for 3.4.1 version
can't upload sample FLV here uploaded to https://bugs.launchpad.net/ubuntu/+source/totem/+bug/993937 direct link https://bugs.launchpad.net/ubuntu/+source/totem/+bug/993937/+attachment/3160052/+files/Egor%20Letov%20-%20Vse%20Idet%20po%20Planu%20%28Live%29.flv this flv file is taken from youtube.com
This is surely a bug in gstreamer. Pitivi can't open such videos either.
But parole is also based on gstreamer and works normaly...
Try it with gst-launch, as per http://projects.gnome.org/totem/#bugs So, with the file in the current folder: gst-launch-0.10 playbin2 uri=file://`pwd`/Egor%20Letov%20-%20Vse%20Idet%20po%20Planu%20%28Live%29.flv and see whether you see the same problem.
Parole works for me too. Trying gst-launch I get: Setting pipeline to PAUSED ... Pipeline is PREROLLING ... and then it hangs (works okay with other video formats though).
Aha - but 'playbin' (rather than playbin2) DOES work.
$ gst-launch-0.10 playbin2 uri=file:///home/nmorozov/1.flv Setting pipeline to PAUSED ... Pipeline is PREROLLING ...
Yep trying playbin works $ gst-launch-0.10 playbin uri=file:///home/nmorozov/1.flv Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstPulseSinkClock ERROR: from element /GstPlayBin:playbin0/GstBin:vbin/GstAutoVideoSink:videosink/GstXvImageSink:videosink-actual-sink-xvimage: Output window was closed Additional debug info: xvimagesink.c(1326): gst_xvimagesink_handle_xevents (): /GstPlayBin:playbin0/GstBin:vbin/GstAutoVideoSink:videosink/GstXvImageSink:videosink-actual-sink-xvimage Execution ended after 8376612709 ns. Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ...
Submitted gstreamer bug on playbin2 0.10.36: https://bugzilla.gnome.org/show_bug.cgi?id=677926
*** Bug 677926 has been marked as a duplicate of this bug. ***
(In reply to comment #14) > Submitted gstreamer bug on playbin2 0.10.36: > https://bugzilla.gnome.org/show_bug.cgi?id=677926 Given that the problem is solely a GStreamer problem, there's no need to create another bug about this.
Works for me using: gst-launch-0.10 playbin2 uri=file://.../Egor\ Letov\ -\ Vse\ Idet\ po\ Planu\ \(Live\).flv Probably fixed since the release you are using. Are you able to test with git gstreamer to confirm that it works for you as well ? If it works for you, or you cannot test git, I'll close this as fixed.
I build git, but i can't use it probable i must update the version installed in system (I don't want to do this). Is the any way to use it just builded ?
There's a gst-uninstalled script that you can use (scripts/gst-uninstalled in GStreamer core), which will let you run a self built GStreamer. There's a help text at the start of it IIRC, and you need to change a path there. If this is too much of a hassle, then it's fine and I'll deem it fixed, though you'll have to wait for next release to use it.
i try some, but i will wait and test next release
gstreamer updated while i was at vacation. Bug still exist dpkg -l | grep gstreamer ii gstreamer0.10-alsa 0.10.36-1ubuntu0.1 GStreamer plugin for ALSA ii gstreamer0.10-ffmpeg 0.10.13-1 FFmpeg plugin for GStreamer ii gstreamer0.10-gnomevfs 0.10.36-1ubuntu0.1 GStreamer plugin for GnomeVFS ii gstreamer0.10-nice 0.1.1-2ubuntu1 ICE library (GStreamer plugin) ii gstreamer0.10-plugins-bad 0.10.22.3-2ubuntu2 GStreamer plugins from the "bad" set ii gstreamer0.10-plugins-base 0.10.36-1ubuntu0.1 GStreamer plugins from the "base" set ii gstreamer0.10-plugins-base-apps 0.10.36-1ubuntu0.1 GStreamer helper programs from the "base" set ii gstreamer0.10-plugins-good 0.10.31-1ubuntu1 GStreamer plugins from the "good" set ii gstreamer0.10-plugins-ugly 0.10.18.3-1ubuntu1 GStreamer plugins from the "ugly" set ii gstreamer0.10-pulseaudio 0.10.31-1ubuntu1 GStreamer plugin for PulseAudio ii gstreamer0.10-tools 0.10.36-1ubuntu1 Tools for use with GStreamer ii gstreamer0.10-x 0.10.36-1ubuntu0.1 GStreamer plugins for X11 and Pango ii libgstreamer-perl 0.16-1build1 Perl interface to the GStreamer media processing framework ii libgstreamer-plugins-bad0.10-0 0.10.22.3-2ubuntu2 GStreamer development files for libraries from the "bad" set ii libgstreamer-plugins-base0.10-0 0.10.36-1ubuntu0.1 GStreamer libraries from the "base" set ii libgstreamer0.10-0 0.10.36-1ubuntu1 Core GStreamer libraries and elements
I can confirm that this clip does not preroll with the last releases. However, it works fine both in 0.10 git and in git master (0.11/1.0), so will close this as OBSOLETE (rather than FIXED, since I don't know what fixed it exactly - probably something in h264parse though).