Skip to main content

Usage of decoder starved

1 reply [Last post]
nirajan
Offline
Joined: 2012-06-17
Points: 0

An event called DECODER_STARVED is present in MediaAPI.java. When does mpeos layer send this event to upper layers? The header file in mpeos layer does not have any such event in RI 1.2.1.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
cpratt
Offline
Joined: 2008-12-18
Points: 0

The starvation event was replaced with a MPE_CONTENT_NOT_PRESENTING subcode: MPE_NOT_PRESENTING_NO_DATA. The definition of DECODER_STARVED/DECODER_NO_LONGER_STARVED in MediaAPI.java is vestigial and should be removed.

The MPE_CONTENT_NOT_PRESENTING/MPE_NOT_PRESENTING_NO_DATA event should be signaled by the platform when the decoder is not able to present video due to lack of data. e.g. when one of the PIDs specified in mpeos_mediaDecode() is not present in the stream.

Note that this event doesn't signal the termination of decoding. The event is an indication of a condition that may resolve (e.g. the PID re-appears). Recovery from the condition would be signaled via MPE_CONTENT_PRESENTING.