Remove the put_frame and put_slice callbacks
The put_frame and put_slice callbacks are not implemented by the AV1
algorithm. Remove the put_frame and put_slice callbacks before the
libaom 2.0.0 release.
BUG=aomedia:2632,aomedia:2651
Change-Id: I6b05028acdc7066e7427455bb5886f69300965ea
diff --git a/usage_dx.dox b/usage_dx.dox
index eef7837..41d3f77 100644
--- a/usage_dx.dox
+++ b/usage_dx.dox
@@ -10,31 +10,8 @@
\ref samples
- \section usage_cb Callback Based Decoding
- There are two methods for the application to access decoded frame data. Some
- codecs support asynchronous (callback-based) decoding \ref usage_features
- that allow the application to register a callback to be invoked by the
- decoder when decoded data becomes available. Decoders are not required to
- support this feature, however. Like all \ref usage_features, support can be
- determined by calling aom_codec_get_caps(). Callbacks are available in both
- frame-based and slice-based variants. Frame based callbacks conform to the
- signature of #aom_codec_put_frame_cb_fn_t and are invoked once the entire
- frame has been decoded. Slice based callbacks conform to the signature of
- #aom_codec_put_slice_cb_fn_t and are invoked after a subsection of the frame
- is decoded. For example, a slice callback could be issued for each
- macroblock row. However, the number and size of slices to return is
- implementation specific. Also, the image data passed in a slice callback is
- not necessarily in the same memory segment as the data will be when it is
- assembled into a full frame. For this reason, the application \ref MUST
- examine the rectangles that describe what data is valid to access and what
- data has been updated in this call. For all their additional complexity,
- slice based decoding callbacks provide substantial speed gains to the
- overall application in some cases, due to improved cache behavior.
-
-
\section usage_frame_iter Frame Iterator Based Decoding
- If the codec does not support callback based decoding, or the application
- chooses not to make use of that feature, decoded frames are made available
+ Decoded frames are made available to the application
through the aom_codec_get_frame() iterator. The application initializes the
iterator storage (of type #aom_codec_iter_t) to NULL, then calls
aom_codec_get_frame repeatedly until it returns NULL, indicating that all
