[Gstreamer-bugs] [Bug 117692] Changed - docs/random/mimetypes needs updating

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=117692

Changed by rbultje at ronald.bitfreak.net.

--- shadow/117692	Sat Jul 19 23:29:47 2003
+++ shadow/117692.tmp.19101	Sun Jul 20 04:27:28 2003
@@ -66,6 +66,24 @@
 
 As for integrating the document into the official docs, should the
 mimetypes file go in the App Developer's Manual or the Plugin Writer's
 Guide ? I'd vote for the PWG, it already has a brief description of
 common MIME types, and application developers shouldn't have to deal
 too much with internally used MIME types like audio/x-raw-int.
+
+------- Additional Comments From rbultje at ronald.bitfreak.net  2003-07-20 04:27 -------
+PWG.
+
+As for the boundaries, it's not intended as decoded/encoded. It's
+intended as a "are we parsed into single frames or not", Imagine MPEG,
+where one MPEG packet could contain exactly one frame (unlikely), or
+could contain part of the previous frame and part of the next frame
+(ugh!). Obviously, this will work for decoders/formats that expect
+this (fortunately, most do), but not for the ones that don't (example:
+AVI). Same goes for others, like mp3. Matroska, too, uses this, they
+call it 'lacing', which can be turned on and off to someone's liking.
+
+As for frames-per-buffer, there's some convenience macro's in
+gst-plugins/gst-libs/gst/audio/audio.h for that, I don't think it
+should be part of the caps, since you assume that each buffer will
+contain the same amount of data, which is by definition not always
+true in GStreamer. I would tend to disagree with adding it...