From: <bug...@wi...> - 2003-07-20 03:29:57
|
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 le...@am.... --- shadow/117692 Thu Jul 17 12:55:16 2003 +++ shadow/117692.tmp.1741 Sat Jul 19 23:29:47 2003 @@ -49,6 +49,23 @@ As for point 2, I don't know how that should work either. I don't think it's media-specific, but mediatype-specific. E.g. audio samples (I think mp3 uses samples here, too), video frames. As for point 3: yes. + +------- Additional Comments From le...@am... 2003-07-19 23:29 ------- +Doesn't the MIME type itself describe whether the stream info is in +encoded/decoded form ? + +Also, Wingo started adding a 'buffer-frames' property to float +audio---the number of audio frames in a buffer (a frame is a set of +samples, one from each channel). This is for synchronization with JACK +networks, but it's a pretty good idea anyway. We could add the same +property to int audio, seems like this would take care of data +boundaries in the raw audio formats. The others, though ... :) + +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. |