[gstreamer-bugs] [Bug 597847] New: Windows Media Player won't play large files produced by avimux

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=597847
  GStreamer | gst-plugins-good | 0.10.14

           Summary: Windows Media Player won't play large files produced
                    by avimux
    Classification: Desktop
           Product: GStreamer
           Version: 0.10.14
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: timzilla at gecoinc.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


The following issue is observed across multiple versions of GStreamer, starting
as early as plugins-good version 0.10.11, and continuing through at least
0.10.14.  I've looked at the changes made between 0.10.14 and (current), and I
don't see anything that would affect this issue.

Our development platform is Ubuntu Linux, i386.  The problem exists on at least
Hardy and Jaunty.

We have a gstreamer-based application that is making AVI files containing
image/x-j2c data in the video stream.  Users play these files on Windows PCs,
using Windows Media Player software and the Morgan JPEG2000 codec.

However, if the files exceed 4GB in size, Windows Media Player will not play
them.  It complains that it "might not support the file type or might not
support the codec".  Under these conditions (as described in the related bug
report...), we have them use the so-called "Media Player Classic" media player,
which successfully plays the file.

If we use mencoder (based on ffmpeg and libavformat) to re-mux the AVI file,
e.g.:
    mencoder large.avi -oac copy -ovc copy -o fixedLarge.avi

the resulting large AVI file plays fine on Windows Media Player.

I have discussed this issue with users "bilboed", "wtay", and "_tim" on the
#gstreamer IRC channel, and they requested that I write this bug.  They
requested that I attach log file output that comes from the following commands:

<bilboed>    tcrews, produce the log with GST_DEBUG=2,avi*:5 gst-launch-0.10
filesrc location=large.avi ! avidemux ! fakesink > large1.log
<bilboed>    tcrews, produce the log with GST_DEBUG=2,avi*:5 gst-launch-0.10
filesrc location=large.avi ! avidemux ! fakesink 2> large2.log

There were two AVI files that I made to support this bug report
    large.avi -- 4GB file recorded by our application.  Does not play in
Windows Media Player
    fixedLarge.avi -- large.avi re-muxed by mencoder as described above.  Plays
in WMP.

I ran bilboed's suggested two commands for both files, resulting in
    large1.log - stdout output for large.avi avidemux
    large2.log - stderr output for large.avi avidemux
    fixedLarge1.log - stdout output for fixedLarge.avi avidemux
    fixedLarge2.log - stderr output for fixedLarge.avi avidemux


These log files are found in the attached (15MB) tarball, wmp_issue_logs.tgz.
WARNING!  Because these are detailed debug logs for very large AVI files, this
tarball expands to about 200MB!  If there is a subset of this data that you
want to see, let me know how I should filter the results.

I have also submitted a related issue (...) about files smaller than 4GB not
playing under different conditions.

-- 
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.