[gstreamer-bugs] [Bug 626057] New: [typfinding] misc. problems with oxo_restaurant.mov

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=626057
  GStreamer | gst-plugins-base | git

           Summary: [typfinding] misc. problems with oxo_restaurant.mov
    Classification: Desktop
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: t.i.m at zen.co.uk
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


$ wget http://www.harveynichols.com/files/other/QTVR/oxo_restaurant.mov

Three problems with this file:

a) typefinding in pull mode doesn't work, but in push mode it does

    $ gst-launch-0.10 filesrc location=oxo_restaurant.mov ! typefind ! fakesink
    ERROR: from element
/GstPipeline:pipeline0/GstTypeFindElement:typefindelement0: Could not determine
type of stream.


    $ gst-launch-0.10 filesrc location=oxo_restaurant.mov ! queue ! typefind !
fakesink
    Setting pipeline to PAUSED ...
    ...
    Got EOS from element "pipeline0".
    Execution ended after 592463 ns.


b) "Failed to configure latency" warning:

    $ gst-launch-0.10 filesrc location=oxo_restaurant.mov ! typefind ! qtdemux
! fakesink
    gstbin.c(2326): gst_bin_do_latency_func (): /GstPipeline:pipeline0:
Failed to configure latency of 0:00:00.000000000

    $ gst-launch-0.10 filesrc location=oxo_restaurant.mov ! qtdemux ! fakesink
    (no warning

c) only one frame in push mode, but multiple frames in pull mode:

    $ gst-launch-0.10 filesrc location=oxo_restaurant.mov ! qtdemux ! jpegdec !
xvimagesink

    vs.


    $ gst-launch-0.10 filesrc location=oxo_restaurant.mov ! queue ! qtdemux !
jpegdec ! xvimagesink

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.