|
Since the API for R5 decoders and encoders was not released, current practice information is limited to informal usage and non-authoritative comments in public forums. This includes nonspecific comments by representatives of Be, Inc., about particular behaviors. For example, responses to emails/web posts about bugs that are exhibited by decoders or encoders.
Most of the information here was gleaned from reading the BMediaTrack BeBook page.
Here are some things that the current decoders support:
- Sniffing - Determining whether or not the data is of the type supported by this decoder.
- Seeking - Seeking by frame number or timestamp. Finding keyframes. (seek both forward and backwards)
- Getting information - Reporting static information from the data, such as duration, quality, media_codec_info. Also reporting dynamic information such as the current frame or current time.
- Reading - Reading decoded data, or the raw undecoded data.
- Output negotiation - Negotiating an media_format for decoded data.
Here are some things that the current encoders support:
- Setting parameters - such as quality, or other encode_parameters.
- Writing - Writing encoded data, or the raw unencoded data. Also, writing information about the data. (Such as a header)
There are currently these decoders bundled with a stock BeOS:
applevideo, ccittadpcm, cinepak, dv, dvaudio, ima4, indeo5, mpeg1audio_fh, mpeg1video, msadpcm, msrle, msvideo, pjpeg, rawaudio, rgbvideo, ulaw, yuvvideo
There are currently these encoders bundled with a stock BeOS:
cinepak, dv, ima4, indeo5, indeo5rt, indeo5rtmmx, mp3 [pro only], msadpc, mpjpeg, raw
|
