[gstreamer-bugs] [Bug 519460] Missed 16byte in AVI header

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=519460

  GStreamer | gst-plugins-base | Ver: 0.10.x




------- Comment #18 from Wang Diancheng  2008-05-19 01:41 UTC -------
(In reply to comment #17)
> The former of the above commits should have fixed the segment warning, as it
> should prevent sinks from doing fancy/nasty stuff with segments, such as
> forcing the format to TIME and complaining later on about BYTE seeks (see also
> bug 519878).  The other one is unrelated.
> 
> In any case, neither deals with any extra bytes in the header.
> MS specs mainly intend these rcFrame fields for use with for several video
> streams, in which case it indicates the rectangle within the movie rectangle
> specified by the main (avi) header.  As such, I suspect another "solution"
> (e.g. mencoder) is to simply add 2 (int32) 0 (size gives the others).  But even
> as it stands, I have known the resulting files to play on Windows (IIRC
> including WMP), as also indicated by other reports.  And one would assume these
> players essentially come down to the same (MS) libs.
> 
> In view of this, how does "only affects Helix" (on Windows?) in Comment #10
> relate to "some players in MS windows" in Comment #2, and that in turn to
> "can't be played in most player in the MS Windows" in the original report ?

sorry, it is my mistake, only Helix(on GNU/Linux) can not play files missing 16
bytes in AVI header. MS Windows Media Player is OK. 

> 


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=519460.